Re: DR 202: custom encodings?

> As proposed by Stuart in [1], I suggest we delete the second sentence
> from this requirement; and that we eventually also drop custom
> encoding (this was also suggested by Hervé).
> 
>               The XML Protocol will allow applications to include
>               custom encodings for data types used for parameters
>               and results in RPC messages.
> 
> Or else we should really emphasize the fact that applications using
> custom encodings WILL NOT be XP compliant.

Why?  In a similar situation, CORBA passes objects by value, which are 
then mapped locally on either end to a native object or type, that isn't 
defined in the CORBA definition.  You have to have the value type 
definition on both ends for it to work.  But passing an object by value 
does not make you non-CORBA-compliant.  I suspect certain bindings may 
have quite common custom encodings, while other particular uses may 
introduce them.

Ray Whitmer
rayw@netscape.com

Received on Wednesday, 15 November 2000 18:31:13 UTC