[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Addendum 2 (RE: Addendum to comment: RE: Metadata Module lacks processing requirements)
|
{Sorry to keep adding to this. I will consolidate in the tracking table} Need to change 2.7.2 to continue to support the maximalist method (no skeleton). Again, since we do not offer any way other than <metadata> to capture attributes when not using a skeleton, the following processing
requirement is problematic: “Tools must not rely on user extensions (either in the Metadata module or custim namespace based) other than the ones possibly defined in <skeleton> to create the translated version of the original document.”
(BTW, “custim” is a typo) Chang to “Tools should not rely on custom namespace based extensions other than the ones possibly defined in <skeleton> to create the translated version of the original document.” Thanks, Bryan From: Schnabel, Bryan S [mailto:bryan.s.schnabel@tektronix.com]
In order to fully enforce this we should also adjust the General Processing topic: 2.1 General Processing Requirements A tool processing a valid XLIFF document that contains XLIFF-defined elements that it cannot handle must preserve those elements. Change this (should): A tool processing a valid XLIFF document that contains custom elements that it cannot handle should preserve those elements. To this (MUST): A tool processing a valid XLIFF document that contains custom elements that it cannot handle
MUST preserve those elements. From: Schnabel, Bryan S [mailto:bryan.s.schnabel@tektronix.com]
Since the only way to enable the capture of attributes for and XML roundtrip, using the maximalist method (i.e., to not use a skeleton) would be to use the metadata module, I think the processing requirement should be that agents may ignore
the <metadata>, but the MUST NOT remove. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]