- From: Martynas Jusevičius <martynas@atomgraph.com>
- Date: Sat, 26 Nov 2022 22:01:13 +0100
- To: Danny Ayers <danny.ayers@gmail.com>
- Cc: Semantic Web <semantic-web@w3.org>
- Message-ID: <CAE35VmxnSiN=j+M45gbckcXawdD+NfgDov6ODt4vp8vtD_dYOQ@mail.gmail.com>
Does that make the output any different? On Sat, 26 Nov 2022 at 21.58, Danny Ayers <danny.ayers@gmail.com> wrote: > also not Java not JS...typescript angular react...rust...wasm! > > On Sat, 26 Nov 2022 at 21:45, Martynas Jusevičius <martynas@atomgraph.com> > wrote: > >> Hi Danny, >> >> You can at least look at your own HTTP-in-RDF data as Turtle :) >> https://github.com/AtomGraph/HTTP-in-RDF >> >> Martynas >> atomgraph.com >> >> On Sat, 26 Nov 2022 at 21.23, Danny Ayers <danny.ayers@gmail.com> wrote: >> >>> re. https://www.w3.org/TR/HTTP-in-RDF10/ >>> >>> This probably applies to a lot of the specs from whatever 2022-2007=. >>> >>> Virtually unintelligible. The arcane spec text is fair enough, the >>> specification is still entirely valid, just it is very hard to read, let >>> alone use. >>> >>> No crit on the original authors, good job well done. But that was ages >>> ago. >>> >>> I don't know what the process would be, but if anyone could see fit to >>> transcribing it into Turtle, that would make a huge difference. Also a lot >>> of editorial to make it more approachable to a fresh young coder in 2022 >>> (and me). I know (/knew) RDF/XML yet now can't read it. >>> >>> I wanted this today, silly thing of a test echoing headers, wanted to >>> have RDF there. Try to find the ref - ok - but the examples are in year >>> 2000 language and I have to bounce around to see what the namespace is. >>> >>> No longer fit for purpose. >>> >>> Cheers, >>> Danny. >>> >>> >>> >>> >>> >>> >>> -- >>> ---- >>> >>> https://hyperdata.it <http://hyperdata.it/danja> >>> >>> > > -- > ---- > > https://hyperdata.it <http://hyperdata.it/danja> > >
Received on Saturday, 26 November 2022 21:01:37 UTC