LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  September 2002

ZNG September 2002

Subject:

DC Index Set

From:

"LeVan,Ralph" <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Thu, 19 Sep 2002 10:25:32 -0400

Content-Type:

multipart/mixed

Parts/Attachments:

Parts/Attachments

text/plain (518 lines) , DcIndexSet.xml (518 lines)

Here's my cut at putting the DC indexes into some XML. Subject to much
debate and change.

Ralph

<indexSet>
    <name>Dublin Core Indexes</name>
    <contactInfo>Ralph LeVan. mailto:[log in to unmask]</contactInfo>
    <description>Indexes to support the Dublin Core Metadata Element Set,
Version 1.1, as
        defined at http://dublincore.org/documents/dces/</description>
    <index>
        <name>TitleWord</name>
        <description>A name given to the resource. Typically, a Title will
be a name by
           which the resource is formally known.</description>
        <oldAttributes attributeSet="bib1" use="4" structure="6"/>
        <oldAttributes attributeSet="bib1" use="1097" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="1"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>
    <index>
        <name>TitleString</name>
        <description>A name given to the resource. Typically, a Title will
be a name by which the
            resource is formally known.</description>
        <oldAttributes attributeSet="bib1" use="4" structure="108"/>
        <oldAttributes attributeSet="bib1" use="1097" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="1"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>

    <index>
        <name>CreatorWord</name>
        <description>An entity primarily responsible for making the content
of the resource. Examples of a
            Creator include a person, an organisation, or a service.
Typically, the name of a Creator should
            be used to indicate the entity.</description>
        <oldAttributes attributeSet="bib1" use="1098" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="3"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            <functionalQualifier attributeSet="bib-2" value="creator"/>
            </newAttributes>
        </index>
    <index>
        <name>CreatorString</name>
        <description>An entity primarily responsible for making the content
of the resource. Examples of a
            Creator include a person, an organisation, or a service.
Typically, the name of a Creator should
            be used to indicate the entity.</description>
        <oldAttributes attributeSet="bib1" use="1098" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            <functionalQualifier attributeSet="bib-2" value="creator"/>
            </newAttributes>
        </index>

    <index>
        <name>SubjectWord</name>
        <description>The topic of the content of the resource. Typically, a
Subject will be expressed
            as keywords, key phrases or classification codes that describe a
topic of the resource.
            Recommended best practice is to select a value from a controlled
vocabulary or formal
            classification scheme.</description>
        <oldAttributes attributeSet="bib1" use="21" structure="6"/>
        <oldAttributes attributeSet="bib1" use="1099" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="2"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>
    <index>
        <name>SubjectString</name>
        <description>The topic of the content of the resource. Typically, a
Subject will be expressed
            as keywords, key phrases or classification codes that describe a
topic of the resource.
            Recommended best practice is to select a value from a controlled
vocabulary or formal
            classification scheme.</description>
        <oldAttributes attributeSet="bib1" use="21" structure="108"/>
        <oldAttributes attributeSet="bib1" use="1099" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="2"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>

    <index>
        <name>DescriptionWord</name>
        <description>An account of the content of the resource. Description
may include but is not
            limited to: an abstract, table of contents, reference to a
graphical representation
            of content or a free-text account of the content.</description>
        <oldAttributes attributeSet="bib1" use="1100" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="4"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>
    <index>
        <name>DescriptionString</name>
        <description>An account of the content of the resource. Description
may include but is not
            limited to: an abstract, table of contents, reference to a
graphical representation
            of content or a free-text account of the content.</description>
        <oldAttributes attributeSet="bib1" use="1100" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="4"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>

    <index>
        <name>PublisherWord</name>
        <description>An entity responsible for making the resource
available. Examples of a
            Publisher include a person, an organisation, or a service.
Typically, the name of a
            Publisher should be used to indicate the entity.</description>
        <oldAttributes attributeSet="bib1" use="1018" structure="6"/>
        <oldAttributes attributeSet="bib1" use="1101" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="3"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            <functionalQualifier attributeSet="bib-2" value="publisher"/>
            </newAttributes>
        </index>
    <index>
        <name>PublisherString</name>
        <description>An entity responsible for making the resource
available. Examples of a
            Publisher include a person, an organisation, or a service.
Typically, the name of a
            Publisher should be used to indicate the entity.</description>
        <oldAttributes attributeSet="bib1" use="1018" structure="108"/>
        <oldAttributes attributeSet="bib1" use="1099" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            <functionalQualifier attributeSet="bib-2" value="publisher"/>
            </newAttributes>
        </index>

    <index>
        <name>ContributorWord</name>
        <description>An entity responsible for making contributions to the
content of the resource.
            Examples of a Contributor include a person, an organisation, or
