Cart
[Home] [By Thread] [By Date] [Recent Entries]
"Henry S. Thompson" wrote: > (...) > The constraints above are equivalent to allowing 'attribute' children > to the 'attribute' element in XML Schema, along with making the > attribute name uniqueness constraint cumulative: > > <element name='person'> > <complexType> > <attribute name='age' type='integer'/> > <attribute name='name'> > <attribute name='first'/> > <attribute name='middle/> > <attribute name='last/> > </attribute> > <element name='children'>...</children> > </complexType> > </element> Henry, I am really disappointed how simple you designed structured attributes: You forgot to add a <complexAttributeType> element! Without that, you cannot distinguish between two completely different concepts: the concrete "name" attribute and the general concept of "name" attributes consisting of first, middle and last. I think without that distinction, it becomes impossible to program powerful XML applications like a general problem solver. BTW: If attributes of attributes would have their own complexType, you could have both, different named attributes replacing "name" in the equivClass of "name" and attributes still named "name", but of a different complexAttributeType. The latter one would just need an xsi:type attribute attribute. Best regards Stefan -- Stefan Haustein University of Dortmund Computer Science VIII www-ai.cs.uni-dortmund.de *************************************************************************** This is xml-dev, the mailing list for XML developers. To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev List archives are available at http://xml.org/archives/xml-dev/ ***************************************************************************
|
