- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Sat, 21 Nov 2015 16:23:32 +0000
- To: public-annotation@w3.org
> > Agreed. > > I'm not sure it's within scope of the Model spec (certainly) to define (even non-normatively) prescriptions of use for motivations. > > I agree with that. It can lead to endless discussions and would be almost impossible to get a consensus by everyone. The model allows the end user or specific communities to add their own motivations (in RDF terms, by adding a new instance of a specific type; in JSON-LD term by adding an extra, community specific `@context` with the mapping). But without having a core we end up by an increased incompatibility, so we need such a core. Not having been part of earlier discussion I yield to the discussion that did happen over several years (as mentioned by @azaroth42) on what such a core could be, and I would prefer to leave things as they are. (Beware of the danger of bikeshedding…) > Certainly the world of implementors can and should blog (et al) about how they're using them in (and out) of their UI, and it is perhaps (and perhaps intentionally) the place where the widest array of variation will be found...but again...that's why it's written the way it is (citing Jacob's mention of October's similar chat from the other perspective). > -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/113#issuecomment-158659832 using your GitHub account
Received on Saturday, 21 November 2015 16:23:34 UTC