Open philbarker opened 11 months ago
@philbarker does it require any engineering work here, or would we cover both items with documentation/configuration enhancements?
@edgarf Assuming the current output matches the model there shouldn't be any work required on your point—I say that as an assumption because since the current documentation is not great there is always a chance of errors.
there are inconsistencies between the model diagram, the term definitions and what is in the actual output:
the model diagram uses rdfs:domain and rdfs:range, which are not suitable to the semantics of multiple classes in domain/range; the output uses desm:domainIncludes and desm:rangeIncludes, which aren't defined in the term definitions. There is a term definition for desm:range that would do for rangeIncldues but nothing for domain.
the model diagram uses desm:Class for domain and range of properties, which is odd. desm:Class is not defined in term definition file but is used for the range of desm:range.
the model diagram has an attribute of desm:Schema called desm:abstractClass which is not in the term definition file, and maybe should be a relationship pointing to a skos:Concept? It is not used in the mapping output.
the model diagram has some text that should be dct:descrption & dct:title
(Changes here are intended to clarify the current model, not deal with other issues such as better modelling of mappers and organizations or adding transformation info to term mappings.)
@philbarker, now as we have merged the PR, can we move this task into column "Merged" or are there some unfinished items?
There is still more to do.
Currently I can only find the RDF data model that underpins the output format in an issue here.