dita — archive

[Robert Anderson]

I don't know why it is FIXED either. Does anybody have a problem with making this attribute CDATA? Regarding class attributes -- Chris, can you give an example of a class attribute that has changed? Other than in bookmap (which was not part of the standard, and does have new OASIS public IDs), these values should not have changed. Some of the class attribute definitions have moved into different DTD modules, but the content should be the same. For the public IDs -- would it help if the catalog we provide declares both public IDs with version, and version-agnostic values that always point to the latest? We could have all three of these public IDs: -//OASIS//DTD DITA Concept//EN -//OASIS//DTD DITA 1.0 Concept//EN -//OASIS//DTD DITA 1.1 Concept//EN The first points to the latest, the second means 1.0, and the third is 1.1. I realize that this is not ideal, because already with the new release, the generic one will change to 1.1. However, other than the DITAArchVersion attribute that I think we should correct, I think that it should really be possible to swap in the new set of DTDs. Robert D Anderson IBM Authoring Tools Development Chief Architect, DITA Open Toolkit (507) 253-8787, T/L 553-8787 "Chris Wong"