Header: `Resource1 ... Resource13`?

[VladimirAlexiev]

Header-AP-Voc-RDFS2020.ttl has 13 props that seem to be bugs:

• names don't comply to naming convention (lowerCamelCase),
• names don't correspond to the comment.

Two of the 13:

dcat:Resource7  rdf:type      rdf:Property ;
        rdfs:comment          "The resoource of a previous version that has this next version." ;
        rdfs:domain           md:Model ;
        rdfs:label            "Resource7"@en ;
        rdfs:range            md:Model ;
        cims:AssociationUsed  "No" ;
        cims:inverseRoleName  dcat:previousVersion ;
        cims:multiplicity     cims:M:0..1 ;
        cims:stereotype       "dcat" .

dcat:Resource8  rdf:type      rdf:Property ;
        rdfs:comment          "The resource that has this next version." ;
        rdfs:domain           md:Model ;
        rdfs:label            "Resource8"@en ;
        rdfs:range            md:Model ;
        cims:AssociationUsed  "No" ;
        cims:inverseRoleName  dcat:nextVersion ;
        cims:multiplicity     cims:M:0..1 ;
        cims:stereotype       "dcat" .

[VladimirAlexiev]

In addition to wrong localnames, the comments of the above two are unnecessarily twisted. Use the wording from DCAT, eg

dcat:previousVersion rdfs:comment "The previous version of a resource in a lineage".
dcat:nextVersion rdfs:comment "The next version of a resource in a lineage".

Note: https://www.w3.org/TR/vocab-dcat-3/#inverse-properties intentionally doesn't define dcat:nextVersion (because inverses are redundant). But all CIM props use inverses, so it's ok for CIM to define it.

[Sveino]

All headers are updated in NC 2.3.1. Hopefully is this fixed.

[VladimirAlexiev]

These are still present: https://github.com/Sveino/Inst4CIM-KG/blob/develop/rdfs-improved%2FCGMES-NC%2Fttl%2FHeader-AP-Voc-RDFS2020.ttl#L106

[griddigit-ci]

We need discussion here.

[VladimirAlexiev]

The problems come from the desire to express DCAT terms.