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 Events <<Experimental>> #406

Open
BirgitBoss opened this issue Apr 12, 2024 · 1 comment
Open

Revisit Events <<Experimental>> #406

BirgitBoss opened this issue Apr 12, 2024 · 1 comment
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

Is your feature request related to a problem? Please describe.

With V3.0 EventElements and BasicEventElement were introduced as <> elements. We need to revisit the specification to decide:

Those who implemented it: did the specification meet the requirements?

Can we set them to standard (i.e. remove stereotype <>?
@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 Apr 12, 2024
@BirgitBoss BirgitBoss added this to the V3.x milestone Apr 12, 2024
@BirgitBoss
Copy link
Collaborator Author

dependency to admin-shell-io/aas-specs-api#297

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