Interoperable-data / ERA-Ontology-3.1.0

Extended version of the ERA Railway Infrastructure Ontology
4 stars 3 forks source link

split off scope notes from definition #45

Open VladimirAlexiev opened 2 weeks ago

VladimirAlexiev commented 2 weeks ago
era:eddyCurrentBraking rdf:type owl:ObjectProperty ;
                       rdfs:comment "Indication of limitations on the use of eddy current brakes."@en ,
                                    "This property has been modified to be a RINF parameter (its eratvIndex is deleted). It is treated as a SKOS by RINF and as a boolean by ERATV. A new ERATV datatype property has been defined, eddyCurrentBrakingFitted with boolean values."@en ;

The first comment is the definition of the prop and that's ok. But the second comment describes its genesis and scope of use. It's better to split it off (and use rdfs:comment only for definitions), eg like this:

skos:editorialNote "This property has been modified to be a RINF parameter (its eratvIndex is deleted)";
skos:scopeNote: "This is a SKOS property, as originally defined by RINF",
  "Another similar property is defined as a boolean by ERATV: it has been split off as era:eddyCurrentBrakingFitted"; 
rdfs:seeAlso era:eddyCurrentBrakingFitted;
VladimirAlexiev commented 2 weeks ago

Last but not least: The owl:Ontology has a longish dcterms:description that describes version changes. This is appreciated, but please change it to skos:changeNote

Interoperable-data commented 1 week ago

skos:changeNote seems to be appealing. But we suspect there is no defined way to use either dcterms or even rdfs:comment as it is withfoaf

VladimirAlexiev commented 5 days ago