Erik Wallin
Karl Hammar
This is a translation of various metadata schemas into OWL annotation properties. The metadata schemas themselves have not been developed by the RealEstateCore Consortium; rather, we simply collate them into one OWL file for stand-alone reuse within the REC ontology suite.
The copyright on the constituent parts (classes, properties, named individuals) of the REC Metadata Module are held by their original authors (see their respective namespaces and the several rdfs:isDefinedBy and dc:source declarations on the Metadata Module ontology as a whole). These parts may have different licenses. The composition of these constituent parts into one file, as published by the RealEstateCore consortium, is provided under MIT license.
RealEstateCore Consortium
RealEstateCore Metadata Module
2019-11-07
metadata
https://w3id.org/rec/metadata/3.1/
3.1
has license
Examples of a Contributor include a person, an organization, or a service. Typically, the name of a Contributor should be used to indicate the entity.
Contributor
Spatial topic and spatial applicability may be a named place or a location specified by its geographic coordinates. Temporal topic may be a named period, date, or date range. A jurisdiction may be a named administrative entity or a geographic place to which the resource applies. Recommended best practice is to use a controlled vocabulary such as the Thesaurus of Geographic Names. Where appropriate, named places or time periods can be used in preference to numeric identifiers such as sets of coordinates or date ranges.
Coverage
Examples of a Creator include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity.
Creator
Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601.
Date
Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
Description
Examples of dimensions include size and duration. Recommended best practice is to use a controlled vocabulary such as the list of Internet Media Types.
Format
Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.
Identifier
Recommended best practice is to use a controlled vocabulary such as RFC 4646.
Language
Examples of a Publisher include a person, an organization, or a service. Typically, the name of a Publisher should be used to indicate the entity.
Publisher
Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
Relation
Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.
Rights
The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.
Source
Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. To describe the spatial or temporal topic of the resource, use the Coverage element.
Subject
Typically, a Title will be a name by which the resource is formally known.
Title
Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary. To describe the file format, physical medium, or dimensions of the resource, use the Format element.
Type
Date may be used to express temporal information at any level of granularity. Recommended best practice is to use an encoding scheme, such as the W3CDTF profile of ISO 8601 [W3CDTF].
Date
Date Modified
Date on which the resource was changed.
The preferred namespace prefix to use when using terms from this vocabulary in an XML document.
Preferred Namespace Prefix
The preferred namespace URI to use when using terms from this vocabulary in an XML document.
Preferred Namespace Uri
This annotation property is used for exemplifying possible requirements the content pattern provides a solution for. Requirements are expressed as natural language competency questions.
OWL entities that are tagged with this annotation will be ignored by the owl2oas code generator.
Ignored
OWL classes tagged with this annotation will only have accessor methods created by the OWL2OAS code generator; no POST, PUT, or DELETE operations will be created.
Read-only