[oslc-core] ChangeLog Proposal Finalization

[Samit Mehta]

Hi Frank,

I wanted to clarify the following regarding your proposal for the 
ChangeLog.

Based on my understanding is that the OSLC client wishing to build a 
queryable index would:
        a) query the resources using simple queries that are already 
documented by OSLC specs
        b) use the change log URI to get "notified" of changes to that 
service provider's resources

Wouldn't there be a significant overlap of the data returned by each HTTP 
GET of the Change Log URI?  If a server doesn't truncate the log for say 
seven days, then over that period the change log would  keep growing and 
will include a large number of change log entries that were already 
processed by the client.

Did I misunderstand your proposal?  Couldn't we design something where the 
client has more control over what change log entries are returned - e.g. 
specify that the provider return the change log entries with entry 
sequence number greater than X, where X is the entry sequence number of 
the sequentially last change log entry that client has already processed?

Also, would you agree that the proposed change log could be used for 
integration scenarios where an OSLC client is needing to react to changes 
to a set of resources?  In such cases, it would be useful if the OSLC 
client could specify the list of resources (especially if it is a small 
set) that it is interested in monitoring changes to - i.e. the client 
could specify that the change log entries associated to a specified set of 
resources be returned.

Regards,
____________________________________________
Samit Mehta
(512) 323-9350 - Work
mailto:samit.mehta at us.ibm.com
IBM Rational Software - Business Development


oslc-core-bounces at open-services.net wrote on 03/29/2011 11:26:13 AM:

> From: Frank Budinsky <frankb at ca.ibm.com>
> To: oslc-core at open-services.net
> Date: 03/29/2011 11:29 AM
> Subject: [oslc-core] ChangeLog Proposal Finalization
> Sent by: oslc-core-bounces at open-services.net
> 
> Hi all,
> 
> We're very close to finalizing the OSLC ChangeLog proposal. The last
> three issues, which are still being discussed are:
> 
> 1. Indexing/ChangeLog resources/scope
> Latest email: http://open-services.net/pipermail/oslc-core_open-
> services.net/2011-March/000898.html
> 
> 2. ChangeLog Pagination (also URI-addressable ChangeLog entries)
> Latest email: http://open-services.net/pipermail/oslc-core_open-
> services.net/2011-March/000893.html
> 
> 3. Better name for OSLC indexing profile
> Latest email: http://open-services.net/pipermail/oslc-core_open-
> services.net/2011-March/000896.html
> 
> We're planning/hoping to finish the discussion of the ChangeLog 
> proposal at tomorrow's OSLC WG meeting, so please send any 
> additional comments or ideas that you have by replying to this or 
> one of the discussion thread emails.
> 
> Thanks to everyone that has provided input so far.
> 
> Frank._______________________________________________
> 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/20110329/28991ba7/attachment-0003.html>