- From: gsergiu via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Aug 2016 08:33:18 +0000
- To: public-annotation@w3.org
gsergiu has just created a new issue for https://github.com/w3c/web-annotation: == Cardinality of the processingLanguage? == There are several complains about the processingLanguage property, some saying that this is not property documented, some of them saying that it is not needed at all #335 The processingLanguage was introduced after the i18n review, mainly as solution to the complain that dc:language has multiple values and NLP algorithms need exactly 1 language as input (which I doubt). #213 This ticket is to clarify why does the processingLanguage need to have cardinality 1, in an annotation which has a dc:language with 2 or more values? Consequently, what is the exact difference between the values that should be included in the processingLanguage and the ones included in dc:language? Who should decide the the value of the processingLanguage in the annotation's life cycle? Is it the end user? (is yes why?) Is it the client application? (if yes how should these values be derived?) Is it the server? (probably, if it uses NLP, which values should be set, and how is ensured the consistency with the dc:language) Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/337 using your GitHub account
Received on Friday, 5 August 2016 08:35:25 UTC