OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE : [xml-dev] RE : [xml-dev] Text or tags choice with XSD

[ Lists Home | Date Index | Thread Index ]

Sory, I did not explain enough.
Bryce have understood my thought.

If I have the choice to write :
<time xsi:type="complexTime"><hour>14</hour><min>59</min></time>
<time xsi:type="simpleTime">14:59</time>

For me it is like writing :
Where <time-complex> type is "complexTime" and <time-simple> type is

The difference is that, in the first case the person who write the instance
document must know that <time> element can be of "complexTime" or
"simpleTime" types, so he must know the XSD abstraction and derivation
mecanisms that appear clearly with the "xsi:type" attribute in the instance
In the second case the person who write the instance document have to know
that he can write a <time-complex> or a <time-simple> element.

Having the choice between :
<e xsi:type="TA"> or <e xsi:type="TB">
is like having the choice between :
<e-TA> or <e-TB> where e-TA type is TA and e-TB type is TB

In that point of view, the initial problem is not perfectly solve :
Having the choice (exclusive) between :
<e>foo</e> or <e><bar/></e> where foo is text and <bar/> element

Will it be possible in future version of XSD rec?

-----Message d'origine-----
De : Chiusano Joseph [mailto:chiusano_joseph@BAH.COM] 
Envoyé : mardi 9 septembre 2003 16:57
À : Bryce K. Nielsen
Cc : xml-dev@lists.xml.org
Objet : Re: [xml-dev] RE : [xml-dev] Text or tags choice with XSD

Pierre, can you please clarify the point of your question?

"Bryce K. Nielsen" wrote:
> > <Quote>
> > practically, from the instances creator point of view (the one that 
> > write an instance), is it differing so much with the following ?
> >
> > <time-complex><hour>14</hour><min>59</min></time>
> >
> > <time-simple>14:59</time>
> > </Quote>
> >
> > Yes it is, and necessarily so. The xsi:type value is needed so that 
> > the schema processor knows which of the types is being used at 
> > runtime.
> >
> I think you're missing his point, being that rather than making the 
> end user include xsi:type, if he just defines a "time-complex" and a 
> "time-simple" element in his schema, the end user now only has to 
> choose which element to use (schema stuff can be confusing to end 
> users, so I agree that whenever you can exclude them from your 
> instance docs, you should).
> Bryce K. Nielsen
> SysOnyx Inc. (www.sysonyx.com)
> Makers of xmlLinguist, the Text-to-XML Translator
> (http://www.xmllinguist.com)
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an 
> initiative of OASIS <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS