+1 Regards, ___________________________________________________________________________
Arthur Ryman DE, Chief Architect, Reporting & Portfolio and Strategy Management IBM Software, Rational Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) From: Vivek Garg <[email protected]> To: [email protected], Date: 03/26/2013 05:57 PM Subject: [oslc-core] Tracked Resource Set: trs:change vs trs:changes Sent by: "Oslc-Core" <[email protected]> Tracked Resource Set specification 2.0 [1] defines the trs:changes property, a multi-valued property, to specify a list of change events. An example from the spec is as follows: <http://cm1.example.com/trackedResourceSet> a trs:TrackedResourceSet ; trs:base <http://cm1.example.com/baseResources> ; trs:changeLog [ a trs:ChangeLog ; trs:changes <#3>, <#2>, <#1>. ] . If the abbreviated form of trs:changes was expanded, it would look as follows: <http://cm1.example.com/trackedResourceSet> a trs:TrackedResourceSet ; trs:base <http://cm1.example.com/baseResources> ; trs:changeLog [ a trs:ChangeLog ; trs:changes <#3>; trs:changes <#2>; trs:changes <#1>. ] . Since each property is an entry for a single change, my suggestion is that we use trs:change as the property name instead of the plural form. This suggestion was originally made by Joe Ross in Lifecycle Query WG call. I am re-surfacing it for consideration by the Core WG. [1] http://open-services.net/wiki/core/TrackedResourceSet-2.0/#Change-Log Regards Vivek_______________________________________________ Oslc-Core mailing list [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
