- From: gsergiu via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Feb 2016 18:20:14 +0000
- To: public-annotation@w3.org
Hi @azaroth42 Well.. for the multilinguality/i18n problem the concept of using a choice construct seems ok for me, still incomplete. With this regard I have additional questions: 1. Why if the user uses simple texts and not resourced that have an id/URI? the current definition says: "A Choice has an ordered list of resources" And the annotation from the example is basically made to link the two previously created resources. In my example I just wanted to post a comment (in something like twitter) "Happy New Year"@en/"Froehes Neues Jahr"@de/"La multi ani"@ro and I would like that my romanian friend see the text deplayed in romanian, the austrian ones in german and the rest in english... Yes, it looks like a choise but with embedded text. 2. Moreover I would like to define a default choice, and probalby also with a preffered choice (e.g. I have some friends that understand both german and romanian) Prefered & Default choice would be very useful for decinding which text to display in the frontend. 3. Is this the way chose to represent the "SemanticTags"? Because for these tags we would like to store the text of "skos:prefferedLabels" within the annotations, becasue I don't want to send 2 or more queries in order to be able to display an annotation (i.e. one for annotation & one for retrieving the labels in all langagues). -- GitHub Notification of comment by gsergiu Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/149#issuecomment-181508503 using your GitHub account
Received on Monday, 8 February 2016 18:20:16 UTC