6
results
-
This is the encoding approved by CRM-SIG in the meeting 21/11/2012 as the official current version for the CIDOC CRM namespace. Note that this is NOT a definition of the CIDOC CRM, but an encoding derived from the authoritative release of the CIDOC CRM v5.0.4 on http://www.cidoc-crm.org/official_release_cidoc.html @en
-
The DBpedia ontology provides the classes and properties used in the DBpedia data set. @en
-
DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web @en
-
The euBusinessGraph (`ebg:`) ontology represents companies, type/status/economic classification, addresses, identifiers, company officers (e.g., directors and CEOs), and dataset offerings. It uses `schema:domainIncludes/rangeIncludes` (which are polymorphic) to describe which properties are applicable to a class, rather than `rdfs:domain/range` (which are monomorphic) to prescribe what classes must be applied to each node using a property. We find that this enables more flexible reuse and combination of different ontologies. We reuse the following ontologies and nomenclatures, and extend them where appropriate with classes and properties: - W3C Org, W3C RegOrg (basic company data), - W3C Time (officer membership), - W3C Locn (addresses), - schema.org (domain/rangeIncludes and various properties) - DBpedia ontology (jurisdiction) - NGEO and Spatial (NUTS administrative divisions) - ADMS (identifiers), - FOAF, SIOC (blog posts), - RAMON, SKOS (NACE economic classifications and various nomenclatures), - VOID (dataset descriptions). This is only a reference. See more detail in the [EBG Semantic Model](https://docs.google.com/document/d/1dhMOTlIOC6dOK_jksJRX0CB-GIRoiYY6fWtCnZArUhU/edit) google document, which includes an informative description of classes and properties, gives examples and data provider rules, and provides more schema and instance diagrams. @en
-
The notion of territory plays a major role in human and social sciences. In an historical context, most approaches are irrelevant as they rely on geometric data, which is not available. In order to represent historical territories,we conceived the HHT ontology (Hierarchical Historical Territory) to represent hierarchical historical territorial divisions, without having to know their geometry. This approach relies on a notion of building blocks to replace polygonal geometry @en
-
LinkedGeoData ontology has been derived from concepts defined by Open Street Map @en
1