Re: TTML2 CR Showing as Outdated

On 2nd thought, I see that link retrieves a JSON document describing the
latest version, not the actual latest version itself.

[image: Screenshot 2024-09-05 at 7.06.46 AM.png]

On Thu, Sep 5, 2024 at 7:03 AM Glenn Adams <glenn@skynav.com> wrote:

> SGTM
>
> On Thu, Sep 5, 2024 at 5:05 AM Nigel Megitt <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 which is the
>> correct one, and the most recent in the history page.
>>
>> Nigel
>>
>>
>> On 05/09/2024, 09:31, "Atsushi Shimono (W3C Team)" <atsushi@w3.org
>> <mailto:atsushi@w3.org>> wrote:
>>
>>
>> hi Nigel, Glenn,
>>
>>
>> Thank you for comments. (and sorry I could not attend meeting last
>> week...)
>>
>>
>> Per comments, we may want to ask to have both /TR/ttml2/ and the latest
>> CR (or publication).
>>
>>
>> Current system is quite simple, that a URL is called for data
>> https://www.w3.org/TR/tr-outdated-spec <
>> https://www.w3.org/TR/tr-outdated-spec>
>> which returns simple json as
>> { "header":"This version is outdated!",
>> "warning":"For the latest version, please look at ",
>> "latestUrl":"https:\/\/www.w3.org\/TR\/ttml2\/"}
>>
>>
>> One way we may ask is that adding new value to point when the latest
>> publication
>> is not /TR/, and showing both link as message. Does such request work?
>>
>>
>>
>>
>> best,
>>
>>
>>
>>
>> On 2024/08/29 20:36, Nigel Megitt wrote:
>> >> On 28/08/2024, 18:47, "Atsushi Shimono (W3C Team)" <atsushi@w3.org
>> <mailto:atsushi@w3.org> <mailto:atsushi@w3.org <mailto:atsushi@w3.org>>>
>> wrote:
>> >> On 2024/08/29 2:19, Glenn Adams wrote:
>> >>> Thanks for that correction. In that case, shouldn't the (outdated)
>> earlier CR I referenced make a reference to this newer snapshot rather than
>> referring to the 1st edition TTML2 Rec at https://www.w3.org/TR/ttml2/ <
>> https://www.w3.org/TR/ttml2/> <https://www.w3.org/TR/ttml2/> <
>> https://www.w3.org/TR/ttml2/&gt;> <https://www.w3.org/TR/ttml2/>? <
>> https://www.w3.org/TR/ttml2/&gt;?> <https://www.w3.org/TR/ttml2/&gt;?> <
>> https://www.w3.org/TR/ttml2/&amp;gt;?&gt;>
>> >>
>> >>
>> >> we may ask for system development and update for more customizable
>> and/or
>> >> rich feature of outdated banner (= might be a customization only for
>> us), but
>> >> linking to simple 'latest link' (as /TR/<shortname>/) seems reasonable
>> to me,
>> >> since we set the latest formal version as the latest REC, and asked to
>> configure
>> >> /TR/ttml2/ as the latest REC, but not to CRS branch under development.
>> Also we
>> >> consider development branch as non official one per standard
>> specification,
>> >> I suppose /TR/ttml2/ could be suitable for most of user who are not in
>> development
>> >> community (or ones writing/using TTML2 documents)...
>> >>
>> >>
>> >> Of course, someone might point that there is a system to show whole
>> history,
>> >> like
>> >> https://www.w3.org/standards/history/ttml2/ <
>> https://www.w3.org/standards/history/ttml2/> <
>> https://www.w3.org/standards/history/ttml2/> <
>> https://www.w3.org/standards/history/ttml2/&gt;>
>> >> and having history link at outdated banner could be better... Note,
>> current
>> >> latest spec template contains history link in details section. (I
>> forgot when
>> >> system started providing this link.)
>> >
>> > Perhaps a useful feature that others would also use is to point to the
>> most recent publication in the /history page
>> >
>> > Nigel
>> >
>> >
>> >>> Screenshot 2024-08-28 at 12.16.09 PM.png
>> >>>
>> >>> On Wed, Aug 28, 2024 at 12:05 PM Atsushi Shimono (W3C Team) <
>> atsushi@w3.org <mailto:atsushi@w3.org> <mailto:atsushi@w3.org <mailto:
>> atsushi@w3.org>> <mailto:atsushi@w3.org <mailto:atsushi@w3.org> <mailto:
>> atsushi@w3.org <mailto:atsushi@w3.org>>>> wrote:
>>
>> >>>
>> >>>
>> >>>
>> >>> On 2024/08/28 23:52, Glenn Adams wrote:
>> >>>> Wrong link. Should have been:
>> >>>>
>> >>>> https://www.w3.org/TR/2020/CR-ttml2-20200128/ <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/&gt;> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/&gt;> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/&gt;> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/&amp;gt;&gt;> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/ <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/&gt;> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/>> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/&gt;&gt;> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/&gt;&gt;> <
>> https://www.w3.org/TR/2020/CR-ttml2-20200128/&amp;gt;&amp;gt;&gt;>
>> >>>
>> >>> Latest should be : https://www.w3.org/TR/2021/CR-ttml2-20210309/ <
>> https://www.w3.org/TR/2021/CR-ttml2-20210309/> <
>> https://www.w3.org/TR/2021/CR-ttml2-20210309/> <
>> https://www.w3.org/TR/2021/CR-ttml2-20210309/&gt;> <
>> https://www.w3.org/TR/2021/CR-ttml2-20210309/> <
>> https://www.w3.org/TR/2021/CR-ttml2-20210309/&gt;> <
>> https://www.w3.org/TR/2021/CR-ttml2-20210309/&gt;> <
>> https://www.w3.org/TR/2021/CR-ttml2-20210309/&amp;gt;&gt;>
>> >>>
>> >>>
>> >>>> On Wed, Aug 28, 2024 at 8:27 AM Glenn Adams <glenn@skynav.com
>> <mailto:glenn@skynav.com> <mailto:glenn@skynav.com <mailto:
>> glenn@skynav.com>> <mailto:glenn@skynav.com <mailto:glenn@skynav.com>
>> <mailto:glenn@skynav.com <mailto:glenn@skynav.com>>> <mailto:
>> glenn@skynav.com <mailto:glenn@skynav.com> <mailto:glenn@skynav.com
>> <mailto:glenn@skynav.com>> <mailto:glenn@skynav.com <mailto:
>> glenn@skynav.com> <mailto:glenn@skynav.com <mailto:glenn@skynav.com>>>>>
>> wrote:
>> >>
>> >>>>
>> >>>> Can the outdated popup and banner be removed? I had asked about this
>> before. This CR is still the latest AFAIK. Correct me if I'm wrong.
>> >>>>
>> >>>> https://www.w3.org/TR/2018/REC-ttml2-20181108/ <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/&gt;> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/&gt;> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/&gt;> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/&amp;gt;&gt;> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/ <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/&gt;> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/>> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/&gt;&gt;> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/&gt;&gt;> <
>> https://www.w3.org/TR/2018/REC-ttml2-20181108/&amp;gt;&amp;gt;&gt;>
>> >>>>
>> >
>> >
>>
>>
>>
>>
>>
>>

Received on Thursday, 5 September 2024 12:09:03 UTC