XLIFF 2.1 open for second public review

Share with
Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+Buffer this pageEmail this to someone

XLIFF Version 2.1 has reached an important milestone in its development. On February 7, the OASIS XLIFF TC members approved the second Committee Specification Draft and sent it out for second public review. The OASIS Administration made the call for public comments on February 9, 2017. The second public review period will end on February 24, 2017.

The public review draft was presented at XML Prague last week. You can read on details of the ITS implementation in XML Prague Proceedings.

The first “dot” release after XLIFF 2.0 delivers on the modularity promise of the XLIFF 2 architecture. XLIFF 2.1 defines three new namespaces and brings a full native ITS 2.0 capability via its ITS Module without breaking the backwards compatibility with XLIFF 2.0.

OASIS logoXLIFF 2 Core and 7 out of 8 XLIFF 2.0 Modules are unaffected by the 2.1 release. Apart from a major bugfix for the Change Tracking Module and the brand new ITS module, XLIFF 2.1 brings Advanced Validation capability. XLIFF 2.1 (and XLIFF 2.0 also) can be now 100% validated with standardized validation artifacts without regressing to custom validation code. The expressivity of the validation framework was greatly enhanced by the usage of Schematron and NVDL schema languages on top of XML Schemas (xsd) that were available in XLIFF 2.0.

This second public review draft implemented all feedback received during the 1st public review we were informing on in November last year. You can view the resolutions for each of the 20 issues opened during the first review here.

All comments from the wider community (those who are not members of the XLIFF TC) are collected through the XLIFF TC’s publicly archived comment list.

When posting a comment, please include the string “XLIFF 2.1 csprd02” in the subject line. You may want to number your comments if you’re sending a few of them, and the subject line should give an idea on what your comment is about.

Collected comments and the progress of their disposition are public and can be followed on the XLIFF TC JIRA project.

The XLIFF TC plans to have satisfactory dispositions for all comments by March 7,  2017, and approve the Committee Specification by March 21, 2017, if this round of the public review does not necessitate material changes to the specification.

For the progression of the standard from the Committee Specification stage to the Candidate OASIS Standard stage, early adopters within the TC and outside of the TC need to demonstrate implementability of the new standard by making public Statements of Use and posting those to the TC. Write to the TC comment list if you are interested in an early implementation and need advice. XLIFF TC will launch the questionnaire to collect the public Statements of Use in late February/early March 2017. We expect the OASIS wide standards approval ballot to take place during the summer of 2017.

Share with
Tweet about this on TwitterShare on FacebookShare on LinkedInShare on Google+Buffer this pageEmail this to someone

About David Filip

David Filip is Chair (Convener) of OASIS XLIFF OMOS TC; Secretary, Editor and Liaison Officer of OASIS XLIFF TC; a former Co-Chair and Editor for the W3C ITS 2.0 Recommendation; and co-moderator of the Interoperability and Standards WG at JIAMCATT. He has been also appointed as NSAI expert to ISO TC37 SC3 and SC5, ISO/IEC JTC1 WG9, WG10 and SC38. His specialties include open standards and process metadata, workflow and meta-workflow automation. David works as a Research Fellow at the ADAPT Research Centre, Trinity College Dublin, Ireland.

Leave a Reply

Find This Post Valuable? Subscribe to MultiLingual Insights

Name *

Email *

Subscribe to MultiLingual Insights

Name *

Email *

Insights Categories

Insights Archives

Submit Insights

Multilingual Insights

The Latest Insights

MultiLingual News

Subscribe To MultiLingual News

  • We use SafeUnsubscribe SafeUnsubscribe®. Email Privacy Policy.
  • This field is for validation purposes and should be left unchanged.