[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff] RE: ISO TC 37 Liaison
As chair of OAXAL I can confirm Bryan's statement. OAXAL is an architectural standard which emphasizes interoperability between standards within a unified workflow automation environment.The importance of the use of Open Standards is paramount, rather than the specific contents.
This message contains confidential information and is intended only for
the individual named. If you are not the named addressee you may not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free as
information could be intercepted, corrupted, lost, destroyed, arrive
late or incomplete, or contain viruses. The sender therefore does not
accept liability for any errors or omissions in the contents of this
message which arise as a result of e-mail transmission. If verification
is required please request a hard-copy version. Unless explicitly stated
otherwise this message is provided for informational purposes only and
should not be construed as a solicitation or offer.
On 18/05/2011 14:23, Schnabel, Bryan S wrote:
8615A00ECE2E6149BB810FCAAEDB0D0C4319889150@us-bv-m10.global.tektronix.net" type="cite">Jamie and Peter, Thank you for guiding us on the correct path here. I am confident that the goals of the XLIFF TC will be met and also the requirements of OASIS. As for OAXAL, I think I'm now the only XLIFF TC member who serves jointly on the OAXAL TC. I agree with Peter that XLIFF is only mentioned in OAXAL as an intact standard at its core, and that the OAXAL TC has never discussed (as far as I know) a need for other capabilities. Thanks, Bryan ________________________________________ From: Peter Reynolds [email@example.com] Sent: Wednesday, May 18, 2011 3:29 AM To: Jamie Clark; firstname.lastname@example.org Cc: Chet Ensign Subject: [xliff] RE: ISO TC 37 Liaison Hi Jamie, Thank you for your advice and support. The OAXAL idea has not been brought up at the TC to the best of the knowledge. Most OAXAL TC members are also members of the XLIFF TC and my understanding is they are not suggesting changes to XLIFF. I think you sending the additional note to ISO TC 37 will be very helpful. Thanks, Peter. -----Original Message----- From: Jamie Clark [mailto:email@example.com] Sent: Wednesday, May 18, 2011 9:19 AM To: Peter Reynolds; firstname.lastname@example.org Cc: Chet Ensign Subject: ISO TC 37 Liaison Peter, thank you for providing the liaison report for ISO TC 37 and for fulfilling this role. I have two comments on the report. 1. On MLIF: Obviously, the view of TC members that XLIFF does not belong as part of MLIF is a technical conclusion well outside of my own expertise. But it does make me mindful that XLIFF may be presented, generally, as part of a suite of functional specs. There is nothing OASIS need do, when someone independently states that users ought to use conformant XLIFF along with specific other methods. On the other hand, if someone wished to alter, integrate and refactor XLIFF into some other work, they'd need to work with OASIS and your TC first. I recall that some LISA experts published about the idea that XLIFF ought to be aggregated with some other capabilities in the manner described in the OASIS OAXAL TC's proposed architecture. Is that something of interest to the XLIFF TC members? 2. On submissions. We do need to make sure that an OASIS submission of XLIFF to ISO is correctly described as a possibility, subject to some conditions, rather than a sure thing. We understand that the TC wishes eventually to have XLIFF shared by submission of the completed v1.2 work to ISO. Our policy permits that, if certain milestones are met [a]. While they seem feasible, in this case, their successful completion is not a certainty. [a] http://www.oasis-open.org/policies-guidelines/liaison#submitwork In case your draft report is mistakenly taken as a promise of certain submission, I will send a supplemental note to the TC 37 secretariat, with a copy to this TC, making it clear that there are some conditions that first must be fulfilled. Kind regards Jamie ~ James Bryce Clark ~ General Counsel, OASIS ~ http://www.oasis-open.org/who/staff.php#clark www.identi.ca/JamieXML www.twitter.com/JamieXML http://t.sina.cn/jamiexml New OASIS HQ number: +1 781-425-5073 New on FB: http://facebook.com/oasis.open --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php