Interoperable-data / ERA-Ontology-3.1.0

Extended version of the ERA Railway Infrastructure Ontology
5 stars 7 forks source link

review ranges xsd:anyURI vs xsd:string #65

Open VladimirAlexiev opened 4 months ago

VladimirAlexiev commented 4 months ago

This range is correct since the prop refers to a document (URL) only:

era:conditionsChargingElectricEnergyStorage rdf:type owl:DatatypeProperty ;
  rdfs:range xsd:anyURI ;
  rdfs:comment "Conditions set by IMs according to a standardised document."@en ;

This range is correct since the prop refers to URL or name (doc description):

era:conditionsSwitchClassBSystems rdf:type owl:DatatypeProperty ;
  rdfs:range xsd:string ;
  rdfs:comment "Name and/or reference of the document specifying the Special technical conditions required to switch over between ERTMS/ETCS and Class B systems."@en ;

These ranges are incorrect since the prop refers to URL or name (doc description). Change them to string:

era:conditionsAppliedRegenerativeBraking rdf:type owl:DatatypeProperty ;
  rdfs:range xsd:anyURI ;
  rdfs:comment "Name and/or reference of the document specifying the conditions applying in regards to regenerative braking."@en ;
era:documentRestrictionPositionContactLineSeparation rdf:type owl:DatatypeProperty ;
  rdfs:range xsd:anyURI ;
  rdfs:comment "Name and/or reference of the document specifying the restriction(s) related to the position of Multiple Traction unit(s) to comply with contact line separation."@en ;
era:documentRestrictionPowerConsumption rdf:type owl:DatatypeProperty ;
  rdfs:range xsd:anyURI ;
  rdfs:comment "Name and/or reference of the document specifying the restriction(s) related to power consumption of specific electric traction unit(s)."@en ;
gatemezing commented 3 months ago

It will be easier to go for a more restrictive range here, since we expect to have a reference to the document; To be double-checked with the domain experts. If it is the case, probably we'll adjust the comment.