-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instances are sometimes wrong #95
Comments
SD Creation Wizard might generate the JSONs wrong |
@robertschubert can we integrate a check "are there any additional claims beside what is defined in the shacl" to the json vs. shacl check? |
@lenasauermann To your question, if we can adjust the validation:
Each domain (functional code owner) needs to decide if they want to have a |
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... |
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 |
Addresses #95 for ositrace Signed-off-by: Pierre R. Mai <[email protected]>
ein funktionierend hdmap-example anbei |
have created a branch, will fix hdmap, scenario, surface there |
Some instances are wrong! Codeowners, please check your instances again!
Our developers need correct test data ;)
The text was updated successfully, but these errors were encountered: