- From: Felix Sasaki <fsasaki@w3.org>
- Date: Thu, 21 Dec 2006 16:48:54 +0900
- To: public-i18n-its@w3.org
Based on http://lists.w3.org/Archives/Public/public-i18n-its/2006OctDec/0058.html and http://lists.w3.org/Archives/Member/member-i18n-its/2006OctDec/0052.html , I have made the following updated proposal about the output format. I now realized that I used strange namespace URIs. Yves suggested "urn:ITSTestResult" recently (that would be used instead of "http://example.com/output"). Any ideas / preferences ? What should we use for (instead of) http://example.com/testresults ? === Translate data category: If the node is translatable: <output translate="yes" xmlns="http://example.com/output"/> If the node is not translatable: <output translate="no" xmlns="http://example.com/output"/> === Localization Note data category: If there is no localization information associated with the node: <output xmlns="http://example.com/output"/> If there is a locNote text associated with the node (locNoteType is required): <output locNoteType="description|alert" xmlns="http://example.com/output"> <locNoteText>The inner text of the node (can be empty, might also contain markup)</locNoteText> </output> If there is a locNote reference associated with the node (locNoteType is required): <output locNoteType="description|alert" xmlns="http://example.com/output"> <locNoteReference>The reference string (can be empty, might also contain markup)</locNoteReference> </output> === Terminology data category: If the node is not a term: <output term="no" xmlns="http://example.com/output"/> If the node is a term and the termInfo is text: <output term="yes" xmlns="http://example.com/output"> <termInfoText>Inner text of the node (can be empty, might also contain markup)</termInfoText> </output> (I assume that we will have no <termInfoText> element if there is no information available) If the node is a term and the termInfo is text: <output term="yes" xmlns="http://example.com/output"> <termInfoReference>The reference string (can be empty, might also contain markup)</termInfoReference> </output> === Element Within Text data category: If the node is within text: <output withinText="yes" xmlns="http://example.com/output"/> If the node is nested: <output withinText="nested" xmlns="http://example.com/output"/> If the node is neither within text nor nested: <output withinText="no" xmlns="http://example.com/output"/> === Directionality data category: If there is explicit directionality information: <output dir="DIRVAL" xmlns="http://example.com/output"/> (DIRVAL is ltr, rtl, lro or rlo) If there is no explicit directionality information: <output dir="ltr" xmlns="http://example.com/output"/> (default is ltr) === Ruby data category: If there is ruby information available: <output> <ruby xmlns="http://example.com/output"> <rb>(can be empty, might also contain markup)</rb> <rp>(can be empty or ommited, might also contain markup)</rp> <rt>(can be empty, might also contain markup)</rt> </ruby> </output> Cheers, Felix
Received on Thursday, 21 December 2006 07:49:09 UTC