OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [dita] Allowing metadata to precede title in 13097 troubleshooting section specializations

That makes sense. I can see now that I was trying to make a distinction that's not particularly useful and it introduces noise into the content model. Given that, the model still needs to change. Now it would become:

<!ENTITY % section.blocks.only.cnt
    (%basic.block; |
    %data.elements.incl; |
    %foreign.unknown.incl; |
    %sectiondiv; |

with an analogous change to the content model for remedy.

Best Regards,
Bob Thomas

On Sat, Dec 21, 2013 at 10:36 AM, Eliot Kimber <ekimber@rsicms.com> wrote:
I disagree: I think that if title is used, it should always be the first
child. index terms can either go in the title (if appropriate), or
immediately follow it. That makes the title pattern consistent for all
titled elements: topics, sections, figures, maps, and topicrefs. It avoids
the need for more-complicated processing in element handling (for example,
to explicitly process any elements that come before the title after
processing the title so that things are in the correct order in the

I can’t think of any reason to need to allow index terms or data before a
title rather than immediately following it—the association with the parent
container is the same and the effective position within the flow of a
rendered document will be essentially the same (since you would normally
anchor to the title of the container when it has one anyway).


Eliot Kimber
Senior Solutions Architect
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368

On 12/21/13, 10:48 AM, "Bob Thomas" <bob.thomas@tagsmiths.com> wrote:

>In a thread about example and section
> on the Yahoo DITA group, I offered the opinion that when mixed content
>is removed from the section model, title ought to be only available at
>the beginning of section preceded only by an optional indexterm. Jeremy
>Griffith pointed out that the data element ought to be allowed there as
>well for the same reasons as indexterm. In general, an optional mix of
>metadata markup needs to be allowed before title.
>The timing for this realization is regrettable. My hope is that it is not
>too late to tweak the content models.
>Here is a tentative list of elements that we should consider allowing to
>precede title:
>* data
>* data-about
>* foreign
>* indexterm
>* indextermref
>* unknown
>I would be happy to have the TC argue away any of these elements. Failing
>that, I am advocating the following change to the DTD:
><!-- used in cause and condition -->
><!ENTITY % section.blocks.only.cnt
>  "(((%indexterm;)*, (%title;))?,
>   (%basic.block; |
>   %data.elements.incl; |
>   %foreign.unknown.incl; |
>   %sectiondiv; |
>   %txt.incl;)*)
>  "
><!ENTITY % section.blocks.only.cnt
>  "(((%data.elements.incl; | %foreign.unknown.incl; |
>      %indexterm; | %indextermref;)*, (%title;))?,
>    (%basic.block; |
>    %data.elements.incl; |
>    %foreign.unknown.incl; |
>    %sectiondiv; |
>    %txt.incl;)*)
>  "
>I also propose allowing the same mix to precede title in remedy.
>Best Regards,
>Bob Thomas+1 720 201 8260 <tel:%2B1%20720%20201%208260>
>Skype: bob.thomas.colorado
>Instant messaging: Gmail chat (bob.thomas@tagsmiths.com) or Skype
>Time zone: Mountain (GMT-7)

Bob Thomas
+1 720 201 8260
Skype: bob.thomas.colorado
Instant messaging: Gmail chat (bob.thomas@tagsmiths.com) or Skype
Time zone: Mountain (GMT-7)

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]