Open delocalizer opened 8 years ago
I had originally thought that maybe RdfKey
would be a pair of the key value and the iri of the named graph. I wanted to avoid coupling those together, but, that might be a nice simplification that would resolve this issue.
Having urn:foo
be a different entity when it's in named graph urn:g
vs when it's in urn:g1
seems like it's probably what users would expect
Yeah, having the graph be part of the key seems nice from a practical pov. I think it's also kosher from a RDF theory pov, not that I am an expert. My understanding that the intended usefulness of named graphs is for store-based operations, and RdfKey is the key to find the entity in the store.
If
MyClass
is annotated with@NamedGraph
(Static or Instance type doesn't matter) and an instance of the class lives in the database,EntityManagerImpl.find(MyClass, itsKey)
won't find it.See https://groups.google.com/forum/#!topic/empire-rdf/BKu0f5uItec