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

Re: RE: Namespace use cases

• From: Elliotte Harold <elharo@ibiblio.org>
• To: Micah Dubinko <micah.dubinko@marklogic.com>
• Date: Tue, 14 Jul 2009 06:52:19 -0700

On Mon, Jul 13, 2009 at 6:26 PM, Micah
Dubinko<micah.dubinko@marklogic.com> wrote:

> #3 may be a non-issue *for HTML*. One reason why this case gets less
> attention is that is no consensus exists that using namespaces as a major
> version number is a best practice (see, for example, the one namespace vs
> three debates from another era of XHTML)
>

Side note: I think there is consensus on this, and the consensus is
that it's a bad idea. Consensus was reached on this, if I recall,
about 10 years ago in the context of XHTML and really hasn't need to
be revisited since.

As long as you're keeping many of the dame elements with the same
meaning a new namespace doesn't help and is usually actively harmful.
Only if you're more or less replacing a language with a completely
different one would a new namespace be appropriate.

-- 
Elliotte Rusty Harold
elharo@ibiblio.org

• Follow-Ups:
  • Re: RE: Namespace use cases
    • From: rjelliffe@allette.com.au

• References:
  • XHTML 2 Working Group won't be renewed?
    • From: Jonathan Robie <jonathan.robie@redhat.com>
  • RE: XHTML 2 Working Group won't be renewed?
    • From: "Michael Kay" <mike@saxonica.com>
  • Do namespaces address all use cases well
    • From: "Jim Tivy" <jimt@bluestream.com>
  • Namespace use cases
    • From: Micah Dubinko <micah.dubinko@marklogic.com>
  • RE: Namespace use cases
    • From: "Jim Tivy" <jimt@bluestream.com>
  • Re: RE: Namespace use cases
    • From: Dimitre Novatchev <dnovatchev@gmail.com>
  • RE: RE: Namespace use cases
    • From: "Michael Kay" <mike@saxonica.com>
  • Re: RE: Namespace use cases
    • From: Dimitre Novatchev <dnovatchev@gmail.com>
  • Re: RE: Namespace use cases
    • From: rjelliffe@allette.com.au
  • Re: RE: Namespace use cases
    • From: Micah Dubinko <micah.dubinko@marklogic.com>