On 14/01/15 14:32, james anderson wrote:
good afternoon;
On 2015-01-14, at 14:56, Andy Seaborne <[email protected]> wrote:
[…]
ok. so, in the lisp sense, these two are the reader and the package definitions.
there still needs to be something which defines the signatures, that is, the
function types.
The functions define their signatures. Some are multi-arity; some have keyword
processing (e.g. distinct). And some evaluations isn't even functional (e.g.
&&).
that is, no one has compiled the information, the individual function
implementation source is the only source and if i use the content of the
Tags.java file to search the source i should find everything?
Could you give some context as to why our asking? Is it to extend ARQ?
Or develop a similar system elsewhere?
Much of this is internal machinery (well, except that much is defined by
the SPARQL spec :-) and gets added to and refined for that purpose. I
never conceived of the implementation as a external contract.
Andy
The idea of a general data structure is that it does not prescribe the
functions or usage.
The SPARQL algebra defines that for it's usage.
All "dynamic" in style.
Andy
best regards, from berlin,
---
james anderson | [email protected] | http://dydra.com
