- From: Edwin Ortega <ortegae@wns.net>
- Date: Wed, 16 Jan 2002 15:05:03 -0800
- To: "Henrik Frystyk Nielsen" <henrikn@microsoft.com>, "Christopher Ferris" <chris.ferris@sun.com>, <xml-dist-app@w3.org>
----- Original Message ----- From: "Henrik Frystyk Nielsen" <henrikn@microsoft.com> To: "Christopher Ferris" <chris.ferris@sun.com>; <xml-dist-app@w3.org> Sent: Wednesday, January 16, 2002 9:53 AM Subject: RE: IDREF vs HREF for graph edges in SOAP encoding > > Yes, the SOAP spec doesn't define an encoding/decoding processor; it > defines for better or for worse a mechanism by which data can be encoded > based on the SOAP data model. How that mechanism is implemented is > entirely up to the implementer. IMO, as spec writers we have nothing to > say about specific implementation choices. In this context, I do not > preclude or assume any of the possible solutions you mention. > > Henrik > > >Are you suggesting that the SOAP spec(s) don't define > >an entity equivalent to the "SOAP (de|en)coding processor" > >and hence we have nothing to say about it? Or, are you > >suggesting that in your view, the (de|en)coding function is > >exclusively an "application" function and hence we have > >nothing to say about it? > >
Received on Wednesday, 16 January 2002 14:07:58 UTC