| 1 | 1) subject-nodes |
|---|
| 2 | Is mapped to a topic with a PSI and a Topic ID equal to the subject-uri |
|---|
| 3 | 2) blank nodes |
|---|
| 4 | are mapped to a topic without a PSI, a uuid will be generated as a Topic ID |
|---|
| 5 | 3) relationships between subject-nodes and literals |
|---|
| 6 | Are mapped to occurrences of the type <preffix:arc> with the datatype of the |
|---|
| 7 | corresponding RDF datatype. When there is no one given, the datatype is set to xml:string. |
|---|
| 8 | 4) relationships between subject-nodes and object-nodes |
|---|
| 9 | Are mapped to assocations of the type <preffix:arc> with the roles |
|---|
| 10 | *of the type http://isidorus/rdf2tm_mapping/subject with the player <subject-node> |
|---|
| 11 | *of the type http://isidorus/rdf2tm_mapping/object with the player <object-node> |
|---|
| 12 | 5) rdf:_n properties |
|---|
| 13 | Are mapped to an assocation of the type http://isidorus/rdf2tm_mapping/listing with the roles |
|---|
| 14 | *of the type http://isidorus/rdf2tm_mapping/subject with the player <subject-node> |
|---|
| 15 | *roles of the type http://www.w3.org/1999/02/22-rdf-syntax-ns#_n with the player <_n:object-node> |
|---|
| 16 | If the <_n:object-node> is a literal node, there has to be produced a topic (T) with the Topic ID |
|---|
| 17 | <UUID> and no PSI corresponding. |
|---|
| 18 | The topic (T) contains an occurrence with the value of the property-element and the type |
|---|
| 19 | http://isidorus/rdf2tm_mapping/literal_occurrence (datatype corresponding to the datatype in RDF). |
|---|
| 20 | Topic T is an instance of http://isidorus/rdf2tm_mapping/literal_topic. |
|---|
| 21 | 6) rdf:li |
|---|
| 22 | All rdf:li elements are transformed to rdf:_n elements starting by rdf_1 and incremented by |
|---|
| 23 | everey iteration. If the content of a node is mixed (the node contains rdf:li and rdf:_n elements) |
|---|
| 24 | there is no specail processing for the transformation of rdf:li to rdf:_n. so it is possible that |
|---|
| 25 | there will be exist two or more items with the name rdf:_1. |
|---|
| 26 | 7) rdf:parseType="Collection" |
|---|
| 27 | This nodes are mapped to topics corresponding to the given resouce-nodes and an association |
|---|
| 28 | of the type <preffix:arc> with the roles: |
|---|
| 29 | *of the type http://isidorus/rdf2tm_mapping/subject with the player <subject-node> |
|---|
| 30 | *roles of the type http://isidorus/rdf2tm_mapping/collectionItem with the player <object-node> |
|---|
| 31 | 8) rdf:type |
|---|
| 32 | Is mapped to an instanceOf association |
|---|
| 33 | 9) rdfs:subClassOf |
|---|
| 34 | Is mapped to a supertype-subtype association |
|---|
| 35 | 10) rdf:ID/reification |
|---|
| 36 | *rdf:ID on subject-nodes: the corresponding subject-nodes are "merged" and the arc |
|---|
| 37 | of the reifying node (B) is pointed to the object-node (C) directly |
|---|
| 38 | from the original node (A) |
|---|
| 39 | *rdf:ID on properties: Generates all topics from the node-IDs, arc-names or creates uuids. |
|---|
| 40 | Additionally there is created an association of the |
|---|
| 41 | type http://isidorus/rdf2tm_mapping/reification with the roles: |
|---|
| 42 | * of the type rdf:subject and the player <subject-node> |
|---|
| 43 | * of the type http://isidorus/rdf2tm_mapping/reifier with theplayer <reifier-node> |
|---|
| 44 | if there is no reifier node theri will be generated a topic with |
|---|
| 45 | the Topic ID <uuid> |
|---|
| 46 | * of the type rdf:predicate and the player <predicate-topic> |
|---|
