dita — archive

[Jeff Ogden]

Eliot wrote: > If there are existing implementations of constraint checking (I'm thinking specifically of > Arbortext Editor here), then I would think we are obligated to wait > until 1.3. Arbortext Editor doesn't implement constraint checking for conrefs. Adding a new construct for weak constraints, w(...), will produce an error message from our Specialization Validation function about an invalid value in a domains attribute, but that validation is only done on request and the error can be ignored without any harm other than possibly some confusion or worry on the part of the person who asked for the validation. What I need to check is if adding the w(...) construct will be ignored by our conref code or if it might cause problems. I'm guessing that it will be ignored, but I've been wrong about such things before. I'll try to check this in more detail this afternoon. Are there implementations other than Arbortext Editor and the DITA Open Toolkit that implement conrefs? I assume there are and I assume it would be good to hear from everyone about what sorts or problems this late change to DITA 1.2 might or might not cause. -Jeff >