W3C home > Mailing lists > Public > public-media-fragment@w3.org > September 2009

Re: URI templates (was Re: fragment or sub-resources)

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Mon, 21 Sep 2009 13:33:03 +1000
Message-ID: <2c0e02830909202033s627207fdv57fd4a3b0593bd8b@mail.gmail.com>
To: Jack Jansen <Jack.Jansen@cwi.nl>
Cc: RaphaŽl Troncy <Raphael.Troncy@cwi.nl>, Yves Lafon <ylafon@w3.org>, public-media-fragment@w3.org
2009/9/21 Jack Jansen <Jack.Jansen@cwi.nl>:
> On 20 sep 2009, at 03:19, Silvia Pfeiffer wrote:
>>>> [1] http://tools.ietf.org/html/draft-gregorio-uritemplate-03
> URI templates look potentially interesting, but there's one big problem:
> their use of { and } for expressions. Because these are already used by
> Attribute Value Templates. These are part of XSL
> (http://www.w3.org/TR/xslt20/#attribute-value-templates), are also used in
> SMIL 3.0 (http://www.w3.org/TR/2008/REC-SMIL3-20081201/smil-state.html#q48),
> and (I think) considered for inclusion by the XForms people
> In these languages, it is the host language that implements the {}
> substitution, and therefore defines the grammar inside the curly braces.
> (XPath in XSL, and XPath by default, but overridable on document level in
> SMIL).
> It seems that this use of curly braces would conflict with uri-templates...

Or maybe URI templates took the idea and generalised it. It may not
conflict, but just standardise it. But I'm not an expert.

Received on Monday, 21 September 2009 03:34:04 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 21 September 2011 12:13:34 GMT