On 26/04/17 07:28, Claude Warren wrote:
Greetings,
I was reading the "who made such idiocy" thread and began to think about
how one might introduce a "function" that could return more than one value
as was noted in the message stack.
I started thinking about how XSLT has extension elements and thought
perhaps a property type that rather than being a standard lookup performs a
function based on the object of the statement.
For example: assume ex:textLookup calls a text index lookup function and
returns the object of triples that have the values. Further assume
textLookup takes an argument list comprising the property to have the value
and a list of text items to look for. Then:
?x ex:textLookup (dc:comment, "now", "is", "the", "time" );
would return a list of objects that have dc:comment properties that contain
"now" or "is" or "the" or "time".
This would be a major change to how properties are handled as any property
that is a function would have to be identified and executed separately.
But I think as a construct it might work and it would be in concept similar
to the XSLT extension element.
Thoughts?
ARQ already has this - called "property functions".
Your specific example is the current text:query.
Andy
Claude
