3495 2006-07-19 17:20:15 +0000 Hard to know what this is about 2006-10-03 14:50:41 +0000 1 1 1 Unclassified ITS ITS tagset WorkingDraft PC Windows XP CLOSED FIXED proposalAccepted, reviewerSatisfied P2 normal AfterLC 3318 1 fsasaki fsasaki fsasaki oldest_to_newest 10603 0 fsasaki 2006-07-19 17:20:15 +0000 Issue #23 of i18nCore comments http://www.w3.org/International/reviews/0606-its/ The definition of flow of content as 'representing how the nodes of the element should be treated as a single unit for linguistic purposes' is not only hard to read, but doesn't tell me anything about its intended use. Could we be talking about identifying noun phrases? I think we are talking about identifying translation unit segmentation breaks. If this is the case, please make that clear. I think people reading this could be either unclear about its intent, or misunderstand in such a way that it is implemented for all sorts of uninteroperable structural definitions of the content. 10715 1 ysavourel 2006-07-24 15:23:56 +0000 This issue is related to the bug #3318 http://www.w3.org/Bugs/Public/show_bug.cgi?id=3318 The proposed new text is: "The data category elements within text expresses information about how text parts that go together from a linguistic viewpoint (e.g. sentences, or paragraphs) are affected by elements. For example, the content of the element in XHTML should not be separated from the text of its parent element. On the other hand the content of the <fn> element in DITA is independent from the content of its parent element. The values associated with this data category are:" 10722 2 fsasaki 2006-07-24 16:53:35 +0000 Action: working group to look at the proposal from Yves at http://www.w3.org/Bugs/Public/show_bug.cgi?id=3495#c1 . 10872 3 fsasaki 2006-07-28 15:26:34 +0000 Discussed at http://www.w3.org/2006/07/28-i18nits-minutes.html#item05 . Action: Yves to reword http://www.w3.org/Bugs/Public/show_bug.cgi?id=3495#c1 taking today's discussion into account. 10884 4 ysavourel 2006-07-31 13:58:48 +0000 Here is my new proposal: ----- This data category expresses how elements affect the way text content is broken down from a linguistic viewpoint. This is used, for example, to provide basic text segmentation for linguistic tools. The values associated with this data category are: - "yes" : The element and its content are part of the content of its parent element. Example: The element in XHTML Appaloosa horses have spotted coats. - "nested" : The element is part of the content of its parent element, but its content is a separate text unit. Example The element <fn> in DITA Palouse horses<fn>A Palouse horse is the same as an Appaloosa.</fn> have spotted coats. - "no" : The element splits the content of its parent element and each part is a separate text unit. Example : The element when inside the element <li> in DITA or XHTML <li>Palouse horses: They have spotted coats. They have been breed by the Nez Perce. </li> Elements not listed are considered to have the value "no". ----- 10918 5 fsasaki 2006-08-01 01:17:28 +0000 Discussed at http://www.w3.org/2006/07/31-i18nits-minutes.html#item08 . Action: working group to look at Yves proposal at http://www.w3.org/Bugs/Public/show_bug.cgi?id=3495#c4 . 11109 6 ysavourel 2006-08-14 13:36:34 +0000 Discussd during teleconference. Christian to propose change in text. See the proposal here: http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0258.html 11202 7 ysavourel 2006-08-17 13:59:08 +0000 *** Bug 3318 has been marked as a duplicate of this bug. *** 11203 8 ysavourel 2006-08-17 14:04:29 +0000 The new text (yves' proposal and christian's edit is: ----- The data category "Elements within text" reveals if and how an element affects the way text content behaves from a linguistic viewpoint. This information is for example relevant to provide basic text segmentation hints for tools such as translation memory systems. The values associated with this data category are: - "yes" : The element and its content are part of the content of its parent element. Example: The element in XHTML Appaloosa horses have spotted coats. - "nested" : The element is part of the content of its parent element, but its content is a separate text unit. Example The element <fn> in DITA Palouse horses<fn>A Palouse horse is the same as an Appaloosa.</fn> have spotted coats. - "no" : The element splits the content of its parent element and each part is a separate text unit. Example : The element when inside the element <li> in DITA or XHTML <li>Palouse horses: They have spotted coats. They have been breed by the Nez Perce. </li> Elements not listed are considered to have the value "no". ----- Action: editors to make the change. 11209 9 christian.lieske 2006-08-18 08:28:17 +0000 Comment has been implemented as follows: <list type="unordered"> <item> <val>yes</val> : the element and its content are part of the flow of its parent element ; the element in XHTML; is an example: Appaloosa horses have spotted coats. </item> <item> <val>nested</val> : the element is part of the flow of its parent element, its content is an independent flow;the element <fn> in DITA is an example: Palouse horses <fn> A Palouse horse is the same as an Appaloosa. </fn> have spotted coats. </item> <item> <val>no</val> : the element splits the text flow of its parent element and its content is an independent text flow; the element when inside the element <li> in DITA or XHTML: <li> Palouse horses: They have spotted coats. They have been breed by the Nez Perce. </li> </item> </list> 11440 10 fsasaki 2006-09-06 21:00:09 +0000 Action: to make the change 11578 11 fsasaki 2006-09-11 02:45:06 +0000 Wait: response sent. See http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0316.html 11710 12 ysavourel 2006-09-14 03:50:56 +0000 Closed. Commenters satisfied see: http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0362.html 12147 13 fsasaki 2006-09-28 06:43:03 +0000 Summary: The Working Group decided to accept the proposal and clarified the description of the "elements within text" data category.