JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for DC-ARCHITECTURE Archives


DC-ARCHITECTURE Archives

DC-ARCHITECTURE Archives


DC-ARCHITECTURE@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

DC-ARCHITECTURE Home

DC-ARCHITECTURE Home

DC-ARCHITECTURE  April 2002

DC-ARCHITECTURE April 2002

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Attributes of DCMI metadata terms

From:

Sugimoto Shigeo <[log in to unmask]>

Reply-To:

This list, which supersedes dc-datamodel, dc-schema, and dc-implementors, i" <[log in to unmask]>

Date:

Fri, 19 Apr 2002 09:13:54 +0900

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (251 lines)

Dear Tom,

I have a question on the attributes from the viewpoint of multilingual
description. I'm CCing this message to DC-international (localization
and internationalization group) since the subscribers might have interests
in this issue.

Given that a term is translated into a language(s) which is officially
approved by a local community(ies), do you mean that "See also" is to
be used to point the translation (or translations)?
Or, no linking from the central description to local but official descriptions?

I'm thinking that DC Term descriptions in non-English languages could have
the same set of descriptive elements, e.g. "Label", "Definition", etc..
And, in addition, each description of an element could have a link to
the corresponding element to the Official description in English,
which maintained in the central registry.

Thank you,

-- Shigeo

