Here's my initial reaction: - I argued for having a query shape, but we decided not to do so. - Each domain will need to define what the shape of query results will be, if there is a result collection, etc.
Let's cover this one in the workgroup meeting today. Thanks, - Dave On Tue, Jul 27, 2010 at 4:56 PM, Steve K Speicher <[email protected]> wrote: > Current JSON guidance [1] doesn't address what the result array name > should be. > > I recommend that we use "oslc:results" array, like for delegated UIs [2] > > See also example at [3], how does a consumer know to look for array named > "oslc_blog:comment" in this example. I think it would be best to use a > general OSLC property. > So this example would become: > "oslc:results" : [{ > "oslc:qname" : "oslc_blog:BlogComment", > "rdf:resource" : "http://example.com/blogs/comment/346";, > }, > > [1] > http://open-services.net/bin/view/Main/OSLCCoreRepresentationsGuidance#Guidelines_for_JSON > [2] > http://open-services.net/bin/view/Main/OslcCoreSpecification#Delegated_User_Interface_Dialogs > [3] > http://open-services.net/bin/view/Main/OSLCCoreSpecAppendixD#Query_Resource > > Thanks, > Steve Speicher | IBM Rational Software | (919) 254-0645 > > > _______________________________________________ > Oslc-Core mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-core_open-services.net >
