W3C home > Mailing lists > Public > www-tag@w3.org > May 2011

Re: ISSUE-57 & ISSUE-63 draft: Information Resources and Web Metadata

From: Noah Mendelsohn <nrm@arcanedomain.com>
Date: Tue, 17 May 2011 23:18:23 -0400
Message-ID: <4DD33A7F.8040608@arcanedomain.com>
To: Jonathan Rees <jar@creativecommons.org>
CC: www-tag@w3.org
 >Very< much appreciated; will reply in detail later but yes, this indeed 
expected, and I already had it in my informal working list of agenda items.

TAG members: [1] is the first entry on the reading list for the F2F.

Thank you!


[1] http://www.w3.org/2001/tag/awwsw/ir/20110517/

On 5/17/2011 9:05 PM, Jonathan Rees wrote:
> http://www.w3.org/2001/tag/awwsw/ir/20110517/ is the first of two
> drafts relating to ISSUE-57 for us to discuss at the June F2F. The
> second, which attacks ISSUE-57 directly by listing current and
> potential solutions, should be ready next week. I hope all TAG members
> (and others) will read them and comment.
> Apparently I had no action to do this, although I think it's common
> knowledge I've been working on it. Noah, if you'd like for me to
> assign myself an action to do this, for agenda purposes, I'd be happy
> to.
> This draft also relates pretty directly to ISSUE-63 (Metadata
> Architecture) and thus to ACTION-282 (draft a finding on same).
> However it is much narrower than metadata architecture generally and
> therefore does not satisfy ACTION-282.
> Keep in mind that there is a third imagined document, which would be
> the output of a community discussion framed by the first two
> documents. That's a ways off.
> -Jonathan
> ---------
> Abstract
> This note considers the semantics of metadata in which the subject of
> the metadata (the "data") is specified using a URI that may be
> dereferenced on the Web. This situation is complicated in that agents
> might obtain different information on different dereference
> operations, raising the question of what metadata is true or not of
> the metadata subject.
> It is proposed that the practical purpose of the "information
> resource" abstraction in web architecture is mainly to supply suitable
> subjects for this kind of metadata. Relating information resources to
> metadata in this way makes concrete the value proposition for the rule
> that a URI should name the information resource related to dereference
> of that URI. It is hoped that this analysis will be of use in future
> work aimed at strengthening or modifying consensus around this rule.
Received on Wednesday, 18 May 2011 03:18:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:33:10 UTC