From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Schnabel, Bryan S
Sent: Tuesday, March 13, 2012 7:41 PM
Subject: [xliff] [reintroducing proposal] Propose promoting "(B25) Preserve metadata without using extensibility" to section 1 (approved)
Sorry for the extra emails.
I propose we promote "(B25) Preserve metadata without using extensibility" (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#XLIFF2.0.2BAC8-Feature.2BAC8-PreserveXMLattributeormetadatawithoutextensibility.A.28B25.29Preservemetadatawithoutusingextensibility ) to section 1 (approved).
If any TC voting member agrees, please second.
In XLIFF 1.2 we sometimes need to use extensibility to preserve source metadata when converting an source files to XLIFF. For XLIFF 2.0, there is a need for preserving metadata; the solution should be generic and contemplate formats like HTML5, PO, or XML attributes in general - removing the need to extend.
Consider this source:
<para id="g_3423_spectrum" alt="It's orders of magnitude faster" rev="c">This is orders of magnitude faster than swept analysis techniques.</para>
We could introduce a module that could store the metadata, with hints that an application could optionally use, for purposes of roundtripping, applying/reporting metrics, etc.
<source> This is orders of magnitude faster than swept analysis techniques.</source>
<meta key=”alt” id="a1.a">It's orders of magnitude faster</meta>
<unit id=”a2” idref="a1.a">
<source>It's orders of magnitude faster</source>
One attribute in the main holder element would indicate the type of metadata and another attribute would define the key of a key-value pair.
In the module specification we could define a set of standard information types that covers what we have in XLIFF 1.2 and add new ones as needed to cover things that are currently handled by custom extensions in XLIFF 1.2.
This schema used in <match > or <matches> would be quite useful for storing metadata that today we can’t store in <alt-trans>.
Applications that don’t understand certain type of metadata would be able to safely ignore the proposed elements, as with any element coming from an optional module.
Content Management Architect