Why does RTC work item service provider OSLC request return nested oslc:creationFactory elements?
The response to an RTC work item service provider OSLC request, such as https://<host>:<port>/ccm/oslc/contexts/_pyf14FrmEeWs66yN_e1diA/workitems/services.xml, contains nested <oslc:creationFactory> elements:
... <oslc:creationFactory> <oslc:CreationFactory> <dcterms:title rdf:parseType="Literal">Location for creation of Task change requests </dcterms:title> <oslc:usage rdf:resource="http://open-services.net/ns/cm#task"/> <oslc:usage rdf:resource="http://open-services.net/ns/cm#requirementsChangeRequest"/> <oslc:resourceType rdf:resource="http://open-services.net/ns/cm#ChangeRequest"/> <oslc:resourceType rdf:resource="https://sport6.rtp.raleigh.ibm.com:9463/ccm/oslc/types/_pyf14FrmEeWs66yN_e1diA/task"/> <oslc:resourceShape rdf:resource="https://sport6.rtp.raleigh.ibm.com:9463/ccm/oslc/context/_pyf14FrmEeWs66yN_e1diA/shapes/workitems/task"/> <oslc:creation rdf:resource="https://sport6.rtp.raleigh.ibm.com:9463/ccm/oslc/contexts/_pyf14FrmEeWs66yN_e1diA/workitems/task"/> </oslc:CreationFactory> </oslc:creationFactory> <oslc:creationFactory> <oslc:CreationFactory> <dcterms:title rdf:parseType="Literal">Location for creation of Story change requests </dcterms:title> <oslc:usage rdf:resource="http://open-services.net/ns/cm#planItem"/> <oslc:resourceType rdf:resource="http://open-services.net/ns/cm#ChangeRequest"/> <oslc:resourceType rdf:resource="https://sport6.rtp.raleigh.ibm.com:9463/ccm/oslc/types/_pyf14FrmEeWs66yN_e1diA/com.ibm.team.apt.workItemType.story"/> <oslc:resourceShape rdf:resource="https://sport6.rtp.raleigh.ibm.com:9463/ccm/oslc/context/_pyf14FrmEeWs66yN_e1diA/shapes/workitems/com.ibm.team.apt.workItemType.story"/> <oslc:creation rdf:resource="https://sport6.rtp.raleigh.ibm.com:9463/ccm/oslc/contexts/_pyf14FrmEeWs66yN_e1diA/workitems/com.ibm.team.apt.workItemType.story"/> </oslc:CreationFactory> </oslc:creationFactory> ...From what I find at OSLC Core Specification Version 2.0 - Resource: Creation Factory, the <oslc:creationFactory> element isn't allowed to contain a nested <oslc:creationFactory> element. So I would think that RTC OSLC response isn't valid. Is my understanding correct? Is this an RTC OSLC defect? |
Accepted answer
The result that you got looks a bit strange. It should've looked like
< oslc:creationFactory>I know that Lyo OSLC4J works with the service provide document just fine, so it should be correct. QM and RM return something similar (re: nested). If you look at the "Resource: Service" table in the specification, there two elements are not the same thing. Note that "queryCapability" has the same "nestedness".
Geoff Alexander selected this answer as the correct answer
Comments Donald, thanks for the response.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.