Omni Systems, Inc. |  | Mif2Go User's Guide, Version 55 |  |  |  |  |

> 13 Converting to HTML/XHTML > 13.16 Passing W3C validation tests > 13.16.5 Avoiding redundant attribute assignments in tables

### 13.16.5 Avoiding redundant attribute assignments in tables

If you use more than one method to add the same attribute to a table, you might end up with duplicate attribute assignments, which are not allowed for W3C validation. For example, suppose you specify access method scope for all tables (see §26.1.3.2 Applying the scope method to all tables):

[Tables]

AccessMethod=Scope

Then if you happen to include a CellScope marker in some table (see §26.2.4 Assigning table-cell attribute values with custom markers 0, the scope attribute assignment appears twice in the output for that table cell.

> 13 Converting to HTML/XHTML > 13.16 Passing W3C validation tests > 13.16.5 Avoiding redundant attribute assignments in tables

| Mif2Go User's Guide: 13.16.4 Removing full-row straddles from tables |  | Mif2Go User's Guide: 13.16.6 Eliminating duplicate ObjectIDs |