On Mon, May 11, 2009 at 1:17 PM, Rowland, Larry <[email protected]> wrote: > As nearly as I can tell, you are attempting to include a chapter inside a > chapter (StaffServices.xml, which is a chapter includes Cataloging.xml, which > is also a chapter). You also have a para following the inclusion of > Cataloging.xml, which would be a para following a chapter (or section, if you > changed Cataloging.xml to have a section as its root element). Once you > start using structures like chapters and sections, you can't follow with > paras.
----------- Yeah, the para wasn't even intended to be there (a n00b and her copy of oXygen... what can I say). Thanks to Eric and Larry for quickly responding. This demonstrates also the importance of thinking through/planning one's hierarchy. I can see it is possible to "run out" of hierarchy (I haven't in this scenario, but I could see where it could quickly happen). I'm at the very early stages (proof of concept and all that) and trying to decide/think through building one huge book, several related books, depth, etc. Nothing needs to be decided this very instant, but there are obvious implications for every organizational decision. (I don't know what they are, but I am sure they exist ;) ) thanks again (oh, and really, I know he knows this but Stayton's book is quite excellent) -- -- | Karen G. Schneider | Community Librarian | Equinox Software Inc. "The Evergreen Experts" | Toll-free: 1.877.Open.ILS (1.877.673.6457) x712 | [email protected] | Web: http://www.esilibrary.com | Be a part of the Evergreen International Conference, May 20-22, 2009! | http://www.lyrasis.org/evergreen --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
