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

Re: ED URLs

From: Shane McCarron <shane@aptest.com>
Date: Thu, 12 Jun 2014 09:05:14 -0500
Message-ID: <CAOk_reEsaZY2C=mQiJNqFtyFk12yOX1-W_USghFTdC6CA7k+bQ@mail.gmail.com>
To: Tobie Langel <tobie.langel@gmail.com>
Cc: "spec-prod@w3.org Prod" <spec-prod@w3.org>
I think it is important to be able to reference a specific spec.  I
wouldn't want ReSpec magically deciding to change my normative reference
from an editors draft to a (potentially very different) WD.


On Thu, Jun 12, 2014 at 7:18 AM, Tobie Langel <tobie.langel@gmail.com>
wrote:

> Hi,
>
> Seems like we're going to be able to get ED urls directly from the W3C RDF
> file soonish.
>
> Would like your thoughts on how to best integrate that in the Specref API.
>
> I see two options:
>
> 1. Pass an extra query param to specify what you want, e.g.:
>
> http://specref.jit.su/bibrefs?refs=service-workers&type=ED|TR|LATEST
>
> Which would give you, respectively:
>
> - https://slightlyoff.github.io/ServiceWorker/spec/service_worker/
> - http://www.w3.org/TR/service-workers/
> - http://www.w3.org/TR/2014/WD-service-workers-20140508/
>
> This has the benefit that ReSpec could be smart about it and pick ED when
> the spec is in ED, but change to TR for publishing WDs for example.
>
> 2. Automatically generate extra references, e.g.:
>
> http://specref.jit.su/bibrefs?refs=service-workers-ED
> http://specref.jit.su/bibrefs?refs=service-workers-TR
> http://specref.jit.su/bibrefs?refs=service-workers-LATEST ?
>
> We could also do a mix of both.
>
> LMK your thoughts.
>
> --tobie
>
>
Received on Thursday, 12 June 2014 14:05:43 UTC

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