W3C home > Mailing lists > Public > public-i18n-its-ig@w3.org > October 2015

Fwd: [members] Call for Comment: proposed Charter for XLIFF Object Model and Other Serializations (XLIFF OMOS) TC

From: Felix Sasaki <fsasaki@w3.org>
Date: Wed, 14 Oct 2015 07:57:52 +0200
To: www International <www-international@w3.org>, public-i18n-its-ig <public-i18n-its-ig@w3.org>
Message-Id: <93C0A013-56FD-40B4-8016-794068A219C0@w3.org>
Apologies for cross posting. This Oasis TC is working on close relation to W3C technologies like ITS 2.0 or the browser DOM, hence this may be of interest for people on these W3C lists.

- Felix

> Anfang der weitergeleiteten Nachricht:
> 
> Von: Chet Ensign <chet.ensign@oasis-open.org>
> Betreff: [members] Call for Comment: proposed Charter for XLIFF Object Model and Other Serializations (XLIFF OMOS) TC
> Datum: 9. Oktober 2015 23:53:41 MESZ
> An: tc-announce@lists.oasis-open.org, members@lists.oasis-open.org, OASIS Charter Discuss List <oasis-charter-discuss@lists.oasis-open.org>
> Kopie: David Filip <filipd@tcd.ie>, dave.lewis@cs.tcd.ie, Yves Savourel <ysavourel@enlaso.com>, pmazanek@sdl.com, lpodereu@sdl.com, "Schnabel, Bryan S" <bryan.s.schnabel@tektronix.com>, felix@sasakiatcf.com, Lucia Morado Vazquez <lucia.morado@unige.ch>
> 
> To OASIS Members:
> 
> A draft TC charter has been submitted to establish the XLIFF Object Model and Other Serializations (XLIFF OMOS) Technical Committee. In accordance with the OASIS TC Process Policy section 2.2: (https://www.oasis-open.org/policies-guidelines/tc-process#formation <https://www.oasis-open.org/policies-guidelines/tc-process#formation>) the proposed charter is hereby submitted for comment. The comment period shall remain open until 23:59 GMT on 23 October 2015.
> 
> OASIS maintains a mailing list for the purpose of submitting comments on proposed charters. Any OASIS member may post to this list by sending email to: oasis-charter-discuss@lists.oasis-open.org <mailto:oasis-charter-discuss@lists.oasis-open.org>. All messages will be publicly archived at: http://lists.oasis-open.org/archives/oasis-charter-discuss/ <http://lists.oasis-open.org/archives/oasis-charter-discuss/>. Members who wish to receive emails must join the group by selecting "join group" on the group home page: http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/ <http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/>. Employees of organizational members do not require primary representative approval to subscribe to the oasis-charter-discuss e-mail.
> 
> A telephone conference will be held among the Convener, the OASIS TC Administrator, and those proposers who wish to attend within four days of the close of the comment period. The announcement and call-in information will be noted on the OASIS Charter Discuss Group Calendar.
> 
> We encourage member comment and ask that you note the name of the proposed TC (XLIFF OMOS) in the subject line of your email message.
> 
> --- TC Charter
> 
> Section 1: TC Charter
>  
> (1)(a) TC Name
>  
> XLIFF Object Model and Other Serializations (XLIFF OMOS) Technical Committee 
>  
> (1)(b) Statement of Purpose
>  
> This committees 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. 
>  
> (1)(c) Scope
>  
> 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. 
>  
> (1)(d) 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 
>  
> (1)(e) IPR Mode
>  
> Non-Assertion 
>  
> (1)(f) 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 
>  
> (1)(g) Language
>  
> 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 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 and DocBook 
> 
> (2)(b) First TC Meeting 
> 
> 08 December 2015 
> 
> (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, filipd@tcd.ie <mailto:filipd@tcd.ie>, Trinity College Dublin (ADAPT) 
> 
> Dave Lewis, dave.lewis@cs.tcd.ie <mailto:dave.lewis@cs.tcd.ie>, Trinity College Dublin (ADAPT) 
> 
> Yves Savourel, ysavourel@enlaso.com <mailto:ysavourel@enlaso.com>, Individual
> 
> Patrik Maznek, pmazanek@sdl.com <mailto:pmazanek@sdl.com>, SDL 
> 
> Lucian Podereu, lpodereu@sdl.com <mailto:lpodereu@sdl.com>, SDL 
> 
> Bryan Schnabel, bryan.s.schnabel@tektronix.com <mailto:bryan.s.schnabel@tektronix.com>, Individual 
> 
> Felix Sasaki, felix@sasakiatcf.com <mailto:felix@sasakiatcf.com>, Individual 
> 
> Luca Morado, lucia.morado@unige.ch <mailto:lucia.morado@unige.ch>, Individual
> 
> (2)(e) Primary Representatives' Support
> 
> I, David Lewis, dave.lewis@cs.tcd.ie <mailto:dave.lewis@cs.tcd.ie>, 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, nlinhares@sdl.com <mailto:nlinhares@sdl.com>, as OASIS primary representative for SDL, confirm our support for this proposed Charter and endorse our participants listed above as named co-proposers. 
> 
> (2)(f) TC Convener
> 
> David Filip, filipd@tcd.ie <mailto:filipd@tcd.ie>, 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
> http://www.etsi.org/deliver/etsi_gs/lis/001_099/002/01.04.02_60/gs_lis002v010402p.pdf <http://www.etsi.org/deliver/etsi_gs/lis/001_099/002/01.04.02_60/gs_lis002v010402p.pdf> 
> 
> (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 join@oasis-open.org <mailto:join@oasis-open.org> for details." 
> 
> (2)(j) Work Product Titles and Acronyms
> 
> TBD
> 
> -- 
> 
> /chet 
> ----------------
> Chet Ensign
> Director of Standards Development and TC Administration 
> OASIS: Advancing open standards for the information society
> http://www.oasis-open.org <http://www.oasis-open.org/>
> 
> Primary: +1 973-996-2298
> Mobile: +1 201-341-1393 
Received on Wednesday, 14 October 2015 05:58:04 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 14 October 2015 05:58:04 UTC