W3C home > Mailing lists > Public > spec-prod@w3.org > April to June 2013

Re: Update on the publication process project

From: Alexandre Bertails <bertails@w3.org>
Date: Thu, 30 May 2013 08:48:15 -0400
Message-ID: <51A74A8F.9080400@w3.org>
To: Tobie Langel <tobie@w3.org>
CC: Marcos Caceres <w3c@marcosc.com>, 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>
On 05/30/2013 03:27 AM, Tobie Langel wrote:
> Did the first (semi-) automatic merge from /TR today (ran scripts/rdf.js).
>
> Here's the output commit: https://github.com/tobie/specref/commit/46240442.
>
> Works like a breeze. This should be the end of manual updates to the biblio.js for all things W3C. :)

Have you talked to Denis? I'm pretty sure that all this stuff will be 
made obsolete by the deployment of the new system (should happen soon) 
as we could expose tr.rdf as JSON directly, just by coding a new 
template for it...

Alexandre.

>
> Note we still have to decide what data the main entry should expose by default and then decide where to implement this (in the API, or in scripts/rdf.js).
>
> I'll be moving the repo to github.com/w3c in the near future.
>
> Best,
>
> --tobie
>
>
> On Monday, May 27, 2013 at 9:03 PM, Tobie Langel wrote:
>
>> This took a bit longer than expected. Was able to deploy today. LMK if you encounter issues.
>>
>> --tobie
>>
>>
>> On Friday, May 24, 2013 at 2:49 PM, Tobie Langel wrote:
>>
>>> 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 Thursday, 30 May 2013 12:48:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:18 UTC