This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3318 - Clarify "within text" data category
Summary: Clarify "within text" data category
Status: CLOSED DUPLICATE of bug 3495
Alias: None
Product: ITS
Classification: Unclassified
Component: ITS tagset (show other bugs)
Version: WorkingDraft
Hardware: PC Windows XP
: P2 normal
Target Milestone: AfterLC
Assignee: Yves Savourel
QA Contact: Felix Sasaki
URL:
Whiteboard:
Keywords: proposalAccepted, reviewerSatisfied
Depends on: 3495
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-07 05:54 UTC by Felix Sasaki
Modified: 2006-10-03 14:56 UTC (History)
0 users

See Also:


Attachments

Description Felix Sasaki 2006-06-07 05:54:51 UTC
Comment from Michael Sperberg-McQueen at http://lists.w3.org/Archives/Member/member-i18n-its/2006AprJun/0097.html :
[[The "with text" data category: Is it styling or text structure
oriented? I explained that the latter is the case. Some clarification
in the draft might be helpful (but is not mandatory).]]
See also Jerry Carter at http://lists.w3.org/Archives/Public/public-i18n-its/2006AprJun/0183.html .
Comment 1 Sebastian Rahtz 2006-06-28 13:04:41 UTC
Please note that my examples in the last comment
were not using the current naming :-{

However, that didnt affect the point, I hope.
Comment 2 Yves Savourel 2006-07-08 13:15:08 UTC
The "Elements within text" data category is text structure-oriented.
We need to clarify the definition:

Current text (http://www.w3.org/TR/its/#within-text-definition):

"The data category elements within text expresses information about how elements should affect the flow of the content. In this context the flow of the content represents how the nodes of the elements should be treated as a single unit for linguistic purposes. Sometimes, a flow can be nested within another one. The values associated with this data category are:"

Proposed text:

"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, in 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:"



Comment 3 Felix Sasaki 2006-07-08 23:19:52 UTC
(In reply to comment #2)
Would be fine with me. See minor editorial change proposal below.

> The "Elements within text" data category is text structure-oriented.
> We need to clarify the definition:
> 
> Current text (http://www.w3.org/TR/its/#within-text-definition):
> 
> "The data category elements within text expresses information about how
> elements should affect the flow of the content. In this context the flow of the
> content represents how the nodes of the elements should be treated as a single
> unit for linguistic purposes. Sometimes, a flow can be nested within another
> one. The values associated with this data category are:"
> 
> Proposed text:
> 
> "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,
> in 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:"
> 
"of its parent element, in the other hand" -> "of its parent element. On the other hand"

Comment 4 Felix Sasaki 2006-07-24 12:35:36 UTC
Action: working group to discuss and reply.
Comment 5 Yves Savourel 2006-08-17 13:59:08 UTC

*** This bug has been marked as a duplicate of bug 3495 ***
Comment 6 Felix Sasaki 2006-09-27 04:46:25 UTC
Closed.
Comment 7 Felix Sasaki 2006-09-28 06:04:00 UTC
Summary: This bug has been marked as a duplicate of bug 3495.