W3C home > Mailing lists > Public > www-tag@w3.org > July 2009

RE: Framing an Architecture for Metadata on the Web

From: Larry Masinter <masinter@adobe.com>
Date: Tue, 21 Jul 2009 17:47:45 -0700
To: "ashok.malhotra@oracle.com" <ashok.malhotra@oracle.com>, Larry Masinter <masinter@adobe.com>
CC: "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <8B62A039C620904E92F1233570534C9B0118D7F3F670@nambx04.corp.adobe.com>
Re:


> [AM] Metadata comes is all kinds of flavors and formats. I don't want a 
> recommendation that says, for example, you must use RDF for all metadata.

Yes, that would be bad.

> [AM] This is http://www.w3.org/2001/tag/group/track/issues/62 and I 
> think we should track it separately.
It's appropriate to track Issue 62 separately, but ISSUE 62 is narrowly
scoped:

> Given the URI of an HTTP-accessible information
> resource R, how can an agent learn the URIs of
> metadata documents about R authorized by
> the owner of the original URI.

in that it is limited to "HTTP accessible resources",
the situation where the metadata is authorized by
the "owner" of the original URI (whoever that might 
be), the situation where the metadata is contained
in separate document(s), and the use case of an agent
wanting to discover the URIs of those metadata 
documents.

A general framework for metadata would show how
that use case might fit into other metadata creation,
manipulation, update scenarios, where perhaps the
resource is not HTTP accessible, where the metadata
is authorized by someone else, or the work process
is something other than discovering the URI, e.g.,
updating the metadata.

Regards,

Larry

-----Original Message-----
From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On Behalf Of ashok malhotra
Sent: Tuesday, July 21, 2009 4:19 PM
To: Larry Masinter
Cc: www-tag@w3.org
Subject: Re: Framing an Architecture for Metadata on the Web

Thanks, Larry.
A couple of comments inline
All the best, Ashok


Larry Masinter wrote:
>
> This email is intended to initiate a framing of ISSUE-63, and to 
> satisfy ACTION-254:
>
> =============================================
>
> Proposed Architecture for Metadata on the Web
>
> Various W3C specifications (as well as specs from other organizations) 
> contain the notion of representing "metadata". While the word 
> "metadata" has many broad definitions, for the purposes of this 
> discussion, it's proposed to consider the application of semantics -- 
> meaning -- specifically to the description of network resources and 
> data. If a URI identifies a resource, metadata describes a resource. 
> While the scope of "metadata" is ambiguous, at its core, it is 
> necessary for a metadata model to clearly address the common metadata of
>
[AM] You lost the end of the line
>
> There are a number of W3C work products and questions which touch on 
> metadata and would benefit from an architectural approach to metadata. 
> This issue is to develop a framework for approaching metadata which 
> allows development and growth in a coherent way of:
>
> * Metadata model: what is the "data model" for typical metadata 
> applications - the datatypes of the endpoints
>
[AM] Metadata comes is all kinds of flavors and formats. I don't want a 
recommendation that says, for example, you must use RDF for all metadata.
>
> * Metadata serialization: how can metadata be encoded in a 
> representation system, be it RDF or something else
>
> * Metadata vocabularies: what are appropriate vocabularies for 
> describing various media objects and network services? What is the 
> process by which new vocabularies can or should be developed, 
> described, extended or changed?
>
> * Metadata linking: What are the various ways in which metadata can be 
> associated with "data" or other resources? Link relationships, 
> protocol elements, mechanisms for embedding metadata in various kinds 
> of data.
>
[AM] This is http://www.w3.org/2001/tag/group/track/issues/62 and I 
think we should track it separately.
>
> These four architectural perspectives interact with each other, of 
> course.
>
> An architectural approach to metadata for the web might review past 
> and current W3C work on metadata look at existing practice around 
> metadata on the web, web content, security issues of trust, the 
> process for updating metadata, the issues around resolving conflicts, 
> overlaps, updates to metadata, determining origin and authority for 
> metadata and so forth.
>
> =====================================
>
> Larry
>
> --
>
> http://larry.masinter.net
>
Received on Wednesday, 22 July 2009 00:48:39 GMT

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