RE: Issue with encodingStyle

The encodingStyle attribute was added in late 1999 in an attempt to
de-emphasize (and arguably deprecate) section 5.  Prior to the
encodingStyle attribute, we MANDATED section 5 EVERYWHERE (emphasis is
important).

As XML Schemas converged on what we needed for a representational type
system and metadata format, the encodingStyle attribute was added to
indicate that pre-XML Schema XML was being used. 

DB



> -----Original Message-----
> From: noah_mendelsohn@us.ibm.com [mailto:noah_mendelsohn@us.ibm.com]
> Sent: Saturday, February 09, 2002 4:44 AM
> To: tjewald@develop.com
> Cc: XMLDISTAPP
> Subject: Re: Issue with encodingStyle
> 
> >> So why not do away with the encodingStyle attribute altogether?
> 
> It greatly facilitates the construction of middleware, especially
bindings
> to programming languages.  While it's true that SOAP processors can
handle
> any message, with or without identified encoding, the idea is that a
SOAP
> processor can provide a richer service when it knows the encoding.
For
> example, many SOAP processors will do a very useful job of mapping to
> programming languages like Java or to ORB-like systems such as .Net.
If
> you only know that it's XML, there tends to be less that you can do.
> Without the encoding, the tendency is that each SOAP application has a
bit
> more work to do.
> 
> ------------------------------------------------------------------
> Noah Mendelsohn                              Voice: 1-617-693-4036
> IBM Corporation                                Fax: 1-617-693-8676
> One Rogers Street
> Cambridge, MA 02142
> ------------------------------------------------------------------
> 
>

Received on Sunday, 24 February 2002 05:27:27 UTC