RE: [WSUS] Sec 2.1.x Data Integrity --- does Unicode gurantees characterencoding interoperability?

>>[XML-JP] is an excellent summary of problems we face today but it does 
not 
>>suggest
>>a solution to them.  Perhaps we should suggest something better beyond 
>>pointing
>>to this document (if we can come up with somethinig better:-)

I think that the WSUS focuses on making scenarios rather than suggesting 
solutions. Some possible solutions may be described in the requirement 
document. Could you please post your solution to the mailing list? 

>My understanding is that 'use utf-8' is a solution. I think
>we are already proposing that. 
>The other solution that XML-JP
>is proposing is to register separate 'charset' labels for
>each of the variants. I think there was an attempt for actual
>registration, but it hasn't been followed through. 

My understanding is as well. So far, using utf-8 is a realistic solution 
for encoding interoperability in the Web Services.

>I would like to share my recent "discovery".  Our field peple told me 
that
>there are PDA-type or embeded device SOAP clients in Japan that only 
support
>Shift_JIS !
>This is obviously violation of XML spec, but the reality is such
>devices exist.  The manufactures probably chose to violate the spec 
because
>of the resource constraints.  Should we mention such situation?

If the WSUS describes a deviation scenario from existent specifications, I 
don't think that we can describe the problems and their solutions. If the 
point on your opinion is about resource constraints of PDA style devices, 
please post your scenarios about PDA-type or embedded device SOAP clients. 


Thanks, 
Kentaroh
+ + +
Kentaroh Noji : nojik@jp.ibm.com