- From: Holger Knublauch <holger@knublauch.com>
- Date: Fri, 01 Feb 2013 09:59:01 +1000
- To: David Booth <david@dbooth.org>
- CC: semantic-web@w3.org
On 2/1/2013 9:33, David Booth wrote: > Hi Holger, > > On Fri, 2013-02-01 at 08:22 +1000, Holger Knublauch wrote: >> Hi David, >> >> the prefixes from the surrounding graph should be used for parsing. In a >> typical application, SPIN rules would be loaded from a file at start-up >> time and then those prefixes are readily available. > That is convenient, but the downside is that it requires the RDF parser > to have special knowledge of SPIN. I don't think so. The RDF parser simply loads this into a string literal. Only the SPIN engines would parse those literals for execution. I may misunderstand your comment. > Another possible approach that would avoid the need for the parser to > have special knowledge of SPIN would be to allow the prefixes to be > explicitly asserted at the triple level, such as: @prefix ex: > <http://example/def#> . ex: spin:globalPrefix "ex:" . or equivalently: > <http://example/def#> spin:globalPrefix "ex:" . Yes, storing prefixes as triples may be a useful extension to RDF anyway, independent of SPIN. For example, they could be attached to the owl:Ontology instance of the graph. But that's a larger change, and I don't understand why it would be critical at this stage. Cheers, Holger
Received on Thursday, 31 January 2013 23:59:35 UTC