- From: Marc Hadley <Marc.Hadley@Sun.COM>
- Date: Wed, 25 Jun 2008 10:26:39 -0400
- To: Anthony Bouch <anthony@abouch.com>
- Cc: "'Joe Gregorio'" <joe@bitworking.org>, "'URI'" <uri@w3.org>
I think a profile of the spec is needed for matching. E.g. {a}{b} is
ambiguous for matching since you don't know where {a} ends and {b}
starts in a given URI. We are only using the basic {var} syntax in JSR
311 (http://jsr311.dev.java.net/) for matching.
Marc.
On Jun 24, 2008, at 8:58 PM, Anthony Bouch wrote:
>
> I've been following the list, and have just looked at Draft 03 of
> the uri
> template spec.
>
> I understand how the uri template specification can be implemented for
> template expansion - but was wondering about template matching. Does
> this
> specification expect that implementers will offer template matching
> - i.e.
> parsing back to variables from a Uri for a given a template?
>
> --Tony
>
> -----Original Message-----
> From: uri-request@w3.org [mailto:uri-request@w3.org] On Behalf Of Joe
> Gregorio
> Sent: Saturday, April 05, 2008 3:19 AM
> To: URI
> Subject: draft-gregorio-uritemplate-03.txt
>
>
> Draft 03 of the uri template spec has been published:
>
> http://www.ietf.org/internet-drafts/draft-gregorio-
> uritemplate-03.txt
>
> HTML and diffs are available here along with an updated
> template explainer service:
>
> http://bitworking.org/projects/URI-Templates/
>
> I've folded in much of the feedback from the last draft.
>
> Here are the revision history notes:
>
> Added more examples. Introduced error conditions and defined
> their handling. Changed listjoin to list. Changed -append to
> -suffix, and allowed -prefix and -suffix to accept list variables.
> Clarified the handling of unicode.
>
>
> Thanks,
> -joe
>
> --
> Joe Gregorio http://bitworking.org
>
>
>
>
>
---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.
Received on Wednesday, 25 June 2008 14:27:21 UTC