twebermartins
commented
9 months ago - should we do it with RDF?
- performance?
- error code not transparent?
- how we realize it so that the user can get useful exceptions?
- who (projects like (Eclipse) FA3ST, Eclipse BaSyx, ...) is using it and needs it? (relevance)
- what if we have a validator feature, but incoming AAS(X) are in 95% not valid? Can we fix it or provide suggestions on how to fix it?
- what are the constraints? do we still have "the" list listing all the constraints? ask IDTA AAS WG or aas-core-works ...
current implementations are based on custom based SHACL shapes. However, SHACL shapes are quite challenging to deal with. But what are the alternatives? => research existing methods / concepts? do it all by ourselves instead? => Next step is to investigate feasible options and decide upon our requirements / criteria
The Metamodel Version 3.0.RC02 led to a number of changes for the AAS Constraints. They need to be reviewed and adopted where necessary.