- From: Martynas Jusevičius <martynas@atomgraph.com>
- Date: Mon, 15 Jun 2020 15:46:49 +0200
- To: Denis Ah-Kang <denis@w3.org>
- Cc: Spec-prod <spec-prod@w3.org>, W3C Team <w3t@w3.org>, Philippe Le Hegaret <plh@w3.org>, Dominique Hazael-Massieux <dom@w3.org>, François Daoust <fd@w3.org>, Tobie Langel <tobie.langel@gmail.com>
There were RDF descriptions and now you are making them *less* machine-readable by replacing them with a plain JSON API? Got it... On Mon, Jun 15, 2020 at 8:17 AM Denis Ah-Kang <denis@w3.org> wrote: > > Hi all, > > 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. > > 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. > > Thank you, > > Denis > > > [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 >
Received on Monday, 15 June 2020 13:47:13 UTC