Re: [Specifications] Retracting operations (#241)

• From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
• Date: Mon, 12 Jul 2021 18:58:45 +0000
• To: public-hydra-logs@w3.org
• Message-ID: <issue_comment.created-878517071-1626116323-sysbot+gh@w3.org>

Off the top of my head, the actual operation being retracted has to be directly associated with a specific resource.

And maybe we could reuse `hydra:operation` and add a class of unsupported operations?

```http
GET /article/1

{
  "@id": "/article/1",
  "@type": "schema:Article",
  "api:status": "api:published",
  "operation": {
    "@type": ["hydra:UnsupportedOperation", "schema:RemoveAction"],
    "rdfs:comment": "Published articles cannot be removed"
  },
  "schema:primaryImageOfPage": {
    "schema:contentUrl": "/image/article-1", 
    "operation": {
      "@type": ["hydra:UnsupportedOperation", "schema:ReplaceAction"],
      "rdfs:comment": "Insufficient permissions"
    }
  }
}
```

This way, a client implemented to go through the inline operations first would gather those unsupported and exclude any matches supported by classes (`schema:Articles`) and properties (`schema:Article schema:primaryImageOfPage`).

-- 
GitHub Notification of comment by tpluscode
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/241#issuecomment-878517071 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 12 July 2021 18:58:47 UTC