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 <[email protected]> Sent by: [email protected] 08/12/2009 04:28 PM To [email protected] 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: [email protected] 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 [email protected] http://open-services.net/mailman/listinfo/community_open-services.net
