julianrojas87 / era-vocabulary Goto Github PK

Vocabulary definition for the European Union Agency for Railways

License: MIT License

Shell 0.15% HTML 97.80% CSS 1.94% Dockerfile 0.10%

railways linked-open-data semantic-web ontology knowledge-graph

era-vocabulary's Introduction

era-vocabulary

Vocabulary definition for the European Union Agency for Railways. The vocabulary documentation is built using the Widoco toolset.

Online documentation for this vocabulary is available at https://data-interop.era.europa.eu/era-vocabulary/

Run WITH Docker

This application has been dockerized to facilitate its deployment. We use a multi-stage approach to build a container that publishes a build of this Web application via a NGINX instance.

To deploy this container follow these steps:

Make sure to have a recent version of Docker installed.
Build the Docker image:
```
docker build -t era-vocabulary ./
```
Start the application:
```
docker run -p ${PORT}:80 era-vocabulary
```
Replace ${PORT} for the TCP port where you want to run the application. Once the container is running you can access these resources:
- The vocabulary documentation at http://localhost:${PORT}/era-vocabulary/index-en.html.
- The reference data at http://localhost:${PORT}/era-vocabulary/era-skos.

Deploy WITHOUT Docker

To directly build this application you need to install first:

Java JRE at least v11.
Node.js at least v12.

Then follow the next steps:

Clone this repository:

git clone https://github.com/julianrojas87/era-vocabulary.git

Normally the latest built version of the Widoco documentation is already available within the repository in the public folder. If you want to deploy this version then skip to step 4, otherwise proceed to delete all the files and folders in public/:
```
cd public
rm -rf *
```
Now continue to the next step.
Generate the Widoco documentation:
```
./generate-docs.sh
```
The resulting sources will be placed in the public/doc folder.
Publish the Web page. In this example we use Node.js's npx utility and http-server for this, but you may choose to publish the static files otherwise (e.g. directly via NGINX).
```
cd public/doc
npx http-server --cors -p ${PORT}
```
Replace ${PORT} for the TCP port where you want to run the application. Once the application is running you may access the following resources:
- The vocabulary documentation at http://localhost:${PORT}/index-en.html.
- The reference data at http://localhost:${PORT}/era-skos.ttl.

Issues

We welcome issues and enhancement requests that follow these guidelines:

Issues opened in this repository should concern the ERA vocabulary definitions. For issues related to the ERA Knowledge Graph, please refer to the data mappings repository.
Please label your issues using the corresponding version tag. For example, using the label v0.9.0.

Contributing

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

Fork this repository on GitHub.
Clone the project in your local machine.
Commit the changes to your own branch.
Push your changes back up to your own fork.
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.

era-vocabulary's People

Contributors

Stargazers

Watchers

Forkers

pietercolpaert polymnia airy59 kvistgaard

era-vocabulary's Issues

Consider removing rdfs:Class declarations for all era: classes

Consider removing
?class a rdfs:Class

in all cases where ?class a owl:Class

because owl:Class rdfs:subClassOf rdfs:Class

unless there is some specific reason to assert such inferences but if that's the case, it should be done for all classes for consistency.

Currently, the following classes are owl:Class, rdfs:Class

era:InternalNodeLink
era:MicroLink
era:MicroNode
era:NodePort
era:OperationalPoint
era:Track
era:Tunnel
era:VehicleType

An ontology should be independent of reference datasets

In the declaration
owl:imports schema:, era-skos:, eu-countries:, wgs:, geosparql: .
schema and georsparl are fine but era-skos and eu-coutries not.

Each controlled vocabulary should be in a separate file (not for the pilot phase)

When the development, maintenance and publishing responsibility for all reference datasets is done by one person/team, it is acceptable to keep them all in one file for convenience. But once proper governance is established, they should be split.

In other words, during the pilot phase is fine to keep them like that, but this should be changed right after.

Misspelling of the labels of two properties about Pantographs

property	rdfs:label
era:numberOfPantographsInContactWithOCL	number of pantpgraphs in contact with OCL
era:shortestDistanceBetweenPantographsInContactWithOCL	shortest distance between pantpgraphs in contact with OCL

