Re: [docbook-tc] Re: RFE 3107140

["Bob Stayton" <bobs@sagehill.net>]

Hi Dave,
I get what you want to do, and support it for accessibility reasons.  I'm not sure 
about how to represent it in a content model, though. The current content model of 
acronym is mixed content of text and inlines.  If <expansion> were added as a child 
element, it would fall into that bag of inlines in the mixed content, but it isn't 
necessarily meant to be part of that displayed content. I don't think the schema 
syntax allows specifying a content model that consists of an optional expansion 
element followed by mixed content, does it?  And I don't think using an attribute on 
acronym is appropriate either, since it is displayable text that might need its own 
child elements (trademark, etc.).  So it seems just adding <expansion> to the existing 
mix would have to be done, with the explanation that its location in the content is 
arbitrary and it may or may not be output, which seems a bit awkward.  What do you 
think?

Bob Stayton
Sagehill Enterprises
bobs@sagehill.net


----- Original Message ----- 
From: "Dave Pawson" <dave.pawson@gmail.com>
To: "DocBook Technical Committee" <docbook-tc@lists.oasis-open.org>
Sent: Wednesday, June 15, 2011 11:36 PM
Subject: [docbook-tc] Re: RFE 3107140


> On 15 June 2011 18:56, Norman Walsh <ndw@nwalsh.com> wrote:
>> Hi Dave,
>>
>> You never responded to our question. Are you still interested?
>>
>> https://sourceforge.net/tracker/?func=detail&aid=3107140&group_id=21935&atid=384107
>
>
> I thought I had Norm?
> Without looking up syntax, I'm looking for two things.
> 1. Expansion of an acronym on first use, which IMHO is simply good English.
> Hence DTC (docbook tech committee)
> 2. If the expansion is marked up, whether shown or not, accessibility software
> can access it and read out the expansion rather than the acronym?
> <acronym>DTC<expansion>Docbook Technical Committee</ </
>
> regards
>
>
>
>
> -- 
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
> http://www.dpawson.co.uk
>
> ---------------------------------------------------------------------
> 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
>
>
>