dita — archive

[Eliot Kimber]

There is certainly a requirement to have controlled values for outputclass within the Publishing business domain, where arbitrary formatting control is a reality. I've approached in several ways to date: - Used CSS values where appropriate, so that a processor can either just use the outputclass value in generated HTML or can key on the value for generating other types of output. Because the values are CSS-defined, there's no need to have a separate definition of them. - Treat outputclass values as the names of named styles. When the primary rendition target is InDesign or similar system, this works well. In this case, the DTP system maintains the master list of style names (e.g., in template documents). - Simply document the expected values. I think it would be useful and appropriate to use the DITA 1.2 controlled values facility (map specialization) to define some useful base sets of values, as might be usefully implemented in the DITA Open Toolkit. Cheers, E. On 9/21/09 3:59 PM, "Park Seth-R01164"