Disputes

[michielbdejong]

List of spec issues that dispute tests we have:

• Decision: Access Rule with acl:default does not imply acl:accessTo solid/specification#193 (comment)

  • Create > Using POST to existing container > Is disallowed otherwise

• Which permissions are required for PUT to create? solid/specification#236 (on hold until we decide #193)

  • Create > Using PUT in existing container > is disallowed without accessTo Write or Append
  • Create > Using PATCH in existing container > is disallowed without accessTo Write or Append
  • Create > Using PUT in non-existing container > is disallowed without accessTo Write or Append
  • Create > Using PATCH in non-existing container > is disallowed without accessTo Write or Append

• Should PUT-to-create c/r in existing container be allowed with only accessTo Write c/? solid/specification#246

  • Create > Using PUT in existing container > is disallowed without default Write
  • Create > Using PATCH in existing container > is disallowed without default Write
  • Create > Using PUT in non-existing container > is disallowed without default Write
  • Create > Using PATCH in non-existing container > is disallowed without default Write

• Is Read required on top of Write for PATCH delete and where ? solid/specification#220 (on hold until we decide Make any deviation of SPARQL UPDATE explicit solid/specification#139)

• Update > Using PATCH to overwrite > Is disallowed with accessTo Write+Control access on resource
• Update > Using PATCH to overwrite > Is disallowed with default Write+Control access on parent

[michielbdejong]

Resolving solid/specification#193 as 'yes' because of arguments we arrived at in solid/specification#193 (comment).

@csarven confirmed that the answer to solid/specification#236 is:
If c/ exists but c/r does not, then PUT to create c/r requires append or write on c/ + write on r.
so answer to solid/specification#246 is also 'no'.
anser to solid/specification#220: 'yes' (but we will use content-type application/sparql-update-single-match from now on, see solid/specification#139 (comment)).