It's all about the answers!

Ask a question

Advise to Query Requirement in RM-Project (part of a Global Configuration)

magnus Elfving (282) | asked Mar 29, 10:09 a.m.

I am querying (for the first time) a RM-project for attribute data, according to the Query shown below.<o:p></o:p>

The RM-project is part of a global configuration with three requirement components.

I have tried numerous variants of the query, but I always receive an empty response, see Response below

Furthermore, I receive attribute data when I sending a GET HttpRequest with the URI of the requirement.

I have read the examples in “” and found the start-up information as follows:<o:p></o:p>

·       Catalog Entry:<o:p></o:p>

o   https://x1.x2.x3.x4/rm/oslc_rm/catalog/<o:p></o:p>

·       Service Provider:<o:p></o:p>

o   https:// x1.x2.x3.x4/rm/oslc_rm/_u9BacHJ7EeuYaNFaR904Vg/services.xml<o:p></o:p>

·       Query Capability:<o:p></o:p>

o   https://x1.x2.x3.x4/rm/views?oslc.query=true&projectURL=https%3A%2F% x1.x2.x3.x4%2Frm%2Fprocess%2Fproject-areas%2F_u9BacHJ7EeuYaNFaR904Vg

Can anyone advise me to be able to properly connect and query the RM-project?




   OSLC-Core-Version: 2.0<o:p></o:p>

   Accept: application/rdf+xml



Response: <o:p></o:p>

<?xml version="1.0"?>

-<rdf:RDF xmlns:rdfs="" <o:p></o:p>

xmlns:rdf="" <o:p></o:p>

xmlns:dcterms="" <o:p></o:p>

xmlns:oslc_rm="" <o:p></o:p>

xmlns:oslc="" <o:p></o:p>

xmlns:nav="" <o:p></o:p>


-<oslc:ResponseInfo rdf:about="https://x1.x2.x3.x4/rm/views?oslc.query=true&"><o:p></o:p>


<dcterms:title>Query Results</dcterms:title><o:p></o:p>




<rdf:Description rdf:about="https://x1.x2.x3.x4/rm/views?oslc.query=true&projectURL=https%3A%2F%2Fx1.x2.x3.x4%2Frm%2Fprocess%2Fproject-areas%2F_u9BacHJ7EeuYaNFaR904Vg"> </rdf:Description><o:p></o:p>



Accepted answer

permanent link
Ian Barnard (662612) | answered Apr 06, 5:51 a.m.
edited Apr 07, 9:32 a.m.


In your query URL the HTTP query string parameters aren't specified correctly. I think the reference for this is

You have:
Which split into URL (the bit before the ?) and query parameters (first parameter is at the ?, subsequent parameters all must start with &) is:


Removing the parameter value encoding this is:

You can see that the and oslc.where parameters don't start with &

I'd expect this to look like:


When the parameter values are encoded these are:


And reassembled into a URL the query URL should be:

ALSO you must provide the configuration URL using a header Configuration-Context on the GET, with the value of the config URL.


magnus Elfving selected this answer as the correct answer

magnus Elfving commented Apr 08, 3:48 a.m.

Thanks Ian!

You are right,  I've got a  valid response from the server.


Your answer

Register or to post your answer.