Steve, We discussed this at the Core meeting today. I suggest you use the member property of the container you are querying. If you don't want to define a container-specific member property, you could use the generic RDFS property rdfs:member [1]
[1] http://www.w3.org/TR/rdf-schema/#ch_member Regards, ___________________________________________________________________________ Arthur Ryman, PhD, DE Chief Architect, Project and Portfolio Management IBM Software, Rational Markham, ON, Canada | Office: 905-413-3077, Cell: 416-939-5063 Twitter | Facebook | YouTube From: Steve K Speicher <[email protected]> To: [email protected] Date: 07/27/2010 04:57 PM Subject: [oslc-core] Proposed change to JSON formatting rules for Query responses Sent by: [email protected] 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
