- From: Marc Portier <marc.portier@gmail.com>
- Date: Tue, 12 Jul 2011 21:58:20 +0200
- To: "Roy T. Fielding" <fielding@gbiv.com>
- CC: URI <uri@w3.org>
Hi Roy, Haven't got the time yet to update the js implementation, but wanted to already give some feedback on a first read... [general] It surely gives a simplified and more natural first impression then previous iteration. But I should probably get into the implementation details before re-asserting that. [section 1.2] * The Level 2 examples already use {x}, so I guess you should add it in the section of defined variables: x := "1024" * The Level 3 examples contain a glitch I think: {+path,x}/here should expand to /foo/bar1024/here and not /foo/bar/1024/here * The Level 4 examples all expand {keys} to a bigger structural content then provided in the variable-definition section I suppose it should be keys := [("semi", ";"),("dot","."),("comma","'")] (comma is not in the definition, but it is in all expansions) [section 3.2.4] * samples are not using the .-dot-prefix label expansion, but the simple string expansion [section 3.2.5] * similar: samples are not using the /-slash-prefix path expansion And one comment of a less serious nature: [section 1] * somehow http://example.com/search?q=chien&lang=fr makes more sense then http://example.com/search?q=dog&lang=fr Anyway, I hope the other comments are more useful, and I hope to get back soon with feedback from my updated js-implementation. regards, -marc= On 12-07-11 02:40, Roy T. Fielding wrote: > I have made another attempt to get consensus on the URI Template > spec by removing some of the obscure bits of draft 04 and splitting > the templates into four levels of implementation. Unfortunately, > I did not have enough time to go back though all the comments on > draft 04 from last year, and there are still a few sections that > are TBD. > > I chose the levels based on perceived complexity, but am not wedded > to any specific order or clustering. For example, it would probably > make more sense to have prefix modifiers in Level 2. > > The only radical change to the syntax is changing the default > specifier delimiter from "=" to "|" and then allowing "=" to > appear in the default value. The suffix, remainder, and labelled > explode modifiers have been removed. > > If you have an implementation of URI Templates (or feel like > writing one), please let us know if any of these changes are > unwelcome. If there are parts of the syntax that need to be > postponed to higher levels (or removed altogether), then let us > all know. > > As usual, all draft formats and a diff from 04 are available at > > http://uri-templates.googlecode.com/svn/trunk/spec/ > > Cheers, > > Roy T. Fielding<http://roy.gbiv.com/> > Principal Scientist, Adobe Systems<http://adobe.com/enterprise> > > Begin forwarded message: > >> From: internet-drafts@ietf.org >> Date: July 11, 2011 4:33:52 PM PDT >> To: i-d-announce@ietf.org >> Subject: I-D Action: draft-gregorio-uritemplate-05.txt >> Reply-To: internet-drafts@ietf.org >> >> A New Internet-Draft is available from the on-line Internet-Drafts directories. >> >> Title : URI Template >> Author(s) : Joe Gregorio >> Roy T. Fielding >> Marc Hadley >> Mark Nottingham >> David Orchard >> Filename : draft-gregorio-uritemplate-05.txt >> Pages : 28 >> Date : 2011-07-11 >> >> A URI Template is a compact sequence of characters for describing a >> range of Uniform Resource Identifiers through variable expansion. >> This specification defines the URI Template syntax and the process >> for expanding a URI Template into a URI reference, along with >> guidelines for the use of URI Templates on the Internet. >> >> Editorial Note (to be removed by RFC Editor) >> >> To provide feedback on this Internet-Draft, join the W3C URI mailing >> list (http://lists.w3.org/Archives/Public/uri/) [1]. >> >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-gregorio-uritemplate-05.txt > > >
Received on Tuesday, 12 July 2011 19:58:56 UTC