- From: aphillips via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Aug 2016 18:23:22 +0000
- To: public-annotation@w3.org
@r12a I disagree with this: > "The value of the property SHOULD be zero or more comma-separated language tags which follow the [bcp47] specification." There is no point in making the property a list. Making the property into a list makes is superfluous: we already have a `language` property that can appear 0 or more times. The point of having `processingLanguage` is to make it a *single* language tag that, in the presence of multiple `language` properties, determines the default language used for processing the resource. It only exists because `language` is already a zero-or-more and because `language` is not (in BCP47-parlance) a "language priority list" (that is, multiple values do not have a fallback order). There is nothing to prevent a resource from actually containing many different languages and the `language` property can already be used to indicate the various languages used. But implementations need an unambiguous way to know which language to use for, say, font selection. I would also prefer that the normative text say that the value of the property MUST be a well-formed BCP47 language tag. -- GitHub Notification of comment by aphillips Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/345#issuecomment-239522763 using your GitHub account
Received on Friday, 12 August 2016 18:23:28 UTC