| 创作者： | 安德鲁·德曼 |
| 发行日期： | 1999-05-25 |
| 最新版本： | //www.voudr.com/specifications/dublin-core/dc-xml-data-description/ |
| 发布历史： | //www.voudr.com/specifications/dublin-core/dc-xml-data-description/release_history/ |
| 描述： | Dublin核心MetaTAdata元素集是一系列，用于分类和目录电子资源的十五个元素。元素足够一般，它们适合分类和描述XML数据模式。本文提出了一种基于都柏林核心元素的架构，然后在XML数据模式中提供其应用指南。 |
Dublin Core™MetaTAdata元素集是一系列的十五个元素，旨在分类和目录电子资源。元素足够一般，它们适合分类和描述XML数据模式。本文提出了一种基于Dublin Core™元素的架构，然后为其在XML数据模式中的应用提供指南。
但首先，一个样本：根据这里描述的元素分类的微型模式可能如下所示：
关于玉米饼工厂的消息的模式。</ title> <creator> <freetext> Andrew Layman </ FreeText> <PersonReference> Mailto：<a href="//www.voudr.com/www/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="bedfd0daccdbc9d2fed3d7ddccd1cdd1d8ca90ddd1d3">[电子邮件受保护]</a></ personreference> </ creator> <主题> <主观指令> urn：caxonomy-biztalk-org：www.census.gov/epcd/naics/1997#3118 </ pecondrefers> <keyware> ortilla制造</ kexigon> </主题> <键入> <resourcreference> URN：Schemas-Microsoft-Com：XML-Data </ Resourcreference> </类型> <类型> <Resourcreference> URN：Schemas-BizTalk-Org / BizTalk-0.8.xml </ Resourcreference></类型> </ cataloginformation> </ description> </ schema></pre> <p><strong>架构</strong></p> <p>这定义了一小组标签，每个标签都基于相应的通用Dublin Core™元素，专门用于编目模式。</p> <pre><！ - 架构目录的架构，版本1，基于Dublin Core，设计了Andrew Layman的5/13/99。- > <schema xmlns ='urn：schemas-microsoft-com：xml-data'xmlns：dt ='urn：schemas-microsoft-com：datatypes'> <description>，这定义了一组小组标签，每个标签相应的通用都柏林核心，但这里专注于编目模式的目的。有关Dublin Core™的更多信息，请访问http://purl.org/dc。</ description> <collementtype name =“personalreference”model =“closed”content =“textonly”> <描述>对一个人的URI引用，可能是自然人，公司或任何其他法人。</描述> <DataType DT：Type =“URI”/> </ ElementType> <ElementType name =“主观调试”Model =“Closed”Content =“Textonly”> <描述>对来自受控分类的标识符的URI引用。</描述> <dataType dt：type =“uri”/> </ mextorype> <exporttype name =“resourcrefereference”model =“closed”content =“textonly”> <datatype dt：type =“Uri”/> </ mextorype> <ElementType name =“FreeText”Model =“打开”内容=“混合”> <描述>混合文本和标记。如果标记，必须是良好的。</描述> <属性类型=“XML：lang”/> </ mementType> <ElementType name =“关键字”Model =“closed”content =“textonly”> <描述>用于分类的关键字，具有人类语言含义，但未从由URI标识的受控词汇绘制。我们建议只使用小写文本。</ description> <属性类型=“xml：lang”/> </ mementtype> <collementype name =“标识符”model =“打开”content =“Eltonly”> <描述>模式的正式标识符。如果该目录信息描述的模式不是封闭文档，请将所描述的文档的URI放在此处。</ description> <group order =“一个”minoccurs =“1”maxoccurs =“*”> <元素类型=“Resourcereference“/> </ group> </ mextorype> <exportype name =”title“model =”closed“content =”textonly“> <描述>此模式的描述性标题。</ description> <属性类型=”XML：lang“/> </ collegytype> <exportype name =”creator“model =”打开“content =”Eltonly“> <描述>主要负责创建此模式的知识内容的人或组织。 </description> <group order="one" minOccurs="1" maxOccurs="*"> <element type="PersonReference" /> <element type="FreeText" /> </group> </ElementType> <ElementType name="subject" model="open" content="eltOnly" > <description>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.</description> <group order="one" minOccurs="0" maxOccurs="*"> <element type="SubjectReference" /> <element type="keyword" /> </group> </ElementType> <ElementType name="description" model="open" content="mixed" > <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.</description> <attribute type="xml:lang" /> </ElementType> <ElementType name="publisher" model="open" content="eltOnly" > <description>The entity responsible for making the resource available in its present form, such as a publishing house, a university department, or a corporate entity.</description> <group order="one" minOccurs="1" maxOccurs="*"> <element type="PersonReference" /> <element type="FreeText" /> </group> </ElementType> <ElementType name="contributor" model="open" content="eltOnly" > <description>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).</description> <group order="one" minOccurs="1" maxOccurs="*"> <element type="PersonReference" /> <element type="FreeText" /> </group> </ElementType> <ElementType name="type" model="open" content="eltOnly" > <description>classification of this schema, not from the standpoint of its subject matter, but rather its characteristics. Specifically, if the described schema conforms to certain specifications, the URI of those specifications should appear here.</description> <group order="one" minOccurs="1" maxOccurs="*"> <element type="ResourceReference" /> <element type="FreeText" /> </group> </ElementType> <ElementType name="format" model="open" content="eltOnly" > <description>Media or format (e.g. MIME type) of the resource.</description> <group order="one" minOccurs="1" maxOccurs="*"> <element type="ResourceReference" /> <element type="FreeText" /> </group> </ElementType> <ElementType name="source" model="open" content="eltOnly" > <description>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.</description> <group order="one" minOccurs="1" maxOccurs="*"> <element type="ResourceReference" /> <element type="FreeText" /> </group> </ElementType> <ElementType name="language" model="closed" content="textOnly" > <description>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.</description> </ElementType> <ElementType name="rights" model="open" content="eltOnly" > <description>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.</description> <group order="one" minOccurs="1" maxOccurs="*"> <element type="ResourceReference" /> <element type="FreeText" /> </group> </ElementType> <ElementType name="catalogInformation" model="open" content="eltOnly" > <description> 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. </description> <group order="seq"> <element type="identifier" minOccurs="0" maxOccurs="1" /> <element type="title" minOccurs="0" maxOccurs="*" /> <element type="creator" minOccurs="1" maxOccurs="*" /> <element type="subject" minOccurs="1" maxOccurs="*" /> <element type="description" minOccurs="0" maxOccurs="*" /> <element type="publisher" minOccurs="0" maxOccurs="*" /> <element type="contributor" minOccurs="0" maxOccurs="*" /> <element type="type" minOccurs="1" maxOccurs="*" /> <element type="format" minOccurs="0" maxOccurs="*" /> <element type="source" minOccurs="0" maxOccurs="*" /> <element type="language" minOccurs="0" maxOccurs="*" /> <element type="rights" minOccurs="0" maxOccurs="*" /> </group> </ElementType> </Schema></pre> <p><strong>如何编目架构</strong></p> <p>对其使用方式至关重要是首先了解几个基于URI的参考的角色，例如人员指导，主观引用和resourcrefere。这些在Dublin Core™中的内容模型非常灵活的元素中。例如，<em>创造者</em>元素可能有自由文本，或者可以通过一些众所周知的识别系统对特定公司或个人提供参考。如果人或公司的名称是自由文本，这意味着它不会来自受控标识符系统，它将在其中<em>FreeText.</em>元素。受控标识符与诸如<em>人格</em>。</p> <p>受控标识符的示例是由DUN和BRADSTET公司定义的D-U-N-S号。在BizTalk目录信息中，所有受控标识符都使用通用资源标识符系统。例如，假设Dun和Bradstreet以“URN：www-dnb-com：dunsno”开头的URI，他们发出的每个号码。一种<em>创造者</em>元素可能看起来像</p> <pre><creator> <personreference> urn：www-dnb-com：dunsno＃123456789012345 </ supantreference> </ creator></pre> <p>同样，受试者分类是合理的，这些分类将由许多当局定义。这些中的每一个都应该具有相应的URI命名空间，类似地使用</p> <pre><主题> <受试者> URN：分类 - BizTalk-Org：www.census.gov/epcd/naics/1997#3118 </ projectimerref> </主题></pre> <p>主题分类还允许来自不受控制的词汇表的关键字，因此可能会看到以下内容：</p> <pre><主题> <受试者> URN：分类 - BizTalk-Org：caxonomy.census.gov/epcd/naics/1997#3118 </ projectimeRef> <kingsorment> ortilla制造</ kexigry> </主题></pre> <p>类型分类标识符合XML数据和BizTalk规范的架构：</p> <pre><type> <resourcree gerutiface> urn：schemas-microsoft-com：xml-data </ resourcreference> </ type> <type> <resourcreference> urn：schemas-biztalk-org / biztalk-0.8.xml </ Resourcereference> </类型></pre> <p>根据此处描述的元素编目的玉米饼工厂的简单架构，可能如下所示：</p> <pre><schema xmlns ='urn：schemas-microsoft-com：xml-data'xmlns：dt ='urn：schemas-microsoft-com：datatypes'> <description> <cataloginformation xmlns ='urn：schemas-biztalk-org / biztalk/ catalog'> <title>关于玉米饼工厂的消息的模式。</ title> <creator> <freetext> Andrew Layman </ FreeText> <PersonReference> Mailto：<a href="//www.voudr.com/www/cdn-cgi/l/email-protection" class="__cf_email__" data-cfemail="4e2f202a3c2b39220e23272d3c213d21283a602d2123">[电子邮件受保护]</a></ personreference> </ creator> <主题> <主观指令> urn：caurononomy-biztalk-org：cauronomy.census.gov/epcd/naics/1997#3118 </ progceferefers> <关键字>玉米饼制造</关键字> </主题> <键入> <resourcreference> URN：Schemas-Microsoft-Com：XML-Data </ Resourcreference> </类型> <类型> <Resourcreference> URN：Schemas-BizTalk-Org / BizTalk-0.8.xml </ Resourcreference></类型> </ cataloginformation> </ description> </ schema></pre> <p>我们不指望大多数此类目录条目将由手工制作。更有可能 - 更可靠 - 他们将由使用工具的人创建。For example, we picture a web page that allows one to categorize a schema by filling in fields for creator, subject, etc. For each, the user can enter free-text keywords, but can also pick URIs from lists (e.g selecting "NAICS" as a SubjectReference taxonomy and then picking a specific classification from the supplied list.) Similarly, we expect that searching will be mediated by tools that are designed for this task.</p> <p><strong>分类学和其他标识符系统</strong></p> <p>BizTalk鼓励根据标准机构和私营公司创建的分类方式进行分类模式。这些分类学会已被纳入URI方案，这意味着分类物有一个已建立的URI，BizTalk将使用这些。存在分类管理但尚未纳入URI方案，BizTalk将提供一般形式的URI前缀“URN：CaCononomy-BizTalk-Org：”。URI的剩余部分将确定特定的分类学和特定标识符。</p> <p>例如，美国人口普查局为北美工业分类系统（NAICS）提供了一系列识别业务类别的数字，但人口普查局目前没有为这些数字定义URI方案。在BizTalk中，这些可以以“URN：分类 - BizTalk-Org：www.census.gov/epcd/naics/1997#118”的形式引用。</p> <p>同样，有几个用于识别人员和公司的系统。BizTalk鼓励通过系统权限提供的URIS使用这些系统，或者，当没有BizTalk提供的URI时，尚未存在此类URI时。</p> <p>BizTalk将发布批准的分类和标识符系统的初始列表，并将在时间随时间扩展列表。</p> <hr> <p><a id="dces" name="dces"></a><a href="http://purl.org/dc/elements/1.1/">http://purl.org/dc/elements/1.1/</a>。另见提议的1.1定义<a href="http://www.dstc.edu.au/RDU/DCAC/version11.html">http://www.dstc.edu.au/rdu/dcac/version11.html.</a>。</p> <p><a id="rfc" name="rfc"></a>RFC2396.<br>IETF（Internet Engineering Task Force）RFC 2396：统一资源标识符（URI）：通用语法，EDS。T. Berners-Lee，R. Fielding，L. Masinter。1998年8月</p> <p><a id="census" name="census"></a>看<a href="http://www.census.gov/epcd/www/naics.html">http://www.census.gov/epcd/www/naics.html.</a>。</p> </div> </div> <div class="row"> <div class="col"> <div id="footer"> <p>除非另有说明，否则DCMI文件在a下进行许可<a rel="license" href="http://creativecommons.org/licenses/by/3.0/">Creative Commons归因于3.0未受平许可</a>。请看<a href="//www.voudr.com/www/about/copyright/">DCMI文件通知</a>有关进一步的说明。</p> <p><a href="//www.voudr.com/www/about/copyright/">版权</a>©1995-2021.<acronym title="Dublin Core Metadata Initiative"><a href="//www.voudr.com/www/">DCMI.</a></acronym>。版权所有。DCMI.<a href="//www.voudr.com/www/about/copyright/">责任</a>那<a href="//www.voudr.com/www/about/copyright/">商标/服务标记</a>那<a href="//www.voudr.com/www/about/copyright/">文件使用规则适用。与本网站的互动符合我们的</a><a href="//www.voudr.com/www/about/privacy/">隐私</a>陈述。</p> <p>都柏林核心元数据倡议（DCMI）是美国国内收入守则下的ASIS＆T-A美国501（C）（3）非营利组织的项目。通过ASIS＆T对DCMI的贡献是在美国的全部范围内扣除税收。</p> <p>随着Hugo v部署0.82.1在SAT，2011年7月31日19:11:27 UTC</p> </div> </div> </div> </div> </body> </html>