- From: r12a via GitHub <sysbot+gh@w3.org>
- Date: Tue, 24 May 2016 09:36:34 +0000
- To: public-annotation@w3.org
@azaroth42 's proposal cuts to the centre of what i see as the problem, which is that given a list of languages it's ambiguous which to use for the default text-processing language, so if it's workable to have the processingLanguage property i think that would probably solve the issue. Just a suggestion: for additional clarity, it may help to add some wording along the lines proposed by Asmus, such as: "The Body or Target SHOULD have exactly 1 language associated with it, but MAY have 0 or more if the language cannot be identified or the resource contains content in more than one language. ..." -- GitHub Notification of comment by r12a Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/213#issuecomment-221216994 using your GitHub account
Received on Tuesday, 24 May 2016 09:36:37 UTC