This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
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 <strong> 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:"
Action: working group to look at the proposal from Yves at http://www.w3.org/Bugs/Public/show_bug.cgi?id=3495#c1 .
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.
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 <strong> in XHTML <p><strong>Appaloosa horses<strong> have spotted coats.</p> - "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 <p>Palouse horses<fn>A Palouse horse is the same as an Appaloosa.</fn> have spotted coats.</p> - "no" : The element splits the content of its parent element and each part is a separate text unit. Example : The element <p> when inside the element <li> in DITA or XHTML <li>Palouse horses: <p>They have spotted coats.</p> <p>They have been breed by the Nez Perce.</p> </li> Elements not listed are considered to have the value "no". -----
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 .
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
*** Bug 3318 has been marked as a duplicate of this bug. ***
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 <strong> in XHTML <p><strong>Appaloosa horses<strong> have spotted coats.</p> - "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 <p>Palouse horses<fn>A Palouse horse is the same as an Appaloosa.</fn> have spotted coats.</p> - "no" : The element splits the content of its parent element and each part is a separate text unit. Example : The element <p> when inside the element <li> in DITA or XHTML <li>Palouse horses: <p>They have spotted coats.</p> <p>They have been breed by the Nez Perce.</p> </li> Elements not listed are considered to have the value "no". ----- Action: editors to make the change.
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 <strong> in XHTML; is an example: <strong> Appaloosa horses </strong> 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 <p> when inside the element <li> in DITA or XHTML: <li> Palouse horses: <p>They have spotted coats.</p> <p>They have been breed by the Nez Perce.</p> </li> </item> </list>
Action: to make the change
Wait: response sent. See http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0316.html
Closed. Commenters satisfied see: http://lists.w3.org/Archives/Public/public-i18n-its/2006JulSep/0362.html
Summary: The Working Group decided to accept the proposal and clarified the description of the "elements within text" data category.