W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 1997

RE: Meta Data Redux

From: Yaron Goland <yarong@microsoft.com>
Date: Thu, 27 Mar 1997 17:32:24 -0800
Message-ID: <11352BDEEB92CF119F3F00805F14F4850277EFA4@RED-44-MSG.dns.microsoft.com>
To: "'Stephen Martin'" <smartin@mks.com>, w3c-dist-auth@w3.org
Metadata, as specified in my proposals, is attached to a resource. So
data attached to a versioned resource is attached to that resource
alone. If one wishes to place meta data on the whole tree then one
should attach meta data to the tree handle resource. Of course,
individual pieces of meta-data are free to override this behavior.

The values accessible via meta* have behavior that is defined on a
meta-data by meta-data basis. The client only knows about tokens and
values, that is it. So, for example, let us say the dublin:author
meta-data token existed and a client tries to change it on a versioned
resource. If the server accepts the token then it also accepts
responsibility for enforcing its behavior, which would probably be
defined that once the resource is versioned, this value can not be
changed. However that is an issue for Dublin Core to solve.

The same logic applies to links. It is up to the person defining the
link type to specify its behavior. Thus a server would probably not
allow someone to delete a DAV.Versioning.NextResource link from a
versioned resource, but that is the server's business. Repositories
would actually be fine with this behavior.

So your question will be answered on a meta-data by meta-data basis.
Since DAV isn't really in the meta-data defining business, these issues
are largely out of scope.


> -----Original Message-----
> From:	Stephen Martin [SMTP:smartin@mks.com]
> Sent:	Thursday, March 27, 1997 11:00 AM
> To:	Yaron Goland; w3c-dist-auth@w3.org
> Subject:	Re: Meta Data Redux
> Yaron Goland wrote:
> > 
> > I propose that DAV's goals in regard to meta-data should be two
> fold:
> > 1.      To provide for a mechanism for clients to place, delete and
> > discover relationships between resources.
> > 2.      To provide for a mechanism for clients to place, delete and
> > discover simple meta-data consisting of a name and a short
> non-content
> > negotiable byte field.
> > 
> I believe that there are a few things missing from your proposal.
> In particular, how does metadata interact with versions? Is a piece
> of metadata attached to a specific version of a document or is it
> attached to the document tree? Is the metadata versioned?
> If the metadata is versioned, how are versions of the attributes
> associated to versions of the document?
> WebDav should clearly define these sorts of things.
> Steve
> -- 
>                                      __
> Stephen Martin         _   _   |    /_ \ MORTICE KERN SYSTEMS INC.
> smartin@mks.com      ,/ \ / \  | / |(  |  185 Columbia Street West
> (519)883-3215        |   |   | |/  | \ /   Waterloo, Ontario
> Fax: (519)884-8861   |   |   | | \ | _)     Canada   N2L 5Z5
>                                     \__/
Received on Thursday, 27 March 1997 20:42:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:10 UTC