[
Lists Home |
Date Index |
Thread Index
]
> Simon,
> The feature isn't useless. Most people agree that attributes are meant for annotating elements. The Namespaces in XML recommendation allows authors to choose between context sensitive attribute values E.g.
>
> <myns:Parent name="must be a number between 1 - 100"><myns:Child name="can be any string"/></myns:Parent>
>
> or creating global attributes that represent the same idea regardless of what element they appear on
>
> <myns:Parent myns:id="must be unique in document"><myns:Child myns:id="must be unique in document"><></myns:Parent>
How would this distinction (which is old hat and agreed upon by *everyone* in
this discussion) be impaired by the specification that unprefixed attributes
are in their element's namespace?
--
Uche Ogbuji Fourthought, Inc.
http://uche.ogbuji.net http://4Suite.org http://fourthought.com
Track chair, XML/Web Services One Boston: http://www.xmlconference.com/
Basic XML and RDF techniques for knowledge management, Part 7 -
http://www-106.ibm.com/developerworks/xml/library/x-think12.html
Keeping pace with James Clark - http://www-106.ibm.com/developerworks/xml/libra
ry/x-jclark.html
Python and XML development using 4Suite, Part 3: 4RDF -
http://www-105.ibm.com/developerworks/education.nsf/xml-onlinecourse-bytitle/8A
1EA5A2CF4621C386256BBB006F4CEC
|
