- From: Felix Sasaki <fsasaki@w3.org>
- Date: Wed, 29 Aug 2012 11:29:42 +0200
- To: public-multilingualweb-lt@w3.org
- Message-ID: <CAL58czoPQK2ZMDP8Czi_2YTmw-OZveue4Oaz4fvBSbZ8jxPotQ@mail.gmail.com>
Hi all, to make inheritance in the spec clearer, I would do the following: - delete the column "overring", since this doesn't provide any new information: every data category that inherits information to (element or attribute) nodes allows for overriding. I would then also delete "*Overriding* describes whether ITS information can be overridden or not. Overriding is only applicable for data categories with inheritance. Overriding thus is not applicable for the Terminology<http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#terminology> and the Ruby<http://www.w3.org/International/multilingualweb/lt/drafts/its20/its20.html#ruby-annotation> data category." And have instead "Each data category that allows for inheritance also allows for overriding ITS information." At the end of section 6.1., I would then add a note like this: "An application is free to decide what pieces of content it uses. For example: - Terminology information is added to a "term" element. The information pertains only to the content of the element, since there is no inheritance. Nevertheless an ITS application can make use of the complete element, e.g. including attribute nodes etc. - Using "ID value", an ID value is identified for a "p" element. An application can make use of the complete "p" element, including child nodes and attributes nodes. The application is also free to make use just of the string value of "p". Nevertheless the ID pertains only to the "p" element in question. - Using "target pointer", a "source" element gets the information that the translation is available in a "target" element; see Example 61. This information does not inherit to child elements of "target pointer". E.g., a "span" element nested in "source" does not have the translation available in "target". Nevertheless, an application is free to use the complete content of "source" e.g. and present it to a translator. Does this help? If yes I'd add it to the spec. Best, Felix -- Felix Sasaki DFKI / W3C Fellow
Received on Wednesday, 29 August 2012 09:30:26 UTC