validate ERA shapes

[VladimirAlexiev]

Go to https://www.itb.ec.europa.eu/shacl/shacl/upload and use "Upload file" to validate the ERA shapes.

• Due to can't fetch SHACL from URL ISAITB/shacl-validator#16, use "Upload" not "URI"
• Chrome supports upload directly from the URLs cited below
• Use "Validation type: Extended W3C syntax rules and best practices"
• I am showing "Aggregated reports"

https://raw.githubusercontent.com/Interoperable-data/ERA_vocabulary/refs/heads/main/public/doc/shacl/RINF-contact-line-systems-sparql.ttl

 [First of 8 occurrences] Each property SHOULD have sh:description (in the context of the target where it appears) to provide further human-oriented details. This is the preferred solution over adding additional usage notes to fit the context.
Location:[Focus node] - [http://data.europa.eu/949/shapes/energySupplySystemTSICompliant] - [Result path] - [http://www.w3.org/ns/shacl#description]Test:[Shape] - [http://itb.ec.europa.eu/ns/shacl-shacl-bp#CountDescriptionProperty]
 [First of 8 occurrences] Each property SHALL have a sh:name (in the context of the target where it appears) to provide human-oriented labels. This is the preferred alternative to overwriting rdfs:labels coming from external foreign vocabularies to fit the context better.
Location:[Focus node] - [http://data.europa.eu/949/shapes/contactLineSystemType] - [Result path] - [http://www.w3.org/ns/shacl#name]Test:[Shape] - [http://itb.ec.europa.eu/ns/shacl-shacl-bp#CountNameProperty]
 Every NodeShape SHOULD contain rdfs:label and rdfs:comment, and they SHOULD only have one value per language tag.
Location:[Focus node] - [http://data.europa.eu/949/shapes/contactLineSystemShape]Test:[Shape] - [http://itb.ec.europa.eu/ns/shacl-shacl-bp#NodeShapeShape] - [Value] - [http://data.europa.eu/949/shapes/contactLineSystemShape]

https://github.com/Interoperable-data/ERA_vocabulary/raw/refs/heads/main/public/doc/shacl/RINF-tunnels-sparql.ttl

 [First of 17 occurrences] Each property SHALL have a sh:name (in the context of the target where it appears) to provide human-oriented labels. This is the preferred alternative to overwriting rdfs:labels coming from external foreign vocabularies to fit the context better.
Location:[Focus node] - [http://data.europa.eu/949/shapes/lengthT] - [Result path] - [http://www.w3.org/ns/shacl#name]Test:[Shape] - [http://itb.ec.europa.eu/ns/shacl-shacl-bp#CountNameProperty]
 [First of 17 occurrences] Each property SHOULD have sh:description (in the context of the target where it appears) to provide further human-oriented details. This is the preferred solution over adding additional usage notes to fit the context.
Location:[Focus node] - [http://data.europa.eu/949/shapes/tunnelStartLineNationalId] - [Result path] - [http://www.w3.org/ns/shacl#description]Test:[Shape] - [http://itb.ec.europa.eu/ns/shacl-shacl-bp#CountDescriptionProperty]
 [First of 2 occurrences] Every NodeShape SHOULD contain rdfs:label and rdfs:comment, and they SHOULD only have one value per language tag.
Location:[Focus node] - [http://data.europa.eu/949/shapes/tunnelsShape]Test:[Shape] - [http://itb.ec.europa.eu/ns/shacl-shacl-bp#NodeShapeShape] - [Value] - [http://data.europa.eu/949/shapes/tunnelsShape]

 [First of 546 occurrences] Each property SHALL have a sh:name (in the context of the target where it appears) to provide human-oriented labels. This is the preferred alternative to overwriting rdfs:labels coming from external foreign vocabularies to fit the context better.
Location:[Focus node] - [http://data.europa.eu/949/shapes/OperationalPoint-hasSchematicOverviewOPDigitalForm] - [Result path] - [http://www.w3.org/ns/shacl#name]Test:[Shape] - [http://itb.ec.europa.eu/ns/shacl-shacl-bp#CountNameProperty]
 [First of 546 occurrences] Each property SHOULD have sh:description (in the context of the target where it appears) to provide further human-oriented details. This is the preferred solution over adding additional usage notes to fit the context.
Location:[Focus node] - [http://data.europa.eu/949/shapes/VehicleType-manufacturer] - [Result path] - [http://www.w3.org/ns/shacl#description]Test:[Shape] - [http://itb.ec.europa.eu/ns/shacl-shacl-bp#CountDescriptionProperty]
 [First of 15 occurrences] Property needs to have at least 1 value
Location:[Focus node] - [http://data.europa.eu/949/MaximumMagneticField-maximumMagneticFieldDirectionY] - [Result path] - [http://www.w3.org/ns/shacl#path]
 [First of 62 occurrences] Every NodeShape SHOULD contain rdfs:label and rdfs:comment, and they SHOULD only have one value per language tag.
Location:[Focus node] - [http://data.europa.eu/949/shapes/Junction]Test:[Shape] - [http://itb.ec.europa.eu/ns/shacl-shacl-bp#NodeShapeShape] - [Value] - [http://data.europa.eu/949/shapes/Junction]

Analysis:

• It gives 3 kinds of warnings about some descriptive props that it considers important, but I think it's ok since the shapes have informative sh:message and informative URLs
• It gives 15 errors, I'll post a separate issue

[ocorcho]

@ednaru will update the repository for the ERA ontology v3.0.1 so as to mirror the latest version maintained in GitLab. After that, we will run these checks to make sure that there are no errors.