W3C home > Mailing lists > Public > public-sparql-12@w3.org > October 2019

SEP - Some technical areas

From: Andy Seaborne <andy@apache.org>
Date: Sun, 27 Oct 2019 10:58:51 +0000
To: "SPARQL 1.2 Community Group" <public-sparql-12@w3.org>
Message-ID: <0a3896bf-564e-485e-0d1b-61b1ca02ab2c@apache.org>
<Personal opinion>

There are some "core" areas that change the evaluation model. For 
example, free text (#40) should use the function call mechanism #6.

== Functions

#6    Function call - algorithms and indexes.
#64   Named arguments for SPARQL functions
#20   Dynamic function invocation

If the function area is defined, access to e.g. graph analytics 
algorithms, or specialized indexing has a common basis.

== Data model

#46   Lists
#44   Named tables
#94   Temporary tables, Views

Data model changes.

Do we need "list" as a list? what about paths as result terms?
A question here is now much change to put in "1.2"


Two areas that seem to have wide appeal.

== Property Paths

#101  Property paths
#99   Predicates in property paths
#65   Allow use of variables in property paths

== Protocol and Result Sets

#51   Paging and partial result errors.
#49   Paging and cursors
#7    Async queries.

Received on Sunday, 27 October 2019 10:58:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:26:45 UTC