Re: [Specifications] Strongly typed collections in API documentation (#233) from Tomasz Pluskiewicz via GitHub on 2021-05-25 (public-hydra-logs@w3.org from May 2021)

From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
Date: Tue, 25 May 2021 18:47:33 +0000
To: public-hydra-logs@w3.org
Message-ID: <issue_comment.created-848156875-1621968451-sysbot+gh@w3.org>

I like what you write in the last paragraph.

If the domain was changed to loosely allow both `Class` and `Collection`

```diff
hydra:memberAssertion 
-  rdfs:domain hydra:Collection ;
+  schema:domainIncludes hydra:Class, hydra:Collection ;
.
```

Then it would be possible to place the assertions on both instances and (sub)class, similarly to what second snippet proposes

```turtle
api:UserCollection
  rdfs:subClassOf hydra:Collection ;
  hydra:memberAssertion [
    hydra:predicate rdf:type ;
    hydra:object api:User ;
  ] ;
.

</users>
  a api:UserCollection ;
  hydra:memberAssertion [
    hydra:predicate rdf:type ;
    hydra:object api:User ;
  ] ;
.
```

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


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

Received on Tuesday, 25 May 2021 18:47:34 UTC