Which namespaces do we need and which namespaces do we want to use?
From Deliverable 3.4:
Contrary to the original plans to link vocabularies as simple SKOS vocabularies, it was decided to implement categorizations of group types, languages, name types, event roles, gender, professions, and nationalities as subclasses in the IDM-RDF, e.g. gender categorizations as subclasses of idm:Gender9.
This has as a consequence, that most properties which would be crm:P2_has_type (http://www.cidoc-crm.org/cidoc-crm/P2_has_type) in a common CIDOC CRM Model, are a rdf:type property now. This decision enables reasoning and consistency checking for numerous correlations in the InTaVia data set. A set of roles in an event can e.g. be restricted for a specific type of event or a group of actors with shared attributes (e.g. persons with a certain occupation).
To store these subclasses, it was decided to apply a modularized OWL approach. Besides the IDM-RDF core (see: Appendix 1), OWL files are created with separate namespaces10 for event types, group types, languages, group membership types, name types, (individual and group) relation types, entity roles, gender, occupations, organization types, materials, technique, and nationalities. The division of the OWL-files and namespaces makes it possible to update the files independently from IDM-RDF core when subclasses are added or removed in data ingestion processes.
The supplementary OWL-files will additionally be converted to SKOS vocabularies to make the vocabularies reusable, published on Zenodo and Vocabs (https://vocabs.acdh.oeaw.ac.at) under the namespace http://www.intavia.eu/vocab/. (Section 2.3.)
Which namespaces do we need and which namespaces do we want to use?
From Deliverable 3.4: Contrary to the original plans to link vocabularies as simple SKOS vocabularies, it was decided to implement categorizations of group types, languages, name types, event roles, gender, professions, and nationalities as subclasses in the IDM-RDF, e.g. gender categorizations as subclasses of idm:Gender9.
This has as a consequence, that most properties which would be crm:P2_has_type (http://www.cidoc-crm.org/cidoc-crm/P2_has_type) in a common CIDOC CRM Model, are a rdf:type property now. This decision enables reasoning and consistency checking for numerous correlations in the InTaVia data set. A set of roles in an event can e.g. be restricted for a specific type of event or a group of actors with shared attributes (e.g. persons with a certain occupation).
To store these subclasses, it was decided to apply a modularized OWL approach. Besides the IDM-RDF core (see: Appendix 1), OWL files are created with separate namespaces10 for event types, group types, languages, group membership types, name types, (individual and group) relation types, entity roles, gender, occupations, organization types, materials, technique, and nationalities. The division of the OWL-files and namespaces makes it possible to update the files independently from IDM-RDF core when subclasses are added or removed in data ingestion processes.
The supplementary OWL-files will additionally be converted to SKOS vocabularies to make the vocabularies reusable, published on Zenodo and Vocabs (https://vocabs.acdh.oeaw.ac.at) under the namespace http://www.intavia.eu/vocab/. (Section 2.3.)