Re: Retiring tr.rdf
Yves Lafon <[email protected]> Mon, 15 Jun 2020 15:34:36 +0200
| Newsgroups | gmane.org.w3c.specifications |
|---|---|
| Message-ID | <[email protected]> |
> On 15 Jun 2020, at 08:17, Denis Ah-Kang <[email protected]> wrote: >=20 > Hi all, >=20 > In the past, the only way to get data related to the > specifications was tr.rdf [1]. However, a few years ago, > we released the W3C API [2] to provide more complete data. > Since we are now focusing our effort to improve the API, > I would like to know who still rely on tr.rdf and what > can we do to remove that dependency in favor of the API. >=20 > I have already identified specref [3] and transition-notifier > [4] in the list of tools using tr.rdf but if you know another > one, please reach to me and I'll get in touch with the > maintainers to see if there's a way to make the switch. IIRC some scripts used by some IETF groups are using tr.rdf (as I = received some bugs report in the past about missing things in it). What is the issue in keeping cool URIs [5]? > [1] https://www.w3.org/2002/01/tr-automation/tr.rdf > [2] https://api.w3.org/doc > [3] https://github.com/tobie/specref > [4] https://github.com/plehegar/transition-notifier [5] https://www.w3.org/Provider/Style/URI --=20 Baroula que barouleras, au ti=C3=A9u toujou t'entourneras. ~~Yves