Hi Rodolfo, all,
A very good list!
I agree with all, with some reservations for #6 and #7.
For #6: I just wonder if it shouldn’t be “extensions SHOULD be public and documented” (more explanations on that on the two other emails I just posted)
For #7: I have no idea if anything IPR-related rules need to be specified. It’s good to bring up that topic though.
Cheers,
-ys
From: Rodolfo M. Raya [mailto:]
Sent: Wednesday, March 21, 2012 11:12 AM
To: Yves Savourel;
Subject: RE: [xliff] Implementing extensions
Hi,
Some points to keep in mind regarding extensibility:
It must be safe to ignore custom extensions while processing an XLIFF file;
Extension points should not be allowed in critical elements, like <source> or <target>;
Extensions must not be used instead of XLIFF standard features;
A tool that generates XLIFF files with custom extensions must be able to accept an XLIFF file processed with other tool as long as the received file is valid XLIFF;
A tool that uses custom extensions should not expect that other tools update custom data while processing an XLIFF file;
XML schemes that define custom extensions must be public and documented;
Any custom extension used in an XLIFF file must be published under the same IP terms the XLIFF standard is published and be freely redistributable;
Custom extensions are subject to standard rules for XML handling and the recommendations regarding XML usage included in the XLIFF specification.
Best regards,
Rodolfo
--
Rodolfo M. Raya
Maxprograms http://www.maxprograms.com
-------- Original Message --------
Subject: [xliff] Implementing extensions
From: Yves Savourel <>
Date: Wed, March 21, 2012 8:52 am
To:
