Instances are sometimes wrong

[lenasauermann]

Some instances are wrong! Codeowners, please check your instances again!

Our developers need correct test data ;)

[lenasauermann]

SD Creation Wizard might generate the JSONs wrong

[lenasauermann]

@robertschubert can we integrate a check "are there any additional claims beside what is defined in the shacl" to the json vs. shacl check?

[robertschubert]

@lenasauermann
It would helf if you specifiy the ontologies where you spotted a concrete error :)

To your question, if we can adjust the validation:
Yes, we can do this with the help of sh:closed true.
Example:

ex:MyShape a sh:NodeShape ;
    sh:targetClass ex:MyClass ;
    sh:closed true ; # Activates the strict validation so additional fields in the jsonld are not allowed anymore.

Each domain (functional code owner) needs to decide if they want to have a closed definition or not.

[lenasauermann]

When we add sh:closed true, we would see every error, right? :D I can try to write down/mark every error but I propably oversee a few...

[lenasauermann]

Scenario:

Im type Scenario:scenario --> müsste Scenario:Scenario sein. Ist schon im shacl falsch!

general:DataResource --> just wrong, does not need to be there

general:media --> doubles at the end

georeference:georeference --> doubles too

OsiTrace:

startTime nicht korrekt

HdMap:

in "hdmap:general" ist "general:media", "general:requiredData" und "hdmap:speedLimit" fälschlicherweise drin

[lenasauermann]

@heuerfin @rcrswld Can you take care about Scenario... there are the most errors (even in the shacl)

[robertschubert]

ein funktionierend hdmap-example anbei
hdmap-working.json

[MircoNierenz]

have created a branch, will fix hdmap, scenario, surface there
georeference and environment-model are currently in separate pull requests.