In <20020417162514.A1856@LEPIDUS>, [log in to unmask] wrote:
>> Date:         Wed, 17 Apr 2002 16:25:14 +0200
>> Reply-To: "This list, which supersedes dc-datamodel, dc-schema, and
>>  dc-implementors, i" <[log in to unmask]>
>> From: Thomas Baker <[log in to unmask]>
>> Subject:      Attributes of DCMI metadata terms
>> To: [log in to unmask]
>>
>> Dear all,
>>
>> Attached at the end of this message is an appendix showing
>> which attributes have been used to describe DCMI terms
>> since 1996.  Based on these sets of attributes, and in light
>> of current discussion on this list, I suggest here a set of
>> attributes for "DCMI term declarations" and suggest that a "See
>> Also" link point to further background information collected
>> by the Usage Board as documentation for new-term proposals.
>>
>> I am currently working on the long-awaited Consolidated Term
>> Declaration (or perhaps Dictionary) that brings DCMES 1.1,
>> the Dublin Core Qualifiers, and the terms approved by Usage
>> Board in 2001 into one document using a consistent set of
>> attributes.  Finishing that task depends on resolving the
>> problem discussed here.
>>
>> I would appreciate if some of you could give this a careful
>> read from various points of view -- Usage Board, Registry,
>> and Architecture (eg, RDF schemas).  A caveat: I have not
>> tested this by formatting all of the DCMI terms yet --
>> uh, I'd rather get consensus on the attributes first...
>> In particular, I'm not very happy with the jargon for "name of
>> term", "namespace URI of term", and "URI of term's namespace".
>>
>> The consolidated term document will supersede all previous
>> documents and become the definitive declaration of DCMI terms
>> and therefore the basis for any machine-understandable
>> representations thereof.
>>
>> I would also like to hear opinions on where this set of
>> attributes should reside -- perhaps in a special Usage Board
>> document, though it is not clear to me that the Usage Board
>> should be the group to maintain the schema attributes.
>>
>> Also, I cite what I see as the major documents setting the
>> context for this set of attributes:
>> http://dublincore.org/documents/dcmi-namespace/
>> http://dublincore.org/usage/documents/process/
>> http://dublincore.org/usage/documents/mission/
>> Am I overlooking any?
>>
>> I propose:
>>
>> ------------start-----------------------------------------------
>> A "DCMI term declaration" (see
>> http://dublincore.org/documents/dcmi-namespace/) should contain:
>>
>>    Label                  The human-readable label assigned to
>>                           the qualifier.
>>    Definition             The definition of the term.
>>                           - or -
>>                           A statement that represents the concept
>>                           and essential nature of the term.
>>    Comment                Additional information associated with
>>                           the term.
>>                           - or -
>>                           Information concerning the possible
>>                           application of the proposed term
>>    See Also               A link to more information about the term.
>>
>>    Name of term           The unique token assigned to the term
>>    URI of terms's         eg, http://purl.org/dc/elements/1.1/ or
>>       namespace           http://purl.org/dc/terms/
>>    Namespace URI of term  eg, http://purl.org/dc/elements/1.1/title or
>>                           http://purl.org/dc/terms/audience
>>    Status                 Cross-Domain, Domain-Specific, or Obsolete
>>                           (typology to be taken from
>>                           http://dublincore.org/usage/documents/process)
>>    Type of term           Element, Element Refinement, or Encoding Scheme
>>                           (typology to be taken from
>>                           http://dublincore.org/usage/documents/mission/)
>>    Term qualified         If an Element Refinement, the Element qualified
>>
>> One "See Also" link should point to the following
>>
>>    Examples             Examples of use of the proposed term, making
>>                         clear what type of literal values are expected
>>    Why needed           A justification of the need for the proposed term
>>    Related DCMI terms   A discussion of possible overlap with existing
>>                         terms
>>    Related non-DCMI     An annotated listing of related terms in non-DCMI
>>       terms             metadata vocabularies
>>    Impact on            An annotated listing of existing applications that
>>    applications         could be affected by recognition of this term
>>    About the proposers  A pointer to a description, in standard
>>                         form (to be specified) of the working group or
>>                         organization putting forward the proposal: its
>>                         scope, aims, a brief history, current status,
>>                         and a pointer to archives.
>>
>> As per Roland's suggestion, the "namespace URI of term" should
>> not be a "clickable" link on any Web pages made from this term
>> declaration to avoid the usual questions about "what is at the
>> end of the namespace".
>>
>> ------------end-----------------------------------------------
>>
>> Thanks,
>> Tom
>>
>>
>> APPENDIX
>>
>> -------------------------------------------------------------
>> Elements Version 1.0, September 1998
>> http://dublincore.org/documents/1998/09/dces/
>>                and
>> RFC 2413, September 1998
>> http://www.ietf.org/rfc/rfc2413.txt
>> -------------------------------------------------------------
>>
>> Except for "Label", the attributes of the metadata terms were
>> not explicitly labelled or discussed in Version 1.0 or RFC 2413.
>>
>>     [Name?]       a natural-language name for the element
>>     Label:        a "formal single-word label" for use in
>>                   "encoding schemes"
>>     [Definition?] a definition was provided
>>
>> -------------------------------------------------------------
>> Elements Version 1.1
>> http://dublincore.org/documents/1999/07/02/dces/
>> -------------------------------------------------------------
>>
>> This version recast the element definitions using attributes
>> defined in ISO/IEC 11179:
>>
>>    Name          The label assigned to the data element
>>    Identifier    The unique identifier assigned to the data element
>>    Definition    A statement that clearly represents the concept and
>>                  essential nature of the data element
>>    Comment       A remark concerning the application of the data element
>>
>> The following ISO/IEC 11179 attributes were assumed to hold for
>> all of the elements:
>>
>>    Version       The version of the data element, here "1.1" (for all)
>>    Registration  The entity authorised to register the data element,
>>       Authority  here "Dublin Core Metadata Initiative" (for all)
>>    Language      The language in which the data element is specified,
>>                  here "en" (for all)
>>    Obligation    Indicates if the data element is required to always
>>                  or sometimes be present (contain a value), here
>>                  "Optional" (for all)
>>    Datatype      Indicates the type of data that can be represented
>>                  in the value of the data element, here
>>                  "Character String" (for all)
>>    Maximum       Indicates any limit to the repeatability of the data
>>      Occurrence  element, here "Unlimited" (always)
>>
>> -----------------------------------------------------------------------
>> Dublin Core Qualifiers, July 2000
>> http://dublincore.org/documents/2000/07/11/dcmes-qualifiers/
>> -----------------------------------------------------------------------
>>
>> The introduction explained that the properties of qualifiers --
>> in particular the terms Name and Label -- differed with respect
>> to those defined for the Dublin Core Metadata Element Set
>> Version 1.1, reflecting a decision to bring Dublin Core schema
>> terminology in line with terminology in the XML community to
>> promote easier integration of Dublin Core schemas in XML and RDF
>> environments.
>>
>>    Name          The unique token assigned to the qualifier.
>>    Label         The human-readable label assigned to the qualifier.
>>    Definition    A statement that represents the concept and essential
>>                  nature of the qualifier.
>>    Comment       Additional information associated with the qualifier
>>                  (if available).
>>    See Also      A link to more information about the qualifier (if
>>                  available).
>>
>> -----------------------------------------------------------------------
>> Current requirements for new-term proposals to Usage Board
>> http://128.253.121.110/DC-UB/DC-UBprocess8.html
>> -----------------------------------------------------------------------
>>
>>    Name                 A suggested unique token for use in encodings
>>    Label                A suggested human-readable label for the proposed term
>>    Definition           The definition of the term
>>    Comment              Information concerning the possible application of the
>>                         proposed term
>>    Examples             Examples of use of the proposed term, making clear what
>>                         type of literal values are expected
>>    Type of term         Is the proposed term an "element," or an "element
>>                         refinement" (as defined in
>>                         http://dublincore.org/usage/documents/mission.shtml)
>>                         [NOTE: Encoding schemes will be registered using a
>>                         separate process]
>>    Term qualified       If the proposed term is a element refinement, which term
>>                         does it qualify?
>>    Why needed           A justification of the need for the proposed term
>>    Proposed status      Is the term proposed as Domain-Specific or Cross-Domain?
>>    Related DCMI terms   A discussion of possible overlap with existing terms
>>    Related non-DCMI     An annotated listing of related terms in non-DCMI
>>       terms             metadata vocabularies
>>    Impact on            An annotated listing of existing applications that
>>    applications         could be affected by recognition of this term
>>    About the proposers  A pointer to a description, in standard
>>                         form (to be specified) of the working group or
>>                         organization putting forward the proposal: its scope,
>>                         aims, a brief history, current status, and a pointer
>>                         to archives.
>>
>>
>> --
>> Dr. Thomas Baker                                [log in to unmask]
>> Institutszentrum Schloss Birlinghoven          mobile +49-171-408-5784
>> Fraunhofer-Gesellschaft                          work +49-30-8109-9027
>> 53754 Sankt Augustin, Germany                     fax +49-2241-14-2619


=========================================================
SUGIMOTO, Shigeo, Ph.D.
Professor
University of Library and Information Science (ULIS)
postal address:  Tsukuba, Ibaraki 305-8550, JAPAN
phones: +81-298-59-1348(office), +81-298-59-1556 (lab.)
        +81-298-59-1090(ULIS, Research Assistance Office)
fax: +81-298-59-1093    email: [log in to unmask]

Top of Message | Previous Page | Permalink

JISCMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2014
March 2014
February 2014
January 2014
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
September 2005
August 2005
July 2005
June 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
March 2004
February 2004
January 2004
November 2003
October 2003
September 2003
August 2003
June 2003
May 2003
April 2003
March 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
December 2000
November 2000
October 2000


WWW.JISCMAIL.AC.UK

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager