- From: Tobie Langel <tobie@w3.org>
- Date: Fri, 24 May 2013 14:49:17 +0200
- To: Marcos Caceres <w3c@marcosc.com>
- Cc: Robin Berjon <robin@w3.org>, Philippe Le Hegaret <plh@w3.org>, spec-prod <spec-prod@w3.org>, Ted Guild <ted@w3.org>, Denis Ah-Kang <denis@w3.org>
Hacked a script that pulls tr.rdf data and turns it into palatable JSON. Now to combine it with the ordered list of authors/editors of specref and profit. Should be able to deploy the output later today. I'll keep the process manual for now. We can always automate it later on. --tobie On Tuesday, May 21, 2013 at 1:34 PM, Marcos Caceres wrote: > > > > On Tuesday, May 21, 2013 at 12:19 PM, Robin Berjon wrote: > > > On 20/05/2013 18:08 , Philippe Le Hegaret wrote: > > > Regarding generating a new /TR page, it appeared clearly at TPAC that > > > the current version wasn't being used much by the W3C experts, mainly > > > due to its painful interface. Even if it is dangerous to extrapolate > > > from just one single session, I suspect that the feeling is relatively > > > general in W3C. The old /TR page was a simple list of the documents but > > > was getting quite long. My thinking has been that we may need a simple > > > TR page for the W3C community, which allows fast search/navigation, and > > > a more complex one for the Web at large. > > > > > > > > > > > > One thing that I recall was brought up during the TPAC session (but I > > forget who said it) was that it would be useful to have some JSON dump > > of the TR information so that people could write their own interfaces. > > > > I'm sure I've asked for this a few times. > > I > > forget if what came out was that that dump already existed but people > > didn't know where to find it, or if it wasn't but was easy to generate, > > but I recall (dimly) that there was general agreement that it could be > > useful (especially if CORS-accessible). > > > > Absolutely. Would make keeping Respec's biblio up to date a breeze! > > -- > Marcos Caceres
Received on Friday, 24 May 2013 12:49:26 UTC