a service. Typically, the name
            of a Contributor should be used to indicate the
entity.</description>
        <oldAttributes attributeSet="bib1" use="1106" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="3"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            <functionalQualifier attributeSet="bib-2" value="contributor"/>
            </newAttributes>
        </index>
    <index>
        <name>ContributorString</name>
        <description>An entity responsible for making contributions to the
content of the resource.
            Examples of a Contributor include a person, an organisation, or
a service. Typically, the name
            of a Contributor should be used to indicate the
entity.</description>
        <oldAttributes attributeSet="bib1" use="1106" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            <functionalQualifier attributeSet="bib-2" value="publisher"/>
            </newAttributes>
        </index>

    <index>
        <name>Date</name>
        <description>A date associated with an event in the life cycle of
the resource. Typically, Date
            will be associated with the creation or availability of the
resource. Recommended best
            practice for encoding the date value is defined in a profile of
ISO 8601 [W3CDTF] and
            follows the YYYY-MM-DD format.</description>
        <oldAttributes attributeSet="bib1" use="30" structure="108"/>
        <oldAttributes attributeSet="bib1" use="1102" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="5"/>
            <comparison attributeSet="utility" value="3"/>
            <formatStructure attributeSet="bib-2" value="1"/>
            </newAttributes>
        </index>

    <index>
        <name>TypeWord</name>
        <description>The nature or genre of the content of the resource.
Type includes terms
            describing general categories, functions, genres, or aggregation
levels for content.
            Recommended best practice is to select a value from a controlled
vocabulary
            (for example, the working draft list of Dublin Core Types
[DCT1]). To describe the
            physical or digital manifestation of the resource, use the
FORMAT element.</description>
        <oldAttributes attributeSet="bib1" use="1103" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="6"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>
    <index>
        <name>TypeString</name>
        <description>The nature or genre of the content of the resource.
Type includes terms
            describing general categories, functions, genres, or aggregation
levels for content.
            Recommended best practice is to select a value from a controlled
vocabulary
            (for example, the working draft list of Dublin Core Types
[DCT1]). To describe the
            physical or digital manifestation of the resource, use the
FORMAT element.</description>
        <oldAttributes attributeSet="bib1" use="1103" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="6"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>

    <index>
        <name>FormatWord</name>
        <description>The physical or digital manifestation of the resource.
Typically, Format may
            include the media-type or dimensions of the resource. Format may
be used to determine
            the software, hardware or other equipment needed to display or
operate the resource.
            Examples of dimensions include size and duration. Recommended
best practice is to
            select a value from a controlled vocabulary (for example, the
list of Internet Media
            Types [MIME] defining computer media formats).</description>
        <oldAttributes attributeSet="bib1" use="1107" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="7"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            <contentAuthority attributeSet="bib-2" value="2"/>
            </newAttributes>
        </index>
    <index>
        <name>FormatString</name>
        <description>The physical or digital manifestation of the resource.
Typically, Format may
            include the media-type or dimensions of the resource. Format may
be used to determine
            the software, hardware or other equipment needed to display or
operate the resource.
            Examples of dimensions include size and duration. Recommended
best practice is to
            select a value from a controlled vocabulary (for example, the
list of Internet Media
            Types [MIME] defining computer media formats).</description>
        <oldAttributes attributeSet="bib1" use="1107" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="7"/>
            <comparison attributeSet="utility" value="3"/>
            <contentAuthority attributeSet="bib-2" value="2"/>
            </newAttributes>
        </index>

    <index>
        <name>Identifier</name>
        <description>An unambiguous reference to the resource within a given
context. Recommended
            best practice is to identify the resource by means of a string
or number conforming to a formal
            identification system. Example formal identification systems
include the Uniform Resource
            Identifier (URI) (including the Uniform Resource Locator (URL)),
the Digital Object
            Identifier (DOI) and the International Standard Book Number
(ISBN).</description>
        <oldAttributes attributeSet="bib1" use="1102" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="5"/>
            <comparison attributeSet="utility" value="3"/>
            <formatStructure attributeSet="bib-2" value="1"/>
            </newAttributes>
        </index>

    <index>
        <name>SourceWord</name>
        <description>A Reference to a resource from which the present
resource is derived. The present
            resource may be derived from the Source resource in whole or in
part. Recommended best
            practice is to reference the resource by means of a string or
number conforming to a
            formal identification system.</description>
        <oldAttributes attributeSet="bib1" use="1108" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="9"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>
    <index>
        <name>SourceString</name>
        <description>A Reference to a resource from which the present
resource is derived. The present
            resource may be derived from the Source resource in whole or in
part. Recommended best
            practice is to reference the resource by means of a string or
