Ryan Lee wrote:
> Emmanuel Pietriga wrote:
>
>> Ryan Lee wrote:
>>
>>> Emmanuel Pietriga wrote:
>>>
>>>> Ryan Lee wrote:
>>>>
>>>>>>>> - be able to apply styling instructions based on conditions at
>>>>>>>> the source RDF model level, i.e. be able to say things like
>>>>>>>> "color in red all ex:age properties that have a value > to 47".
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> This is not a core requirement, is it? I agree that being able
>>>>>>> to distinguish part of the RDF model for later styling is
>>>>>>> important, but complex conditions implies that it's outside of
>>>>>>> core's capabilities.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> No, this is not part of core. But I think it would be really
>>>>>> useful. And I guess it has consequences on the overall design.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Perhaps if the style hook proposal is general enough it could be
>>>>> adapted for this.
>>>>
>>>>
>>>>
>>>>
>>>> I'm not sure. Do you have any specific idea in mind about how this
>>>> could help ?
>>>
>>>
>>> If the styleHook predicate is structured properly, then one could
>>> attach a hook to any part of the graph (resource, property, object,
>>> label, etc.) no matter what selection conditions apply. So
>>> (embellishing a bit on my last proposal) :resourceHook,
>>> :propertyHook, :objectHook, etc
>>
>>
>> I'm not really following you here. An example would help.
>
>
> If Chris is amenable to our discussion direction thus far, I'll send out
> a revised proposal. As we said, requirements agreement should come
> first so we don't get bogged down in technical discussions that will
> ultimately go unused.
Ok.
FYI, I am currently working on my Java-based FSL selection engine. My
goal is to have an API that builds a programmer friendly representation
of FSL paths in Java from the AST generated by ANTLR. The objects
composing this API could then easily be specialized (subclassed) or used
in any other way so that one could actually perform selection on various
representations of RDF model. For instance, I am more interested in
evaluating an FSL path against a Jena model, while you seem to be more
interested in doing so against a Sesame repository.
Hopefully, the implementation work required to actually evaluate the
path against a specific kind of repository/model/... should be small.
I hope to be done with the generic API at the end of next week.
Emmanuel
--
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 http://www.lri.fr/~pietriga
Received on Fri Jun 03 2005 - 06:07:09 EDT