ANN: Griller - RDF from other places

I've subjected this "ANN", but there's nothing written down yet. I'd
appreciate suggestions from behind other eyeballs.

The proposal is to upcycle the notion contained in GRDDL [1], apply it more
widely, starting with JSON and markdown.

For ref, below is an example from the GRDDL spec, but you need not look,
it boils down a really simple idea : in a particular document you include 2
URLs. One declares there is a processing model that may be applied to this;
the other points to that specific process.

GRDDL was motivated by the idea that it's pretty straightforward to
transform an XML doc, which is likely to be data-shaped, into an RDF
representation. It really is a neat way of doing it. Just two URLs, one
says "we have a mapping" the other says "this is the mapping".

(I was in the Working Group, DanC didn't credit me, but the spec was
thoroughly ignored, hey ho)

Implementation-wise, discussions didn't really get beyond what was obvious
at the time. You apply an XSLT stylesheet to the doc, you get the RDF. With
one stylesheet, swathes of docs are transparently RDF. Or if you really
want to do it manually, take the doc, get the XSLT, use your XSLT engine of
choice, out pops the RDF (I forget, we put down RDF/XML? was probably
pre-Turtle syntax, but irrelevant, conneg innit).

But the mechanism can work elsewhere. I had to leg it from the JSON-LD
working group when it became clear the other folks knew what they were
talking about whereas I didn't.
But years later, I got the reductio :

{
   data-view-transformation : "http://purl.org/stuff/griller.js"

   stuff : { this: ["all", "the", "jsons"] }
}

Yeah, I'm thinking just one URL, and put in a reserved name in whatever the
RFC for those is.

A recipient takes the above, applies the script given by griller.js, spits
out whatever it's transformed into. (I'd incline towards "text/turtle", but
again, conneg).

So there you have any JSON exposed in a syntax that can be interpreted in
the RDF model.

But one thing I feel I need right now in my own project is the same for
markdown. So here we go :

<!-- data-view-transformation : "http://purl.org/stuff/make-me-sing.js"-->

Markdown processors typically pass through HTML, seems like a comment will
either be a verbatim comment, or non-existent in the output. Use it or not,
is very little extra load.

 The plus side to this is that implementation can be really low cost, the
default being do nothing. The downside is that it calls for at least one
special name, something like "data-view-transformation"


Cheers,
Danny.




 <html xmlns="http://www.w3.org/1999/xhtml">

  <head *profile="http://www.w3.org/2003/g/data-view
<http://www.w3.org/2003/g/data-view>"*>
    <title>Some Document</title>

    <link *rel="transformation"*
       href="http://www.w3.org/2000/06/dc-extract/dc-extract.xsl" />
    <meta name="DC.Subject"
       content="ADAM; Simple Search; Index+; prototype" />
    ...
  </head>
  ...
</html>


[1] https://www.w3.org/TR/grddl/



-- 
----

https:// <http://hyperdata.it/danja>danny.ayers.name

Received on Friday, 9 August 2024 14:41:33 UTC