OASIS XLIFF Object Model and Other Serializations (XLIFF OMOS) Technical Committee

The original Call For Participation for this TC may be found at https://lists.oasis-open.org/archives/xliff-omos/201511/msg00000.html.

  1. Name of the TC

    XLIFF Object Model and Other Serializations (XLIFF OMOS) Technical Committee

  2. 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.

  3. Scope of Work

    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.

  4. Deliverables

    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

  5. IPR Mode

    This TC will operate under the Non-Assertion IPR mode as defined in the OASIS Intellectual Property Rights (IPR) Policy.

  6. Audience

    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
  7. Language

    English (US spelling)