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.

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

Improve coverage GRAPH ?g {} #160

Merged
merged 2 commits into from
Jan 16, 2025
Merged

Improve coverage GRAPH ?g {} #160

merged 2 commits into from
Jan 16, 2025

Conversation

Tpt
Copy link
Contributor

@Tpt Tpt commented Jan 14, 2025

Graph <...> {} should return a single empty solution if the graph exists and no solution if it does not

@@ -0,0 +1 @@
SELECT * { GRAPH <unknown> {} }
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unknown should probably become a valid IRI, such as

Suggested change
SELECT * { GRAPH <unknown> {} }
SELECT * { GRAPH <ex:unknown> {} }

Copy link
Contributor

@afs afs Jan 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<ex:unknown> is fine. Realistically, a URI scheme of ex meaning anything else is asking for trouble!

Aside --

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is already a valid IRI because of the implicit base IRI. I have moved to ex:unknown to make it less confusing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your reviews!

`Graph <...> {}` should return a single empty solution if the graph exists and no solution if it does not
@Tpt Tpt force-pushed the sparql-more-empty-graph branch from 9cd8215 to 16566fa Compare January 15, 2025 17:10
@afs afs requested a review from rubensworks January 16, 2025 08:55
@afs afs merged commit 9501792 into main Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants