[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Namespaces in XML and XHTML

• From: james anderson <James.Anderson@m...>
• To: "xml-dev@i..." <xml-dev@i...>
• Date: Fri, 10 Sep 1999 07:54:43 +0200

Jon Bosak wrote:
> ...
> ------------------------------
> What are namespaces all about?
> ------------------------------
> 
> Namespaces are about unique identification; they are not about
> meaning.  Identification is necessary to the establishment of meaning,
> but it does not constitute meaning in itself.
> 
> [followed by a long discussion to the point that namespaces govern identity in the
>  encoding and decoding process only and leading to the following conclusions: ]
>
> -------------------------------------
> Should XHTML use multiple namespaces?
> -------------------------------------
> 
> ...
>
>  - The main argument for specifying three namespaces for XHTML rests
>    on the assumption that there is a one-to-one association between
>    namespaces and schemas.  This is not true.

as established above, it is also insignificant.

> 
>  - A second argument for specifying three namespaces is that it's
>    intended to indicate that XHTML actually specifies three different
>    tag languages and that <h2> in one of these languages means
>    something basically different from <h2> in the other two.  In my
>    opinion, <h2> means basically the same thing in all three
>    versions. ...
>    ...  If the HTML WG decides to maintain the position that
>    XHTML is defining three different languages, then it should be
>    ready to explain how an <h2> in one would materially differ in
>    meaning from an <h2> in another, "meaning" here being expressed in
>    terms of the intention of the person who causes elements to have
>    the type "h2."

which is also, as established above, insignificant.

> 
>  - Another way of making what I believe to be essentially the same
>    point is that distinctions between a strict <h2> and a
>    transitional <h2> are not reflected in actual machine processing
>    outside of validation.

which decides the issue. as the namespaces are about unambiguously identifying
the encoded specifications for the validation, it is appropriate to make
adequate distinctions.
? is it specified somewhere that the various XHTML forms will never appear in
the same document?

> 
>  - If XHTML really is several languages and the similarly named
>    elements of those languages really are different from each other,
>    then those different languages are going to require different HTML
>    DOMs.

i don't understand this one: if the variants are in different namespaces, then
elements of each could well be mixed in the same dom instance. isn't that the
point of the whole thing?


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • Namespaces in XML and XHTML
    • From: Jon Bosak <Jon.Bosak@e...>

• Prev by Date: RE: RFP: Namespace URI for HTML
• Next by Date: Ps --> xml (or html)
• Previous by thread: RE: Namespaces in XML and XHTML
• Next by thread: Re: Namespaces in XML and XHTML
• Index(es):
  • Date
  • Thread