本文档建立了跨域资源描述词汇表，称为都柏林核心元数据术语（以下简称DCMI元数据术语）。它包括DCMI元数据术语[1]（以下简称“术语/名称空间”）主名称空间中的所有属性和类，如2012年DCMI推荐文件“DCMI元数据术语”（DCMI-Terms和附录A）中所述。如附录B所述，这些属性和类别可以通过URI识别，以便在链接数据中使用。 请注意名称空间中定义的原始都柏林核心元数据元素集的15个术语https://purl.org/dc/elements/1.1/（以下简称“元素/1。 DCMI建议“DCMI元数据术语”和ISO 15836-1中也有记录。 本文件不包含“DCMI元数据条款”规范中的以下支持条款: a） 来自/elements/1.1/名称空间的术语（包括在ISO 15836-1中）； b） 词汇编码方案； c） 语法编码方案； d） DCMI型词汇； e） 与DCMI抽象模型相关的术语。 ISO 15836-1和本文档都包含15个所谓的核心术语，但在ISO 15836-1中，它们来自/elements/1.1/名称空间，在本文档中来自/terms/名称空间。在后者中，由于形式化的域和范围规范，这些术语的语义更窄。 本文档不限制可能的资源。 本文件未提供具体的实施指南。属性和类通常在应用程序概要文件的上下文中使用，应用程序概要文件根据本地或基于社区的需求和策略约束或指定它们的使用。 [1] 网址:https://purl.org/dc/terms/.

This document establishes a vocabulary for cross-domain resource description, known as the Dublin Core metadata terms (hereafter DCMI Metadata Terms). It includes all of the properties and classes in the main namespace of DCMI Metadata Terms[1] (hereafter "the /terms/ namespace"), as published in the DCMI Recommendation document "DCMI Metadata Terms" of 2012 (DCMI-TERMS and Annex A). As explained in Annex B, these properties and classes can be identified by URIs for use in linked data. NOTE The 15 terms of the original Dublin Core Metadata Element Set, as defined in the namespace https://purl.org/dc/elements/1.1/ (hereafter "the /elements/1.1/ namespace"), are also documented in the DCMI Recommendation "DCMI Metadata Terms" and in ISO 15836-1. This document does not contain the following supporting terms from "DCMI Metadata Terms" specification: a) terms from the /elements/1.1/ namespace (included in ISO 15836-1); b) vocabulary encoding schemes; c) syntax encoding schemes; d) DCMI Type vocabulary; e) terms related to the DCMI Abstract Model. Both ISO 15836-1 and this document include the 15 so-called core terms, but in ISO 15836-1 they are from the /elements/1.1/ namespace, and in this document from the /terms/ namespace. In the latter, the terms have narrower semantics due to formal domain and range specifications. This document does not limit what might be a resource. This document does not provide specific implementation guidelines. The properties and classes are typically used in the context of an application profile, which constrains or specifies their use in accordance with local or community-based requirements and policies. [1] Available at: https://purl.org/dc/terms/.