OASIS XML Localisation Interchange File Format (XLIFF) TC

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. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs=" http://www.w3.org/2001/XMLSchema" ; elementFormDefault="qualified" xmlns:ctr="urn:oasis:names:tc:xliff:changetracking:2.0" xmlns:xlf="urn:oasis:names:tc:xliff:document:2.0" targetNamespace="urn:oasis:names:tc:xliff:changetracking:2.0"> <!-- Import --> <xs:import namespace="urn:oasis:names:tc:xliff:document:2.0" schemaLocation="../xliff_core_2.0.xsd"/> <!-- Elements for change tracking --> <xs:element name="changeTrack"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="ctr:revisions"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="revisions"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="ctr:revision"/> </xs:sequence> <xs:attribute name="appliesTo" use="required" type="xs:NMTOKEN"/> <xs:attribute name="ref" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="currentVersion" use="optional" type="xs:NMTOKEN"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> </xs:element> <xs:element name="revision"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="ctr:item"/> </xs:sequence> <xs:attribute name="author" use="optional"/> <xs:attribute name="datetime" use="optional"/> <xs:attribute name="version" use="optional" type="xs:NMTOKEN"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> </xs:element> <xs:element name="item"> <xs:complexType mixed="true"> <!-- Added the following line for allowing inline annotations in item element --> <xs:group ref="xlf:inline" minOccurs="0" maxOccurs="unbounded"/> <xs:attribute name="property" use="required"/> <xs:anyAttribute namespace="##other" processContents="lax"/> </xs:complexType> </xs:element> </xs:schema> item Container for a specific revision associated with a sibling element, or a child of a sibling element, to the change track module within the scope of the enclosing element. Contains: - Text - Zero, one or more <cp> elements - Zero, one or more <ph> elements - Zero, one or more <pc> elements - Zero, one or more <sc> elements - Zero, one or more <ec> elements - Zero, one or more <mrk> elements - Zero, one or more <sm> elements - Zero, one or more <em> elements Constraints: - It can contain any of <cp>, <ph>, <pc>, <sc>, <ec>, <mrk, <sm>, <em> elements if and only if the following are true: - The value of the attribute "appliesTo" of the parent <revisions> element is either "source" or "target". - The "property" attribute of the <item> element is set to "content" If the above conditions are not met, then only plain text is allowed. Attributes: - property, REQUIRED - attributes from other namespaces, OPTIONAL Attachment: ctrsample.xlf Description: ctrsample.xlf

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.

Hi Phil, Yves,
 
I agree with Yves on the namespace value needing to change.
 
I have one more observation regarding what is allowed in <item>. I think as was discussed in the TC call that it would be better to allow any element as a child of <item> and not just the Inline elements. This
allows change tracking to work on any XLIFF element that can have children. And have some language changes in the spec, especially to mention that “appliesTo” must be used to interpret the contents of the tracked contents inside <item>.
 
Regards,
Fredrik Estreen
 


From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org]
On Behalf Of Yves Savourel
Sent: den 29 november 2015 02:34
To: 'Phil Ritchie' <Phil.Ritchie@vistatec.com>; xliff@lists.oasis-open.org
Cc: 'Marta Borriello' <Marta.Borriello@vistatec.com>; 'Chase Tingley' <chase@spartansoftwareinc.com>
Subject: RE: [xliff] Proposal For Change Tracking in XLIFF 2.1


 
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.