[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: TAUS role extended to Interoperability Watchdog
I'm glad that you are moving forward on providing the XLIFF TC with substantive, actionable guidance (forgive me if I'm reading more into your affirmative reply than was meant - of course I am wearing my TC Chair hat at the moment, in full-on-recruit mode).
Your question/request seems to be more at the OASIS level than the XLIFF level. That is fine. But I think scheduling a conference call with just me would not help us find the way for TAUS members who are not OASIS members to participate in XLIFF TC work and technical discussions. For that guidance, we'd need to look to OASIS.
Toward that end, I think the best approach would be for TAUS to strike up a technical liaison arrangement with OASIS, as described in the OASIS guidelines on this topic (http://www.oasis-open.org/committees/liaisons.php). As you see on this page, there are examples of other standards-related bodies like IEC, ISO, ITU, NIST, and even LISA. I am also cc'ing our acting OASIS representative, Robin Cover, to help guide this effort.
Meanwhile, if your intent is less hands-on than I implied, we would still gratefully welcome the expert input. In this case, there are existing channels that the XLIFF TC utilizes for gathering input and advice from the public, at large. This link will take you to the Mailing lists and comments section of our TC page (http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=xliff#feedback). The xliff-comment list notes go directly to each TC member's inbox. And the xliff-users list is more for technical user issues, and is monitored by some of the members of the XLIFF TC.
I look forward to helping TAUS and the XLIFF TC advance in providing the community with the best possible specification.
Chair, OASIS XLIFF Technical Committee
My apologies for the delayed response.
It would be great to schedule a conference call with yourself and or someone from the OASIS organization. We would like to understand how we can best connect and represent the TAUS members (who are not also OASIS members) in the technical discussions. Dr. Klemens Waldhör, copied on this email, will be the TAUS ‘standards representative’.
Please let us know when is a good time to talk.
Jaap van der Meer
Thanks for this informative debrief! I downloaded the Annual Plan (http://www.translationautomation.com/images/stories/pdf/taus-annual-plan-2011-extended.pdf). I have not yet given it a thorough read, but I intend to.
I did notice on page 14 an encouraging quote: "TMX and XLIFF are flagged as the most important interchange standards in the TAUS interoperability survey. TAUS will get actively involved in the technical committees and help resolve outstanding issues and ensure a timely and purposeful release of future releases."
Speaking on behalf of the XLIFF TC, this is most welcomed! Improving XLIFF is (at least) a two fronted effort. On one front, we are most fortunate that we have the excellent input from a vocal group of user who are forthcoming and concise in communicating XLIFF 1.2's deficiencies and areas that need improvement. For this I am most grateful. But the other front is the actual committee work. Our TC is now doing the difficult, but necessary work of collecting, understanding, consolidating inputs; and (in some cases) resolving conflicting inputs. TAUS' active involvement on this front will help us greatly. In fact the timing could not be better. We are at a point now where we are working on both fronts to deliver XLIFF 2.0 in such a way that it better serves our community, and that (hopefully) the community does not have to wait so long for the improvements to reach them.
If you need any help in joining the TC, or need to know other ways to "get actively involved" I will be very happy to help.
Chair, OASIS XLIFF TC
ps., I hope you don't mind, I cc'd the XLIFF TC list. This will give us a reference to add to the agenda to address this effort.
No virus found in this incoming message.