- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Thu, 2 Jul 2015 22:56:48 +0200
- To: Markus Lanthaler <markus.lanthaler@gmx.net>
- Cc: public-linked-data-fragments@w3.org, Miel Vander Sande <Miel.VanderSande@UGent.be>, Joachim Van Herwegen <Joachim.VanHerwegen@ugent.be>, Laurens De Vocht <Laurens.DeVocht@UGent.be>
Hi Markus,
I'll start with the most important thing:
> Would this replace the TPF spec?
Certainly not.
The TPF spec also defines a feature, and quite an important one.
This spec will remain as-is, and it will remain an important building block for APIs.
> Do you intend to make some features required to define a least common
> denominator between clients and servers?
That's not the intention at the moment.
The common denominators are the features themselves.
Client are free, however, to demand more.
For instance, if a client needs to solve a complex SPARQL query,
but the server only offers substring search,
then the client cannot complete the task.
However, the client might solve simple queries with this interface, such as:
SELECT ?literal {
?s ?p ?literal.
FILTER REGEX(?literal, "abc")
}
as this can be evaluated using only substring search.
> Another nice weekend read. Could you please share a direct link to the
> papers themselves as well?
The camera-ready versions aren't complete yet,
we will definitely share once they are.
I can share submitted versions in private to those who mail me.
> How do you intend to spec it? Would this replace the TPF spec? Or would
> there be two additional specs?
It would be two (small) additional feature specs, and more could follow later.
The approximate membership metadata spec requires the server also implements TPF.
The substring feature is independent of other features.
(However, to use substrings in complex SPARQL queries, the client also needs TPF.)
Think of it as the machine equivalent of UI controls / widgets.
One spec defines autocompletion, the other defines a search bar,
yet another defines a people tagging control.
But they can all be used together, and depending on what is present
the client/user can or cannot do certain things (more efficiently).
Best,
Ruben
Received on Thursday, 2 July 2015 20:57:23 UTC