W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > April 2009

Issue 6413-D: Dropped Boxcarring. Was: Issue 6413: WS-Transfer with Extensible Fragment Support

From: Geoff Bullen <Geoff.Bullen@microsoft.com>
Date: Fri, 10 Apr 2009 16:51:44 -0700
To: "public-ws-resource-access@w3.org" <public-ws-resource-access@w3.org>
Message-ID: <5AAAA6322448AA41840FC4563A30D6E8439E644FC5@NA-EXMSG-C122.redmond.corp.microsoft.com>
Issue D: Dropped Boxcarring

The proposal drops the concept of boxcarring from RT.  This would be one way to resolve issue 6422 [1].  It would seem that if we want to move forwards with this proposal, we must now first decide on our desired resolution for issue 6422.  If the group's resolution for 6422 is not to drop boxcarring, then this proposal would obviously not align with that decision.

--Geoff

[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=6422

From: public-ws-resource-access-request@w3.org [mailto:public-ws-resource-access-request@w3.org] On Behalf Of Katy Warr
Sent: Wednesday, March 25, 2009 9:23 AM
To: public-ws-resource-access@w3.org
Cc: David Snelling; Doug Davis
Subject: Issue 6413: WS-Transfer with Extensible Fragment Support


Following discussions on issue 6413 during the March F2F, Dave and I were tasked to create a new proposal that integrated basic fragment support (from WS-RT) into WS-T: http://www.w3.org/2002/ws/ra/tracker/actions/39.

Dave, Doug and I have worked on this and have the following proposal:

A key requirement of this action item was minimum change to the core WS-T specification (as the amount of change to the WS-T spec was a concern with the initial proposal).  With this in mind, our proposal adds only an optional 'Dialect' attribute to each operation.  This attribute specifies how the extensibility elements in the in the body will be processed - thus providing a fully extensible mechanism to the WS-Transfer spec, but with minimum changes.

We were sensitive to the fact that WS-T implementations should not need to process the soap body unnecessarily.  The dialect attribute has the useful side effect of indicating whether processing of extensibility elements in the soap body is required.   More importantly, its absence indicates when processing is not required.  For the Get and Delete operations, (where processing of the body is not necessary if there is no extensibility), we state: "When this attribute is not present, child elements of the wst:Get MUST be ignored."

In terms of dialect definition, we have defined one dialect only: XPath Level 1 Expression Dialect and this is contained in Appendix A.  Implementation of this dialect is optional and other (optional) dialects may be defined by other specifications.  The XPath Level 1 Expression Dialect was chosen because it satisfies the core fragment use cases without introducing additional complexity.   XPath Level 1 restricts the evaluation of an XPath 1.0 expression to a single element thus providing simple fragment support for the majority of use cases.  Multiple elements could still be targeted via an XPath Level 1 expression by inclusion of a parent element by the application to encapsulate child multiple elements.

Note the following with respect to the defined  XPath Level 1 expression dialect:
- We have restricted the dialect to disallow multiple fragment support (i.e. only one expression/fragment per request).   Again, this was to ensure that we were covering core use case without introducing unnecessary complexity.
- For simplification, we have not introduced the Put 'Mode' element from WS-RT.  Fragment deletion may be performed with Delete and the XPath Level 1 expression dialect.  Fragment insertion may be performed with Create and the XPath L 1 Dialect.

Note that the schema has not been updated to reflect the proposal as it seemed prudent to await decision by the group prior to spending time on this.

The proposed document with markup in word and html is here:
http://www.soaphub.org/public/files/w3c/WSTWithBasicFragmenSupport.htm
http://www.soaphub.org/public/files/w3c/WSTWithBasicFragmenSupport.doc

Thanks,
Katy


________________________________


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
Received on Friday, 10 April 2009 23:52:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:48 UTC