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

performanceRequirements: linking configurations #698

Closed
MarAlder opened this issue Mar 10, 2021 · 1 comment
Closed

performanceRequirements: linking configurations #698

MarAlder opened this issue Mar 10, 2021 · 1 comment
Milestone
cpacs 3.3

Comments

@MarAlder
Copy link
Collaborator

MarAlder commented Mar 10, 2021 •
edited
Loading

The performanceRequirements as implemented in the current beta release candidate reference a configurationUID. This element must not be required. Should it be removed or optional? In the answer we should consider the result of #697 .

grafik
@MarAlder MarAlder added this to the cpacs 3.3 milestone Mar 22, 2021
@MarAlder MarAlder mentioned this issue Mar 26, 2021
Closed
@MarAlder
Copy link
Collaborator Author

In a working group on this topic it has been agreed on implementing the configurationUID as an optional element.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
cpacs 3.3
Development

No branches or pull requests
1 participant
@MarAlder