search

Interoperable-data / ERA-Ontology-3.1.0

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

readme

ERA Ontology version 3.1.0

This is a draft update of the RINF extension of the ERA Ontology. It defines the entities and thier relationships within the domain of railway infrastructure. It includes concepts such as railway lines, operational points, tracks, signals, junctions, and other various components of the railway network.

The previous version of the ERA ontology is here.

Documentation

Current documentation

Legal context

This version of the ontology reflects the collaborative efforts undertaken by the EU Agency for Railways within a specialized workgroup for the European Register of Infrastructure, dedicated to the multi level description of interoperable railway network, aligning and making RINF compliant to the most recent text of the Regulation (EU) 2019/777 of 16 May 2019 amended by Regulation (EU) 2023/1694 of 10 August 2023.

Issues

We welcome issues and enhancement requests that follow these guidelines:

  1. Issues opened in this repository should concern the ERA vocabulary definitions.
  2. Please label your issues using the corresponding version tag. For example, using the label "v3.1.0".

Contributing

Please read and respect the ERA principles while contributing to this repository.

For contributions we follow the "fork-and-pull" Git workflow:

  1. Fork this repository on GitHub.
  2. Clone the project in your local machine.
  3. Commit the changes to your own branch.
  4. Push your changes back up to your own fork.
  5. Submit a Pull request to the dev branch so we can review your changes.

NOTE: Make sure to merge the latest "upstream" version before submitting a pull request.

Validation procedure for user requests

  1. Any actor can request improvements to the RINF extension of the ERA Ontology.
  2. The Ontology team evaluates if the request is technically sound and its impact in the current deployment of the Ontology itself and on the RINF System.
  3. ERA evaluates its impact from the business and project management point of view and ultimately approves (or not) the request.
  4. The actor who requested the improvements is informed on when the request will be attended, including an indication of the Ontology release number that will include the request.
  5. The request, if approved, is implemented by the Ontology team.