[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] Prototype DITA 1.1 DTDs
I'm not against DITA 1.1 doctypes but I'd like to understand the real problem. If you replace your DITA 1.0 DTDs with DITA 1.1 DTDs, everything should continue to work. That's what backwards compatibility of the DITA 1.x series is about. The only problem would be if a 1.1 document ended up on a desktop with only 1.0 installed. But this would be a problem in any case.
Version-dependent doctypes can cause problems. The user will install a new version of their tools and DTDs and find that they have no access to DITA 1.1 elements until they update their DOCTYPE statements. If we presume a low-tech user, this could involve manually changing hundreds of documents to get access to those new elements. I don't really see such a user as "lazy". Lazy binding is a very common and valid technique. Programmer classes seldom have version numbers in their interfaces because of exactly this issue.
The obvious compromise is to create both version-dependent and version-independnt public identifiers, but I would like to understand precisely what problems were caused by the current scheme in case it is something that should be fixed in the DITA DTDs (in particular, if a backwards incompatibility introduced).
Rodolfo |
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]