I went back and checked the Arbortext 5.4 release (our current release)
which uses the preliminary DITA 1.2 DTDs and XSDs and adding a domains
attribute construction such as w(...) to allow the declaration of weak
constraints won't cause any problems. Of course we just ignore the new
construct at this point, but since we haven't implemented DITA 1.2
constraint checking on conrefs, all constraints are "weak".
As I said in a previous note, if our Specialization Validation function
encounters the new w(...) construct, it will flag it as an error with
the message:
Domain attribute value at "xxxx" is improperly formatted
But this validation is only done upon request, the error can be safely
ignored, and in some future release we can update things so w(...) isn't
flagged as an error.
-Jeff
>