- From: Renato Iannella via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Dec 2016 04:18:37 +0000
- To: public-poe-archives@w3.org
We have a slight issue now... Scope was modelled for Parties as explicit subclasses of Parties. For example, "All2ndConnections" is a type of Party - (which I think is not correct ;-) And, or course, this is not reusable for Asset. Hence, I propose we add an class called Scope and relation (has scope) to the ontology. These can then be used for Asset. I propose we re-classify the Party-based Scopes to be all subclasses of Scope (and Party then needs to use the "has scope" property) >From the implementors survey, it seems no-one has used these Scope classes, so there should be minimal impact. It will mean that these examples will have to be updated: http://w3c.github.io/poe/vocab/#sc-example10 Thoughts???? -- GitHub Notification of comment by riannella Please view or discuss this issue at https://github.com/w3c/poe/issues/59#issuecomment-265929928 using your GitHub account
Received on Friday, 9 December 2016 04:18:44 UTC