Call for Participation: XLIFF Object Model and Other Serializations (XLIFF OMOS) TC
A new OASIS technical committee is being formed. The XLIFF Object Model and Other Serializations (XLIFF OMOS) Technical Committee (TC) has been proposed by the members of OASIS listed in the charter below. The TC name, statement of purpose, scope, list of deliverables, audience, IPR mode and language specified in this proposal will constitute the TC's official charter. Submissions of technology for consideration by the TC, and the beginning of technical discussions, may occur no sooner than the TC's first meeting.
The eligibility requirements for becoming a participant in the TC at the first meeting are:
(a) you must be an employee or designee of an OASIS member organization or an individual member of OASIS, and
(b) you must join the Technical Committee, which members may do by using the Roster "join group: link on the TC's web page at [a].
To be considered a voting member at the first meeting:
(a) you must join the Technical Committee at least 7 days prior to the first meeting (on or before 01 December 2015); and
(b) you must attend the first meeting of the TC, at the time and date fixed below (08 December 2015).
Participants also may join the TC at a later time. OASIS and the TC welcomes all interested parties.
Non-OASIS members who wish to participate may contact us about joining OASIS [b]. In addition, the public may access the information resources maintained for each TC: a mail list archive, document repository and public comments facility, which will be linked from the TC's public home page at [c].
Please feel free to forward this announcement to any other appropriate lists. OASIS is an open standards organization; we encourage your participation.
[b] See http://www.oasis-open.org/join/
CALL FOR PARTICIPATION
OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) Technical Committee Charter
The charter for this TC is as follows.
Section 1: TC Charter
(1)(a) TC Name
XLIFF Object Model and Other Serializations (XLIFF OMOS) Technical Committee
(1)(b) Statement of Purpose
This committee’s high level purpose is to further advance standards based payload and metadata interoperability in the Globalization, Internationalization, Localization and Translation (GILT) industries. This TC will be describing and defining standard serialization independent interchange objects based predominantly on state of the art and legacy XML standards that have been successfully used in the GILT industries ever since inception of XML. Defining specific serializations, transaction models, standard interfaces and web services based on the defined objects and object models is also in scope as far as it facilitates the high level purpose set out here.
The following items belong to the Scope of Work and are expected to be refined as the TC gains additional insights into evolving GILT industry use cases. Members will gather insights and requirements from consultations with the wider community of industry stakeholders, annual Symposia, questionnaires, etc. and use these insights to produce concrete technical deliverables.
In particular, in case that XLIFF TC identifies the need for a major new version of the XLIFF standard and starts moving away from the XLIFF 2 family of standards, this TC will work in concert with those developments and develop a serialization independent Object Model for the major new version, non-XML serializations etc. exactly as it now works on these items for the XLIFF 2 family of standards, TMX etc.
i) Define and maintain a serialization independent Object Model for the XLIFF 2 family of standards that is being developed by the OASIS XLIFF TC.
ii) Define and maintain non-XML serializations of the said XLIFF Object Model, prominently a JSON serialization, but also any other serializations that could not be developed by the XLIFF TC for scope restriction reasons, as industry needs arise.
iii) Define specific standard Application Interfaces (API) and abstract service architectures for various XLIFF serializations and other related standards (such as TMX, TBX, ITS, SRX etc.) and their various serializations used in concert for GILT payload and metadata interchange.
iv) Host and maintain TMX 1.4b (1.4.2), develop and maintain any successor versions of the TMX standard including its serialization independent Object Model and various serializations as the need arises.
v) Define and describe lossless or nearly lossless mappings between XLIFF and related GILT standards, define those mappings in an abstract way and for specific serializations as the need arises.
vi) Define and describe informative best practices and abstract services architecture recommendations with regards to usage of the XLIFF 2 family of standards and related standards including but not limited to current and successor versions of TMX, TBX, SRX, ITS and other related standards used for data and metadata interchange in the GILT industries.
The following are high priority technical deliverables that should be developed and published in the OASIS standards track within 24 months from TC initiation:
i) Serialization independent Object Model for the XLIFF 2 family of standards
ii) JSON serialization of XLIFF 2.1
Work on the following may start during the work on the above high priority deliverables or later on given the general sense of urgency for those within the GILT industries
iii) Republishing of TMX 1.4b (1.4.2) under OASIS IPR
iv) Major new version of TMX, compatible with XLIFF 2 family of standards
(1)(e) IPR Mode
The expected audience for the work of the XLIFF OMOS TC includes but is not limited to:
- Multilingual content and software architects and strategists, multilingual content publishers
- GILT services architects and developers
- Content owners and managers that seek to publish their content in multiple localized versions
- Software providers for internationalization, localization, and translation tools and processes, including language technology components
- Technical communicators employing localization tools and processes for multilingual publishing of their content
- Localization service providers who need to interact seamlessly with localizable and localized content of their customers
English (US spelling)
Section 2: Additional Information
(2)(a) Identification of Similar Work
This TC is intended as the sister committee to OASIS XLIFF TC. The Scope of Work of this TC is designed so that it complements the Scope of Work of the XLIFF TC that could not work on this TCs work items because of legacy scope restrictions. Strong and close liaison will be maintained with XLIFF TC, membership is expected to overlap to large extent.
Other related standards, standards bodies and groups are currently the following:
W3C ITS 2.0 and the W3C ITS Interest Group
ULI TC at Unicode Consortium, their contributions to CLDR (for instance natural languages segmentation behavior), hosting and maintenance work on SRX, word counting and match similarity related standards and best practices
ISO TC 37 TBX and LTAC work on TBX
This TC is also ready to receive Localization related work items from ETSI on behalf of the disbanded ETSI ISG LIS, as long as those fall under XLIFF OMOS Scope of Work and were not transferred to other more closely related standardization body or group
Other standardization work items at other groups may arise that are relevant for this TCs.
This TC will also strive to work in concert with other OASIS committees, prominently CMIS, UBL, DITA, DocBook, and ARIP.
(2)(b) First TC Meeting
08 December 2015 at 4pm GMT(Western European Time). The meeting will be sponsored by Trinity College Dublin (ADAPT).
(2)(c) Ongoing Meeting Schedule
The ongoing meetings will be held on 2nd and 4th Tuesdays each month, at 4pm GMT (Western European time with or w/o DST depending on the season). The meetings will be initially sponsored by Trinity College Dublin (ADAPT). TC members can agree to skip a regular Tuesday meeting from time to time if quorum will not likely be achieved due to holiday seasons, or a majority of voters otherwise unavailable.
(2)(d) TC Proposers
David Filip, firstname.lastname@example.org, Trinity College Dublin (ADAPT)
Dave Lewis, email@example.com, Trinity College Dublin (ADAPT)
Yves Savourel, firstname.lastname@example.org, Individual
Patrik Mazanek, email@example.com, SDL
Lucian Podereu, firstname.lastname@example.org, SDL
Bryan Schnabel, email@example.com, Individual
Felix Sasaki, firstname.lastname@example.org, Individual
Lucia Morado, email@example.com, Individual
Loic Dufresne de Virel, firstname.lastname@example.org, Intel Corporation
(2)(e) Primary Representatives' Support
I, David Lewis, email@example.com, as OASIS primary representative for Trinity College Dublin (ADAPT), confirm our support for this proposed Charter and endorse our participants listed above as named co-proposers and convener.
I, Nuno Linhares, firstname.lastname@example.org, as OASIS primary representative for SDL, confirm our support for this proposed Charter and endorse our participants listed above as named co-proposers.
I, Katalin Bartfai-Walcott, email@example.com, as OASIS primary representative for Intel Corporation, confirm our support for this proposed Charter and endorse our participants listed above as named co-proposers.
(2)(f) TC Convener
David Filip, firstname.lastname@example.org, Trinity College Dublin (ADAPT)
(2)(g) OASIS Member Section
Decision to be deferred.
(2)(h) Anticipated Contributions
TMX 1.4.2 (1.4b) from ETSI
(2)(i) FAQ Document
Q1 [IPR Mode]: "Why did you choose the Non-Assertion mode?"
A1 [IPR Mode] "Under the Non-Assertion mode, all parties agree not to seek to enforce any patent or other intellectual property rights they may have in case usage of those is essential to implement the standards produced by that committee. This precludes the need for licensing terms altogether and makes it easier for open-source developers in particular to participate. The majority of new OASIS Technical Committees choose to work under the Non-Assertion mode."
Q2 [Join OASIS] "How do I get involved in XLIFF OMOS TC?"
A2 [Join OASIS] "All interested parties are welcome to participate in the XLIFF OMOS TC as long as they are or are willing to become OASIS members; contact email@example.com for details."
(2)(j) Work Product Titles and Acronyms