On 5/2/06, Michel Pelletier <
[EMAIL PROTECTED]> wrote:
[...]
[...]
> - Use RDF as an environment model store: all context information is
> stored in an rdflib Graph and entities can be retrieved using SPARQL
> queries. This seems to work well and I should have a first version
> running soon. What I do not understand, yet, is how I can use RDFS to
> describe an ontology for the environment and enforce it in the graph.
You can certainly use RDFS in rdflib, just write RDFS statements in
whatever flavor of syntax you want (xml, n3, etc.). Enforcement is
something rdflib doesn't do, yet. That's something we can put on the
roadmap however. For now you have to roll your own enforcement.
Any ideas on how to do this effectively and efficiently?
> Is it possible to use RDF reasoners with rdflib?
Sure! Although most reasoners would need you to serialize the rdflib
data to some syntax (like xml) and then reason on it, and then
de-serialize it back into a graph. For very large graphs this is
probably inefficient, but a reasoner that interfaced directly with the
Graph API would be very cool.
Has anybody done this, yet? Would be very cool and useful. Still have to try out what Chimezie suggested...
>
> Here are some observations:
>
> - The 'pretty-xml' serializer omits the subject. It does not appear in
> the about parameter of the Description tag.
Ouch. Anyone want to tackle that one? ;)
This does not seem to have been repaired. What to do about it? It is important that this works.
>
> - The xml parser interprets the about parameter when it is manually
> inserted in an rdf file. For example:
> <rdf:Description about=" http://python.openspace.nl/foaf#donna
> < http://python.openspace.nl/foaf#donna >">
>
> - The n3 serializer uses the subject as one would expect.
>
> - The n3 parser does not work. I get the following error messages when
> trying to parse the n3 output that was just serialized:
>
> - The xml parser interprets the about parameter when it is manually
> inserted in an rdf file. For example:
> <rdf:Description about=" http://python.openspace.nl/foaf#donna
> < http://python.openspace.nl/foaf#donna >">
>
> - The n3 serializer uses the subject as one would expect.
>
> - The n3 parser does not work. I get the following error messages when
> trying to parse the n3 output that was just serialized:
>
[...]
This looks like you are trying to use the XML parser, not the n3 parser,
perhaps that's why it apears broken.
You are right. The parser does not automatically detect the dialect, of course...
Still, the n3 parser does not read the subject, but creates a new one.
BEFORE:
(u'donna', u' http://xmlns.com/foaf/0.1/name', <Literal language=None datatype=None value=Donna Fales>)
- Serialize to n3, Parse n3
AFTER:
(u'bpISlBxO11', u'http://xmlns.com/foaf/0.1/name', <Literal language=None datatype=None value=Donna Fales>)
Hope this helps, how's spyse coming along?
Pretty well, we are working on the next release and there is quite some interest around the world. Keep you updated! http://spyse.sf.net/
Thanks
kind regards
André
_______________________________________________ Dev mailing list [email protected] http://rdflib.net/mailman/listinfo/dev
