- From: Jeffrey Schlimmer <jeffsch@windows.microsoft.com>
- Date: Thu, 22 May 2003 14:06:38 -0700
- To: "WS-Description WG" <www-ws-desc@w3.org>
- Message-ID: <DDE1793D7266AD488BB4F5E8D38EACB8FD6A5A@WIN-MSG-10.wingroup.windeploy.ntdev.micr>
(Forwarding to the public list.)
Issue 6e [1] reads:
For http:urlReplacement it is not clear what should happen for "search
patterns" where there is no correspondingly named part in the message.
I propose that this be a fatal error; here is how it would look in the
current specification (marked in red underline):
3.3.1 Case of Input Parts Cited in location Attribute
The location attribute information item MAY cite input message parts to
be serialized in the path of the request URI by enclosing a part name
within curly braces (e.g. "{partName}"). When constructing the request
URI, each pair of curly braces (and enclosed part name) is replaced by
the corresponding part value. The value MUST be URI escaped.
A double curly brace (i.e. "{{" or "}}") MAY be used to actually include
a single, literal curly brace in the request URI.
Parts MUST NOT be cited more than once within the location attribute
information item.
<-- begin proposed addition -->
Strings enclosed within single curly braces MUST be input message part
names; any other strings enclosed within single curly braces are a fatal
error.
<-- end proposed addition -->
If cited input message parts are defined using an XML Schema type, they
MUST derive from xsd:simpleType but MUST NOT derive from xsd:hexBinary,
xsd:base64Binary, or any simple list type.
--Jeff
[1]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html#
x6e
Received on Thursday, 22 May 2003 17:07:21 UTC