Jump to content

The Dublin Core ontology


H123
 Share

General

  • Ontologically Committed

    Generic

Vertical

  • Parent-arity Type Instance

    Unconstrained
  • Boundedness Type Instance - Downward

    Bounded
  • Boundedness Type Instance - Fixed Finite Levels

    Fixed
  • Boundedness Type Instance - Number of Fixed Levels

    2
  • Stratification Type Instance

    Stratified
  • Relation Class-ness Type Instance

    Second-class
  • Relation Class-ness Super Sub Type

    Second-class

Horizontal

  • No data to show

Universal

  • Indexicals: Here And Now

    Not-supported

F.9 DC – Dublin Core

F.9.1 Overview

The Dublin Core schema is a small set of vocabulary terms that can be used to describe digital resources (video, images, web pages, etc.), as well as physical resources such as books or CDs, and objects like artworks.

From https://en.wikipedia.org/wiki/Dublin_Core

See also: http://dublincore.org/

F.9.2 Top-level

image.jpeg

Figure 1 – the DCMI resource model 

image.jpeg

Figure 2 – the DCMI description set model 

From https://www.dublincore.org/specifications/dublin-core/abstract-model/

F.9.3. Key Characteristics

Dublin Core is a generic TLO with a focus on digital resources.

F.9.4 Relevant extracts

From https://www.dublincore.org/specifications/ dublin-core/abstract-model/


Extract 1 – The DCMI Vocabulary Model 

2.3 The DCMI Vocabulary Model 

The abstract model of the vocabularies used in DC metadata descriptions is as follows:

  • A vocabulary is a set of one or more terms. Each term is a member of one or more vocabularies.
  • A term is a property (element), class, vocabulary encoding scheme,  or syntax encoding scheme. 
  • Each property may be related to one or more classes by a has domain relationship. Where it is stated that a property has such a relationship with a class and the property is part of a property/value pair, it follows that the described resource is an instance of that class. 
  • Each property may be related to one or more classes by a has range relationship. Where it is stated that a property has such a relationship with a class and the property is part of a property/value pair, it follows that the value is an instance of that class. 
  • Each resource may be an instance of one or more classes. 
  • Each resource may be a member  of one or more vocabulary encoding schemes. 

Each class may be related to one or more other classes by a sub-class of relationship (where the two classes are  defined such that all resources that are instances of the sub-class are also instances of the related class). 

Each property may be related to one or more other  properties by a sub-property of relationship. Where it is stated that such a relationship exists, the two properties are defined such that whenever the sub-property is part of a property/value pair describing a resource, it follows that the resource is also described using a second property/value pair made up of the property and the value. 

Each syntax encoding scheme is a class (of literals).

Note that the word “vocabulary” is used here to refer specifically to a set of terms, a set in which the members are properties (elements), classes, vocabulary encoding schemes, and/or syntax encoding schemes.

image.jpeg

 

 

 

Figure 3 – the DCMI vocabulary model 

Return to top

Return to Appendix : Candidate source top-level ontologies – longlist

Return to Contents

Continue to Appendix G: Prior ontological commitment literature

 Share


User Feedback

Recommended Comments

There are no comments to display.


Top
×
×
  • Create New...