Simple version of creating mappings to external vocabularies

[psiotwo]

Currently, creating mappings to external vocabularies is not supported in the assembly line. Some options to tackle it.

1) Do not use assembly line and make the mappings directly in TTL files on GitHub.

2) Using unmapped properties in TermIt A simple way, which would allow C2 to create external mappings themselves, would be to use TermIt unmapped properties to do this. Since mappings are typically done using rdfs:subClassOf/owl:equivalentClass and rdfs:subPropertyOf/owl:equivalentProperty, a simple way to support mappings would be to:

• allow using the above mentioned properties in the unmapped properties field.
• make sure the property value is written as an IRI (not as a literal)

3) Add support to OntoGrapher to link to external terms In the term detail, a new field with URI values for external mappings that would translate to rdfs:subClassOf.

4) Create custom tool.

[psiotwo]

@MichalMed @karelklima @bindeali Yesterday, we had a discussion with @martinnec about creating mappings out of SGoV using assembly line.

Option 1 is what we have now. Option 2 seems quite feasible and doable, yet quite unsystematic w.r.t. what the tools should do. Option 3 seems OK, but probably more difficult to do. Option 4 seems out of resources IMO.

[martinnec]

Regarding option 1 - we also need to wrote a methodology. Mapping to external vocs is a necessary step IMO. It would be strange to cover this step by refering to something which is outside the production line.

[karelklima]

This feature should probably be both in TermIt and OntoGrapher. Anywhere you're editing a SGoV term, you should be able to add a reference to an external vocabulary.