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

Re: Elements within text

From: Andrzej Zydron <azydron@xml-intl.com>
Date: Fri, 28 Apr 2006 08:03:36 +0100
Message-ID: <4451BE48.7000408@xml-intl.com>
To: Yves Savourel <yves@opentag.com>
CC: public-i18n-its@w3.org

Hi Yves,

Makes sense to me!

Well done,


Yves Savourel wrote:
> 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: <b>)
> "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 "yes+subflow"]
> "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:
> --------------------
> Definition
> 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".
> Implementation
> 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>
>  <prolog>
>   <its:rules xmlns:its="http://www.w3.org/2005/11/its" its:version="1.0">
>    <its:withinTextRule withinText="yes" selector="//term"/>
>    <its:withinTextRule withinText="subflow" selector="//fn"/>
>   </its:rules>
>  </prolog>
>  <conbody>
>   <ol>
>    <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 horse.</p>
>    </li>
>   </ol>
>  </conbody>
> </concept>
> 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).
> Cheers,
> -yves
> ---------------------------------------------------------------------------------------------------
> Text inserted by Panda Platinum 2005 Internet Security:
>  This message has NOT been classified as spam. If it is unsolicited mail (spam), click on the following link to reclassify it:
> ---------------------------------------------------------------------------------------------------


email - azydron@xml-intl.com
smail - c/o Mr. A.Zydron
	PO Box 2167
         Gerrards Cross
         Bucks SL9 8XF
	United Kingdom
Mobile +(44) 7966 477 181
FAX    +(44) 1753 480 465
www - http://www.xml-intl.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
may not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version. Unless
explicitly stated otherwise this message is provided for informational
purposes only and should not be construed as a solicitation or offer.
Received on Friday, 28 April 2006 07:03:50 UTC

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