W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2006

Re: Elements within text

From: Lieske, Christian <christian.lieske@sap.com>
Date: Fri, 28 Apr 2006 15:43:19 +0200
Message-ID: <0F568FE519230641B5F84502E0979DD104F85381@dewdfe12.wdf.sap.corp>
To: <public-i18n-its@w3.org>

Hi there,

This looks powerful and sensible to me. However, I am worried about the
wording ...

1. What is a flow? What is a sub-flow?

2. What does "element is part of its parent content" mean? I
guess this is not a statement related to the Infoset ... Rather, I
guess its a linguistic notion.

I am not sure if we could borrow from typography some terminology
related to widows and orphans.

<its:orphanRule orphan="yes" selector="//term"/>

Best regards,
Hi Andrzej, Felix, and all,

Here is a proposal for handling subflow for withinText: Instead of
having a additional subflow attribute I propose to have three
values for withinText: "yes", "subflow", "no". That will avoid to have
cases which makes no sense: withinText="no" with
subflow="no|yes". Elements not listed in withinText will be assumed to
have the value "no".

For the behavior:

"yes": Content of the element is part of the parent content (example:

"subflow": Content of the element is an independent flow, but the
content of the parent element around the subflow element stays
together (example: <fn> in DITA) [So basically "subflow" would be like a

"no": Parent content is split into two flows and element content is an
independent flow (example: <p> inside <li>)

The new text for the data category would be:


The data category elements within text expresses information about
whether an element is part of its parent content. The values
associated with this data category are:
- "yes" (the element and its content are part of the text flow of its
parent element),
- "subflow" (the element is part of the text flow of its parent element,
its content is an independent text flow),
- and "no" (the element splits the text flow of its parent element and
its content is an independent text flow).
Elements not listed are considered to have the value "no".


This data category can be expressed only in a set of rules. It cannot be
expressed as local markup on an individual element.

Element within text is expressed with a withinTextRule element with a
attribute. The attribute has the values "yes", "subflow",
or"no". In addition, a selector attribute is required.

Example 30:

<concept id="myConcept" xml:lang="en-us">
 <title>Types of horses</title>
  <its:rules xmlns:its="http://www.w3.org/2005/11/its"
   <its:withinTextRule withinText="yes" selector="//term"/>
   <its:withinTextRule withinText="subflow" selector="//fn"/>
   <li>Palouse horse:
    <p><term>Palouse horses</term><fn>A palouse horse is the same as an
Appaloosa.</fn> have spotted coats.</p>
    <p>Nez Perce Indians have been key in breeding this type of

The flows for this documents are:

- "Palouse horse:"
- "<term>Palouse horses</term><fn></fn> have spotted coats."
- "A palouse horse is the same as an Appaloosa."

This should address your need for having a way to set 'subflow" and in
addition allow us to have provision to allow some elements to
"break" the flow 9rather than have a subflow).

Received on Friday, 28 April 2006 13:43:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:07 UTC