[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)

• To: "'Tim Bray'" <tbray@t...>,"'Simon St.Laurent'" <simonstl@s...>
• Subject: RE: Re: URIs, concrete (was Re: Un-ask the question)
• From: "Aaron Skonnard" <aarons@d...>
• Date: Thu, 1 Aug 2002 09:47:14 -0600
• Cc: "'XML DEV'" <xml-dev@l...>
• Importance: Normal
• In-reply-to: <3D494A51.6070705@t...>

> I mostly agree.  You've argued that doing the following
> 
> <x:y xmlns:x="http://example.com/" x:a="1" a="2" />
> 
> while legal per the ns rec, is idiotic and shouldn't be done.  
> Agreed. You've further argued that it was a design error that 
> the ns rec allws this.  Agreed.
> 
> Where we may disagree is, if you're making an API, you'd better 
> not report the final attribute above (to use JJC's notation) as
> {http://example.com}a, whether or not the first attribute is 
> there or not.  For better or worse, at the API level, the final 
> attribute there has a local part of "a" and no namespace name, 
> but is attached to an element with a namespace name. -Tim

+1

I thought what Simon meant by "treat unprefixed attributes as part of
the same namespace as the owner element" contradicted this. If not, then
"treating" attributes this way is just additional application semantics
as with local scoping in XML Schema.

-aaron
http://staff.develop.com/aarons

• References:
  • Re: Re: URIs, concrete (was Re: Un-ask the question)
    • From: Tim Bray <tbray@t...>

• Prev by Date: RE: Re: URIs, concrete
• Next by Date: Re: Re: URIs, concrete
• Previous by thread: Re: Re: URIs, concrete (was Re: Un-ask the question)
• Next by thread: Re: Re: URIs, concrete (was Re: Un-ask the question)
• Index(es):
  • Date
  • Thread