Re: [docbook-publishers] RFE 3602904: line group and block quote elements

[Richard Hamilton <hamilton@xmlpress.net>]

Hi Scott,

Interesting idea. Sounds like you're suggesting <linegroup> be allowed recursively. Is that the idea?

Dick
-------
XML Press
XML for Technical Communicators
http://xmlpress.net
hamilton@xmlpress.net



On Apr 4, 2013, at 3:08 PM, Scott Hudson wrote:

> The problem I see is with the blockquote model:
>    ## A quotation set off from the main text
>     element blockquote {
>       db.blockquote.attlist,
>       db.blockquote.info,
>       db.attribution?,
>       db.all.blocks+
>     }
> }
> 
> As you can see it's able to include db.all.blocks. Should we consider that line is a block-level element? If so:
> 
> db.all.blocks =
>   (db.nopara.blocks | db.para.blocks | db.extension.blocks)
> 
> db.publishers.blocks = db.dialogue | db.poetry | db.drama
> 
> db.extension.blocks = db.publishers.blocks
> 
> Do we modify db.publishers.blocks = db.dialogue | db.poetry | db.drama | db.linegroup | db.line
> 
> That might have more downstream consequences than we want.
> 
> We could just modify    
> db.blockquote =
> ## A quotation set off from the main text
>     element blockquote {
>       db.blockquote.attlist,
>       db.blockquote.info,
>       db.attribution?,
>       (db.all.blocks | db.linegroup | db.line)+
>     }
> }
> 
> at which point we might as well make blockquote the same model as linegroup?
> 
> db.linegroup =   
>     ## A grouping of lines in dialogue or other form of communication.
>     element linegroup {
>       db.linegroup.attlist, db.speaker*, (db.stagedir | db.line | db.all.blocks)+
>     }
> }
> 
> db.blockquote =
> ## A quotation set off from the main text
>     element blockquote {
>       db.blockquote.attlist,
>       db.blockquote.info,
>       db.attribution?,
>       (db.stagedir | db.line | db.all.blocks)+
>     }
> }
> 
> if this is the case, why wouldn't you just use linegroup and forget blockquote altogether?
> 
> Thanks and best regards,
> 
> --Scott
> Scott Hudson   |   PELCO  by Schneider Electric   |   United States  |   Standards Lead 
> Phone: +1 970 282 1952  |  Fax: +1 970 282 1950 | Email: scott.hudson@schneider-electric.com |   Site: pdn.pelco.com
> 
> 
> 
> 
> 
> 
> 
> On Apr 2, 2013, at 4:02 PM, Richard Hamilton <hamilton@xmlpress.net> wrote:
> 
>> I exchanged messages with pcthoms regarding this RFE:
>> https://sourceforge.net/tracker/?func=detail&aid=3602904&group_id=21935&atid=1037852)
>> 
>> He/she is asking that the following be legal:
>> 
>> <drama>
>>  <linegroup><speaker></speaker>
>>    <line>Text.</line>
>>    <blockquote>
>>      <line>Song.</line>
>>    </blockquote>
>>    <line>Text.</line>
>>  </linegroup>
>> </drama>
>> 
>> Right now, you cannot have <line> inside of a <blockquote> element. That's the addition the RFE is asking for.
>> 
>> At first, I thought he/she was just looking for a way to (ab)use the <blockquote> element to get an indent. But, while that is one result of doing this, the actual purpose is to markup a fragment of a song or a poem in the lines from a particular speaker, which sounds like a reasonable thing to do (though I don't know if <blockquote> is the best element to use for this purpose).
>> 
>> Does anyone have any thoughts on whether we should consider this change (allowing <line> inside <blockquote>, at least when <blockquote> is inside <linegroup>) or is there some other, hopefully better, way to achieve the same purpose?
>> 
>> Thanks,
>> Dick
>> -------
>> XML Press
>> XML for Technical Communicators
>> http://xmlpress.net
>> hamilton@xmlpress.net
>> 
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> 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 Symantec Email Security.cloud service.
>> ______________________________________________________________________
>