W3C home > Mailing lists > Public > www-tag@w3.org > February 2003

RE: Proposed issue: site metadata hook (slight variation)

From: Jeffrey Winter <JeffreyWinter@crd.com>
Date: Wed, 12 Feb 2003 10:28:15 -0500
Message-ID: <3A9933B568A24543B6AD9E02C7E6ADA0C15CE0@moe.crd.com>
To: <Patrick.Stickler@nokia.com>, <miles@milessabin.com>, <www-tag@w3.org>


> I think that once rich metadata is available in volume, once a
> reasonable architecture is in place to serve it, that *most* 
> automated agents and web services will be wanting metadata alot.

A lot, sure, but IMO not so often (i.e., relative to the actual
resource) that it would warrant not making it a separately 
addressable resource bound via some form of location header (e.g.,
Costello's Meta-Location:, Meta-About: headers).

> > I take issue with the original premise the that metadata should 
> > ever be non-addressible.
> 
> I've never presumed nor asserted that. Ever. Go re-read my posts.
> 
> I've only ever said that one should not need a *different* URI
> from that of the resource in order to publish or obtain or
> otherwise interact with descriptions of that resource.

True, but no matter how you slice it, the resource and its metadata
"smell" like separate entities that are each important enough to 
warrant their own distinct URIs - and thus would not require an
entire new body of semantics.  They would be bound by the headers
mentioned about.  This would have a much better chance of acceptance
than new methods.
Received on Wednesday, 12 February 2003 10:28:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:16 GMT