都柏林核心术语和都柏林核心元素词汇之间有什么区别 [英] What is the difference between dublin core terms and dublin core elements vocabularies

问题描述

有2个Dublin Core词汇DC术语和DC元素.

There's 2 Dublin Core vocabularies DC terms and DC elements.

它们定义几乎相同的类和属性.

They define almost the same classes and properties.

那么它们之间的主要区别是什么，何时使用它们.

So what is the key differences between them, and when to use each one.

推荐答案

元素集 :

• 命名空间:http://purl.org/dc/elements/1.1/
• 预定义的前缀:dc11
• 它定义了 15个条款.
• 这些术语也以ISO 15836，ANSI/NISO Z39.85和RFC 5013标准发布.

• Namespace: http://purl.org/dc/elements/1.1/
• Predefined prefix: dc11
• It defines 15 terms.
• These terms are also published as the standards ISO 15836, ANSI/NISO Z39.85, and RFC 5013.

条款 :

• 命名空间:http://purl.org/dc/terms/
• 预定义的前缀:dc，dcterms
• 它定义了所有条款，

• Namespace: http://purl.org/dc/terms/
• Predefined prefixes: dc, dcterms
• It defines all terms, including the 15 terms from the Element Set.

术语不仅包含 Element Set 中的15个术语，而且还在其自己的命名空间下定义了与这15个术语同名的术语.因此，例如，有两个名为coverage的术语:

Terms does not only include the 15 terms from Element Set, it defines terms with the same names as these 15 terms under its own namespace in addition. So, for example, there are two terms named coverage:

• http://purl.org/dc/elements/1.1/coverage
• http://purl.org/dc/terms/coverage

• http://purl.org/dc/elements/1.1/coverage
• http://purl.org/dc/terms/coverage

它们都应具有相同的描述.差异:

They should all have the same description. Differences:

• 元素集命名空间中的15个属性没有范围/ Terms 命名空间中的15个属性中有很多具有范围(rdfs:range)
• 术语"" 中的15个属性是 Element Set (rdfs:subPropertyOf)中的15个同名术语的子属性.

• The 15 properties from the Element Set namespace don’t have a range / many of the 15 properties from the Terms namespace do have a range (rdfs:range).
• The 15 properties from the Terms namespace are sub-properties of the 15 same-named terms from the Element Set (rdfs:subPropertyOf).

除非您有理由使用 Element Set 中的术语(例如，由于必须遵守所提到的标准)，否则请使用 Terms 命名空间:

Unless you have a reason for using the terms from the Element Set (e.g., because of having to conform to the mentioned standards), go with the terms from the Terms namespace:

• 有能力的用户代理可以识别它们是 Element Set 中相应子属性的子属性(即，也将其含义应用于您的数据).
• 有能力的用户代理可以推断出指定范围内的内容.
• 在RDF中定义的前缀要少一些(如果您使用 Terms 名称空间中的更多术语).

• Capable user agents can recognize that they are subproperties of the corresponding ones from Element Set (i.e., apply their meaning to your data, too).
• Capable user agents can infer things from the specified range.
• One less prefix to define in your RDF (if you use more terms from the Terms namespace).

这也是 元素集简介建议:

This is also what the Element Set introduction recommends:

实施者可以根据应用要求自由选择在其旧版dc:变体(例如http://purl.org/dc/elements/1.1/creator)或dcterms:变体(例如http://purl.org/dc/terms/creator)中使用这15个属性. DCMI名称空间的RDF架构描述了dcterms:creator与dc:creator的子属性关系，供语义Web感知应用程序使用.但是，随着时间的流逝，鼓励实现者使用语义上更精确的dcterms:属性，因为它们更充分地遵循了新兴的关于机器可处理元数据的最佳实践的概念.

Implementers may freely choose to use these fifteen properties either in their legacy dc: variant (e.g., http://purl.org/dc/elements/1.1/creator) or in the dcterms: variant (e.g., http://purl.org/dc/terms/creator) depending on application requirements. The RDF schemas of the DCMI namespaces describe the subproperty relation of dcterms:creator to dc:creator for use by Semantic Web-aware applications. Over time, however, implementers are encouraged to use the semantically more precise dcterms: properties, as they more fully follow emerging notions of best practice for machine-processable metadata.

这篇关于都柏林核心术语和都柏林核心元素词汇之间有什么区别的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！