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

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-comment message

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


Subject: Draft of XLIFF 2.1 in ISO template


Dear XLIFF TC, Chet,

 

I have done a first draft of XLIFF 2.1 in the ISO template. I am submitting to the XLIFF Comments so that the XLIFF TC and OASIS can consider it, edit it and create a draft that is proposed to ISO.  

 

I have added the paragraph called ‘Abstract’ in the OASIS standard as the Scope in the ISO one. There must be a Scope in an ISO document. I have also added a paragraph to the scope stating that the document is created, revised and approved by the XLIFF TC and comments should be sent there.

 

In the definitions of the OASIS document there is a sentence: “The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL are to be interpreted as described in [RFC 2119].” ISO has the same meaning assigned to these words through their directives. I am not sure they will be happy with this.

 

I have included the Non-Normative References in the bibliography section at the end.

 

I have included specification URIs from the beginning of the OASIS standard as an Annex at the end.

 

Annex D has acknowledgements of people on the TC who have contributed to developing the standard. ISO may have an issue with this. The first time we did this ISO central secretariat were concerned with the IPR statement on the XLIFF TC web pages: OASIS XML Localisation Interchange File Format (XLIFF) TC | IPR (oasis-open.org). They may have similar concern about referencing individuals.

 

There is a lot of internal hyperlinks within the OASIS document. I have left these in the ISO draft but they reference the OASIS document. I would suggest just removing all these. Anyone who is working with the standard is likely to be using the OASIS version anyway. With TBX, an ISO standard, they do not have internal links.

 

Best regards,

 

Peter.

 

memoq.com
Peter Reynolds
Co-CEO  Management
   
memoQ Translation Technologies Ltd.
Headquarters Rákóczi út 70-72. II. em. H-1074 Budapest, Hungary

Attachment: ISO 21720 XLIFF.docx
Description: ISO 21720 XLIFF.docx



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