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

Revisit <<experimental>> SubmodelElement Range #450

Open
BirgitBoss opened this issue Jul 19, 2024 · 0 comments
Open

Revisit <<experimental>> SubmodelElement Range #450

BirgitBoss opened this issue Jul 19, 2024 · 0 comments
Labels
requires workstream approval strategic decision proposal needs to be prepared in TF spec team specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Milestone
V3.x

Comments

@BirgitBoss
Copy link
Collaborator

With V3.0 Range was set to experimental. Reason: discussion in IEC 63268 working group whether the submodel element is needed.

We need to revisit the specification to decide:

Can we set them to standard (i.e. remove stereotype <>?
Should we set the class to "deprecated"?
@BirgitBoss BirgitBoss added specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally requires workstream approval strategic decision proposal needs to be prepared in TF spec team labels Jul 19, 2024
@BirgitBoss BirgitBoss added this to the V3.x milestone Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
requires workstream approval strategic decision proposal needs to be prepared in TF spec team specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Projects
None yet
Milestone
V3.x
Development

No branches or pull requests
1 participant
@BirgitBoss