Unsufficient restriction over user supplied containment triples

Open

#451 opened on Aug 28, 2022 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 35/100

Issue type: Feature
Clarity: Needs clarification
Activity status: Stale
Domain: api

Research direction

Read the existing PUT/PATCH requirement and its cited Solid specification issue comment first. Then determine whether POST-created container representations may carry containment triples; done requires an agreed normative requirement for that case to be recorded in the specification.

Written by the indexing model from the issue text.

Description

Currently following requirement is the only one that restricts user supplied containment triples.

Servers MUST NOT allow HTTP PUT or PATCH on a container to update its containment triples; if the server receives such a request, it MUST respond with a 409 status code. [Source]

But that allows including containment triples in representation of to be created container, when container is created through POST on parent container.

It may not be the intention.

Dominant language: HTML
Stars: 563
Forks: 110
Avg merge: 4d 13h
Merged PRs (30d): 3

Contributor guide

Open the contributing 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.

Similar issues

`Array.initialize` and `Array.repeat` throw on a negative count Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

gren-lang/core#167 · Opened Sep 25, 2026
fix(pg-meta): schemas.update and schemas.remove DO blocks fail when a name contains "$$" Open

external-issue to-triage

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

supabase/supabase#50882 · Opened Sep 24, 2026
wkt: `WKTFieldMask.paths` is an immutable `public let paths: [String]` with no default `init(paths: [String] = [])` or `.with(_:)` helper, preventing in-place mutation Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

googleapis/google-cloud-swift#1151 · Opened Sep 24, 2026
SqliteSaver.list(filter=...) silently misses nested metadata values containing non-ASCII text Open

external

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

langchain-ai/langgraph#9074 · 1 comment · Opened Sep 24, 2026
Correct FileCitationBody.index documentation to describe its position in output text Open

documentation specification

Difficulty 1/5 Under an hour Newbie friendliness 90/100

openai/openai-openapi#584 · Opened Sep 24, 2026

More Backend & API Design issues