Open MathiasVDA opened 1 year ago
ocorcho
commented
1 year ago Indeed, these were legacy terms that were inherited from the very early versions of the vocabulary, but their change had lots of implications in many different components related to routing and the Route Compatibility Check application, as well as during the knowledge graph generation process, hence we decided to keep them at least for the initial release of all applications.
This will hence be dealt with later.
sixdiamants
commented
1 year ago This issue likely originates from the source KG that was generated from a UML model (visible on the RSM site).
Tangent to this, the KG that UIC generated from the UML may need revamping to meet recently published guidelines that appear to underpin SEMIC guidance from the EC. Notably, there's the OSLO UML Transformer.
At present, I'm looking at how the EULYNX Data Prep model, a treasure trove for railway signalling concepts, should map to a KG. One issue that probably merits closer analysis is the representation of enumerations aka codelists in terms of skos:conceptScheme as defined in the modelling rules published here, see p. 68-69.
Regards, Bob Janssen
Some object properties have a name and URI that are easily confused with class names. Some examples:
The ERA principles state that: * For properties, a verbal form (or adjective) and the initial character is lowercase
This is clearly not the case. Could the vocabulary be refactored to have consistent URI's for the properties that conform with the principles?
In general, I would also recommend to compare the era-principles with the gist style guide.