Re: [docbook-publishers] Poetry Markup

[Scott Hudson <scott.hudson@schneider-electric.com>]

Hi Nic,

We only had a few samples that people submitted for consideration when we
were developing the model for poetry. Here is a thread that might be useful:
http://lists.oasis-open.org/archives/docbook-publishers/200905/msg00011.html
also
http://markmail.org/search/?q=linegroup&q=list%3Aorg.oasis-open.lists.docboo
k-publishers#query:linegroup%20list%3Aorg.oasis-open.lists.docbook-publisher
s%20order%3Adate-forward+page:1+mid:dp66s6kpprwwqziu+state:results

All of our samples are located here:
https://docbook.svn.sourceforge.net/svnroot/docbook/trunk/docbook/relaxng/pu
blishers/samples/

The reason we opted for a more open model, was to accommodate the various
needs of publishers. We did not want to be too strict and then find out that
some particular set of content could not be marked up using our schema. It
seemed better to be more open and flexible.

You could still assign canto, verse, couplet, etc. as a role attribute on a
line, linegroup, or phrase as appropriate.

As for nesting of linegroup, I think you have a valid point. This should be
filed as an RFE here:
http://sourceforge.net/tracker/?atid=1037852&group_id=21935&func=browse

As there are 4 open RFEs to consider regarding the Publishers schema, it is
perhaps time to re-convene the Publishers SC. I'll send a separate note to
the list.

Thanks and best regards,

--Scott

Scott Hudson |  Pelco by Schneider Electric | United States | Publication
Standards and Technology Lead
Ph: +1-970-282-1952  | M: +1-720-663-7268 |
scott.hudson@schneider-electric.com





On 7/27/11 3:33 AM, "Nic Gibson" <nicg@corbas.net> wrote:

> Hi folks
> 
> Has anyone actually used the poetry model in anger as it were? I've been doing
> some working mapping the Penguin model (I understand that the Penguin model
> was one of the inputs to DocBook Publishers' poetry model) to DocBook
> Publishers so I can render content. I've come across some things I don't quite
> understand.
> 
> I was wondering why the model is *quite* so open. I wrote the Penguin model
> based on the experience of marking up several hundred poems. Not once did I
> need to intersperse every line with arbitrary blocks or mediaobjects! Now, I
> don't really have a problem with the openness of the model per se. However, I
> don't see why the model needs to be so complex - poetry has a fairly
> restrictive content model in general.
> 
> There doesn't appear to be any way of representing any structure more complex
> than a simple verse structure either. For example, if I were marking up Dante
> I would want to be able to represent cantos and verses. I might also want a
> way to mark up couplets. All of these can be done with linegroups but they
> would need to be able to nest. I don't appear to be able to nest them with the
> current model (although I could nest poems).
> 
> I was wondering if there was any discussion I could refer to so that I can
> understand the model. I don't see anything in the list archives but I may have
> missed something.
> 
> The main reason I'm looking at this is that I'm migrating my XSLT for the
> Penguin model to handle DocBook Publishers properly. At the moment, I don't
> see any sane way of rendering poetry without ignoring the majority of the
> content model.
> 
> 
> nic
> --
> Nic Gibson
> Corbas Consulting
> Digital Publishing Consultancy and Training
> http://www.corbas.co.uk, +44 (0)7718 906817 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> ______________________________________________________________________


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________