Skip to content
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

Minimal viable examples from ACCORD #4

Open
1 of 4 tasks
nataschake opened this issue Aug 1, 2024 · 8 comments
Open
1 of 4 tasks

Minimal viable examples from ACCORD #4

nataschake opened this issue Aug 1, 2024 · 8 comments

Comments

@nataschake
Copy link
Collaborator

nataschake commented Aug 1, 2024

@avillar @rob-metalinkage Is that correct?

In ACCORD we will generate/extract some minimal GML examples (possibly anonimized) serving particular compliance check goals.

  • We provide a CityGML file serving a single interesting case or repetitive pattern caused by e.g. conversion from XPlan or from IFC.

OGC BBlocks machinery will generate:

  • JSON file from GML
  • apply ours (or generates itself, here I need clarification) SHACL rules serving consistency purposes
  • perform semantic uplift (JSON-LD) and publish a profile.
@ar-chad
Copy link
Collaborator

ar-chad commented Aug 8, 2024

I have added land use related ontologies, previously used to model plots, land uses and regulations in Singapore. More details here: A semantic web approach to land use regulations in urban planning: The OntoZoning ontology of zones, land uses and programmes for Singapore

The initial idea is to break it down further to reusable pieces and adopt some of it to modelling XPlan regulations.

@rob-metalinkage
Copy link
Collaborator

This is a good start - IMHO next steps are:

  1. example instances for each ontology - including any key examples we need to integrate between these and cityRDF concepts.
  2. An architecture diagram showing how these and other ontologies relate to each other, and to processing we intend to test
  3. SHACL rules derived from the ontologies to validate instances.
  4. SHACL Rules to test elements are present for a given query/planning rule (profiles)
  5. SHACL or other code to execute validation of planning rules (this does not need to be part of the specification layer - but all other elements do)

I can then turn these into building blocks that test examples and inherit

@nataschake
Copy link
Collaborator Author

nataschake commented Nov 21, 2024

Decided on 21 November 2024:

  • prepare one turtle instance data for Building.ttl
  • prepare one turtle instance to something else, in relation with Building.

@nataschake
Copy link
Collaborator Author

@rob-metalinkage @avillar What is the desired size of the sample files? I can propose 70Mb, 8Mb, or here we need like 10Kb?

@nataschake
Copy link
Collaborator Author

I will reuse the data from lod3-road-space-models , there are buildings and road network surrounding them.

@nataschake
Copy link
Collaborator Author

nataschake commented Nov 29, 2024

@rob-metalinkage @avillar
examples added, both with bldg:measuredHeight, in one case it is converted smoothly to TTL (lod3), in the other case the height is currently lost, because its measure is defined as <bldg:measuredHeight uom="urn:adv:uom:m">5.463</bldg:measuredHeight>, which I need to resolve locally first

@rob-metalinkage
Copy link
Collaborator

We are looking first for unit tests. As small as possible. Ideally 1 object per file. Larger files to demonstrate graph exploitation would be good later, but now we need to show mappings from schema to rdf, so having the rdf target as a test case means small examples.

Failure cases are also super useful for any shacl validation. Name them {x}-fail.ttl e.g something claiming to be lod 2 but having elements from lod 3

@nataschake
Copy link
Collaborator Author

files are in citygml-owl/examples

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants