Re: [wsrp] Public Review comment: encoding in entity character refs

[Rich Thompson <richt2@us.ibm.com>]

This is the difference between full
URL decoding and entity dereferencing. The spec only requires the later
while full URL decoding would recognize the entity reference even if all
of the characters were escaped into their hexadecimal form. 

Can anyone provide numbers for the performance
impact of requiring full URL decoding so that we can compare it against
the value (?) of supporting such encodings?

Rich

Michael Freedman <michael.freedman@oracle.com>

06/27/06 06:14 PM

To	wsrp <wsrp@lists.oasis-open.org>
cc
Subject	[wsrp] Public Review comment:  encoding in entity character refs

Section 10.2.1 states:
Consumers MUST accept both the "&" character and the corresponding
entity reference (i.e. "&") as separators between the
name/value 
pairs as this allows Portlets to produce markup fragments valid for a 
larger range of mime types. We encourage Portlets to use the entity 
reference form ("&") in static markup as this is likely
to result in 
the ability to include that markup in a larger set of enclosing mime types.

An issue has come up concerning client code that has been over ambitious
and URL encoded the ; of the & -- i.e. it emits &amp%3b.  As
the use 
in this case isn't reserved by HTML urls (though ; is a reserved 
character) should consumers treat &amp%3b as equivalent to &?
 It 
appears that browser do so.
     -Mike-

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs
in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php