RE: HTMLEncoding

[Martin W Sachs <mwsachs@us.ibm.com>]

Dale,

Thanks for the reference.  That text indeed looks like it is what  I am
looking for although the word "HTMLEncoding" is never used.

As to why we are including information about encoding schemes, the reason
is that this is one of several areas (especially security) that was lifted
from IBM's tpaML and still needs scrubbing.  To the extent that the
combination of transport protocols, packaging protocols, and language
specifications removes any element of choice, the function in question
(e.g., transport encoding) should be deleted.  We should definitely discuss
this in Vancouver but we really need the draft packaging section of our
specification in front of us to discuss the subject.

Actually, we should try to move as far along as we can before Vancouver so
that much of our effort in Vancouver can be devoted to preparing the next
QR submission, which should be no later than the end of the Vancouver
meeting.

Regards,
Marty
*************************************************************************************

Martin W. Sachs
IBM T. J. Watson Research Center
P. O. B. 704
Yorktown Hts, NY 10598
914-784-7287;  IBM tie line 863-7287
Notes address:  Martin W Sachs/Watson/IBM
Internet address:  mwsachs @ us.ibm.com
*************************************************************************************



"Moberg, Dale" <Dale_Moberg@stercomm.com> on 01/25/2001 01:39:58 PM

To:   Martin W Sachs/Watson/IBM@IBMUS, ebxml-tp@lists.ebxml.org
cc:
Subject:  RE: HTMLEncoding




Try

http://www.w3.org/TR/html4/charset.html#entities

sections 5.3.1 and 5.3.2

I think this may be a description of the
encoding scheme you mention.

I did at one time ask why we were including
information about encoding schemes since
they are already specified by the combinations
of transport protocols, packaging
protocols, and language specifications.

I would like that general issue still
on the table for Vancouver.

> -----Original Message-----
> From: Martin W Sachs [mailto:mwsachs@us.ibm.com]
> Sent: Thursday, January 25, 2001 1:20 PM
> To: ebxml-tp@lists.ebxml.org; ebxml-transport@lists.ebxml.org
> Subject: HTMLEncoding
>
>
> The CPP-CPA specification mentions a form of transport encoding called
> HTMLEncoding.  This mention is inherited from IBM's tpaML.
> HTMLEncoding is
> a data transformation scheme in which certain characters in
> the payload of
> a message sent by HTTP are transformed so that a receiving
> browser won't
> attempt to process them.  An example is replacement of < by &lt.
>
> I have been unable to find a reference to a specification of
> HTMLEncoding.
> If it is mentioned in the CPA-CPP specification, there should be a
> reference to its specification.
>
> Can someone point me to a specification for HTMLEncoding?
>
> Regards,
> Marty
>
> **************************************************************
> ***********************
>
> Martin W. Sachs
> IBM T. J. Watson Research Center
> P. O. B. 704
> Yorktown Hts, NY 10598
> 914-784-7287;  IBM tie line 863-7287
> Notes address:  Martin W Sachs/Watson/IBM
> Internet address:  mwsachs @ us.ibm.com
> **************************************************************
> ***********************
>