[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: unanswered query on comment list
Hi Andrzej, Thank you for fielding this question. As I said, given that my expertise and experience are not strong on the xml:tm side, I did not feel I was the best TC member to answer this. Your explanation is pretty clear to me. Thanks, Bryan ________________________________________ From: Andrzej Zydron [azydron@xml-intl.com] Sent: Friday, December 11, 2009 4:07 AM To: Schnabel, Bryan S Cc: oaxal@lists.oasis-open.org; joann.hackos@comtech-serv.com Subject: Re: unanswered query on comment list Hi Bryan, Thank you for your email. The question in the link regarding the DocZone's claim to be the reference implementation is not quite accurate. They are to the best of my knowledge a reference implementation of the proposed OAXAL level 1 conformant Reference Architecture. OAXAL is an OASIS TC that is bound by the rules and regulations of the TC and conforms to the OASIS IP policy. All procedural rules required by OASIS have been adhered to at all times and all decisions have been subjected to committee vote. OAXAL as an OASIS reference architecture proposal is open to all vendors to implement. The fact that a company has chosen to implement a proposed standard in no way compromises the fact that it is vendor agnostic. If, for instance, a company were do declare that it has a reference implementation of XLIFF 2.0, would this in any way mean that XLIFF 2.0 is not vendor agnostic? There are I believe already other OAXAL implementations in existence. OAXAL is entirely composed of Open Standards and I cannot see how an implementation of OAXAL Level 1 could be anything but vendor agnostic. xml:tm and/or W3C ITS is not mandated in certain implementations of OAXAL according to the Conformance Guidelines (http://wiki.oasis-open.org/oaxal/FrontPage#ConformanceCategories). This means in fact that those aspects of the workflow concerning segmentation and extraction of text from an XML document can be done using vendor specific techniques. The freedom to implement these is acknowledged through the Conformance Categories. This was arrived at through our democratic TC process under OASIS rules. Best Regards, AZ On 10/12/2009 19:11, bryan.s.schnabel@tektronix.com wrote: > > Hi Andrzej, > > Rodolfo asked JoAnn and I to seek an answer to the not-yet-addressed > query he posted on the comment list: > > http://lists.oasis-open.org/archives/oaxal-comment/200909/msg00000.html > > I will summarize the points he made to JoAnn and me. > > He has indicated that since xml:tm is claimed as required to achieve > full compliance, and in his opinion xml:tm is not necessary, and the > vendor mentioned in his question is claimed to be OAXAL's reference > implementation, he seeks a compelling explanation to indicate that > OAXAL is indeed vendor agnostic. > > I could not address his concerns because I do not have broad knowledge > of, or experience with, xml:tm. This seems to better fit your expertise. > > Thanks, > > Bryan > -- email - azydron@xml-intl.com smail - c/o Mr. A.Zydron PO Box 2167 Gerrards Cross Bucks SL9 8XF United Kingdom Mobile +(44) 7966 477 181 FAX +(44) 1753 480 465 www - http://www.xml-intl.com 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.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]