Hey Jim, Thanks for the review
> From: Jim des Rivieres <[email protected]> > To: [email protected] > Cc: Steve K Speicher/Raleigh/IBM@IBMUS > Date: 06/12/2014 02:42 PM > Subject: Re: [oslc-core] Alignment needed with TRS 2.0 and recent LDP-Paging > specification changes > > These changes look good. > > re: "The first single-page resource of a Base MUST include a trs:cutoffEventproperty." > > 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. Right, that seems like a necessary change. Perhaps one reason if it were just an ldp:BasicContainer it wouldn't have this problem. Either way, I think it reasonable to add this restriction. If I don't hear any objection/concerns in the coming week(s), I will make the change. Thanks, Steve Speicher IBM Rational Software OSLC - Lifecycle integration inspired by the web -> http://open-services.net > Regards, > Jim > > > From: > > Steve K Speicher <[email protected]> > > To: > > [email protected], > > 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" <[email protected]> > > > > > > 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@IBMUS > > To: [email protected] > > 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" <[email protected]> > > > > 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 > > [email protected] > > http://open-services.net/mailman/listinfo/oslc-core_open-services.net > _______________________________________________ > Oslc-Core mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-core_open-services.net >
