Implemented your suggestion for csprd01 32 Metadata Module (thanks for the good suggestion)

["Schnabel, Bryan S" <bryan.s.schnabel@tektronix.com>]

Chase,

 

With regard to your comment on the Metadata module (which we are tracking as "csprd01 32 Metadata Module" on our wiki, https://wiki.oasis-open.org/xliff/XLIFF%202.0%20Public%20Review%20submitted%20comments%20tracker ), once again thank you very much for your valuable feedback.

 

I implemented your suggestion.

 

I added a use case on how to use the Metadata module to preserve source XML attribute values and names in an XLIFF file, to facilitate a roundtrip in cases where a skeleton is not used.

 

Your point that there are no processing requirements is a good one. However the Metadata module's general processing requirements are defined in the "Extension Mechanisms" section and the "Conformance" section.

 

The processing requirements are that Extension Mechanisms (be they custom namespaces, or the Metadata module) MUST NOT be used to implement existing core features or existing modules - and applications SHOULD preserve them.

 

The consensus of the TC is that there are no further processing requirements needed for Metadata beyond that.

 

I hope you find this to be a good implementation of your suggestion.

 

Please let me know if you have further questions or comments on this.

 

Thanks,

 

Bryan