A datast containing instances for the media types in the IANA registry.
Media types and the IANA registry are standardized in RFC 6838.
How to use this dataset
This dataset provides instances for media types. You can use the following existing properties in order to relate these media types to your resources:
dct:format
- This is the standard way to denote a media type according to the Dublin Core Terms vocabulary.
sdo:encodingFormat
- This is the standard way to denote a media type according to the Schema.org vocabulary.
Explanation of the data model
The following diagram gives an overview of the data mode for this dataset:
This dataset uses the following existing class and property from Dublin Core Terms:
dct:MediaType
- Every media type is an instance of this class.
dct:identifier
- The identifier for each media type and top-level type.
This dataset introduces the following new class and properties:
tmt:ToplevelType
- Every top-level type is an instance of this class.
tmt:altExtension
- Specifies a file name extension that is sometimes used on files with content in this particular media type. This is not the preferred file name extension to use of files with content in this particular media type (see
tmt:prefExtension
). tmt:prefExtension
- Specifies the preferred file name extension for a particular media type.
tmt:toplevelType
- Relates a media type to its corresponding top-level type.
tmt:subtype
- Relates a media type to its subtype name.
This vocabulary allows versions to be identified for arbitrary resources.
Explanation of this vocabulary
This vocabulary innovates over current ontologies, which only allow OWL ontologies to be versioned (OWL), and/or only allow versions to be expressed in simple numbers or strings (Schema.org).
This vocabulary introduces the following two version types:
Version instances are related to the resources with the following property:
This vocabulary allows prefix declarations to be represented for arbitrary resources.
Explanation of this vocabulary
This vocabulary innovates over current vocabularies, which only allow one single prefix declaration to be defined (VANN), and/or only allow prefix declarations to be asserted for ontologies (SHACL, VANN).
At the same time, this vocabulary does reuse those aspects of SHACL and VANN that are generic enough to be reused here. From SHACL the following class and properties are reused:
From VANN the following properties are reused:
The following property is newly introduced by this vocabulary:
The following diagram shows how these classes and properties interact:
Use cases for this vocabulary
Examples of resource types for which prefix declarations are commonly asserted include:
- Datasets
- Prefix declarations to abbreviate IRIs that appear in the dataset.
- Queries
- Prefix declarations used in (collections of) SPARQL queries.
- Rules
- Prefix declarations that are used in (collections of) SHACL rules.
- Services
- Prefix declarations that can be used to query service endpoints.
Relation to sh:declare
At Triply we our policy is to not publish direct assertions about nodes published by other organizations, but the intention of the property introduced by this vocabulary is to act as a superproperty of sh:declare
:
prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>
prefix sh: <http://www.w3.org/ns/shacl#>
prefix tp: <https://triplydb.com/Triply/tp/def/>
sh:declare rdfs:subPropertyOf tp:prefixDeclaration.