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.
Two forms of Dublin Core exist: Simple Dublin Core and Qualified Dublin Core. Simple Dublin Core expresses elements as attribute-value pairs using just the 15 metadata elements from the Dublin Core Metadata Element Set.
Dublin Core is comprised of 15 “core” metadata elements; whereas the "qualified" Dublin Core set includes additional metadata elements to provide for greater specificity and granularity.
The Dublin Core, also known as the Dublin Core Metadata Element Set (DCMES), is a set of fifteen "core" elements (properties) for describing resources. This fifteen-element Dublin Core has been formally standardized as ISO 15836, ANSI/NISO Z39. 85, and IETF RFC 5013.
Element Set:
http://purl.org/dc/elements/1.1/
dc11
Terms:
http://purl.org/dc/terms/
dc
, dcterms
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
They should all have the same description. Differences:
rdfs:range
).rdfs:subPropertyOf
).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:
This is also what the Element Set introduction recommends:
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.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With