[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to get the 1st element in DTDD
- From: Marcus Carr <firstname.lastname@example.org>
- To: Murali Mani <mani@CS.UCLA.EDU>
- Date: Sat, 23 Jun 2001 12:25:16 +1000
Murali Mani wrote:
> Thanks. actually that makes lot of sense... especially your schema
> describes an inventory of lot of stuff, even quite unrelated..??
Yes, if your focus is on what could be termed as fielded information, this might
be less relevant, but there is a lot of narrative data being created in XML as
> but actually do you have a concrete example when this might actually
> happen... that will be good...
Sure - you may have numerous authors working on a single document. They may each
be writing a chapter, then the book will be validated in it's entirety.
Another example - the tool of choice for many markup people is a text editor, but
when it comes to tables, they often prefer to use an editor that provides visual
support. (CALS syntax is doable but difficult without.) External entities are
used to provide a placeholder for the table markup in the main document and the
tables are created and validated independently. The final step is a normalisation
of the document, generally (but not necessarily) pulling everything into one
These are real-world examples - we have been doing both as standard practice for
ten years. Limiting the root elements would diminish the effectiveness of data
creators. I'm guessing that you feel there are downstream processes that would
benefit from limiting the set of possible root elements - if so, could you
explain what they might be and how they would benefit?
Marcus Carr email: email@example.com
Allette Systems (Australia) www: http://www.allette.com.au
"Everything should be made as simple as possible, but not simpler."