Re: DocBook TC action item reminders

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

Folks,
here is what I found regarding my AI to research the CALS table standard:

DocBook is using a modified OASIS Exchange Table model.

The requirements for the accessibility enhancement request is:
1. Column headers  - marked via thead/row/entry, if scope is needed, XSL
customization necessary?
2. Row headers - marked via attribute rowheader, if scope is needed, XSL
customization necessary?
3. multiple header attributions - perhaps by customization???
* possibly: mark up entrys containing header information with xml:id
* but: there is no entry attribute that can be used to reference applicable
headers?

According to the OASIS Exchange DTD specs (
https://www.oasis-open.org/specs/tr9503.html), specific changes of substance
between this Exchange Model and the CALS table model contained in the
Example DTD published in MIL-HDBK-28001 (30 June 95) include:

1. allow content model for table to include title on the graphic+ form of
table content when there are no tgroups;
2. change most explicit attribute defaults from value to #IMPLIED to allow
value inheritance, possibly from a style sheet;
3. eliminate <entrytbl>;
4. eliminate <tfoot>;
5. eliminate <spanspec>;
6. eliminate the char and charoff attributes from <tgroup>;
7. eliminate the rotate attribute from <entry>;
8. eliminate references to security attributes.

However, it must be realized that overriding declarations of these parameter
entities that enlarge the model (i.e., that define a superset of the model
or a different model) may reduce practical interoperability. It is therefore
recommended that the parameter entities be used primarily to define a subset
of the default model. Any parameter entity redefinition other than to define
a more constrained model than the default model must be done carefully with
the knowledge of ones target toolset's capabilities and with the realization
that interoperability may be reduced. The portion of the model where
constraining changes only are reasonable is its geometric aspects, including
some table attributes, and the elements and attributes of the table
structure: tgroup through row and some entry attributes. The table content
model and its exceptions other than table self-exclusion and the entry
content model and its exceptions are candidates for change.

I believe we have already modified the Exchange model for <entry> to allow
DocBook markup. With the above paragraph, I believe this gives us enough
room to add the necessary attributes to improve accessibility.

Here is what I'd propose:
<! ENTITY % tbl.entry.scope "scope (row|col)  #IMPLIED">
<! ENTITY % tbl.entry.headers "headers (#PCDATA)  #IMPLIED">
<! ENTITY % tbl.entry.att      "(%tbl.entry.scope; %tbl.entry.headers;)">
<!ENTITY % tbl.table.att        "
    pgwide      %yesorno;       #IMPLIED "
    rowheader   NMTOKEN         #IMPLIED ">

I think xml:id is allowed on every element, so not sure anything needs to be
changed to allow it explicitly?


Thanks and best regards,

--Scott

Scott Hudson |  Pelco by Schneider Electric | United States | Standards Lead
Site: pdn.pelco.com | scott.hudson@schneider-electric.com





On 6/14/12 11:23 AM, "Bob Stayton" <bobs@sagehill.net> wrote:

> If you are getting this mail, then you have an
> action item in the list below, and this is your friendly
> reminder service before the next meeting.
> If you have already completed your action items, then
> good for you!
> 
> Next meeting is Wednesday 20 June 2012.
> 
> 
> Actions:
> 
>   a.  Norm to publish an XSD for 5.1 when it is finished.
> 
>   b.  Norm to document XLink support in The Definitive
>       Guide for 5.1, including the concern about
>       translatable text in the title attribute.
> 
>   c.  Scott to research the degree of flexibility in the
>       CALS table standard.
> 
> Bob Stayton
> Sagehill Enterprises
> bobs@sagehill.net
> 
> 
> 
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> ______________________________________________________________________