Cart
[Home] [By Thread] [By Date] [Recent Entries]
The software will process whatever the document format we design is. I am more concerned with the best practice for scoping attributes. No namespace or namespaced/prefixed. -----Original Message----- From: Tim Bray [mailto:tbray@t...] Sent: Tuesday, November 20, 2001 2:10 PM To: Xml-Dev@Lists. Xml. Org (E-mail) Subject: Re: Should attributes be prefixed At 01:17 PM 20/11/01 -0800, Doug Ransom wrote: >i.e. global attribute <V units="Volts" xmlns="<mailto:Doug.Ransom@p...>mailto:Doug.Ransom@p..."/> >vs attribute in the namespace > <p:V p:units="Volts" xmlns:p="<mailto:Doug.Ransom@p...>mailto:Doug.Ransom@p..."/> > >In both cases, the units value must exist within the V element for the element to be valid. The first is prettier. However, only in the second example is the "units" attribute in the "mailto:..."; namespace in the sense defined by the W3C Recommendation "Namespaces in XML". It depends what the software does. If the software insists that the attribute be in the namespace itself, you use the second style. If it is written to look for namespace-less attributes attached to an element in the namespace, then the first is fine. When you're writing the spec for this language, you should be clear which case you're prepared to handle. I'm pretty sure the term "global" is misleading in the sense you use it. -Tim ----------------------------------------------------------------- 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>
|
