Hi Phil,
A few questions:
- Adding inline codes to <item> would be a 2.1 feature. So the namespace used in the example should be xmlns:ctr="urn:oasis:names:tc:xliff:changetracking:2.1".
- I’m not 100% sure: I don’t think we can we have a 2.1 CTR element in a 2.0 document. So it’s likely the document itself should be 2.1 as well.
-ys
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Phil Ritchie
Sent: Friday, November 20, 2015 11:36 AM
To: xliff@lists.oasis-open.org
Subject: [xliff] Proposal For Change Tracking in XLIFF 2.1
All
Please find our proposal for modifications to Change Tracking for XLIFF 2.1.
Attached are modified *.xsd, a sample *.xlf with serialzed changes and proposed changes to the specification text.
We forked the Okapi library and our Pull Request can be viewed here: https://bitbucket.org/okapiframework/xliff-toolkit/pull-requests/1/chane-trackin-module-implementation/diff
Phil
Phil Ritchie | Chief Technology Officer | VistaTEC
VistaTEC House, 700 South Circular Road, Kilmainham, Dublin 8, Ireland.
Tel: +353 1 416 8000 | Direct: +353 1 416 8024
Email: Phil.Ritchie@vistatec.com | www.vistatec.com | ISO 9001 | EN 15038
Expert Leadership in Global Content Solutions
VistaTEC Ltd. Registered in Ireland 268483.
Registered Office, VistaTEC House, 700, South Circular Road, Kilmainham. Dublin 8. Ireland.
The information contained in this message, including any accompanying documents, is confidential and is intended only for the addressee(s). The unauthorized use, disclosure, copying, or alteration of this message is strictly forbidden. If you have received this message in error please notify the sender immediately.