danbri: For #mashed
http://209.85.135.104/search?q=cache:XTwcwbrHdRoJ:n2.talis.com/svn/playground/kwijibo/PHP/arc/plugins/trunk/ARC2_RDFaSerializer/ARC2_RDFaSerializerPlugin.php+ARC2_RDFaSerializer&hl=pl&gl=pl&strip=1
http://n2.talis.com/svn/playground/kwijibo/PHP/arc/plugins/trunk/ARC2_RDFaSerializer/ARC2_RDFaSerializerPlugin.php
bblfish: How does one specify the meaning of Fresnes selector namespaces?
bblfish: There is some documentation here: http://isweb.uni-koblenz.de/Research/lena
bblfish: But that does not tell how to link individual selectors to the appropriate name space declaration
bblfish: looks like this will only work with some particular lifting rules. One will need to know the contxt in which a fresnel statement was made to know it's meaning... Or was there some hope that xml name space inheritance might be part of a future RDF standard?
bblfish: in N3 one could think of graph notations using { } as being literals that know how to deal with namespace inheritance. Is there a way to integrate SPARQL into N3?
bblfish: There is some documentation here: http://isweb.uni-koblenz.de/Research/lena
bblfish: But that does not tell how to link individual selectors to the appropriate name space declaration
bblfish: looks like this will only work with some particular lifting rules. One will need to know the contxt in which a fresnel statement was made to know it's meaning... Or was there some hope that xml name space inheritance might be part of a future RDF standard?
bblfish: in N3 one could think of graph notations using { } as being literals that know how to deal with namespace inheritance. Is there a way to integrate SPARQL into N3?