Asami 2.0.3 is out. • This fixes a bug where the internal ID generator was not initializing correctly when reconnecting to a persistent store. • Also fixes ID collisions after importing data that was exported from another store.
1🪨👋 Not actually doing this yet; but I was considering running naga over some RDF stores, e.g. rdf4j’s native store, and possibly arbitrary sparql repositories
That’s an adapter that I always intended to write. It’s where all of this started, after all
Let me know if I should put some time into it 🙂
yeah, it looked like it would be relatively easy to add to what is there already. I think the bulk of it would be coercing the naga keywords into URIs via a registry of prefixes
If using the rule language, then yes. But if using the API, then it’s not needed, since URIs can be provided directly
yeah, agreed, I was meaning via pabu
The rule language (Pabu) was literally a 30 minute hack just so I had a quick way to write and modify rules :rolling_on_the_floor_laughing:
Somehow, it stayed with us! 😳
I guess, it’s almost good enough 😆
Pabu was also a good opportunity to learn about parser combinators! (I used to work with Nate Young who wrote the Parsatron)
I just like that it’s so similar to prolog
though it probably does cause me more grief than using the API
The syntax is specifically taking the same format as QNames, intentionally
yeah, which again is nice for me because I’m using RDF 🙂
though if I were to actually use any of the rules I’ve written I’ll need to coerce them into URIs on whatever backend I use (Jena/RDF4j)
It’s missing the PREFIX part, so I should add that
yeah I was going to mention that; though you’ll need a way to register / hook in URI constructors
though that sort of thing might be better bolted on rather built in
I was thinking of the @prefix
syntax, to distinguish it from rules