- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Aug 2017 16:22:44 +0000
- To: public-hydra-logs@w3.org
*[drafts/use-cases/1.1.security-considerations.md, line 18 at r2](https://reviewable.io:443/reviews/hydracg/specifications/132#-KrUSFWcxbytETQ1yIEc:-KrafHHAVaZSxiDYZx8V:ba321m7) ([raw file](https://github.com/hydracg/specifications/blob/8c2db652e54f3e4ed52b855e05c73330d9d2d2ea/drafts/use-cases/1.1.security-considerations.md#L18)):* <details><summary><i>Previously, tpluscode (Tomasz Pluskiewicz) wrote…</i></summary><blockquote> The element type of `friends` and `enemies` will both be a Person in the manages block? Again, the client cannot distinguish between two collection having clearly different meaning... </blockquote></details> In case above manages blocks wouldn't rely on 'type' `property: rdf:type` but instead on properties like: * http://purl.org/vocab/relationship/friendOf * http://purl.org/vocab/relationship/enemyOf * http://smiy.sourceforge.net/cco/spec/cognitivecharacteristics.html#interest Which capture the relation between `/some-person` and each member in the collection. Not the 'type' of the member - relation between some instance of `rdfs:Class` and each member in the collection. Have you participated in defining [Collection Design](https://www.w3.org/community/hydra/wiki/Collection_Design)? Possibly it needs better documentation and clarified motivation beyond linking to gh issues. We didn't think about use case of `rdf:type` property when we discussed his design but it seems perfectly fit to handle it as well. --- *Comments from [Reviewable](https://reviewable.io:443/reviews/hydracg/specifications/132)* <!-- Sent from Reviewable.io --> -- GitHub Notification of comment by elf-pavlik Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/132#issuecomment-322515869 using your GitHub account
Received on Tuesday, 15 August 2017 16:22:45 UTC