Content deleted Content added
CAPTAIN RAJU (talk | contribs) m Reverted 1 edit by 47.211.128.234 identified as test/vandalism using STiki |
m →Namespace names: Link to archived O'Reilly page on RDDL and change the XML.com link to HTTPS |
||
Line 9:
Although the term ''namespace URI'' is widespread, the W3C Recommendation refers to it as the ''namespace name''. The specification is not entirely prescriptive about the precise rules for namespace names (it does not explicitly say that parsers must reject documents where the namespace name is not a valid [[Uniform Resource Identifier]]), and many XML parsers allow any character string to be used. In version 1.1 of the recommendation, the namespace name becomes an [[Internationalized Resource Identifier]], which licenses the use of non-ASCII characters that in practice were already accepted by nearly all XML software. The term ''namespace URI'' persists, however, not only in popular usage, but also in many other specifications from W3C and elsewhere.
Following publication of the Namespaces recommendation, there was an intensive debate about how a relative URI should be handled, with some intensely arguing that it should simply be treated as a character string, and others arguing with conviction that it should be turned into an absolute URI by resolving it against the base URI of the document.<ref>{{cite web|title=News from the trenches|first=Leigh|last=Dodds|date=24 May 2000|url=
The use of URIs taking the form of URLs in the http scheme (such as ''http://www.w3.org/1999/xhtml'') is common, despite the absence of any formal relationship with the HTTP protocol. The Namespaces specification does not say what should happen if such a URL is dereferenced (that is, if software attempts to retrieve a document from this ___location). One convention adopted by some users is to place an [[RDDL]] document at the ___location.<ref>{{
== Namespace declaration ==
| |||