XSchema: root element

Ron Bourret rbourret at dvs1.informatik.tu-darmstadt.de
Fri Jul 3 13:57:31 BST 1998

Marcus Carr wrote:

> Not me - conversion work of legacy data routinely involves pulling documents 
> pieces, working on a fragment (such as a table) then putting it all back
> together. A language such as OmniMark will allow you to find fragments without
> parsing the data around it - under those circumstances, what is proposed is
> unduly restrictive.

I'm not sure I understand.  We want to give an authoring tool/XSchema 
explorer/etc. a way to determine the roots of useful/possible documents.  That 
is, it is a way for the XSchema designer to say, "If you start with any of these 
elements, the resulting documents can be interpreted by the nifty software I 
wrote to go with this XSchema."

Simon's proposal (Recommended | Possible | Forbidden) identifies those elements 
that, when used as roots, result in documents that work with the associated 
software (Recommended), those elements that that result in useful documents 
(Possible), and those elements that for some reason (I'm not sure what) should 
never be used as a root.  (Note also that this attribute does not say anything 
about whether an element should be included in a different XSchema.  Presumably, 
all elements can be included in other XSchemas.)

I don't understand what this has to do with working on the individual fragments 
of a document.  

-- Ron Bourret

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)

More information about the Xml-dev mailing list