RE: Update to draft-ietf-webdav-dublin-core

I was arguing for a requirement to efficiently support reading, updating,
and querying single semantic properties ("author") without
disturbing other properties ("title"). If you want to say that both
"title" and "author" are part of a single dav "dublincore" property, then
you need a way to efficiently read, update, and query components
of properties. It does seem that with nested values, there may be no
other way -- multiple independent properties might not solve the problem.

But then, I wonder at the division between 'dublin core' style properties
and any other bits of metadata that is considered currently to be a
'property' of a resource. You could say that 'propfind' and 'proppatch'
are merely the methods by which parts of the 'metadata' property are
read and updated. Can the be extended to do more duty at other levels
of the hierarchy?

Larry
--
http://www.parc.xerox.com/masinter

Received on Sunday, 11 October 1998 23:16:03 UTC