Re: [dita] scope attribute on <entry> from proposal 62

Hi Robert,

The inclusion of the scope attribute implies that the entry is a header for the given scope. So, an entry with scope=“row” would be considered the header for the row it is contained within. An entry with scope=“col” would be considered the header for the column that contains that header entry. 

The rowgroup and colgroup would apply for a span of rows or columns as appropriate.

The scope attribute will likely not be used by itself in a complex table (it would be fine for a simple table), but would also anticipate that the headers attribute be applied to clearly indicate the header id that covers individual entries.

Hope this helps.

Thanks and best regards,

--Scott
Scott Hudson   |   PELCO  by Schneider Electric   |   United States  |   Standards Lead 
Phone: +1 970 282 1952  |  Mobile: +1 720 369 2433  | Email: 

Sites: pdn.pelco.com , partnerfirst.pelco.com 

On Dec 17, 2013, at 1:03 PM, Robert D Anderson <> wrote:

I'm working on fixing attribute tables and encountered this new definition for @scope on <entry>:

The scope attribute can contain one of "row" or "col" or "rowgroup" or "colgroup".

scope="row"Applies to the row.

scope="col"Applies to the column.

scope="rowgroup"Applies to the row group.

scope="colgroup"Applies to the column group.

Scott (or somebody else) - can you clarify what this means? From this I really only know what values are legal, but I don't know what it means. 

Does the use of this attribute imply that the entry is a header, or is this attribute only valid when the entry is already identifiable as a header?

Also, can you clarify what a "row group" or "column group" are? My best guess is that a row group would be all rows covered by the current entry, if the entry spans rows - but I need to confirm that before it goes into the specification.

Thanks,

Robert D Anderson

IBM Authoring Tools Development

Chief Architect, DITA Open Toolkit (http://dita-ot.sourceforge.net/)
______________________________________________________________________

This email has been scanned by the Symantec Email Security.cloud service.

______________________________________________________________________