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

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook message

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


Subject: Assemblies, topics, sections and type


Hi,

currently, I'm playing around with DocBook assemblies. I've created an
assembly file, referenced some modules and a structure. The modules and
structure is not really important, but the module. The structure
declares to render the <topic> into a <section>.

The module contains a <topic> element, but I also used a type attribute.
As the TDG says, it "identifies the topic type" I use it to distinguish
between a concept, task, or any other types. IMHO, that's a good fit, right?

When I start the assembly process with the assembly.xsl stylesheet, the
realized document renders the <topic> element into a <section>. So far,
so good.

However, as the <topic> contained a type attribute, this attribute is
passed onto the <section> as well. Unfortunately, type is not allowed on
a <section>, so the validation fails.

I have some possible scenarios:

a) deal with the removal of type inside the assembly file?
   Would <transforms> be feasible for this task? Or should
   that be better done outside?

b) use a post-processing (XSLT) step and remove the annoying
   attribute manually?

c) allow type in <section>?
   would require to amend the DocBook schema.

d) customize assembly.xsl and remove type?

e) anything else?


What would you choose?

Would like to hear your opinion. Thank you!


--
GruÃ/Regards
  Thomas Schraitle


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