Re: TTML2 CR Showing as Outdated

   hi Nigel,

   Wondered on what should be final request,, and took time before building text, sorry.


1. Background

   Usual specifications on /TR/ marks the latest publication as /TR/<shortname>/.
This latest is returned via latest api request like [1] (actually redirected to
dated api request), and uri will point to the latest one which is used for
/TR/<shortname>/
   And all former publications will have outdated banner with a link pointing
/TR/<shortname>/ which is the same as dated latest publication.

*1 https://api.w3.org/specifications/ttml2/versions/latest


   For TTML2, we specifically request to systems team and set /TR/ttml2/ to the
latest Recommendation [2], but not to the latest publication [3].
   In back-end system, it seems there is some quick hack -ish fix on specific
URL requests. Like, latest api returns the latest publication (CR) but not
the latest REC which is used for /TR/ttml2/.

*2 https://www.w3.org/TR/2018/REC-ttml2-20181108/

*3 https://www.w3.org/TR/2021/CR-ttml2-20210309/



2. What should be achieved?

   In ideal case, we may want to have links in outdated banner as:
- publications before the latest REC (= /TR/ttml2/) : pointing to the latest REC
- publications after the latest REC : pointing to the latest publication

   is this correct?

   Following discussions, incl. uri from latest api link (= the latest publication
but not /TR/ttml2), I really wondered on this point.


   a) If we want to set the latest publication to everything, which is returned for
      latest api, we should simply ask to replace an entry in tr-outdated-spec [4]
      to point dated version
   b) If we want to point both (/TR/ttml2/ and latest api), we should ask several
      updates both [4] and outdated banner

*4 https://www.w3.org/TR/tr-outdated-spec



   hrm,,,


On 2024/09/05 21:35, Nigel Megitt wrote:
> Yes, apologies for the shorthand, I meant the value for the uri key in that JSON response, not the response itself.
> 
> Nigel
> 
> *From:* Glenn Adams <glenn@skynav.com>
> *Sent:* 05 September 2024 1:08 PM
> *To:* Nigel Megitt <nigel.megitt@bbc.co.uk>
> *Cc:* Atsushi Shimono (W3C Team) <atsushi@w3.org>; public-tt@w3.org <public-tt@w3.org>
> *Subject:* Re: TTML2 CR Showing as Outdated
> 
> *External: * Think before clicking
> 
> On 2nd thought, I see that link retrieves a JSON document describing the latest version, not the actual latest version itself.
> 
> Screenshot 2024-09-05 at 7.06.46 AM.png
> 
> On Thu, Sep 5, 2024 at 7:03 AM Glenn Adams <glenn@skynav.com <mailto:glenn@skynav.com>> wrote:
> 
>     SGTM
> 
>     On Thu, Sep 5, 2024 at 5:05 AM Nigel Megitt <nigel.megitt@bbc.co.uk <mailto:nigel.megitt@bbc.co.uk>> wrote:
> 
>         Hi Atsushi,
> 
>         I would propose that it should return the value at https://api.w3.org/specifications/ttml2/versions/latest <https://api.w3.org/specifications/ttml2/versions/latest> which is the correct one, and the most recent in the history page.
> 
>         Nigel

Received on Friday, 20 September 2024 04:59:39 UTC