Topic: Attributes of DCMI Terms ("Usage Board profile")
Modified: 2004-03-22 09:41, Monday
Maintainer: Tom Baker
Latest version: http://dublincore.org/usage/meetings/2004/03/ISSUES/profiles-usage/
See also: http://dublincore.org/usage/meetings/2004/03/ISSUES/
Shepherd: Thomas Baker
ITHACA 5 steps
1. Define the set of properties and encoding schemes for describing terms.
2. Understand how they relate to existing terms.
3. Ask DCMI Directorate for UB namespace.
4. Set up UB namespace and declare terms as necessary.
5. Define an application profile.
Timeframe: steps 1-3 for Seattle.
ITHACA ACTION ITEM Tom: Submit something to the UB list by 4 July 2003.
Title: Usage Board Application Profile (draft)
Creator: Tom Baker
Date: 2003-11-21
Note: Need to add Broader Than/ Narrower Than here...
Mandatory
Name: The unique token assigned to the term.
Namespace: The Uniform Resource Identifier of the namespace
within which the term is defined.
URI: The Uniform Resource Identifier used to uniquely
identify a term.
Label: The human-readable label assigned to
the term.
Definition: A statement that represents the concept
and essential nature of the term.
Type of term: The type of term, such as Element or Encoding
Scheme, as described in the DCMI Grammatical
Principles.
Status: Status assigned to term by the DCMI Usage Board,
as described in the DCMI Usage Board Process.
Date issued: Date on which a term was first declared.
When appropriate
Comment: Additional information about the term
or its application.
See: A link to authoritative documentation.
References: A citation or URL of a resource referenced
in the Definition or Comment.
Refines: A reference to a term refined by an Element
Refinement.
Qualifies: A reference to a term qualified by an Encoding
Version-related
Date modified: Date on which a term declaration was subsequently
modified.
Decision: A link to the Usage Board decision describing
the creation or modification of a term
declaration.
Version: An historical version of a term declaration.
Replaces: A reference to the immediately precedent
historical version of a term declaration.
Is Replaced By: A reference to the immediately subsequent
historical version of a term declaration.
RDF schema bindings:
Name: NOT USED
Namespace: rdfs:isDefinedBy rdf:resource="xxx"
Label: rdfs:label xml:lang="en-US"
Definition: rdfs:comment xml:lang="en-US"
Type of term: rdf:type rdf:resource="http://.../#element"
Status: dcu:status rdf:resource="http://.../#recommended"
Date issued: dcterms:issued
Comment: dc:description xml:lang="en-US"
See: rdfs:seeAlso rdf:resource="http://..."
References: dcterms:references rdf:resource="http://.../#W3CDTF"
Refines: rdfs:subPropertyOf
Qualifies: dcu:qualifies
Date modified: dcq:Modified
Decision: dcu:decision rdf:resource = "uri"
-- Harry Wagner suggests dcterms:isReferenceBy
Version: dcu:version rdf:resource = "uri"
-- Harry Wagner suggests dcterms:hasVersion
Replaces: NOT USED
Is Replaced By: NOT USED
Terms that would need to be declared in a Usage Board namespace:
Status: dcu:status
Qualifies: dcu:qualifies
Decision: dcu:decision
Version: dcu:version
Vocabulary for "Status"
http://dublincore.org/usage/documents/process/#conforming
http://dublincore.org/usage/documents/process/#recommended
http://dublincore.org/usage/documents/process/#registered
Vocabulary for "Type of Term"
http://dublincore.org/usage/documents/principles/#element-refinement
http://dublincore.org/usage/documents/principles/#element
http://dublincore.org/usage/documents/principles/#encoding-scheme
http://dublincore.org/usage/documents/principles/#vocabulary-term
------------------------------------------------------------------------
From: "Wagner,Harry" <wagnerh@oclc.org>
To: "'Thomas Baker'" <thomas.baker@bi.fhg.de>
Subject: RE: Rest vs. Soap (was Registry Extensions)
Date: Thu, 11 Dec 2003 14:00:28 -0500
------------------------------------------------------------------------
Tom,
At the next UB meeting can you also consider hasStatus (in addition to
isTranslationOf) as a refinement to relation? Thanks... hw
> > -----Original Message-----
> > From: Thomas Baker [mailto:thomas.baker@bi.fhg.de]
> > Sent: Friday, November 14, 2003 11:38 AM
> > To: Wagner,Harry
> > Cc: DC-REGISTRY@JISCMAIL.AC.UK
> > Subject: Re: Rest vs. Soap (was Registry Extensions)
> >
> >
> > Harry,
> >
> > I mean something like:
> >
> > <rdf:Property rdf:about="http://purl.org/dc/terms/audience">
> > <rdfs:label xml:lang="jp">[Label in Japanese]</rdfs:label>
> > <rdfs:comment xml:lang="jp">[Definition in
> > Japanese]</rdfs:comment>
> > <xyz:translates
> > rdf:resource="http://dublincore.org/usage/terms/history/#audie
> > nce-001"/>
> >
> > ..where xyz: is either a DCMI-maintained vocabulary or
> > something like OWL.
> >
> > In other words, the declaration of the translation of a term
> > would carry an extra assertion pointing to the specific
> > historical version in English used as the basis of the
> > translation. To be clear: I do _not_ mean the translation
> > should be "about" the specific historical version instead of
> > the generically identified entity "Audience".
> >
> > Now, if the Japanese site _also_ were to give a version
> > identifier to each successive revision of the _Japanese
> > translation_, then one might want to add yet _another_
> > assertion, such as:
> >
> > <dcterms:hasVersion
> > rdf:resource="http://www.ulis.ac.jp/dublincore/#audience-jp-001"
> >
> > following the model used for the declaration of Audience
> (in English)
> > at http://dublincore.org/2003/03/24/dcq#.
> >
> > Tom
> >
> > On Fri, Nov 14, 2003 at 10:41:51AM -0500, Harry Wagner wrote:
> > > > In that case, I would like to suggest the model of identifying
> > > > particular historical versions of a term with a separate URI, as
> > > > in:
> > > > http://purl.org/dc/terms/audience
> > > >
> > > > the "term URI" supported by the DCMI Namespace Policy, as
> > opposed to:
> > > >
> > > >
> > > http://dublincore.org/usage/terms/history/#audience-002
> > >
> > http://dublincore.org/usage/terms/history/#audience-001
> > >
> > > the successive historical states of that term. In other words,
> > > a Japanese translation of the term "Audience" could include the
> > > assertion:
> > >
> > > Translates:
> > http://dublincore.org/usage/terms/history/#audience-001
http://purl.org/dc/elements/1.1/title
http://dublincore.org/2003/03/24/dces#title
http://dublincore.org/usage/terms/history/#title-001
http://dublincore.org/usage/terms/history/#title-002
http://dublincore.org/usage/terms/history/#title-003
http://dublincore.org/usage/terms/history/#title-004
http://purl.org/dc/elements/1.0/title
http://purl.org/dc/elements/1.1/title