[oslc-core] Alignment needed with TRS 2.0 and recent LDP-Paging specification changes

Jim des Rivieres Jim_des_Rivieres at ca.ibm.com
Thu Jun 12 14:42:30 EDT 2014


These changes look good.

re: "The first single-page resource of a Base MUST include a 
trs:cutoffEvent property."

Good point. Don't the same considerations apply to the 
ldp:membershipResource and ldp:hasMemberRelation properties (and perhaps 
rdf:type as well)? The client would need these values up front so that it 
can process single-page resources as it reads them.

Regards,
Jim



From:
Steve K Speicher <sspeiche at us.ibm.com>
To:
oslc-core at open-services.net, 
Date:
06/11/2014 03:28 PM
Subject:
Re: [oslc-core] Alignment needed with TRS 2.0 and recent        LDP-Paging 
specification changes
Sent by:
"Oslc-Core" <oslc-core-bounces at open-services.net>



I was able to make the updates to the TRS specification [1] to catch up 
with the current revision of the LDP-Paging specification [2].  Moved 
around some of the text and placed the bulk of paging related content 
named "Paged Base" as a subsection of "Base Resources".  This does not 
close issue TRS-9 [3] but I've updated it to reflect this. 

[1]: 
http://open-services.net/wiki/core/TrackedResourceSet-2.0/revision/4582/, 
http://open-services.net/wiki/core/TrackedResourceSet-2.0/ 
[2]: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html 
[3]: 
http://open-services.net/wiki/core/OSLC-Core-V2-Issues/#TrackedResourceSet-2.0-Issues 


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

> From: Steve K Speicher/Raleigh/IBM at IBMUS 
> To: oslc-core at open-services.net 
> Date: 04/10/2014 04:02 PM 
> Subject: [oslc-core] Alignment needed with TRS 2.0 and recent LDP-Paging 

> specification changes 
> Sent by: "Oslc-Core" <oslc-core-bounces at open-services.net> 
> 
> This issue has to do with OSLC TRS 2.0 specifications [1] usage of W3C 
LDP-
> Paging [2].  The W3C LDP WG has undergone some recent changes wrt to the 
way
> paging is representing using HTTP headers compared with expressing it 
with 
> the content.  Therefore I'd recommend bringing TRS in line with 
LDP-Paging 
> and marking it as awaiting stabilization as LDP WG continues to advance 
this draft. 
> 
> Let me know if there are any concerns with this approach. 
> 
> [1]: 
http://open-services.net/wiki/core/TrackedResourceSet-2.0/revision/4473/ 
> [2}: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-paging.html 
> 
> Thanks,
> Steve Speicher
> IBM Rational Software
> OSLC - Lifecycle integration inspired by the web -> 
http://open-services.net
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net
_______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20140612/c9cd9100/attachment-0003.html>


More information about the Oslc-Core mailing list