[OSLC] Reporting Domain

[Benjamin Williams]

Hi Arthur

Its a terminology issue for sure.

Many might associate links with traceability relationships, as opposed to 
logically nested data (what I believe is really being referred to here)

e.g. 

When we want to retrieve all of the requirements within a DOORS module, 
that is logically nested data.
Linked data might be test cases associated with each requirement.

In the first case, we would expect to be able to retrieve all the required 
data for those requirements in a single call.
In the second case we would expect to need 2 calls to retrieve all of the 
requirements and all of the test cases.


/Ben

-----------------------------------------------------------------------------
Benjamin Williams
Senior Product Manager - Rational Publishing Engine

Email: bwilliams at uk.ibm.com
Tel: +44 20 8818 4360
Cell: +44 7710 637 067
IBM Extension: 364360
IBM ITN: 37364360
-----------------------------------------------------------------------------



From:
Arthur Ryman <ryman at ca.ibm.com>
To:
Benjamin Williams/UK/IBM at IBMGB
Cc:
community at open-services.net, community-bounces at open-services.net
Date:
01/09/2009 14:09
Subject:
Re: [OSLC] Reporting Domain




Ben, 

The intended meaning was to include properties from linked data. I don't 
see the ambiguity. The goal is to avoid multiple GET calls. 

Arthur Ryman, IBM DE
Chief Architect, Rational Project and Portfolio Management
Office: 905-413-3077, Cell: 416-939-5063
Assistant: Nancy Barnes, 905-413-4182 


Benjamin Williams <bwilliams at uk.ibm.com> 
Sent by: community-bounces at open-services.net 
08/12/2009 04:28 PM 


To
community at open-services.net 
cc

Subject
[OSLC] Reporting Domain








Ref: http://open-services.net/bin/view/Main/ReportingHome 

One of the key requirements for a reporting consumer is what is being 
referred to as inlining. 
This was formerly named 'Self Contained XML' 

inlining - linked data should be inlined in the response to reduce the 
number of requests 

I believe that this description should be modified to avoid ambiguity and 
misunderstanding. 

I think most people will understand that definition as meaning the data 
from linked resources rather than its intended meaning of a full set of 
self contained data being returned for the initial query (vs the common 
OSLC model of atomic transactions) 

I suggest modifying this definition as below: 

inlining - all queried data should be returned inline in the response with 
no need for further HTTP GET requests 

Regards 


/Ben

-----------------------------------------------------------------------------
Benjamin Williams
Senior Product Manager - Rational Publishing Engine

Email: bwilliams at uk.ibm.com
Tel: +44 20 8818 4360
Cell: +44 7710 637 067
IBM Extension: 364360
IBM ITN: 37364360
-----------------------------------------------------------------------------



Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU 





_______________________________________________
Community mailing list
Community at open-services.net
http://open-services.net/mailman/listinfo/community_open-services.net






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20090901/976a1253/attachment-0003.html>