- From: James M Snell <jasnell@gmail.com>
- Date: Sun, 15 Oct 2006 12:51:52 -0700
- To: Jan Algermissen <jalgermissen@topicmapping.com>
- CC: uri@w3.org
URI Templates are primarily designed to go the other way (e.g. starting
with the {a}{b} and working to the "fredbarney". Parsing a URI to
determine the values of the parameters has generally been out of scope.
It's certainly possible to do (I've implemented it, in fact) but doing
so requires that each token be associated with a regex pattern that
extracts out the necessary bits.
- James
Jan Algermissen wrote:
>
> Hi,
>
> (sorry if this has been raised before)
>
> In the uritemplate draft there is the following example:
>
> http://example.org/{a}{b}/ --> http://example.org/fredbarney/
>
> I am having trouble to understand how a uritemplate parser is supposed
> to come up with a = fred and b = barney
> when parsing http://example.org/fredbarney/; e.g. a = f and b =
> redbarney is as good as a result.
>
> I'd say that templates like http://example.org/{a}{b}/ should be ruled
> out (there is a term for ambigous grammars like that,
> but I'd need to look that up and can't right now).
>
> Thanks,
>
> Jan
>
>
>
>
>
>
>
>
Received on Sunday, 15 October 2006 19:52:04 UTC