- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Jan 2016 11:32:22 +0000
- To: public-annotation@w3.org
I respectfully disagree. Setting the type for resources where this is not necessary is an extra load on users where this does not add any relevant information. That section of the document has a number of examples where the type information is not present. Implementers may find the type of the resources based on the properties that are used. In the RDF world, this is a fairly standard approach if the vocabulary clearly specifies the domain and/or the range or predicates. (There may be ambiguous cases where having the type information is good to have.) Having the vocabulary and its usage be simpler for users has a higher priority than saving some extra work for implementers... -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/137#issuecomment-171938756 using your GitHub account
Received on Friday, 15 January 2016 11:32:25 UTC