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

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-tc message

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


Subject: Re: [docbook-tc] Implementing DocBook assemblies with XProc


Hi Norm,

I was reading through your analysis/documentation last week. I think it 
was very helpful. I don't really have any additional comments from what 
you've added.

Did you get my feedback/example for relationships?

Thanks!

--Scott

Scott Hudson
Senior XML Architect
+1 (303) 542-2146  |  Office
+1 (720) 663-SCOT [7268]  |  Gvoice
Scott.Hudson@flatironssolutions.com
http://www.flatironssolutions.com






Norman Walsh wrote:
> Folks,
>
> I continued to tinker with assemblies while I was offline the last
> couple of weeks. I now have a fairly complete solution based on an
> XSLT stylesheet that generates an XProc pipeline.
>
> I've moved a few things around for convenience. I added a <transform>
> element to modules so that more than one transform can easily be
> specified.
>
> I've also decided that inheriting the preceding-sibling's "renderas"
> is more confusing than not. Consider this example:
>
> <structure xml:id="user-guide">
>   <output renderas="book"/>
>   <info>
>     <title>Widget User Guide</title>
>   </info>
>   <module resourceref="full-toc"/>
>   <module resourceref="tut1">
>     <output renderas="chapter"/>
>   </module>
>   <module resourceref="tut2">
>     <output renderas="chapter"/>
>   </module>
>   <module resourceref="task1">
>     <output renderas="chapter"/>
>   </module>
>   <module>
>     <output renderas="appendix"/>
>     <info>
>       <title>Troubleshooting</title>
>     </info>
>     <module resourceref="tut3">
>       <output renderas="section"/>
>       <info>
>         <title>Troubleshooting spindle and bearing problems</title>
>       </info>
>       <module resourceref="tut5" contentonly="true"/>
>       <module resourceref="task4">
>         <output renderas="section"/>
>       </module>
>       <module resourceref="task3"/>
>     </module>
>   </module>
>   <module resourceref="index"/>
> </structure>
>
> Having my index turned automatically into an appendix was quite
> puzzling at first.
>
> I'm still wondering if anyone sees any major functionality holes in my
> earlier documentation of assembly.
>
>                                         Be seeing you,
>                                           norm
>
> P.S. I also submitted a paper proposal on this topic to the XML Prague
> 2010 conference.
>
>   


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