Cart
[Home] [By Thread] [By Date] [Recent Entries]
As for part of your problem: When you create an interface that has multiple syntactic constructs with redundant (non-orthoganal) semantics you pretty much guarantee frustrating extra work in designing, implementing, documenting, using, and maintaining that interface for all direct and indirect users of that interface for all time. Attributes in XML are a canonical example of this. The other parts of your problems such as using 'object' as a element name sound much more like bad design (got to live with it) or some extenuating circumstances not presented in your example. I promise I will not whine about attributes in XML I promise I will not whine about attributes in XML I promise I will not whine about attributes in XML I promise I will not whine about attributes in XML I promise I will not whine about attributes in XML I promise I will not whine about attributes in XML erik xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To unsubscribe, mailto:majordomo@i... the following message; unsubscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
