RE: Elaborate: Cannot be Serialized as XML 1.0

In response to this issue [1], the Working Group agreed to rework this
text to make it clear that we are talking about the version of XML, and
to clarify that this is due to unserializable constructs in the XML
itself, and not related to validity under a particular version of XML
Schema.  We'll assume you agree with this resolution if we don't hear
from you in 2 weeks.

[1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC23

> -----Original Message-----
> From: public-ws-desc-comments-request@w3.org [mailto:public-ws-desc-
> comments-request@w3.org] On Behalf Of Asir Vedamuthu
> Sent: Tuesday, August 24, 2004 5:12 AM
> To: 'public-ws-desc-comments@w3.org'
> Cc: Christopher St. John
> Subject: Elaborate: Cannot be Serialized as XML 1.0
> 
> 
> I am writing this issue on behalf of Christopher St. John, webMethods.
> 
> ref: http://www.w3.org/TR/2004/WD-wsdl20-20040803/#component_model
> 
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-
> issues.html#x177
> 
> "This document does not specify a means of producing an XML Infoset
> representation from a given set of WSDL components. Furthermore, given
a
> particular serialization, not all valid sets of components need be
> serializable to it. For instance, due to the use in the component
model of
> types that cannot be described using XML schema (.e.g wsdls:string),
it is
> possible to come up with a valid set of WSDL components that cannot be
> serialized as an XML 1.0 document."
> 
> Last two sentences (above) sound very serious. I understand the issue
and
> reasoning behind it. But, this paragraph does not provide sufficient
> information to first time readers. I request the editors to elaborate
on
> why
> components cannot be serialized as an XML 1.0 doc and provide a link
to
> the
> section that describes wsdl simple types.
> 
> Regards,
> Asir S Vedamuthu
> asirv at webmethods dot com
> http://www.webmethods.com/

Received on Friday, 29 October 2004 22:35:31 UTC