Tack, In your sample writeup you suggest adding a property to the Query Capability. <oslc:isResourceNodeQuery>true</oslc:isResourceNodeQuery>
I recently added this to the spec, but it's named oslc:isMultiSubject. "true" means more than one subject (result if rdf:RDF), "false" means a single subject node (result is rdf:Description). 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: Tack Tong/Toronto/IBM@IBMCA To: [email protected] Date: 04/15/2010 11:34 AM Subject: [oslc-core] Example Use Case for the Core Sent by: [email protected] I built an example for the Core using one of the Reporting Use Case. to illustrate how the Core can be used in an end to end scenario (Service Provider Resource....Query Capability.....Resource Shape Resource.......Query Syntax.....Query Resource.....RDF/XML representation) to validate my understanding of the Core (please give me feedback if I misuse and let me know what is the right way) through this experience, to identify any issues or questions (I highlighted those in red in the doc. Dave, I would appreciate responses on those and whether I need to raise formal issues in the Issue page.) use this example to help the Reporting WG to understand the Core use this example as the base for the Reporting Spec. Implementation Validation work Dave, you asked for examples for the Core. You are welcome to take any snippets from this example, edit and include in the Core, if you feel appropriate. (See attached file: oslc implementation 100412.doc) Tack Tong IBM Rational software [email protected] 905-413-3232 tie line 313-3232_______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
<<attachment: oslc_implementation_100412.doc>>
