My "move" is just that there seems to be no mechanism currently to use the
encoding scheme URI with several of the elements, such as
Rights and Description, since they were never approved. So my suggestion
is to register them however that is done. That is true that their
relationship to the element is different as Andy points out below, but
there still needs to be a way to point to a URI for Rights and
Description. Then in the definition of that encoding scheme it could be
stated for example under Description that it is used for the value of that
description, since we do list encoding schemes separately that are
applicable under each element.
Rebecca
On Mon, 15 Oct 2001, Roland Schwaenzl wrote:
> > From [log in to unmask] Sun Oct 14 22:03 MET 2001
> > X-Meta: <rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
> > xmlns:dc="http://purl.org/dc/elements/1.1/"> <rdf:Description about="">
> > <dc:publisher> UKOLN
> > MIME-Version: 1.0
> > Date: Sun, 14 Oct 2001 20:53:33 +0100
> > From: Andy Powell <[log in to unmask]>
> > Subject: Re: URIs
> > To: [log in to unmask]
> >
> > On Fri, 12 Oct 2001, Rebecca S. Guenther wrote:
> >
> > > The encoding scheme URI has been registered in DCQ for some elements but
> > > not all. However, some people have said that a URI may be used for any
> > > element. We need to either register URI for all (or all that are deemed
> > > appropriate) or for none of them. Other elements that need URI that I
> > > have identified through my work on the library application profile are
> > > Description and Rights. I'm not sure whether it's appropriate for others
> > > where it isn't already defined.
> > >
> > > Could we have a consistent approach? Maybe these can be "fast tracked"?
> >
> > Note that the semantics of 'URI' are different in Identifier, Relation and
> > Source than they are in Rights and Description.
> >
> > In Identifier, Relation and Source, the use of 'URI' as an encoding
> > scheme means "here is the value and it is a URI".
> >
> > In Rights and Description, the use of 'URI' as an encoding scheme would
> > mean "the value can be found at the following URI".
> >
> > These two things are not the same and therefore shouldn't be encoded using
> > the same mechanism.
> >
> > Andy.
>
> Dear Andy,
>
>
> Providing a URI is to give a resource (in the sense of the web). In general there is nothing more than just that.
> Everything else - meaning for instance - comes via properties (metadata), which might be given in the record explicitly
> or can be obtained by using knowledge. Knowledge (for instance) can be obtained
> by understanding the definition of properties (assuming the definitions are understandable).
>
> I'm not quite sure, whether i understand Rebecca's move exactly, but my feeling is - it's pointing the right way.
>
> rs
>
>
> >
> > > Rebecca
> > >
> >
> > Andy
> > --
> > Distributed Systems and Services
> > UKOLN, University of Bath, Bath, BA2 7AY, UK [log in to unmask]
> > http://www.ukoln.ac.uk/ukoln/staff/a.powell Voice: +44 1225 323933
> > Resource Discovery Network http://www.rdn.ac.uk/ Fax: +44 1225 826838
> >
>
|