|
Although Web3 has an internal model based on the Topic Maps standard, the application is capable of presenting its data as RDF triples. The RDF model is simpler than the Topic Maps model and so on export some information is lost.
Topics are exported as an RDF resource with the following properties:
| • | For each topic type an rdf:Type property where the property value is the URI of the typing topic |
| • | For each arc in the topics outgoing arcs collection, a property where the property type is the RDF resource for the topic that defines the arc type and the property value is the RDF resource for the end topic of the arc. |
| • | For each binary association that the topic participates in, a property where the property value is the RDF resource for the other topic in the association and the property type is the RDF resource for the topic that defines the type of role played by the other topic in the association. |
| • | For each name or occurrence, a property where the property type is the RDF resource for the topic that defines the property type and the property value is the value of the name or occurrence. |
The export process will omit the following information:
| • | Scope on associations, names and occurrences |
| • | All associations with more than two role players |
| • | The type of any binary association exported |
| • | The role played by the topic in any binary association |
However, it should be noted that all binary associations will result in two separate RDF triples being exported - one for each topic that participates in the association.
|