- From: Ruben Taelman <Ruben.Taelman@UGent.be>
- Date: Fri, 24 Nov 2023 07:10:31 +0000
- To: Pierre-Antoine Champin <pierre-antoine@w3.org>
- CC: Vincent Emonet <vincent.emonet@gmail.com>, Semantic Web <semantic-web@w3.org>
Hi all, I created this tool a while ago: https://rdf-play.rubensworks.net/ It runs client-side (JS), can dereference RDF documents in all recommended serializations, and returns it as Turtle/TriG. There’s no manual RDF input at the moment, or a way to modify the output format. Kind regards, Ruben Taelman > On 23 Nov 2023, at 19:20, Pierre-Antoine Champin <pierre-antoine@w3.org> wrote: > > > On 23/11/2023 15:42, Vincent Emonet wrote: >> (...) >> From my point of view: >> - A minimal modern validator should at least enable users to provide RDF in various format (the classic xml, turtle, trig, n3, nquads, ntriples, ideally it could even support JSON-LD). >> - And it should enable users to convert from any formats to any other format (if you can do parsing, you can also do serializing, so why not doing both?) >> - Ideally it should be implemented to work fully on the client (because decentralization, and scalability, and we have now good JS/wasm options to parse in the browser now), so that it can be deployed to any CDN without the cost of hosting a server. If people needs an API we can find a way to setup a client-side API (look like an API, query like an API, but execution on the client) > you mean, something like that ? :-) > (disclaimer: this is a very rough and early prototype) > The reason I asked the 2nd point was precisely to determine whether this prototype could be a satisfactory replacement from the current ageing validator. >> >> >> Best, >> >> Vincent >> >> >> Le mer. 22 nov. 2023 à 13:46, <hans..teijgeler@quicknet.nl> a écrit : >> Hi Pierre-Antoine, >> >> I use the IDLab Turtle Validator >> >> Regards, Hans > <OpenPGP_0x9D1EDAEEEF98D438.asc>
Received on Friday, 24 November 2023 07:10:44 UTC