40
edits
| Line 3: | Line 3: | ||
Fresnel is SIMILE's RDF query mechanism. It builds on SPARQL or XPath and provides query modularization. To allow for a fully functional Fresnel Query Processor, the builder and result interfaces would have to be enhanced. | Fresnel is SIMILE's RDF query mechanism. It builds on SPARQL or XPath and provides query modularization. To allow for a fully functional Fresnel Query Processor, the builder and result interfaces would have to be enhanced. | ||
Fresnel supports "get-all" where you can get the values of all of the predicates of an object or all but a particular group. I imagine that most query mechanisms have this facility. Problem is that the XUL Builder doesn't support this. It needs explicit names for all the predicate values it receives. It can't just walk a result object using value="?*" or some such wildcard | * Fresnel supports "get-all" where you can get the values of all of the predicates of an object or all but a particular group. I imagine that most query mechanisms have this facility - SPARQL does too in a round about way. Problem is that the XUL Builder doesn't support this. It needs explicit names for all the predicate values it receives. It can't just walk a result object using value="?*" or some such wildcard. | ||
Fresnel supports label attachment for values so for example, if you get a value for the predicate "http:.../wife" of say "Mary", you can also attach the label "Wife" to Mary for the builder to use. By default that label | * Fresnel supports label attachment for values so for example, if you get a value for the predicate "http:.../wife" of say "Mary", you can also attach the label "Wife" to Mary for the builder to use. By default that label comes from OWL. The result object, [TemplateResult http://wiki.mozilla.org/XULTemplatesAPI#Result_Objects] passed from the Query processor to Builder doesn't have a slot for "label". Without it, you loose one of the nicest features of a Fresnel processor or similar OWL-aware Query Processor. | ||
==== Scope: must a Query Processor sort or ensure uniqueness? ==== | ==== Scope: must a Query Processor sort or ensure uniqueness? ==== | ||
edits