- From: gsergiu via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Aug 2016 10:16:30 +0000
- To: public-annotation@w3.org
and .. thank you for the good example for the "language" problem. This is very good to take it as concrete input and to annalize what is needed for correct representation. 1. If .. the provided webpage is used as external resource, ... it is clear than the language needs to be included in the html code, for correct representation, and not in the annotation. (as I said above, the list of used dc:languages can be used for search/filtering purposes, but not for correct rendering ) 2. The example you provided could be also used as embedded text ... which is probably best to be formated as html, however ... a pure json based API might not like to embedd html but would like to split the text in multiple bodies .. so that a 1 tp 1 text-language asignment is possible. (In fact ... this is what the i18n reviewers tried to explain ... without having a deep understanding of the WA model) -- GitHub Notification of comment by gsergiu Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/337#issuecomment-237815324 using your GitHub account
Received on Friday, 5 August 2016 10:16:37 UTC