- From: makxdekkers via GitHub <sysbot+gh@w3.org>
- Date: Thu, 14 Feb 2019 09:44:24 +0000
- To: public-dxwg-wg@w3.org
An advantage that I see for using SKOS roles is that the responsibility is moved to someone else and this group doesn't have to worry about it, beyond defining a property to point to a role concept. The disadvantage is that, when people start creating their own role vocabularies, it will be hard to interoperate across different role vocabularies. This risk would be mitigated by having a 'central' role vocabulary, but then there is a need for a maintenance agency. A W3C working group cannot be responsible for that kind of governance as its lifespan is limited. Creating a small set of subproperties of at least has the advantage that there is a fixed set of anchor points that people can rely on. With a set of subproperties, a lazy publisher can decide just to use one (or more) of those; if the roles are expressed as SKOS concepts, the publisher **must** search for an existing role vocabulary that fits their needs or create their own. The question for me is how much precision is going to be required to distinguish roles and how more or less precision is going to help or hinder interoperability. -- GitHub Notification of comment by makxdekkers Please view or discuss this issue at https://github.com/w3c/dxwg/issues/747#issuecomment-463561380 using your GitHub account
Received on Thursday, 14 February 2019 09:44:25 UTC