We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
We believe they got into the shapes by mistake: https://lists.oasis-open-projects.org/g/oslc-op/topic/89289996#762
oslc:allowedValue "com.ibm.rqm.execution.common.state.failed" , "com.ibm.rqm.execution.common.state.inconclusive" , "com.ibm.rqm.execution.common.state.passed" , "com.ibm.rqm.execution.common.state.deferred" , "com.ibm.rqm.execution.common.state.incomplete" , "com.ibm.rqm.execution.common.state.blocked" , "com.ibm.rqm.execution.common.state.part_blocked" , "com.ibm.rqm.execution.common.state.perm_failed" , "com.ibm.rqm.execution.common.state.error" ;
Proposal: remove the oslc:allowedValue restriction altogether.
oslc:allowedValue
The text was updated successfully, but these errors were encountered:
Notified OASIS in the QM OS publication ticket: https://issues.oasis-open.org/browse/TCADMIN-4143?focusedCommentId=80793&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-80793
Sorry, something went wrong.
jamsden
No branches or pull requests
We believe they got into the shapes by mistake: https://lists.oasis-open-projects.org/g/oslc-op/topic/89289996#762
Proposal: remove the
oslc:allowedValue
restriction altogether.The text was updated successfully, but these errors were encountered: