|
List Info
Thread: Question on double curly braces with HTTP Location
|
|
| Question on double curly braces with
HTTP Location |

|
2006-12-18 11:44:42 |
|
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{" 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.
|
| Question on double curly braces with
HTTP Location |

|
2006-12-19 22:42:28 |
|
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=̶1;?
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={}221;.
To say it another way, the templating
mechanism replaces any occurance of with the value of the element foo,
and any occurances of {} with the single character respectively.
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{" 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.
|
[1-2]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|