[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Re: URIs, concrete (was Re: Un-ask the question)
> I'm saying that applications and humans should ignore the > distinction.) maybe it's just a wording thing. but it sems to me that if I'm to treat the href attribute in <html:a href=... as being in the XHTML namespace then I am to think of it as being equivalent to <html:a html:href=... and that if I am to think of the html namespace as having an href attribute then I should expect to be able to use it on any element if I declare the html namespace (just as for xlink). > though I'm not sure I want to hold > up XLink or W3C XML Schema's xsi:stuff as a shining example. well no, certainly not schema:-) but the general idea of namespaced attributes seems useful (if not so far well used). And I think your proposed change would impact on that (even though you explictly stated that it would not). Any sensible application that has both namespaced and unnamespaced attributes will have application specific rules to avoid the rdf example that you state. For example xslt has both a version attribute (for use on xslt elements) and an xsl:version attribute for use on other elements) XSLT rules ensure that you can not use xsl:version on xslt elements. David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Scanning Service. For further information visit http://www.star.net.uk/stats.asp or alternatively call Star Internet for details on the Virus Scanning Service.
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|