[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Feature Request: Make tgroup optional w/in table
The story seems related to the choice of the OASIS XML Exchange Table Model as the definitive version for DITA. http://www.oasis-open.org/specs/tm9901.html In that default DTD, the content model for table is effectively: <!ENTITY % tbl.table-titles.mdl "%titles;,"> <!ENTITY % tbl.table-main.mdl "tgroup+"> <!ENTITY % tbl.table.mdl "%tbl.table-titles.mdl; %tbl.table-main.mdl;"> ... <!ELEMENT %tbl.table.name; (%tbl.table.mdl;)> In the DITA adaptation, the equivalent specialization-enabled declaration is: <!ENTITY % tbl.table-titles.mdl "((%title;)?, (%desc;)?)?,"> <!ENTITY % tbl.table-main.mdl "(%tgroup;)+"> <!ENTITY % tbl.table.mdl "%tbl.table-titles.mdl; %tbl.table-main.mdl;"> ... <!ELEMENT %tbl.table.name; (%tbl.table.mdl;)> Thus, tgroup effectively remains one or more by inheritance from the Exchange Table Model. Due to the wide use of this model across most XML DTDs that use tables, we are sort of faced with either changing this design uniquely for DITA, or with pushing the Why question back to the framers of the 1999 document. With my DITA specialization hat on, I can see the rationale of your request. With my Chair hat on, I worry what impact such change might have on editor implementations that may have somehow built dependencies on the requiredness of tgroup (ensuring that new tables get a default setup when created, perhaps) in which the relaxation might affect how usability is perceived. Regards, -- Don Day Chair, OASIS DITA Technical Committee IBM Lead DITA Architect Email: dond@us.ibm.com 11501 Burnet Rd. MS9033E015, Austin TX 78758 Phone: +1 512-838-8550 T/L: 678-8550 "Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" --T.S. Eliot "W. Eliot Kimber" <ekimber@innodata -isogen.com> To <dita@lists.oasis-open.org> 03/02/2007 02:48 cc PM Subject [dita] Feature Request: Make tgroup optional w/in table I am creating documents from legacy where all the tables are being used by reference. Because tgroup is required w/in table, it means that all my conrefs look like this: <table conref="tables_205-15-60.xml#table-001"> <tgroup cols="1"> <tbody> <row> <entry></entry> </row> </tbody> </tgroup> </table> Which seems a little silly. Cheers, Eliot -- W. Eliot Kimber Professional Services Innodata Isogen 8500 N. Mopac, Suite 402 Austin, TX 78759 (214) 954-5198 ekimber@innodata-isogen.com www.innodata-isogen.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]