The skos concepts do not belong to one ontology, they are defined like separate ontologies.

This becomes obvious from the different prefix per class.

Change {era dct:contributor "Julián Rojas"} to {era dct:creator "Julián Rojas"}

as discussed

Consider changing the label of era:category

Since the domain of the ontology is larger than train vehicles, "category" is ambiguous. The URI may remain but consider changing the label to "vehicle category", after consulting with ERA.

Same of subCategory.

Merge the object properties "Other" with the equivalent ones from the taxonomies.

For example: era:otherEnergySupplySystem with era:energySupplySystem

Similarly for:
era:otherAxleBearingConditionMonitoring
era:otherRailInclination
era:otherWheelSetGaugeChangeoverFacility
era:otherSnowIceHailConditions
era:otherPantographHead
era:otherContactStripMaterial
era:otherPlatformHeight
era:otherProtectionLegacySystem
era:otherLegacyRadioSystem

in #v0.9.0

Change the Author at the published ERA Vocabulary with "European Union Agency for Railways"

Currently:
Author = https://julianrojas.org/#me, therefore the Cite as = https://julianrojas.org/#me. ERA vocabulary. Revision: v0.9.0.

Modify to:
Author = European Union Agency for Railways, therefore Cite as = European Union Agency for Railways. ERA Vocabulary. Revision: v0.9.0

Intended meaning of era:inCountry

Currently IRI: http://era.europa.eu/ns#inCountry is defined with the intended use

Indicates the country in which the entity resides.

    rdfs:label "in country"@en ;
    rdfs:comment "Indicates the country in which the entity resides."@en ;
    rdfs:isDefinedBy era: ;
    rdfs:domain [ a owl:Class ;
                  owl:unionOf ( era:OperationalPoint era:VehicleType )
                ] ;
    rdfs:range skos:Concept ;
    dct:created "2020-09-01"^^xsd:date ;
    dct:modified "2020-09-01"^^xsd:date ;
    vs:term_status "stable" .

It has domain owl:unionOf ( era:OperationalPoint era:VehicleType . OP have location rather than residence. For VT the issue the intended use is ambiguous: "manufactured in", "spend most of it's lifecycle in", "has manufacturer with coutry of residence" etc.

Possible solutions: changing the comment, creating a sub-property, changing the domain (OP or Manufacturer).

The domain of era:inCountry is unnecessarily restrictive

Currently the domain of era:inCountry is the union of VT and OP.

However, the actual use is broader.

1 | era:OperationalPoint
2 | geosparql:Feature
3 | wgs:SpatialThing
4 | era:VehicleType

Apart from that to allow for a higher interoperability and re-use, the era ontology should "learn" but not be coupled with the current dataset.
Suggestion: remove domain declaration and for orientation list in the note the typical expected domain classes, based on the current data set.

There is no "subclass" relationship between classes and there are potential ones.

Inherited from the relational database, there is no relationship between classes but we should review and add those if they exist.

Rename the era-uic: UICCode to imply "National Identification number of line "

Proposal:
era-lnid:LineNationalID
in #v.0.9.0

(It is an identifier for the whole line, so broader than the SoL or Track)

Add a property to indicate ERATV and/or RINF index ID

As suggested in #8, we could add a predicate to refer to the index ID of every parameter, as they were defined originally in ERATV and/or RINF.

Fixes to SKOS modeling

These are wrong

era-op-types:OperationalPointType
skos:inScheme era-skos:  .
era-skos: a skos:ConceptScheme

because a ConceptScheme is a single thesaurus and consists of Concepts, not of subclasses of Concept .

It's better to declare

era-op-types:OperationalPointType
rdfa:isDefinedBy era-skos:  .
era-skos: a owl:Ontology

each Concept must belong to a ConceptScheme. So in addition to this

era-op-types:borderPoint a era-op-types:OperationalPointType

You better add this

era-op-types:borderPoint skos:inScheme era-op-types:OperationalPointType.
era-op-types:OperationalPointType a skos:ConceptScheme.

I don't think it's a bug problem that era-op-types:OperationalPointType wull become both an individual ( skos:ConceptScheme) and a Class. OWL Punning allows that.