Object Graph doesn't contain undefined properties about spira HOT 3 CLOSED

This is a limitation of original design (which, at the same time, prevents possible hacks/gotchas where the database has properties with the same name as "sensitive" object methods of Spira objects, e.g. to_s, new or the like). I think it should possible to "declare" properties based on the data, instead of using explicit declarations in the Ruby class, but there would be many other implications throughout the gem that we decided to "avoid" for now.
I do not have any objections to your idea, in general, so you're welcome to send us a pull request implementing this "dynamic" declaration of properties.

from spira.

Sorry for the lateness. I don't really need dynamic properties, and think that's more dangerous than it's worth, I just need access to the entire RDF graph for that object - whether I can get to those properties via setters or not. We'll work on a pull request over here.

from spira.

Since Spira is based on RDF.rb, you can always use its lower level API to access stuff directly, e.g. get your object repository (r = my_object.class.repository), get your object's subject (s = my_object.subject) and finally, get all triples with that subject using RDF.rb API: ts = r.statements(:subject => s) (or something among those lines).

from spira.