[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: [docbook-tc] [bobs@caldera.com: Dublin Core in DocBook]
I'm following up on the DocBook TC action item for Norm, Dick, and I to develop a mapping of DocBook to Dublin Core. Norm suggested I send this to the TC before the meeting on Tuesday. Here is a copy of the Dublic Core Metadata Element Set[1], with an initial mapping to DocBook element content. Most of them have an excellent match in DocBook, but a few cannot be expressed directly in DocBook (unless I've missed some elements, in which case I'm sure I'll hear about it 8^). In some cases, the mapping will be application-specific because of how elements can be used for different purposes, and the way the role attribute modifies element semantics. Title Label: Title The name given to the resource, usually by the Creator or Publisher. DocBook: <title> Author or Creator Label: Creator The person or organization primarily responsible for creating the intellectual content of the resource. For example, authors in the case of written documents, artists, photographers, or illustrators in the case of visual resources. DocBook: <author>, <corpauthor> Subject and Keywords Label: Subject The topic of the resource. Typically, subject will be expressed as keywords or phrases that describe the subject or content of the resource. The use of controlled vocabularies and formal classification schemas is encouraged. DocBook: <keywordset> for freely chosen words, <subjectset> for controlled vocabulary. Description Label: Description A textual description of the content of the resource, including abstracts in the case of document-like objects or content descriptions in the case of visual resources. DocBook: <abstract> Publisher Label: Publisher The entity responsible for making the resource available in its present form, such as a publishing house, a university department, or a corporate entity. DocBook: <publishername> Other Contributor Label: Contributor A person or organization not specified in a Creator element who has made significant intellectual contributions to the resource but whose contribution is secondary to any person or organization specified in a Creator element (for example, editor, transcriber, and illustrator). DocBook: <othercredit>, <collab>, <editor>, possibly another <author> with a role attribute. Date Label: Date A date associated with the creation or availability of the resource. Recommended best practice is defined in a profile of ISO 8601 ( http://www.w3.org/TR/NOTE-datetime ) that includes (among others) dates of the forms YYYY and YYYY-MM-DD. In this scheme, the date 1994-11-05 corresponds to November 5, 1994. DocBook: <date>, <pubdate> Resource Type Label: Type The category of the resource, such as home page, novel, poem, working paper, technical report, essay, dictionary. For the sake of interoperability, Type should be selected from an enumerated list that is under development in the workshop series. DocBook: no element matches the Dublin Core Types [2]. Implied values: text, image. This could be a new metadata element. Format Label: Format The data format and, optionally, dimensions (e.g., size, duration) of the resource. The format is used to identify the software and possibly hardware that might be needed to display or operate the resource. For the sake of interoperability, the format should be selected from an enumerated list that is currently under development in the workshop series. DocBook: no element describes this. The XML is an implied text/xml value. When processed to another format, then other format values apply. This does not need a new element, IMHO. Resource Identifier Label: Identifier A string or number used to uniquely identify the resource. Examples for networked resources include URLs and URNs (when implemented). Other globally-unique identifiers, such as International Standard Book Numbers (ISBN) or other formal names would also be candidates for this element. DocBook: <isbn>, <issn>, <invpartnumber>, <pubsnumber>. Also id attribute (but not globally unique). Where would a globally unique URN go? Source Label: Source Information about a second resource from which the present resource is derived. While it is generally recommended that elements contain information about the present resource only, this element may contain metadata for the second resource when it is considered important for discovery of the present resource. DocBook: no element matches this. An XML document could refer to a data repository from which it is derived, or formatted output could refer to its XML source. Possibly a new DocBook metadata element. Language Label: Language The language of the intellectual content of the resource. Recommended best practice is defined in RFC 1766 http://info.internet.isi.edu/in-notes/rfc/files/rfc1766.txt DocBook: <lang> Relation Label: Relation An identifier of a second resource and its relationship to the present resource. This element is used to express linkages among related resources. For the sake of interoperability, relationships should be selected from an enumerated list that is currently under development in the workshop series. DocBook: <xref>, <link>, <ulink>, <olink>. Also, any number of implied relationships among a document's elements (next, previous, etc.). XLink elements can also express relations to other resources. This is a potentially very rich area. Coverage Label: Coverage The spatial and/or temporal characteristics of the intellectual content of the resource. Spatial coverage refers to a physical region (e.g., celestial sector) using place names or coordinates (e.g., longitude and latitude). Temporal coverage refers to what the resource is about rather than when it was created or made available (the latter belonging in the Date element). Temporal coverage is typically specified using named time periods (e.g., Neolithic) or the same date/time format ( http://www.w3.org/TR/NOTE-datetime ) as recommended for the Date element. DocBook: no element matches this. Could be a new metadata element. Rights Management Label: Rights A rights management statement, an identifier that links to a rights management statement, or an identifier that links to a service providing information about rights management for the resource. DocBook: <copyright>, <legalnotice>. -- [1] http://dublincore.org/documents/1998/09/dces/ [2] http://dublincore.org/documents/1999/08/05/resource-typelist/ Bob Stayton 400 Encinal Street Publications Architect Santa Cruz, CA 95060 Technical Publications voice: (831) 427-7796 Caldera International, Inc. fax: (831) 429-1887 email: bobs@caldera.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC