James Clark wrote: > > David Brownell wrote: > > > > The namespace spec states that there are two "implicitly declared" > > namespace prefixes, "xml" and "xmlns". But it doesn't give their > > associated URIs, as needed for uniformity within implementations. > > I don't see a need for a URI for "xmlns". Names with the "xmlns" > prefix are never seen by applications. That's not in the current spec. How will applications know where the namespaces are declared, if not through this (IMHO) natural model? Or you assuming that preserving the declaration structure of source data is not a goal? I note that the XSL draft includes a requirement that applications be able to see the list of namespace prefixes that are "in scope". (2.4.2) Looks like some API-like requirements are bubbling up; I don't think they would naturally belong in this document. > We know we need a URI for "xml". Good ... > The intention on "xmlns" is that's it's a keyword. That might simplify some things. Like supporting default namespace declarations. But -- just "xmlns", and not "xml"? So it'd be allowable to say "xmlns:xml='http://www.example.com'" and thus change the meaning of an "xml:space" or "xml:lang" attribute? - DaveReceived on Tuesday, 25 August 1998 23:02:00 GMT
This archive was generated by hypermail 2.2.0 + w3c-0.30 : Tuesday, 12 April 2005 12:17:16 GMT