3.2.3. Application ontologies

If the concepts of CIDOC CRM are not sufficient, sub-concepts can be created on the basis of these building blocks and a separate domain account created. In our example, the document or collection object is a subclass of E84 Information Carrier. Subconcepts can be created not only for the entities, but also for properties for your own application area. In the case of the Erlangen collections, these specific concepts can be recognized by the fact that the entities are marked with an "S" and a sequential number before the name. The properties initially have an "N" and are also consecutively numbered.

The modeling of the terms and relationships mentioned above is event-driven using CIDOC CRM. The data record for document ER 16197 is used again as an example:
If, for example, one wishes to model that Nezadal, W. was the collector of the document and the place where the plant was found, was Casariche, the event of the collection process is at the centre of the modelling. All other information, such as the document, the collector and the location of the find, are linked by the event Collecting:

\\gnm.de\daten und bilder\Projekte\Objekte im Netz\WissKI\Workshops_WissKI\Screenshots\Screenshot_Pfadaufbau.jpg

The input field of the document or collection object requires a semantic path that leads from the object or information carrier to be described - according to CIDOC CRM E84 Information Carrier - to the collector who is involved in the collection process of the object. Using the classes and properties of CIDOC CRM and ECRM results in the following path structure: 
The information carrier E84 Information Carrier is collected via the property N23i was related to the event S20 Collection process. This event in turn is linked via the property P14 carried out by with the entity E21 Person, which in turn is linked via P131 is identified by with E82 Actor Appellation. Finally, the entity E82 Actor Appellation is connected via the property P3 has note with the string "Nezadal, W. (43881)". The path can be read semantically like this: The object was collected at the event of the collection process. A person was involved in the event of the collection process. The person is identified by the actor name, which is characterized by the name "Nezadal, W. (43881)".          
The path for the input field of the place of manufacture can be described in the same way: The starting concept here is again the information carrier (document or collection object) that was collected during the event of the collection process. This collection process took place at a location that is identified by a location name called "Casariche".