W3C home > Mailing lists > Public > public-html@w3.org > December 2008

Re: metadata content

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 25 Dec 2008 10:30:35 +0000 (UTC)
To: Julian Reschke <julian.reschke@gmx.de>
Cc: public-html@w3.org
Message-ID: <Pine.LNX.4.62.0812251026310.12643@hixie.dreamhostps.com>

On Thu, 25 Dec 2008, Julian Reschke wrote:
> Ian Hickson wrote:
> > That does seem to a spec for it, indeed. How about "adobe:ns:meta/"?
> > 
> > (Another reason to have a centralised registry rather than URIs or 
> > java-like identifiers is to make it possible for conformance checkers 
> > to catch typos.)
> 
> So are you saying that a single central Wiki-shaped registry for XML 
> namespaces would actually work in practice?

XML Namespaces on the Web, or XML Namespaces in general? The use cases are 
very different. For XML in general, there are multiple completely 
unrelated markets, within which different rules will be needed. It doesn't 
matter if a car manufacturer doesn't know about flower namespaces, because 
they won't be interacting with flower shops.

For HTML, where interoperability matters (i.e. "on the Web"), there is a 
single, very large, market. It's a very different situation, and warrants 
different solutions. Web sites for car manufacturers will be accessed with 
tools that are also used for flower shops. There are no silos.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 25 December 2008 10:31:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:27 GMT