Adrian,
I'm not against JS per se, I'm against reinventing the bike, wasting
effort and using imperative tech where declarative could do.
RDF/JS is a great initiative, as an RDF API for JS was lacking. Is it
anything specific to JS though? Hardly, it's just OO interfaces and
implementations.
I'm aware of JSON-LD, but it is hardly relevant here. Not to start a
flame, but I see it as another RDF syntax, no more.
RDF processing can happen on the server as well as on the browser.
SPARQL processor is still a SPARQL processor, no matter where you
place it. And I will at all costs avoid
On 15.05.20 12:39, Martynas Jusevičius wrote:
Hi
> RDF JavaScript frameworks are still ~20 years behind Java. So this had
> me thinking for a while -- instead of reinventing the wheel, would it
> be possible to transpile Jena to TypeScript or JavaScript?
When my colleague sees that I answer
Dear Martynas,
I think that Jena is more focused on back-end process, may i'm wrong :/...
Perhaps would be better to focus more on JSON-LD that is an improved JSON (+-)
lol.
They already have some javascript implementations for that:
For example:
https://github.com/digitalbazaar/jsonld.js/
For
Hi,
RDF JavaScript frameworks are still ~20 years behind Java. So this had
me thinking for a while -- instead of reinventing the wheel, would it
be possible to transpile Jena to TypeScript or JavaScript?
ARQ would probably be my number #1 target, but RIOT would also be useful.
>From what I've
Dear Ken,
I hope this example helps you:
String rules = "[rule1: (?a eg:p ?b) (?b eg:p ?c) - (?a eg:p ?c)]";
Reasoner reasoner = new GenericRuleReasoner(Rule.parseRules(rules));
reasoner.setDerivationLogging(true);
InfModel inf = ModelFactory.createInfModel(reasoner, rawData);
You can check
