OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [xliff-comment] XLIFF 2.0 public review comments

Thanks, Martin, for catching the typo. I will of course fix it on the next commit.

Dr. David Filip
University of Limerick, Ireland
telephone: +353-6120-2781
cellphone: +353-86-0222-158
facsimile: +353-6120-2734
mailto: david.filip@ul.ie

On Mon, Aug 5, 2013 at 4:53 PM, Martin Chapman <martin.chapman@oracle.com> wrote:

There is a a typo in the sentence at the end of section 3 (delete the extraneous s in presvious):


    Conformant applications are NOT REQUIRED to support XLIFF 1.2 or presvious Versions.


Other than that looks ok to me.





From: Dr. David Filip [mailto:David.Filip@ul.ie]
Sent: 04 August 2013 16:04
To: Martin Chapman
Cc: xliff-comment@lists.oasis-open.org; xliff@lists.oasis-open.org
Subject: Re: [xliff-comment] XLIFF 2.0 public review comments


Martin, all, sorry for confusion, resending this from my official address..

On Sat, Aug 3, 2013 at 12:33 AM, David Filip <davidf@davidf.org> wrote:



sorry for our prolonged silence.


In response to your comments and following the discussion in the TC on May 21, 2013 https://lists.oasis-open.org/archives/xliff/201305/msg00019.html

we have made the following changes to the spec:

- UPPERCASED the normtaive keywords and changed the front matter respectively

- Indicated that backwards compatibility with XLIFF 1.2 is not REQUIRED.

- made sure that all normative references are used in the body and all body references called out as normative or non normative in the References sections 1.2 and 1.3


Please let us know if everything seems alright with you in the editor's copy https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/xliff-core.pdf




David Filip, Ph.D.
cellphone: +353-86-0222-158


On Thu, May 9, 2013 at 6:56 PM, Martin Chapman <martin.chapman@oracle.com> wrote:

In my role as a TAB member I was asked to review XLIFF 2.0. These comments are individual and do not represent any consensus of the TAB.


Document reviewed:




The TAB are trialling a checklist to aim for consistency across reviews. I have attached my responses, I hope they make sense.


There are only two areas that should be fixed.


1: please check that all references are listed in the references section. There were some references to Unicode in the document that were not listed in the ref section. Same for ISO 8601

  Also make sure all references are used in the body of the spec.

2.In the conformance section add a statement about compatibility with xliff 1.x  e.g. applications [are/are not] required to support xliff 1.x and xliff 2.0 – something like that.


Let me know if anything needs clarified.






Oracle is committed to developing practices and products that help protect the environment






[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]