Re: What's the problem? "Reuse of 1998 XHTML namespace is potentially misleading/wrong"

Larry Masinter wrote:
> My view was that ISSUE-60 on namespaces could be addressed if there
> is a versioning mechanism which can disambiguate between different
> languages that share the same namespace (as a possible resolution
> to ISSUE-4).

How about this: before we start contemplating solutions to the problem 
of sharing the namespace with XHTML2, we should understand why the 
problem needs to exist in the first place.

The XHTML2 WG need to provide some really solid technical justification 
for *why* they need to use the same namespace, which they have never 
even attempted to provide. Sharing the same namespace is doing nothing 
but creating an unnecessary problem that, frankly, should not be our 
responsibility to deal with, and the whole issue could be avoided by 
XHTML2 using a different namespace.

If this issue is to be pursued at all, then it should be taken to the 
XHTML2 WG, and the XHTML2 WG should provide valid technical 
justification for why this problem needs to be created at all.  Without 
such justification, spending time working on a solution to the problems 
they're unnecessarily creating is a waste of our time and effort.

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/

Received on Monday, 16 February 2009 23:44:22 UTC