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

N3 Patch contradiction about blank nodes: can they be part of ?insertions? #704

Open
lecoqlibre opened this issue Jan 7, 2025 · 2 comments · May be fixed by #711
Open

N3 Patch contradiction about blank nodes: can they be part of ?insertions? #704

lecoqlibre opened this issue Jan 7, 2025 · 2 comments · May be fixed by #711

Comments

@lecoqlibre
Copy link
Contributor

In the current section 5.3.1 Modifying Resources Using N3 Patches of the Solid protocol (v0.11.0 - 12 May 2024), we can both read that:

The ?insertions and ?deletions formulae MUST NOT contain blank nodes. (source)

AND:

The triples resulting from ?insertions are to be added to the RDF dataset, with each blank node from ?insertions resulting in a newly created blank node.

The latter suggests that ?insertions can contain blank nodes while the former explicitly forbids.

@bourgeoa
Copy link
Member

bourgeoa commented Feb 1, 2025

@csarven @CxRes @timbl

This N3PATCH in RdfLib is a valid test (not spec compliant) should be allowed in spec and then in CSS

https://github.com/linkeddata/rdflib.js/blob/82f693dc10d5b915f97eedeab5351cf831c3611e/tests/unit/update-manager-n3patch-insert-test.ts#L84-L99

The same triple is a also a valid application/sparql-update test and is working in both NSS/CSS PATCH

@csarven
Copy link
Member

csarven commented Feb 6, 2025

There is a proposal to resolve this issue in #711 .

@csarven csarven linked a pull request Feb 6, 2025 that will close this issue
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 a pull request may close this issue.

3 participants