On Thu, 6 Dec 2001, Rachel Heery wrote:
> On Thu, 6 Dec 2001, Wagner,Harry wrote:
<snip>
>
> > - remove the eor:tags used to define the schemas themselves, as in:
> >
>
> I have not gone thro all of the schemas identifying use of the eor tag....
> are you suggesting replacing the prefix 'eor' with something else or do
> you think all these tags are redundant..... I'm not sure i understand the
> motivation.
>
>
> > <eor:Schema rdf:about="&dcns;">
> > <rdf:value>The Dublin Core Element Set v1.1</rdf:value>
> > <dc:title>The Dublin Core Element Set v1.1</dc:title>
> > <dc:publisher>The Dublin Core Metadata Initiative</dc:publisher>
> > <dc:description>The Dublin Core metadata vocabulary is a simple vocabulary
> > intended to facilitate discovery of resources. </dc:description>
> > <dc:language>English</dc:language>
> > <dc:relation rdf:resource="http://dublincore.org/documents/dces/"/>
> > <dc:date>2000-07-02</dc:date>
> > </eor:Schema>
> >
> > This information should be captured by the registry application when it is
> > imported (and built into a very similar model), but does not need to be part
> > of the schema.
> >
>
> As I see it any expression of a schema would usefully contain this sort of
> administrative metadata... such as who wrote it, significant dates, name
> of vocabulary etc. Are you suggesting we use another prefix for the tag
> or remove all the information?
>
> I'm not sure I understand why you would want to leave such information
> out of the schema?... the DCMI schema might be imported by a registry,
> for example, so that that particular schema could be navigated along with
> several other schema. In which case the registry might want to provide an
> export functionality whereby that schema is exported. Or the registry
> might more efficiently point at schemas in distributed way and index them
> centrally.
>
> Whichever way the information in the schema needs to include
> the admin metadata??
>
I think it is reasonable, in a distributed environment, to expect third
parties to provide such admin metadata using a canonical vocab such as DC,
but it is unreasonable to expect them to know and use a vocab that is
being used internally within an application (registry). This goes against
the grain of reusability/scalability.
I can envisage that this type of admin metadata could be provided via a
fill-in form at the time a vocab is registered with the registry and hence
the eor tags, or equivalent would be generated internally to the registry.
This admin metadata does not necessarily have to be stored as part of the
vocab encoding either.
Manjula
-----------------------------------------------------------------------
Manjula Patel PhD E-mail: [log in to unmask]
UKOLN Voice: (+44) 1225 826547
University of Bath, Claverton Down, Fax: (+44) 1225 826838
Bath, BANES, BA2 7AY URL: http://www.ukoln.ac.uk/
-----------------------------------------------------------------------
|