nodeSolidServer / nodeSolidServer/node-solid-server
Fix conformance to SPARQL Update / Query's prefix declaration
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
Snippet of an example request:
PATCH https://example.org/test.ttl HTTP/1.1
Content-Type: application/sparql-update
PREFIX acl: <http://www.w3.org/ns/auth/acl#>
Snippet of an example response:
HTTP/1.1 400 Bad Request
X-Powered-By: solid-server/5.7.11
Accept-Patch: application/sparql-update
Content-Type: text/plain; charset=utf-8
Content-Length: 206
Patch document syntax error: Line 1 of <https://example.org/test.ttl>: Bad syntax:
Unknown syntax at start of statememt: 'PREFIX acl: <http://'/
at: "PREFIX acl: <http://www.w3.org/"
AFAICT, https://github.com/linkeddata/rdflib.js/issues/651 captures the issue in that NSS rejects SPARQL Update requests with valid payload using PREFIX (and accepts invalid payload containing @prefix).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named. Start by reproducing the PATCH request with Content-Type application/sparql-update and the PREFIX declaration, then compare the parser behavior with rdflib.js issue 651; done means valid PREFIX payloads are accepted while invalid @prefix handling follows the intended SPARQL conformance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100