| 创作者： | 安德鲁·德曼 |
| 发行日期: | 1999-05-20 |
| 最新版本: | //www.voudr.com/specifications/dublin-core/dc-xml-data-schemas/ |
| 发布历史: | //www.voudr.com/specifications/dublin-core/dc-xml-data-schemas/release_history/ |
| 描述： | 都柏林核心元数据元素集是由图书管理员设计的15个元素的集合，用于对文档进行分类和编目。这些元素非常通用，适合对xml数据模式进行分类和描述。本文提出了一种基于Dublin Core元素的模式，并给出了其在xml数据模式中的应用指导。 |
Dublin Core™元数据元素集是由图书管理员设计的15个元素的集合，用于对文档进行分类和编目。这些元素非常通用，适合对xml数据模式进行分类和描述。本文提出了一个基于Dublin Core™元素的模式，并给出了在XML-Data模式中应用该模式的指导原则。
但首先，我们来看一个示例:根据这里描述的元素分类的一个简单模式可能如下所示:
<标题>我的琐碎架构 安德鲁·守工士 mailto：(电子邮件保护) urn:electrocommerce-org/taxonomy/teapot teapot urn:electrocommerce-org/taxonomy/coffee coffee caff< /keyword>
的模式
这定义了一小组标记，每个标记都基于附录a中所示的相应通用Dublin Core™元素，但专门用于编目模式。
<！ - 架构目录的架构，版本1，基于Dublin Core，由AJL生成5/13/99。- >，这定义了一组小组标签，每个标签相应的通用都柏林核心，但这里专注于编目模式的目的。有关Dublin Core™的更多信息，请访问http://purl.org/dc。 <描述>混合文本和标记。如果标记，必须是良好的。 <属性类型=“XML：lang”/> <描述>用于分类的关键字，具有人类语言含义，但未从由URI标识的受控词汇绘制。我们建议仅使用小写文本。 <属性类型=“xml：lang”/> <描述>这种模式的描述性标题。 <属性类型=“xml：lang”/> <描述>人或组织主要负责创建此模式的智力内容。 <元素类型=“personReference”/> <元素类型=“freeText”/> The topic of the schema. Typically, subject will be expressed as keywords or phrases that describe the subject or content of the schema. The use of controlled vocabularies and formal classification schemes is encouraged. 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. The entity responsible for making the resource available in its present form, such as a publishing house, a university department, or a corporate entity. 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). 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 are also candidates for this element. 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 a date, creator, format, identifier, or other metadata for the second resource when it is considered important for discovery of the present resource; recommended best practice is to use the Relation element instead. For example, it is possible to use a Source date of 1603 in a description of a 1996 film adaptation of a Shakespearean play, but it is preferred instead to use Relation "IsBasedOn" with a reference to a separate resource whose description contains a Date of 1603. Source is not applicable if the present resource is in its original form. The language of the intellectual content of the resource. When used, he content of this field must coincide with RFC 1766 [Tags for the Identification of Languages, http://ds.internic.net/rfc/rfc1766.txt ]; examples include en, de, es, fi, fr, ja, th, and zh. 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. A small set of tags, each based on the corresponding generic Dublin Core™ element, but here specialized for the purpose of cataloging schemas. See http://purl.org/dc for more information on Dublin Core™. Many tags may be repeated at this level, and also allow multiple occurences of their subelments. The intended usage is that distinct items (for example distinct creators) should be expressed with separate elements, while alternative forms of reference to the same item (for example, several ways of referring to the same creator) should be expressed as alternate subelements.
如何使用架构
理解如何使用它的关键是首先理解几个基于uri的引用的角色，比如personReference、subjectReference和resourceReference。这些都发生在Dublin Core™中内容模型非常灵活的元素中。例如，在DC中，创建者元素可能有自由文本，或者它可能通过一些众所周知的标识系统引用特定的公司或个人。控制的名称集，例如D-U-N-S数字，是很好的标识符。我们将它们与通用资源标识符规范配对，并建议控制标识符的公司和组织应该用URI来命名它们的标识符集，从而允许我们在需要受控标识符的地方使用数据类型“URI”。
例如，假设Dun和Bradstreet给他们发布的每个数字都提供了一个以“urn:www-dnb-com/dunsno”开头的URI。一个创建者元素可能看起来像
<创造者> < personRef > urn: www-dnb-com dunsno / 123456789012345 < / personRef > < / >创造者
类似地，主题分类法将由许多权威机构合理地定义。每一个都应该有一个对应的URI名称空间，使用类似于
<主题> < subjectRef > urn: electrocommerce-org /分类/茶壶< / subjectRef > < / >主题
主题分类也允许不受控制的词汇表中的关键字，因此可能会看到以下情况:
<主题> <受试者> URN：电力信息 - org / cathonononomy / taxody / teapot <关键字>茶壶
根据这里描述的元素分类的普通模式可能如下所示:
<标题>我的琐碎架构 安德鲁·守工士 mailto：(电子邮件保护) urn:electrocommerce-org/taxonomy/teapot teapot urn:electrocommerce-org/taxonomy/coffee coffee caff< /keyword>
附录A:通用都柏林核心™元素集
这使得以完全无限制的方式定义十五个元素。每个元素都可以包含任何内容。