Comments (10)
- Every ontology is created in its own folder
- -> Codeowners --> updated and improved README.md
- -> Rename: VARAIBLES -> prefix_properties.md OR PROPERTIES.md
- -> files and folders without capitals --> enhanced README.md
- -> prefix is always the same as the folder name --> enhanced README.md
- -> prefix names use "-" as separators --> enhanced README.md
- -> Classes PascalCase --> enhanced README.md
- -> Properties camlCase --> enhanced README.md
- Rename examples folder to example
- -> Carlo: merge examples. Question of taste --> I would prefer to leave it as it is.
- Add test vector as example .json file into each ontology folder --> added for gx and example, enhanced README.md. The rest is up to the data providers.
- -> not extra folder, just same level --> documented in README.md
- -> everyone adding an ontology must add an example --> documented in README.md
- Add CI workflows
- -> test if ontology/shacl parses successfully --> introduced ci pipeline
- -> test if example .json complies with shacl property definitions (schema) --> introduced ci pipeline
- Add gaiax ontologies as sub repository and link resources in readme
- -> GaiaX definitions are provided as json and not as a repo
- -> we add an extra folder to the repo named e.g. "gaiax" with a readme and original json plus pthon converter to .ttl
- Can we discuss some structural elements used in the old demo as Carlo thinks it is useful
- -> token meta data
from ontology-management-base.
from ontology-management-base.
regarding
"test if example .json complies with shacl property definitions (schema)"
This task is simple for shapes that do not reference "external" shapes.
Example:
prefix:SomeShape a sh:NodeShape ;
sh:property [ sh:minCount 1 ;
sh:node gx:PostalAddressShape ;
sh:path general:myAddress;
sh:order 5 ] ;
sh:targetClass general:General .
With this syntax you would be able to reference an "external" gx:PostalAddressShape
. The validation in the Federated Catalogue is no problem as long the gx:PostalAddressShape
was uploaded before. All shapes are loaded for validation in the Federated Catalogue upfront.
In the context of this repository we will not have access to gx:PostalAddressShape
so no validation against this shape is possible.
from ontology-management-base.
Can the shapes also be uploaded somewhere more independend from EDC? Reference to a URL? I don't want to use custom software to access the shapes. Just a trusted source.
from ontology-management-base.
Task "-> test if ontology/shacl parses successfully":
solved with PR #58
from ontology-management-base.
Can the shapes also be uploaded somewhere more independend from EDC? Reference to a URL? I don't want to use custom software to access the shapes. Just a trusted source.
@jdsika not sure if I understand the question. Which subtask are you referring to? Or where do we have a link to EDC in this issue / repository?
from ontology-management-base.
I am sorry, I was reading this comment and may have misunderstood it? It was regarding "where" are the ontologies uploaded to in order to have a source for the validation.
With this syntax you would be able to reference an "external" gx:PostalAddressShape. The validation in the Federated Catalogue is no problem as long the gx:PostalAddressShape was uploaded before. All shapes are loaded for validation in the Federated Catalogue upfront.
from ontology-management-base.
I am sorry, I was reading this comment and may have misunderstood it? It was regarding "where" are the ontologies uploaded to in order to have a source for the validation.
With this syntax you would be able to reference an "external" gx:PostalAddressShape. The validation in the Federated Catalogue is no problem as long the gx:PostalAddressShape was uploaded before. All shapes are loaded for validation in the Federated Catalogue upfront.
The source for validation is the federated catalogue. Ontologies and shapes must be uploaded so the catalogue knows what an HdMap is (as an example). The validation against the shacl shape is then done in the federated catalogue when someone uploads a self description containing an HdMap.
Since we now have a working (because fixed) gx ontology in our repo I will also have access to the PostalAddressShape in the context of this repo.
So it should work out to load all existent SHACLs and validate one json-ld against all loaded shapes. I will have a look.
from ontology-management-base.
Task "-> test if example .json complies with shacl property definitions (schema)":
solved with PR #58
from ontology-management-base.
@jdsika
my proposal is that I create a new Issue for
Rename: VARAIBLES -> prefix_properties.md OR PROPERTIES.md
See #71
After the open branches are merged I will make the change.
Is there anything else that has to be done in this Issue or can we close it?
from ontology-management-base.
Related Issues (20)
- Extend docu to explain overall metadata approach and link to related repos (asset-examples) HOT 1
- Where is the code of the wizard? HOT 5
- Add hash-value of assets to metadata general-shape HOT 1
- Overall ontology required to show-case dependencies between multiple ontologies within federated catalogue
- Add a Ontology-Class for every Shape into the ontology.ttl HOT 5
- GeoReferenceShape and Instance not matching HOT 2
- environment-model: _instance.json not conform to shacl shape HOT 2
- scenario: instance.json not conform to shacl shape HOT 1
- surface-model: instance.json not conform to shacl shape HOT 2
- ID-definition for 'domain-specific' claims HOT 4
- Alignment for sensor-data metadata acquisition HOT 2
- LinkShape alows to define or describe there an link to the location of the asset HOT 5
- Rename VARIABLES.md to PROPERTIES.md
- Readme for each ontology HOT 2
- GeoReference clarification and real world relations HOT 1
- Define which information has to be provided per class, node or simple data types HOT 1
- Missing versioning of SHACL shapes & reference of shape-version in metadata
- SD-Wizard does not process Logical Constraint Components HOT 1
- Missing sh:name und sh:property in properties with sh:node HOT 1
- General Shape contains dataecosystem specific information
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ontology-management-base.