Martynas Jusevičius

I made the following sketch that introduces a new high-level API and implements it using the existing lower-level API: * new abstract classes `Resource`, `Property`, `Graph`, `Dataset` are introduced together...

Are you suggesting that `Graph` should have an inherent URI name? I think that was one of the reasons that RDFLib API and implementation was so weird, but I would...

@Tpt my conclusion is that we need `Store` as an interface (with DB-specific methods removed, leaving quad-related methods) with two implementations: `RocksDBStore` and `MemoryStore`. For performance both should be implemented...

It seems that we would also need something like Jena's [`GraphView`](https://github.com/apache/jena/blob/main/jena-arq/src/main/java/org/apache/jena/sparql/core/GraphView.java) which combines dataset and graph name.

I put together a PoC implementation and an example that shows it usage. Seems to work correctly. https://github.com/namedgraph/oxijen/blob/main/example.py

@osma can you confirm?

I don't understand how typing one less character (`property` instead of `:property`) can justify thousands of manhours of specification and implementation work this change would incur on the ecosystem.

@HolgerKnublauch I disagree. IMO we should make RDF-based software so flexible and powerful (in ways that would be impossible with RDF) so that we can empower the non-software people to...

@dbooth-boston why do you see it as a competition? RDF will always lose out in the marketing sense because Neo4J alone has received $500M+ in VC funding. Just stop trying...

@dbooth-boston you should enable Discussions :)