[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Relative Namespaces
- From: Charles Reitzel <email@example.com>
- To: Matt Sergeant <firstname.lastname@example.org>
- Date: Thu, 15 Mar 2001 09:38:24 -0500
But the XML 1.0 spec does reserve all attribute names beginning with 'xml' (regardless of case). Thus, the "xmlns:foo" attribute in an element in *no* namespace is illegal.
At 02:20 PM 3/15/01 +0000, Matt Sergeant wrote:
>On Thu, 15 Mar 2001, Martin Gudgin wrote:
>> > Also to clarify-- is Tim saying that the following is pointless because it
>> > equates to a prefixed name being treated as a non namespace name or is he
>> > saying that the document is in error wrt to namespaces because the prefix
>> > can not logically be resolved?
>> > <foo:bar xmlns:foo="http://foo.com">
>> > <foo:baz xmlns:foo=""/>
>> > </foo:bar>
>> The document is in error and most ( but not all :-) ) XML parsers would
>> throw an error of some kind.
>Not in my experience, but then those parsers might be incorrect... I see
>two statements that could be seen as conflicting:
>In the XML spec:
> The Namespaces in XML Recommendation [XML Names] assigns a meaning to
> names containing colon characters. Therefore, authors should not use the
> colon in XML names except for namespace purposes, but XML processors
> must accept the colon as a name character.
>So assuming there is no foo prefix in scope in the above, the processor
>must accept the colon anyway?
>But then in the namespaces spec:
> The Prefix provides the namespace prefix part of the qualified name, and
> must be associated with a namespace URI reference in a namespace
>Two possibly conflicting uses of "must" ?
>Expat and Gnome's libxml both accept the above document, FWIW.
> /|| ** Founder and CTO ** ** http://axkit.com/ **
> //|| ** AxKit.com Ltd ** ** XML Application Serving **
> // || ** http://axkit.org ** ** XSLT, XPathScript, XSP **
> // \\| // ** mod_perl news and resources: http://take23.org **
> // \\
take it easy,