- From: Kinateder, Markus <markus.kinateder@sap.com>
- Date: Thu, 30 Aug 2001 09:37:09 +0200
- To: "'www-ws@w3.org'" <www-ws@w3.org>
Hello Jeff,
as you said:
"...the string content of an element of the required type is a valid value
for the corresponding HTTP GET parameter."
So maybe constructions like that would be possible:
<types>
<schema>
<complexType name="versionType">
<all>
<element name="someElement" type="simpleType1" minOccurs="0"/>
</all>
</complexType>
<complexType name="requestType">
<all>
<element name="someElement" type="simpleType2"/>
</all>
</complexType> <!-- further type definitions -->
</schema>
</types>
<message...>
<part name="VERSION" type="versionType"/>
<part name="REQUEST" type="requestType"/>
</message>
Valid elements of the defined types (in XML representation) would look like:
<VERSION>
<someElement>1.1</someElement>
</VERSION>
or
<VERSION/>
and
<REQUEST>
<someElement>GetQuote</someElement>
</REQUEST>
The string content of those elements is "1.1", "" and "GetQuote",
respectively. As you said, this gives valid values for the HTTP GET
parameters.
In this picture the type of a HTTP GET-Parameter would be the concatenation
of all "TextNode-Types" contained within the element- or type-definition
referenced in the message part. The name of the HTTP GET-Parameter still
could remain the name of the message part.
Best regards,
Markus
Received on Thursday, 30 August 2001 03:37:45 UTC