Re: [docbook-apps] section in sidebar?

[Scott Hudson <scott.hudson@flatironssolutions.com>]

I'm trying to hold true to the semantics of sidebar, in that this 
content is outside the narrative flow. It is indeed a side-feature, and 
should not be assumed to be a sibling-level section.

We could certainly use the section approach, but it felt more like a 
workaround, rather than being semantically accurate.

The problem isn't the sidebar, but the fact that this sidebar content 
has sub sections with titles, and the current model doesn't support that.

Best regards,

--Scott



Colin Shapiro wrote:
> Perhaps I am not fully understanding this problem, but I fail to see why 
> this kind of content would *need* to be in a sidebar.
> 
> Would something like <section role="side-feature"> really be 
> inappropriate?  Take a look at the sidebar example from the Guide:
> 
> <sect1>
>   <para>Some narrative text.</para>
>   <sidebar>
>     <title>A Sidebar</title>
>     <para>Sidebar content.</para>
>   </sidebar>
>   <para>The continuing flow of the narrative text, as if the sidebar was 
> not present.</para>
> </sect1>
> 
> Here, the sidebar content is understood to be outside of the narrative 
> flow.  Why would this be conceptually different on a larger scale...
> 
> <section>
>   <para>Some narrative text.</para>
>   <para> Some more narrative text.</para>
> </section>
> 
> <section role="side-feature">
>   <para>Text outside of narrative flow.</para>
>   <para>More text outside of narrative flow.</para>
> </section>
> 
> <section>
>   <para>The continuing flow of the narrative text, as if the sidebar was 
> not present.</para>
> </section>
> 
> ...?
> 
> Then, put section[@role='side-feature'] in a block-container or 
> something and position it as you please.
> 
> Maybe I'm still misunderstanding, though.
> 
> Colin
> 
> On 4/12/07, *Keith Fahlgren* <abdelazer@gmail.com 
> <mailto:abdelazer@gmail.com>> wrote:
> 
>     On 4/11/07, Scott Hudson < scott.hudson@flatironssolutions.com
>     <mailto:scott.hudson@flatironssolutions.com>> wrote:
>      > Unfortunately, this is content that is outside the narrative flow
>     of the
>      > main text, and is about a page or two long. It's more like a
>     "feature"
>      > that you might see in many Trade publications...
> 
>     Yeah, I immediately thought of the comparable material in some of our
>     more layout-intensive titles. Perhaps this sort of content would be a
>     good thing to discuss at the DocBook SubCommittee for Publishers....
> 
> 
>     Keith
> 
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail:
>     docbook-apps-unsubscribe@lists.oasis-open.org
>     <mailto:docbook-apps-unsubscribe@lists.oasis-open.org>
>     For additional commands, e-mail:
>     docbook-apps-help@lists.oasis-open.org
>     <mailto:docbook-apps-help@lists.oasis-open.org>
> 
> 


-- 
*  Scott Hudson*
  / XML Business Architect/

   scott.hudson@FlatironsSolutions.com
<mailto:scott.hudson@FlatironsSolutions.com>



   O:  303.542.2146

   C:  303.332.1883

   F:  303.544.0522



   www.FlatironsSolutions.com <http://www.flatironssolutions.com/>

/  An Inc. 500 Company/

/ /