RE: Question on double curly braces with HTTP Location

I think the intention was to support curly braces in URIs without them being
interpreted as templates.  That is, how would one set a location uri to the
literal uri "http://example.com?first={name}"?  WSDL will look for an
element named name to replace.  If I wanted the literal uri I'd have to
write it "http://example.com?first={{name}}".

 

To say it another way, the templating mechanism replaces any occurance of
{foo} with the value of the element foo, and any occurances of {{ or }} with
the single character { or } respectively.

 

Jonathan Marsh -  <http://www.wso2.com> http://www.wso2.com -
<http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com

 

  _____  

From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of John Kaputin (gmail)
Sent: Monday, December 18, 2006 3:45 AM
To: www-ws-desc@w3.org
Cc: woden-dev@ws.apache.org
Subject: Question on double curly braces with HTTP Location

 

Part 2 section 6.7.1.1 which describes the curly brace template syntax used
for {http location} contains the sentence:

"A double curly brace (i.e. "{{" or "}}") MAY be used to include a single,
literal curly brace in the request IRI."

I am a bit confused about why this sentence is here. I assume it is not
describing how to include a literal curly brace within the string enclosed
by matching curly braces in the WSDL because this string must be the local
name of an element, which by definition cannot contain a curly brace.

E.g.   whttp:location="?first={First{{Name}" is meaningless because
'First{Name' is not a valid local name.

So instead it seems to describe how to include a curly brace within the
value substituted for the local name enclosed within matching curly braces
during the construction of the request IRI. 

E.g. for whttp:location="?first={FirstName}", FirstName might be substituted
with the value 'Marvin{{' in the request IRI which represents the literal
value 'Marvin{'

Is this correct? If so, does this need to be specified here in Part 2 - it
seems it belongs in the specification that describes how to construct the
message (e.g. HTTP spec for an HTTP request)? If my understanding is
incorrect could someone please explain with some examples.

thanks,
John Kaputin.