Emmanuel Pietriga wrote:
> Ryan Lee wrote:
>> Emmanuel Pietriga wrote:
>> 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: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
>> PREFIX ex: <http://www.example.org/ns#>
>> 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.
I may have to opt for Longwell to have some independent configuration
for this. I don't believe there is a programmatic way to extract
namespace info in Sesame 1.2.2 and guarantee its correctness.
--
Ryan Lee ryanlee_at_w3.org
W3C Research Engineer +1.617.253.5327
http://simile.mit.edu/
Received on Tue Dec 06 2005 - 02:47:11 EST