It's all about the answers!

Ask a question

How can I find out the direction of a DoorsNG 5.0.1 link with OSLC-API?


Guido Schneider (3.3k137699) | asked Nov 11 '14, 4:24 p.m.

I’m trying to find out the direction of a RDNG 5.0.1 link.  In the example below, the red part is a <supported by> link to other DNG requirements.

But I cannot tell from the OSLC response, which direction each is pointing, i.e. if it is  <supports> or <supported by>.  In this case the first one is <supported by>, the second <supports>.

 

The OSLC query was

https://rrcServer/rm/views?oslc.query=true&projectURL=https://rrcServer/rm/process/project-areas/_tgOWwrPVEeGsn_ToVY7h1A&oslc.prefix=dcterms=<http://purl.org/dc/terms/>&oslc.select=dcterms:identifier, dcterms:title, dcterms:description, *&oslc.where=dcterms:identifier>0&oslc.limit=50&oslc.paging=true&oslc.pageSize=50

 

Should I use another query or call another service?





<rdf:Description rdf:about="https://rrcServer/rm/views">

        <rdfs:member>

            <oslc_rm:Requirement rdf:about="https://rrcServer/rm/resources/_wmPNgLUqEeGsn_ToVY7h1A">

                <f1:accessControl rdf:resource="https://rrcServer/rm/accessControl/_tgOWwrPVEeGsn_ToVY7h1A"/>

                <rt:_vkqM6_2FEeGx9oa7c1CPwg rdf:resource="https://rrcServer/rm/resources/_woU4MLUqEeGsn_ToVY7h1A"/>

  <dcterms:description>Documentation and Training</dcterms:description>

                <nav:parent rdf:resource="https://rrcServer/rm/folders/_WLQp2wGlEeKx9oa7c1CPwg"/>

                <rt:_Qy3YG_f9EeGx9oa7c1CPwg rdf:resource="https://rrcServer/rm/types/_LZ6Wa_f9EeGx9oa7c1CPwg#f4bdb529-420b-4a71-8f3e-6288da71f1ae"/>

                <dcterms:contributor rdf:resource="https://rrcServer/jts/users/xxx%40siemens.com"/>

                <oslc:instanceShape rdf:resource="https://rrcServer/rm/types/_9L7oa7PaEeGsn_ToVY7h1A"/>

                <rt:_MAsny7PcEeGsn_ToVY7h1A rdf:resource="https://rrcServer/jts/users/xxx%40siemens.com"/>

                <rt:_uJ8pO7PVEeGsn_ToVY7h1A rdf:resource="https://rrcServer/jts/users/xxx%40siemens.com"/>

 <rt:_vkqM6_2FEeGx9oa7c1CPwg rdf:resource="https://rrcServer/rm/resources/_Ccq1RzWMEeOOtrqmazH1pA"/>

              

                <dcterms:identifier rdf:datatype="http://www.w3.org/2001/XMLSchema#integer">941</dcterms:identifier>

                <dcterms:creator rdf:resource="https://rrcServer/jts/users/xxx%40siemens.com"/>

                <rt:__sYn6_vkEeGx9oa7c1CPwg rdf:resource="https://rrcServer/rm/types/_7xdDa_vkEeGx9oa7c1CPwg#78721e01-bb48-40b8-8435-36815ec99bc6"/>

                <dcterms:created rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">2012-06-13T07:38:25.24Z</dcterms:created>

                <rt:_icR4S_gdEeGx9oa7c1CPwg rdf:resource="https://rrcServer/rm/types/_6JwMcPgYEeGx9oa7c1CPwg#2f803a68-1d19-4c91-8b61-73aa45dad9e1"/>

                <rt:_uK2BHLPVEeGsn_ToVY7h1A rdf:resource="https://rrcServer/jts/users/xxx%40siemens.com"/>

                <rt:_u44y27PVEeGsn_ToVY7h1A rdf:resource="https://rrcServer/rm/types/_uyoZ5rPVEeGsn_ToVY7h1A#a10635ea-b775-451a-853a-60d1cfeb1c41"/>

                <rt:_2kS1y_glEeGx9oa7c1CPwg rdf:resource="https://rrcServer/rm/types/_zbIse_glEeGx9oa7c1CPwg#70d05ae9-f95a-4ecb-8de6-557694461d50"/>

                <rt:_Ewg-u7PcEeGsn_ToVY7h1A>not implemented</rt:_Ewg-u7PcEeGsn_ToVY7h1A>

                <rt:_hnLNEP1_EeGx9oa7c1CPwg rdf:resource="https://rrcServer/jts/users/xxx%40siemens.com"/>

                <rt:_k3ypS_1_EeGx9oa7c1CPwg rdf:resource="https://rrcServer/jts/users/xxx%40siemens.com"/>

                <oslc_rm:implementedBy rdf:resource="https://rrcServer/ccm/resource/itemName/com.ibm.team.workitem.WorkItem/18582"/>

                <rt:_uKZVK7PVEeGsn_ToVY7h1A rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">2012-06-13T07:38:25.24Z</rt:_uKZVK7PVEeGsn_ToVY7h1A>

                <dcterms:title>Documentation and training material for MP1.1 (SYSREQ22-1)</dcterms:title>

                <jazz_rm:primaryText>Create an easy to understand, as short as possible documentation and training for Desigo CC MP1.1</jazz_rm:primaryText>

                <rt:_u731YLPVEeGsn_ToVY7h1A rdf:resource="https://rrcServer/rm/types/_uxcHJLPVEeGsn_ToVY7h1A#41377dfc-4909-4c9b-a6be-1e578b3e979b"/>

                <dcterms:modified rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">2013-02-19T18:19:08.59Z</dcterms:modified>

                <rmTypes:ArtifactFormat rdf:resource="https://rrcServer/rm/types/_uE4jC7PVEeGsn_ToVY7h1A#Text"/>

                <rt:_uMME67PVEeGsn_ToVY7h1A rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime">2013-02-19T18:19:08.59Z</rt:_uMME67PVEeGsn_ToVY7h1A>

            </oslc_rm:Requirement>

        </rdfs:member>


2 answers



permanent link
Rosa Naranjo (2.8k11420) | answered Nov 12 '14, 4:50 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Guido
When reading your question, I thought of this article which you may already have found: https://jazz.net/library/article/1197
In it, you will notice the section on modifying, adding and removing links where the links are designated by the oslc_rm:<linktype> where linktype is for ex., implementedBy, validatedby, etc. These link types are OSLC link types not internal link types which was discussed further in the comments section of the article.  So, I believe if you are talking about the direction of an oslc link type it will tell you but if you are talking about an internal link type or a custom link type then it probably will not show up.

You could try the RRC ReportableREST API and see if that exposes internal link types. It should since this is for document generation. https://jazz.net/wiki/bin/view/Main/RRCReportableRestAPI

permanent link
Donald Nong (14.3k213) | answered Nov 12 '14, 7:03 p.m.
If you want to go further on the same route, just append the UUID found after the <rt:> tag to https://rrcServer/rm/types/ and you should see what it is. In your case
https://rrcServer/rm/types/_vkqm6_2feegx9oa7c1cpwg
P.S. If I read it correctly, the UUID is the same in both of your quoted text, so the links in both sections should be of the same type.

Your answer


Register or to post your answer.