RE: [xliff] RE: [xliff-comment] Section 2.5.4 Validating Documentswith Extensions - needs revision

Having said all that, I just realized a serious drawback to using "strict".
Because XLIFF is used as an interchange format (the 'I' in XLIFF), the file
is processed multiple times by various applications and vendors. Using
"strict" would require ALL the vendors to HAVE ALL the proprietary schemas
used within the XLIFF document. Obviously, this is not practical. So I guess
"strict" is not an option.