-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LDflex over In-Memory RDF Data #62
Comments
Yes, in the sense that LDflex wiring is completely configurable. However, it would be difficult in the sense that:
Yeah, but so as mentioned above, there is thus still the JSON-LD parsing and the querying that is asynchronous, and the fact that
I see the appeal indeed. That would not be impossible to wire, but would take some implementation work. |
So I have been away from the JS community for a while, so I wonder what the status or RDF in JS is today. |
RDF/JS is the main thing now: https://rdf.js.org/
Super! Blocker is that most of RDF/JS is async now. |
Hm, so the datamodel and dataset API seem very synchronous to me. So having an interface for a set of quads with a synchronuous match(g, s, p, o) method is already a good start - although I am a bit worried not seeing a graph abstraction (triples). W.r.t async calls, if they are used to fetch graphs or datasets at once, then there is no issue, because once it is placed as a whole into the (view) model, the view can update itsel synchronously afterwards (I am thinking of vue2 models now). |
Yeah, for in-memory stores indeed.
Parsers etc. are typically
Not sure about that, you can just pass a constant |
Yeah its not too complicated, its just somewhat unfortunate that I'd have to roll my own 'Graph' interface. Because it feels like reinventing over and over again. I suppose rdfstore-js already had something - but AFAIK its discontinued (right?) And when I look at the definition of
On the positive side, the most important method of Graph are just 3:
So the proven architecture from the Java world is essentially this:
|
But you're looking in the wrong place: https://rdf.js.org/data-model-spec/#quad-interface (and also, those strings have special markers to indicate the term type)
Not sure if there's a strong need for that, depending on what you want to achieve. Best to take that up in https://github.com/rdfjs/dataset-spec |
Yes, the cleanest approach for me seems to build on https://github.com/rdfjs/dataset-spec - add a small graph abstraction and then the plumbing work is already done. |
Hi,
Is there a way to use the proxying approach over in-memory data so that the await is no longer necessary? it feels quite clumsy in cases where all data RDF data is locally available anyway.
For my use case I just want to import static RDF files (or fetch an RDF graph in batch from an endpoint), and then have a resource-centric view over it (in contrast to triple based ones), and finally have a JavaScript proxy over it that exposes outgoing and ingoing triples as virtual JSON attributes - in the simplest case by just matching magic JSON atttributes to RDF local names.
To illustrate it conceptually step-by-step:
The main benefit is, that one can then really create fuzz free HTML views just like:
The text was updated successfully, but these errors were encountered: