Thanks, Steve Speicher | IBM Rational Software | (919) 254-0645
[email protected] wrote on 03/14/2012 10:05:40 AM: > From: Ian Green1 <[email protected]> > To: [email protected], > Cc: Brett Graf <[email protected]> > Date: 03/14/2012 10:08 AM > Subject: [oslc-core] Question on oslc.properties > Sent by: [email protected] > > Would someone confirm/clarify the behaviour of oslc.properties in the case > of resources containing blank nodes? > > > Consider the following RDF (turtle): > > @prefix dc: <http://purl.org/dc/terms/>. > @prefix oslc_rm: <http://open-services.net/ns/rm#>. > @prefix foaf: <http://xmlns.com/foaf/0.1/>. > @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>. > @prefix doors: <http://doors.example.com/req/>. > > doors:r1 a oslc_rm:Requirement; > dc:title "Title"; > dc:contributor [ a foaf:Person; foaf:givenName "caligula" ]. > > > The following request > GET /req/r1?oslc.properties=* > Host: doors.example.com > > Will return the following RDF: > @prefix dc: <http://purl.org/dc/terms/>. > @prefix oslc_rm: <http://open-services.net/ns/rm#>. > @prefix foaf: <http://xmlns.com/foaf/0.1/>. > @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>. > @prefix doors: <http://doors.example.com/req/>. > > doors:r1 a oslc_rm:Requirement; > dc:title "Title"; > dc:contributor [ ]. > > > Which is not really that useful. Nested properties could be requested but > this may include more information that desired. Beyond V2, what might be > more useful is a concise bounded description [1] of the blank node to be > included in the response. Well if a client want to get specific, it could just use: GET /req/r1?oslc.properties=dc:title,dc:contributor{*} > Any comments or clarifications? > > [1] http://www.w3.org/Submission/2004/SUBM-CBD-20040930/ What would the priority of this be for immediate resolution? Looks at our list of items, seems like it is fairly narrow and not necessarily a widespread problem. Please confirm/deny. - Steve
