It's been a while since the URI Template draft has been updated, and in the interim there has been some implementation experience: http://blog.springsource.com/2009/03/08/rest-in-spring-3-mvc/ http://code.google.com/p/uri-templates/wiki/Implementations In the intervening months two things have happened: 1. In all the URI Template examples I've seen, only the simplest case {foo} has even been shown. 2. I've been repeatedly asked about "going the other way", i.e. parsing URIs based on templates. This leads to two questions: 1. Are there any real-world uses of the more complex URI Templates, or is {foo} enough? 2. *If* the syntax is simplified to {foo} there is an opportunity to support the parsing case, ala http://bitworking.org/projects/1812/wsgidispatcher.html Is that of interest to anyone? Thanks, -joe -- Joe Gregorio http://bitworking.orgReceived on Monday, 18 May 2009 19:26:29 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 18 May 2009 19:26:30 GMT