Skip to content

Latest commit

 

History

History
104 lines (82 loc) · 4.25 KB

URI-patterns.md

File metadata and controls

104 lines (82 loc) · 4.25 KB
Raw

URI patterns for EOKG data

This is the documentation of the URI design pattern used by the European Olfactory Knowledge Graph (EOKG). The following SPARQL query provides the number of instances of each type (results):

SELECT ?class (COUNT(DISTINCT ?s) as ?count) (SAMPLE(?s) as ?ex)
WHERE {
    GRAPH ?g {
       ?s a ?class
    }
    
    VALUES(?g ) {(<http://data.odeuropa.eu/text-annotation>) (<http://data.odeuropa.eu/image-annotation>)}
}
GROUP BY ?class
ORDER BY DESC(?count)

Main entities

Pattern:

http://data.odeuropa.eu/<group>/<uuid>
# e.g. http://data.odeuropa.eu/Smell/055b8a36-1515-502c-8974-5a1e2850f498

The <group> is taken from this table

Class Group
crm:E70_Thing thing
od:L11_Smell smell
od:L12_Smell_Emission emission
od:L13_Olfactory_Experience experience
od:L7_Gesture gesture
crm:E22_Human-Made_Object object
crmsci:S10_Material_Substantial object
crm:E39_Actor actor
crm:E21_Person actor
crm:E53_Place place
time:TemporalEntity time
crm:E33_Linguistic_Object source
crm:E36_Visual_Item source
crm:E24_Physical_Human-Made_Thing source-object
crm:E57_Material material
oa:Annotation annotation
prov:Activity provenance

Secondary entities

This group includes entities that cover specific information about the main entities. The URI is realized appending a suffix to the parent main entity.

The used pattern is the following:

<uri of the main entity>/<suffix>/<sub identifier>
# i.e. <http://data.odeuropa.eu/OlfactoryExperience/ffd3be49-13ae-59ce-bc76-366070a17756/assignment/1>

The <suffix> is taken from this table:

Class Group Suffix
od:L7_Gesture experience /gesture/{progressive int}
crm:E13_Attribute_Assignment experience /assignment/{progressive int
ma:MediaFragment source #xywh={coordinates}
E33_Linguistic_Object (text snippet) source /fragment/{uuid generated from text content}
E54_Dimension source /E54_Dimension/{progressive int}

UUID and seed generation

The UUID is computed deterministically starting from a seed string. A real UUID taken from an example above looks like this: ffd3be49-13ae-59ce-bc76-366070a17756.

The seed is usually generated based on:

  • class (e.g. 'L11_Smell', ...)
  • source (e.g. 'image-annotation', 'text-annotation', ...)
  • the id of the current document id (filename ID)
  • the id of the current annotation (in the input file or generated as a progressive integer)

There are some exceptions to this rule, in order to allow automatic cross-source alignment:

  • For Visual Item, only class and filename are used
  • For Linguistic Object, only class and the document id are used.
  • For Places and Actors, only the class and label (e.g. 'Rome') are used.
  • For Temporal Entity, we use the class and the EDTF representation of the time (when successfully parsed, otherwise the label).
  • For prov:Activity, we use the source and (if available) the annotator id
  • For Annotation, we use the URI of the target Media Fragment

Examples:

  • For most classes: [class] + [source] + [document_id] + [annotation_internal_id]
  • For Place (E53) and Actors (E39): [class]+[label]
  • For Visual Item (E36): [class]+[filename]
  • For Linguistic Object (E33): [class]+[document_id]
  • For Temporal Entity: [class] + [edtf]
  • For prov:Activity : [source] + [annotator_name]
  • For Annotation : [media_fragment_uri]