Reto,
There's lots to be learnt from Clerezza. Clerezza is a "presentation
API" - it is aimed at giving applications a programming model. That it
also claims to encapsulate other systems is, to the application code,
secondary - users adopt the Clerezza API in their applications and all
it's
** Basic concepts
The most basic RDF concepts.
Node
IRIs
Literal(lexical form, datatype node, lang tag) No "value"
BlankNode
and add in
Var (a named variable), NodeGraph (graph literals)
NodeSymbol (a keyword e.g. ANY for a wildcard)
Adding these generalized-RDF node typ
Very glad you've started such a uniformications discussion on the jena
mailing list. I think it would be good to have such an API adopted by Jena
as well. I think it would be important for such an API to be based on
standards and not specifically on triple-stor design as to allow exposing
other obj
Rob's comments on inverting the reader process [2] suggest to me pulling
out an API and I wonder if we can identify a portability layer that
enables some (not all) interoperability and mix-n-match.
The term "API" is creating some confusion in the discussions triggered
by the Clerezza incubator
