Chet, all, resubmitting with 1st meeting specifics as advised.
The only additional tracked change in the attached 1.0.1 version is adding the 1st meeting specifics.
XLIFF OMOS 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 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.
(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 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, , Trinity College Dublin (ADAPT)
Dave Lewis, , Trinity College Dublin (ADAPT)
Yves Savourel, , Individual
Patrik Mazanek, , SDL
Lucian Podereu, , SDL
Bryan Schnabel, , Individual
Felix Sasaki, , Individual
Lucia Morado, , Individual
(2)(e) Primary
Representatives' Support
I, David Lewis, , 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, , 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, , 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
(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 for details."
(2)(j) Work Product
Titles and Acronyms
TBD
[DF1]The
correct form is “Mazánek” unfortunately the extended character “á” had not survived the submission so we had
to go with a plain “a” this time round L
[DF2]The
correct form is “Lucía” unfortunately the extended character “í” had not survived the submission so we had
to go with a plain “i“ this time round L
Dr. David Filip
===========
OASIS XLIFF TC Secretary, Editor, and Liaison Officer
Spokes Research Fellow
ADAPT Centre
KDEG, Trinity College Dublin
Mobile: +420-777-218-122
On Tue, Nov 3, 2015 at 4:27 PM, Chet Ensign <> wrote:
Hi David,
This looks great. I did catch one correction that we need:
2b - first meeting. This also needs the time (e.g. 4PM GMT as the next section states) and it needs to state who will sponsor the call (e.g. Trinity College).
If you can just tweak and send back to me, that'll be fantastic.
Thanks,
/chet
On Tue, Nov 3, 2015 at 7:48 AM, David Filip <> wrote:
Chet, all,
this is the submission of the final XLIFF OMOS TC Charter that will be published by OASIS Admin on 6th November.
Other co-proposers may be added up until 5th November.
Attached is the final charter docx with tracked changes from the reviewed version.
Apart from explicitly adding the ARIP TC liaison, three minor editorial changes were made (WRT special characters handling and ETSI ISG LIS formulation clarified)
XLIFF OMOS 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 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.
(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 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
(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, ,
Trinity College Dublin (ADAPT)
Dave Lewis, ,
Trinity College Dublin (ADAPT)
Yves Savourel, ,
Individual
Patrik Mazanek, , SDL
Lucian Podereu, ,
SDL
Bryan Schnabel, ,
Individual
Felix Sasaki, ,
Individual
Lucia Morado, ,
Individual
(2)(e) Primary
Representatives' Support
I, David Lewis, ,
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, ,
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, ,
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
(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 for
details."
(2)(j) Work Product
Titles and Acronyms
TBD
[DF1]The
correct form is “Mazánek” unfortunately the extended character “á” had not survived the submission so we had
to go with a plain “a” this time round L
[DF2]The
correct form is “Lucía” unfortunately the extended character “í” had not survived the submission so we had
to go with a plain “i“ this time round L
Dr. David Filip
===========
OASIS XLIFF TC Secretary, Editor, and Liaison Officer
Spokes Research Fellow
ADAPT Centre
KDEG, Trinity College Dublin
Mobile: +420-777-218-122
On Tue, Oct 27, 2015 at 6:53 PM, David Filip <> wrote:
Hi again, all,
Even though we did not record any comment to the proposed draft charter it will be beneficial - for the current co-proposers and potential other co-proposers and early joiners that might be on the publicly archived list - to record changes made and potentially to be made to this charter.
Changes to date
----------------------
Compared to the version that was first communicated in XLIFF P&L SC of the XLIFF TC, this publicly reviewed draft contains the following changes:
- explicitly adding architecture blueprint deliverables along with APIs (that were in from the start) to the scope
- explicitly calling out NLP tool makers in the audience section of the charter
The above already is in the reviewed charter, this is tracked just for the benefit of people who saw earlier drafts.
Pending/proposed changes
------------------------------------
Other changes that we expect to make by 5th November, when the final charter will need to be submitted for the call for participation:
- We want to list OASIS ARIP TC as an explicit liaison https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=arip
ARIP TC looks into adding the Augmented Reality feature into Information products and also into making content fit for AR. There is a close relationship between this TC and DITA TC and also what we are trying to do at XLIFF OMOS.
- If we receive other co-proposer primaries statements of support by 6th November, these statements and the co-proposers will be added to the part 2.
Feel free to clarify anything of the above with the publicly archived list OASIS Charter Discuss List <> on CC or privately, whichever you prefer.
Cheers and thanks
dF
Dr. David Filip
===========
OASIS XLIFF TC Secretary, Editor, and Liaison Officer
Spokes Research Fellow
ADAPT Centre
KDEG, Trinity College Dublin
Mobile: +420-777-218-122
On Tue, Oct 27, 2015 at 6:02 PM, David Filip <> wrote:
Hi all, this is to record in my position as the convener that no comments were recorded during the OASIS membership at large review.
Cheers and thanks
dF
Dr. David Filip
===========
OASIS XLIFF TC Secretary, Editor, and Liaison Officer
Spokes Research Fellow
ADAPT Centre
KDEG, Trinity College Dublin
Mobile: +420-777-218-122
On Fri, Oct 9, 2015 at 11:53 PM, Chet Ensign <> wrote:
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) 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: . All messages will be publicly archived at: 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/. 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, , Trinity College Dublin (ADAPT)
Dave Lewis, , Trinity College Dublin (ADAPT)
Yves Savourel, , Individual
Patrik Maznek, , SDL
Lucian Podereu, , SDL
Bryan Schnabel, , Individual
Felix Sasaki, , Individual
Luca Morado, , Individual
(2)(e) Primary Representatives' Support
I, David Lewis, , 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, , 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, , 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
(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 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
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
--
/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Attachment:
XLIFF_OMOS_TC_OASIS-new-tc-proposal-submission_v1.0.1.docx
Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
