- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Sat, 21 Nov 2015 16:13:12 +0000
- To: public-annotation@w3.org
*As a user* I would think that restricting the number of roles to zero or one is too much of a restriction. In any similar situations (tagging, usage of ARIA role attribute; in some sense assigning a class to a term in RDF) the fact of being able to add several such labels seems natural for me. *As an implementer* I of course see the additional complication. However... in my experience, in everyday usage of Javascript (and, as an extension, in models using JSON) this type of type overloading is fairly widespread. (We have faced similar issues in the case of the CSV Metadata vocabulary.) Javascript programmers are pretty much used by such checks and branches. We should give higher priority to the user expectations; within reasonable bounds implementers will follows. Ie, I would prefer to allow possible more than one role per resource. -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/104#issuecomment-158659339 using your GitHub account
Received on Saturday, 21 November 2015 16:13:14 UTC