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.

Sign up for GitHub

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

Jump to bottom

Upgrade of the Validator to Metamodel Version 3.0 #9

Open
sebbader-sap opened this issue Jun 13, 2022 · 1 comment
Open

Upgrade of the Validator to Metamodel Version 3.0 #9

sebbader-sap opened this issue Jun 13, 2022 · 1 comment
Assignees
@sebbader-sap
Labels
3.0 Final AAS V3 Final Release V.1.1.0 Final Release V.1.1.0 incl. additional features

Comments

@sebbader-sap
Copy link
Contributor

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.
@twebermartins twebermartins changed the title Upgrade of the Validator to Metamodel Version 3.0.RC02 Upgrade of the Validator to Metamodel Version 3.0 Mar 14, 2023
@twebermartins twebermartins added the 3.0 Final AAS V3 Final Release label Mar 14, 2023
@twebermartins twebermartins added the V.1.1.0 Final Release V.1.1.0 incl. additional features label Jun 5, 2023
@twebermartins
Copy link
Contributor

twebermartins commented Feb 27, 2024 •
edited
Loading

  • 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sebbader-sap sebbader-sap

Labels
3.0 Final AAS V3 Final Release V.1.1.0 Final Release V.1.1.0 incl. additional features
Projects
Eclipse AAS4J Dev
Status: 📋 Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@twebermartins @sebbader-sap