Issues with constructing an oslc.where URL and valid XML results

Hi Jim,
Sadly, the alteration of the where clause continues to produce the same results.  The issue isn't even related to dc:identifier or any specific prefix, but all prefixes or attempts at filtering.  I've attempted virtually filtering on virtually all prefixes I can identify in the XML by visual inspection, with nary a variation in result.

The returned XML still contains no namespace specifications in the results, but I've found my way around that with some post processing on my own.  My biggest issue is the attempt, via an oslc.where clause, to return, in XML, a list of all Change Requests to which a given user subscribes.  While that is clearly more complicated than what I provided in my example, it was meant to demonstrate the issues I'm experiencing while attempting to use that oslc.where clause for even simple filtering. 

Thanks!

Jim,
The issue isn't just restricted to the dc prefix, which is defined in the oslc_cm:Collection root node for the result set.  Literally any attempted use of the oslc.where clause in the URL returns the same set of results, regardless of parameter or identifier. 

Thanks!

I think that oslc_cm:Collection is from OSLC 1.0 and in that version you need to use oslc_cm.query=dc:identifier=... to filter results. See http://open-services.net/bin/view/Main/CmQuerySyntaxV1#Query_Syntax

Fernando,
Changing the Accept header did produce something different.  Unfortunately, it's an Error 406 from the server.  However, I still consider this a step in the right direction, as it tells me something is coming back that I just can't seem to process correctly.  I'm still investigation the URL change you suggested. 

Thanks!

 Normally, I only got the 406 error when I forget to include the accept header. Could you share the code that create the url and execute the GET request?