PATCH does not work on turtle
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
Research direction
Reproduce the supplied PATCH against the original Turtle resource, comparing the prefixed xsd:nonNegativeInteger form with the full datatype IRI. Trace the PATCH handling and Turtle/RDF parsing path; done means the DELETE DATA request succeeds when the resource uses the xsd prefix, with a regression test covering both forms.
Written by the indexing model from the issue text.
Description
Hi all,
I was unsuccessfully trying to HTTP PATCH a turtle file. If I don't prefix the 'xsd' namespace the patch works.
Original resource:
@prefix : <#>.
@prefix as: <https://www.w3.org/ns/activitystreams#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
@prefix p: <./>.
@prefix notes: <../>.
p:546851bd-1db4-4b8d-bea2-1a33e982c73b
a as:OrderedCollectionPage;
as:partOf notes:mynotes;
as:startIndex "0"^^<xsd:nonNegativeInteger>.
PATCH:
DELETE DATA { <https://diegoalbuquerque.localhost:8443/tests/collections/notes/pages/546851bd-1db4-4b8d-bea2-1a33e982c73b> <https://www.w3.org/ns/activitystreams#startIndex> "0"^^<http://www.w3.org/2001/XMLSchema#nonNegativeInteger>. }
RESULT:
The patch could not be applied. Could not find to delete: <https://diegoalbuquerque.localhost:8443/tests/collections/notes/pages/546851bd-1db4-4b8d-bea2-1a33e982c73b> <https://www.w3.org/ns/activitystreams#startIndex> "0"^^<http://www.w3.org/2001/XMLSchema#nonNegativeInteger> .
This works:
@prefix : <#>.
@prefix as: <https://www.w3.org/ns/activitystreams#>.
@prefix p: <./>.
@prefix notes: <../>.
p:546851bd-1db4-4b8d-bea2-1a33e982c73b
a as:OrderedCollectionPage;
as:partOf notes:mynotes;
as:startIndex "0"^^<http://www.w3.org/2001/XMLSchema#nonNegativeInteger>.
Am I doing something wrong?
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
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.
More from nodeSolidServer/node-solid-server
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
nodeSolidServer/node-solid-server#1848 · 2 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nodeSolidServer/node-solid-server#1841 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
nodeSolidServer/node-solid-server#1147 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
nodeSolidServer/node-solid-server#1867 ·
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
nodeSolidServer/node-solid-server#1853 ·
All issues in nodeSolidServer/node-solid-server
Similar issues
-
bug customer-eng Durable Agents Inngest status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-cao#13475 ·
-
[BUG]: "Clear All" in Settings doesn't clear the saved analysis, old data comes back after reload Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
AOSSIE-Org/OrgExplorer#253 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
oxc-project/oxc#26944 ·
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100