made by pyLODE

RealEstateCore Metadata Module

Metadata

IRI
https://w3id.org/rec/metadata/
Publisher(s)
RealEstateCore Consortium
Contributors(s)
Erik Wallin
Karl Hammar
Modified
2019-11-07
Version Information
3.1.1
Ontology Source
RDF (xml)

Description

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.

Table of Contents

  1. Annotation Properties
  2. Namespaces
  3. Legend

Classes

Annotation Properties

has licenseap

IRI http://creativecommons.org/ns#license

Contributorap

IRI http://purl.org/dc/elements/1.1/contributor
Description 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.

Coverageap

IRI http://purl.org/dc/elements/1.1/coverage
Description 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.

Creatorap

IRI http://purl.org/dc/elements/1.1/creator
Description 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.

Dateap

IRI http://purl.org/dc/elements/1.1/date
Description 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.

Descriptionap

IRI http://purl.org/dc/elements/1.1/description
Description 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.

Formatap

IRI http://purl.org/dc/elements/1.1/format
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.

Identifierap

IRI http://purl.org/dc/elements/1.1/identifier
Description Recommended best practice is to identify the resource by means of a string conforming to a formal identification system.

Languageap

IRI http://purl.org/dc/elements/1.1/language
Description Recommended best practice is to use a controlled vocabulary such as RFC 4646.

Publisherap

IRI http://purl.org/dc/elements/1.1/publisher
Description 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.

Relationap

IRI http://purl.org/dc/elements/1.1/relation
Description Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system.

Rightsap

IRI http://purl.org/dc/elements/1.1/rights
Description Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.

Sourceap

IRI http://purl.org/dc/elements/1.1/source
Description 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.

Subjectap

IRI http://purl.org/dc/elements/1.1/subject
Description 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.

Titleap

IRI http://purl.org/dc/elements/1.1/title
Description Typically, a Title will be a name by which the resource is formally known.

Typeap

IRI http://purl.org/dc/elements/1.1/type
Description 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.

Dateap

IRI http://purl.org/dc/terms/date
Description 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].
Super-properties dc:dateap
Range(s) rdfs:Literalc

Date Modifiedap

IRI http://purl.org/dc/terms/modified
Description Date on which the resource was changed.
Super-properties dcterms:dateap
Range(s) rdfs:Literalc

Preferred Namespace Prefixap

IRI http://purl.org/vocab/vann/preferredNamespacePrefix
Description The preferred namespace prefix to use when using terms from this vocabulary in an XML document.

Preferred Namespace Uriap

IRI http://purl.org/vocab/vann/preferredNamespaceUri
Description The preferred namespace URI to use when using terms from this vocabulary in an XML document.

coversRequirementsap

IRI http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl#coversRequirements
Description This annotation property is used for exemplifying possible requirements the content pattern provides a solution for. Requirements are expressed as natural language competency questions.

definitionap

IRI http://www.w3.org/2004/02/skos/core#definition

endpointap

IRI https://karlhammar.com/owl2oas/o2o.owl#endpoint
Description This annotation, when applied to an OWL class that is included for processing in OWL2OAS, governs the endpoint name that is generated for the class.

includedap

IRI https://karlhammar.com/owl2oas/o2o.owl#included
Description Usage of this annotation, in conjunction with the ClassInclusionPolicy and PropertyInclusionPolicy run time options, coverns whether OWL entities are included or ignored by the owl2oas code generator.
Range(s) xsd:booleanc

Namespaces

default (:)
https://w3id.org/rec/metadata/3.1.1/
:
https://w3id.org/rec/metadata/
cc
http://creativecommons.org/ns#
cpannotationschema
http://www.ontologydesignpatterns.org/schemas/cpannotationschema.owl#
dc
http://purl.org/dc/elements/1.1/
dcam
http://purl.org/dc/dcam/
dcmitype
http://purl.org/dc/dcmitype/
dcterms
http://purl.org/dc/terms/
o2o
https://karlhammar.com/owl2oas/o2o.owl#
owl
http://www.w3.org/2002/07/owl#
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
skos
http://www.w3.org/2004/02/skos/core#
vann
http://purl.org/vocab/vann/
xml
http://www.w3.org/XML/1998/namespace
xsd
http://www.w3.org/2001/XMLSchema#

Legend

cClasses
opObject Properties
fpFunctional Properties
dpData Properties
dpAnnotation Properties
pProperties
niNamed Individuals