Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Criteria for evaluating errata changes for EXISTS #130

Open
afs opened this issue Oct 28, 2023 · 2 comments
Open

Criteria for evaluating errata changes for EXISTS #130

afs opened this issue Oct 28, 2023 · 2 comments
Labels
spec:bug Change fixing a bug in the specification (class 3) –see also spec:substantive

Comments

@afs
Copy link
Contributor

afs commented Oct 28, 2023

This issue is to collect criteria we can use to assess the different proposals for EXISTS.

https://github.com/w3c/sparql-query/issues?q=is%3Aissue+is%3Aopen+exists

SPARQL Tests:
SPARQL 1.1 test suite - exists
SPARQL 1.1 test suite - negation

TPAC 2023 Slides:
SPARQL @ TPAC 2023.pdf
@afs
Copy link
Contributor Author

afs commented Oct 28, 2023

Criterion: continuity

SPARQL 1.1 queries that do not involve the identified problem areas should not be affected.

@Tpt
Copy link
Contributor

Tpt commented Oct 31, 2023 •
edited
Loading

Criterion: provide interesting features

The MINUS operator already exists with anti-join semantic. It would be nice for FILTER NOT EXISTS to not be a duplicate of MINUS by not making it have the exact same semantic as MINUS.

@pfps pfps added the spec:bug Change fixing a bug in the specification (class 3) –see also spec:substantive label Jan 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
spec:bug Change fixing a bug in the specification (class 3) –see also spec:substantive
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@afs @Tpt @pfps