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.

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

OSLC CM is missing properties that link Change Requests to AM Resources. #575

Open
DavidJohnHoney opened this issue Jun 8, 2022 · 1 comment

Comments

@DavidJohnHoney
Copy link

Curently, IBM Rational Engineering Workflow Management declares the following OSLC property in resource shapes:

<https://jazz.net/jazz04/oslc/shapes/workitems/_9XNFQJmkEeqYMbGm-_64MA/property/com.ibm.team.workitem.linktype.am.elaboratedBy.architectureElement>
      a       oslc:Property ;
      jrs:inversePropertyLabel
              "Elaborates"^^rdf:XMLLiteral ;
      oslc:name "relatedArchitectureElement"^^<http://www.w3.org/2001/XMLSchema#string> ;
      oslc:occurs oslc:Zero-or-many ;
      oslc:propertyDefinition
              <http://open-services.net/ns/cm#relatedArchitectureElement> ;
      oslc:range <http://open-services.net/ns/am#Resource> ;
      oslc:readOnly "false"^^<http://www.w3.org/2001/XMLSchema#boolean> ;
      oslc:representation oslc:Either ;
      oslc:valueType oslc:Resource ;
      dcterms:title "Elaborated by Architecture Element "^^rdf:XMLLiteral .

The issue here is that it is using an oslc_cm namespace predicate of http://open-services.net/ns/cm#relatedArchitectureElement which is not defined in the current or previous OSLC Change Management specifications. One way of resolving this would be to regularize the above by including the property into one or more resource shapes in that specification.

@jamsden
Copy link
Member

jamsden commented Nov 15, 2023

Same with oslc_cm:tracksChangeRequest and oslc_cm:trackedByChangeRequest

@jamsden jamsden changed the title New Change Management property OSLC CM is missing properties that link Change Requests to AM Resources. Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants