- From: Rob Atkinson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 03 Sep 2019 03:50:23 +0000
- To: public-dxwg-wg@w3.org
I suggest looking at some concrete examples that matter to you and trying to describe the roles they have. Resources can have multiple roles - and be both human readable or machine readable if they are identified by URIs that support content negotiation - so you would need to declare what each conformsTo (its nature) and its available formats - trying to shoehorn that sort of information into role naming conventions then asking clients to interpret would be counterproductive. (I'm not arguing for the existing roles - but we need good evidence of something that cannot be properly described using them, including using multiple roles if needed. looking at the list above they are mainly mixed concerns better described formally with conformsTo and hasFormat. The one that sticks out as possibly having a unique and important semantics is "vocabulary" - what sort of a role is "vocabulary" - can we identify a concrete case in the wilde of a resource that performs this role? -- GitHub Notification of comment by rob-metalinkage Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1049#issuecomment-527293429 using your GitHub account
Received on Tuesday, 3 September 2019 03:50:25 UTC