[oslc-core] Tracked Resource Set: trs:change vs trs:changes

[Steve K Speicher]

Since I haven't heard any objections and this seems like an obvious fix, 
I'm going to declare it 'closed' and make the proposed change to 
trs:change.

Thanks,
Steve Speicher
IBM Rational Software
OSLC - Lifecycle integration inspired by the web -> 
http://open-services.net


> From: Vivek Garg/Cupertino/IBM at IBMUS
> To: oslc-core at open-services.net
> Date: 03/26/2013 05:59 PM
> Subject: [oslc-core] Tracked Resource Set: trs:change vs trs:changes
> Sent by: "Oslc-Core" <oslc-core-bounces at open-services.net>
> 
> 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
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net