Re: FSL engine for Sesame

From: Emmanuel Pietriga <>
Date: Fri, 02 Dec 2005 09:45:07 +0100

Ryan Lee wrote:
> Emmanuel Pietriga wrote:
>> I've made these public and checked it against your Sesame122 classes.
>> It seems to work fine.
>> You can get the new IsaViz-FSL version from the W3C cvs or the JAR
>> file from
>> Let me know if there is anything wrong.
>> Emmanuel
> It works perfectly, as does upgrading Ant to the latest as you suggested
> earlier.


> Are we agreed at all about how prefix mapping looks when using FSL in
> Fresnel? I recall we said we weren't going to solve this problem in a
> standard form after much discussion, and, accordingly, the manual has no
> information on how to do it. I could try to come up with something in
> my own implementation, though it might be hard since I don't think
> Sesame 1.x records prefix maps in its models.
> Chris' example Fresnel configurations contain this sort of approach:
> """PREFIX rdf: <>
> PREFIX ex: <>
> rdf:Class[ex:something]"""^^fresnel:fslSelector
> which seems to bring into question what exactly a fresnel:fslSelector
> datatype means (though his examples do predate the precise invention of
> that datatype).

I took the path of "each application does it as it wants":
- in the IsaViz engine (visual FSL debugger), the namespace prefixes are
taken from all the declarations in the Namespaces tab of the GUI
- in the Jena and Sesame 2 engines, there is a class FSLNSResolver that
has to be instantiated by programmers using these engines when they
create a new FSLEvaluator object. This FSLNSResolver class having a
simple API for declaring namespace prefix bindings.

Emmanuel Pietriga
INRIA Futurs - Projet In Situ    tel : +33 1 69 15 34 66
Bat 490, Université Paris-Sud    fax : +33 1 69 15 65 86
91405 ORSAY Cedex FRANCE
Received on Fri Dec 02 2005 - 08:39:32 EST

This archive was generated by hypermail 2.3.0 : Thu Aug 09 2012 - 16:40:51 EDT