number conforming to a
            formal identification system.</description>
        <oldAttributes attributeSet="bib1" use="1108" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="9"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>

    <index>
        <name>LanguageWord</name>
        <description>A language of the intellectual content of the resource.
Recommended best practice
            for the values of the Language element is defined by RFC 1766
[RFC1766] which includes
            a two-letter Language Code (taken from the ISO 639 standard
[ISO639]), followed optionally,
            by a two-letter Country Code (taken from the ISO 3166 standard
[ISO3166]). For example,
            'en' for English, 'fr' for French, or 'en-uk' for English used
in the United Kingdom.</description>
        <oldAttributes attributeSet="bib1" use="54" structure="6"/>
        <oldAttributes attributeSet="bib1" use="1105" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="10"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>
    <index>
        <name>LanguageString</name>
        <description>A language of the intellectual content of the resource.
Recommended best practice
            for the values of the Language element is defined by RFC 1766
[RFC1766] which includes
            a two-letter Language Code (taken from the ISO 639 standard
[ISO639]), followed optionally,
            by a two-letter Country Code (taken from the ISO 3166 standard
[ISO3166]). For example,
            'en' for English, 'fr' for French, or 'en-uk' for English used
in the United Kingdom.</description>
        <oldAttributes attributeSet="bib1" use="54" structure="108"/>
        <oldAttributes attributeSet="bib1" use="1105" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="10"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>

    <index>
        <name>RelationWord</name>
        <description>A reference to a related resource. Recommended best
practice is to reference
            the resource by means of a string or number conforming to a
formal identification system.
            </description>
        <oldAttributes attributeSet="bib1" use="1109" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="11"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>
    <index>
        <name>RelationString</name>
        <description>A reference to a related resource. Recommended best
practice is to reference
            the resource by means of a string or number conforming to a
formal identification system.
            </description>
        <oldAttributes attributeSet="bib1" use="1109" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="11"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>

    <index>
        <name>CoverageWord</name>
        <description>The extent or scope of the content of the resource.
Coverage will typically
            include spatial location (a place name or geographic
coordinates), temporal period (a
            period label, date, or date range) or jurisdiction (such as a
named administrative entity).
            Recommended best practice is to select a value from a controlled
vocabulary (for example,
            the Thesaurus of Geographic Names [TGN]) and that, where
appropriate, named places or
            time periods be used in preference to numeric identifiers such
as sets of coordinates or
           date ranges.</description>
        <oldAttributes attributeSet="bib1" use="1110" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="12"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>
    <index>
        <name>CoverageString</name>
        <description>The extent or scope of the content of the resource.
Coverage will typically
            include spatial location (a place name or geographic
coordinates), temporal period (a
            period label, date, or date range) or jurisdiction (such as a
named administrative entity).
            Recommended best practice is to select a value from a controlled
vocabulary (for example,
            the Thesaurus of Geographic Names [TGN]) and that, where
appropriate, named places or
            time periods be used in preference to numeric identifiers such
as sets of coordinates or
           date ranges.</description>
        <oldAttributes attributeSet="bib1" use="1110" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="12"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>

    <index>
        <name>RightsWord</name>
        <description>Information about rights held in and over the resource.
Typically, a Rights element
            will contain a rights management statement for the resource, or
reference a service providing
            such information. Rights information often encompasses
Intellectual Property Rights (IPR),
            Copyright, and various Property Rights. If the Rights element
is absent, no assumptions can
            be made about the status of these and other rights with respect
to the resource.</description>
        <oldAttributes attributeSet="bib1" use="1111" structure="6"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="13"/>
            <expansionInterpretation attributeSet="utility" value="1"/>
            <expansionInterpretation attributeSet="utility" value="3"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>
    <index>
        <name>RightsString</name>
        <description>Information about rights held in and over the resource.
Typically, a Rights element
            will contain a rights management statement for the resource, or
reference a service providing
            such information. Rights information often encompasses
Intellectual Property Rights (IPR),
            Copyright, and various Property Rights. If the Rights element
is absent, no assumptions can
            be made about the status of these and other rights with respect
to the resource.</description>
        <oldAttributes attributeSet="bib1" use="1111" structure="108"/>
        <newAttributes>
            <accessPoint attributeSet="xd" value="13"/>
            <comparison attributeSet="utility" value="3"/>
            </newAttributes>
        </index>

    <mappings>
        <map name="bib1" oid="1.2.840.10003.3.1"/>
        <map name="xd" oid="1.2.840.10003.3.12"/>
        <map name="utility" oid="1.2.840.10003.3.11"/>
        <map name="bib2" oid="1.2.840.10003.3.18"/>
        </mappings>
    </indexSet>


 <<DcIndexSet.xml>>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 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
October 2005
September 2005
August 2005
July 2005
June 2005
May 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
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 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

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager