Updated proposal for 168: type of referenced data

 Hello all. 8-)
 During last week's WG telcon we discussed the issue 168 and
the ETF was tasked to include a proposal for handling situations 
where the type of a node cannot be determined on the receiver. So 
here's our expanded proposal:

 We propose that we add a text into the encoding section 
(probably near the encoding rule #2) to this effect:
 "In case the receiving node cannot determine the xsi:type of a
node, for example because it doesn't follow a schema during
deserialization and the types are expressed in a schema, the node
MAY generate a fault with the faultcode of env:Sender and the
subcode of enc:UntypedValue."

 It is not really clear that the faultcode should be Sender, but 
since it can be expected that the same request will always fail, 
it kind of fits the description of Sender faults. If people think 
a Receiver fault would be more appropriate, I'm ready to accept 
that.

 Best regards,

                   Jacek Kopecky

                   Senior Architect, Systinet (formerly Idoox)
                   http://www.systinet.com/

Received on Monday, 28 January 2002 12:43:35 UTC