OASIS XML Localisation Interchange File Format (XLIFF) TC

Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added: trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process.

Bryan, all, I uploaded onto the TC SVN a docx version of XLIFF 2.0 that Peter Reynolds produced by copy pasting the HTML (authoritative version). http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/%21Admin/SubmissionToISO/xliff-2-0.docx It is a requirement of the ISO fast track process that we submit the standard in the docx format. @Jamie, Chet, any advice how to go about this? Would a simple call for dissent do? We jumped all the hoops and produced the OASIS standard and then approved the letter asking OASIS Leadership to submit the standard to ISO. So this should be considered just a technicality? It should be noted that this is a verbatim copy of the authoritative HTML version of the published standard. Anyways, whatever procedure Jamie or Chet advise on this, I'd like to address this in the April 5 TC meeting. Cheers and thanks dF  Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 ---------- Forwarded message ---------- From: < workgroup_mailer@lists.oasis-open.org > Date: Wed, Mar 23, 2016 at 5:27 PM Subject: [xliff] Version Control Commit by DavidFilip To: xliff@lists.oasis-open.org Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added:    trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process. --------------------------------------------------------------------- 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

Hi David,  I noticed that the TOC links in the file don't work. Since the HTML was pasted into the document, the HTML links remained pointing to docs.oasis-open.org . I'm trying a couple of utilities right now to see if we can get that fixed. If they work, I'll send you the file.  I'll let Jamie handle procedural questions.  Best,  /chet On Wed, Mar 23, 2016 at 1:49 PM, David Filip < david.filip@adaptcentre.ie > wrote: Bryan, all, I uploaded onto the TC SVN a docx version of XLIFF 2.0 that Peter Reynolds produced by copy pasting the HTML (authoritative version). http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/%21Admin/SubmissionToISO/xliff-2-0.docx It is a requirement of the ISO fast track process that we submit the standard in the docx format. @Jamie, Chet, any advice how to go about this? Would a simple call for dissent do? We jumped all the hoops and produced the OASIS standard and then approved the letter asking OASIS Leadership to submit the standard to ISO. So this should be considered just a technicality? It should be noted that this is a verbatim copy of the authoritative HTML version of the published standard. Anyways, whatever procedure Jamie or Chet advise on this, I'd like to address this in the April 5 TC meeting. Cheers and thanks dF  Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 ---------- Forwarded message ---------- From: < workgroup_mailer@lists.oasis-open.org > Date: Wed, Mar 23, 2016 at 5:27 PM Subject: [xliff] Version Control Commit by DavidFilip To: xliff@lists.oasis-open.org Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added:    trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process. --------------------------------------------------------------------- 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 -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 

Well, close but TOC links still didn't work. Your copy looks better too.  On Wed, Mar 23, 2016 at 2:30 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi David,  I noticed that the TOC links in the file don't work. Since the HTML was pasted into the document, the HTML links remained pointing to docs.oasis-open.org . I'm trying a couple of utilities right now to see if we can get that fixed. If they work, I'll send you the file.  I'll let Jamie handle procedural questions.  Best,  /chet On Wed, Mar 23, 2016 at 1:49 PM, David Filip < david.filip@adaptcentre.ie > wrote: Bryan, all, I uploaded onto the TC SVN a docx version of XLIFF 2.0 that Peter Reynolds produced by copy pasting the HTML (authoritative version). http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/%21Admin/SubmissionToISO/xliff-2-0.docx It is a requirement of the ISO fast track process that we submit the standard in the docx format. @Jamie, Chet, any advice how to go about this? Would a simple call for dissent do? We jumped all the hoops and produced the OASIS standard and then approved the letter asking OASIS Leadership to submit the standard to ISO. So this should be considered just a technicality? It should be noted that this is a verbatim copy of the authoritative HTML version of the published standard. Anyways, whatever procedure Jamie or Chet advise on this, I'd like to address this in the April 5 TC meeting. Cheers and thanks dF  Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 ---------- Forwarded message ---------- From: < workgroup_mailer@lists.oasis-open.org > Date: Wed, Mar 23, 2016 at 5:27 PM Subject: [xliff] Version Control Commit by DavidFilip To: xliff@lists.oasis-open.org Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added:    trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process. --------------------------------------------------------------------- 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 -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 

Chet, this is a bigger issue than just the TOC. The standard contains hundreds of internal cross-references that all point back to the authoritative html version from the copy-pasted docx. I don't know maybe Bettina (ISO TC37 SC5 Secretary) has ways to deal with that? There are lots of references that should stay absolute but the vast majority should be relative within the document. Mass replace of this http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html within the inside XML of the docx should do the trick for vast majority of crosslinks, just a handful would need switching back to absolute manually.. Also this is a multipart product and we need to send along also the schemas and ctalogue. Cheers and thanks dF  Cheers dF Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 On Wed, Mar 23, 2016 at 7:28 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Well, close but TOC links still didn't work. Your copy looks better too.  On Wed, Mar 23, 2016 at 2:30 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi David,  I noticed that the TOC links in the file don't work. Since the HTML was pasted into the document, the HTML links remained pointing to docs.oasis-open.org . I'm trying a couple of utilities right now to see if we can get that fixed. If they work, I'll send you the file.  I'll let Jamie handle procedural questions.  Best,  /chet On Wed, Mar 23, 2016 at 1:49 PM, David Filip < david.filip@adaptcentre.ie > wrote: Bryan, all, I uploaded onto the TC SVN a docx version of XLIFF 2.0 that Peter Reynolds produced by copy pasting the HTML (authoritative version). http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/%21Admin/SubmissionToISO/xliff-2-0.docx It is a requirement of the ISO fast track process that we submit the standard in the docx format. @Jamie, Chet, any advice how to go about this? Would a simple call for dissent do? We jumped all the hoops and produced the OASIS standard and then approved the letter asking OASIS Leadership to submit the standard to ISO. So this should be considered just a technicality? It should be noted that this is a verbatim copy of the authoritative HTML version of the published standard. Anyways, whatever procedure Jamie or Chet advise on this, I'd like to address this in the April 5 TC meeting. Cheers and thanks dF  Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 ---------- Forwarded message ---------- From: < workgroup_mailer@lists.oasis-open.org > Date: Wed, Mar 23, 2016 at 5:27 PM Subject: [xliff] Version Control Commit by DavidFilip To: xliff@lists.oasis-open.org Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added:    trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process. --------------------------------------------------------------------- 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 -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  

Hi David,   I will look into internal cross references now and send it to you in a few hours.   Thanks,   Peter.   From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of David Filip Sent: Thursday 24 March 2016 13:53 To: Chet Ensign <chet.ensign@oasis-open.org> Cc: XLIFF Main List <xliff@lists.oasis-open.org>; Schnabel, Bryan S <bryan.s.schnabel@tektronix.com>; Jamie Clark <jamie.clark@oasis-open.org> Subject: Re: [xliff] Version Control Commit by DavidFilip   Chet, this is a bigger issue than just the TOC. The standard contains hundreds of internal cross-references that all point back to the authoritative html version from the copy-pasted docx. I don't know maybe Bettina (ISO TC37 SC5 Secretary) has ways to deal with that? There are lots of references that should stay absolute but the vast majority should be relative within the document. Mass replace of this http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html within the inside XML of the docx should do the trick for vast majority of crosslinks, just a handful would need switching back to absolute manually..   Also this is a multipart product and we need to send along also the schemas and ctalogue.   Cheers and thanks dF    Cheers dF Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122     On Wed, Mar 23, 2016 at 7:28 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Well, close but TOC links still didn't work. Your copy looks better too.    On Wed, Mar 23, 2016 at 2:30 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi David,    I noticed that the TOC links in the file don't work. Since the HTML was pasted into the document, the HTML links remained pointing to docs.oasis-open.org . I'm trying a couple of utilities right now to see if we can get that fixed. If they work, I'll send you the file.    I'll let Jamie handle procedural questions.    Best,    /chet   On Wed, Mar 23, 2016 at 1:49 PM, David Filip < david.filip@adaptcentre.ie > wrote: Bryan, all,   I uploaded onto the TC SVN a docx version of XLIFF 2.0 that Peter Reynolds produced by copy pasting the HTML (authoritative version). http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/%21Admin/SubmissionToISO/xliff-2-0.docx It is a requirement of the ISO fast track process that we submit the standard in the docx format.   @Jamie, Chet, any advice how to go about this? Would a simple call for dissent do? We jumped all the hoops and produced the OASIS standard and then approved the letter asking OASIS Leadership to submit the standard to ISO. So this should be considered just a technicality? It should be noted that this is a verbatim copy of the authoritative HTML version of the published standard.   Anyways, whatever procedure Jamie or Chet advise on this, I'd like to address this in the April 5 TC meeting.   Cheers and thanks dF  Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122     ---------- Forwarded message ---------- From: < workgroup_mailer@lists.oasis-open.org > Date: Wed, Mar 23, 2016 at 5:27 PM Subject: [xliff] Version Control Commit by DavidFilip To: xliff@lists.oasis-open.org Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added:    trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process. --------------------------------------------------------------------- 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     -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393     -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393    

Hi David, hi Peter,  Have a look at the attached. I saved xliff-core-v2.0-os.html from the server, opened it locally in Word and saved it as a .docx file.  It has other problems. The formatting doesn't exactly match - it was originally Times but I changed the fonts over to Arial so that looks more like a regular OASIS spec. The line breaks in examples and schemas disappeared. So there is some clean up needed. BUT all the TOC and internal links appear to work now.  See what you think - maybe with a bit more clean up this will work?  Best,  /chet On Thu, Mar 24, 2016 at 8:52 AM, David Filip < david.filip@adaptcentre.ie > wrote: Chet, this is a bigger issue than just the TOC. The standard contains hundreds of internal cross-references that all point back to the authoritative html version from the copy-pasted docx. I don't know maybe Bettina (ISO TC37 SC5 Secretary) has ways to deal with that? There are lots of references that should stay absolute but the vast majority should be relative within the document. Mass replace of this http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html within the inside XML of the docx should do the trick for vast majority of crosslinks, just a handful would need switching back to absolute manually.. Also this is a multipart product and we need to send along also the schemas and ctalogue. Cheers and thanks dF  Cheers dF Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 On Wed, Mar 23, 2016 at 7:28 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Well, close but TOC links still didn't work. Your copy looks better too.  On Wed, Mar 23, 2016 at 2:30 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi David,  I noticed that the TOC links in the file don't work. Since the HTML was pasted into the document, the HTML links remained pointing to docs.oasis-open.org . I'm trying a couple of utilities right now to see if we can get that fixed. If they work, I'll send you the file.  I'll let Jamie handle procedural questions.  Best,  /chet On Wed, Mar 23, 2016 at 1:49 PM, David Filip < david.filip@adaptcentre.ie > wrote: Bryan, all, I uploaded onto the TC SVN a docx version of XLIFF 2.0 that Peter Reynolds produced by copy pasting the HTML (authoritative version). http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/%21Admin/SubmissionToISO/xliff-2-0.docx It is a requirement of the ISO fast track process that we submit the standard in the docx format. @Jamie, Chet, any advice how to go about this? Would a simple call for dissent do? We jumped all the hoops and produced the OASIS standard and then approved the letter asking OASIS Leadership to submit the standard to ISO. So this should be considered just a technicality? It should be noted that this is a verbatim copy of the authoritative HTML version of the published standard. Anyways, whatever procedure Jamie or Chet advise on this, I'd like to address this in the April 5 TC meeting. Cheers and thanks dF  Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 ---------- Forwarded message ---------- From: < workgroup_mailer@lists.oasis-open.org > Date: Wed, Mar 23, 2016 at 5:27 PM Subject: [xliff] Version Control Commit by DavidFilip To: xliff@lists.oasis-open.org Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added:    trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process. --------------------------------------------------------------------- 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 -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  Attachment: xliff-core-v2.0-os.docx Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document

Also, as far as packaging, take a look at the attached zip file.  I downloaded the zip file from XLIFF OS folder. I unzipped it, added the .docx file I just sent to you, and zipped it back up again.  This way, Bettina would get the schemas and catalog, the .docx file as well as the .xml, .html and .pdf files of the standard.  Jamie, there would be no problem in giving her *more* than she asked for, correct?  Best,  /chet On Thu, Mar 24, 2016 at 9:39 AM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi David, hi Peter,  Have a look at the attached. I saved xliff-core-v2.0-os.html from the server, opened it locally in Word and saved it as a .docx file.  It has other problems. The formatting doesn't exactly match - it was originally Times but I changed the fonts over to Arial so that looks more like a regular OASIS spec. The line breaks in examples and schemas disappeared. So there is some clean up needed. BUT all the TOC and internal links appear to work now.  See what you think - maybe with a bit more clean up this will work?  Best,  /chet On Thu, Mar 24, 2016 at 8:52 AM, David Filip < david.filip@adaptcentre.ie > wrote: Chet, this is a bigger issue than just the TOC. The standard contains hundreds of internal cross-references that all point back to the authoritative html version from the copy-pasted docx. I don't know maybe Bettina (ISO TC37 SC5 Secretary) has ways to deal with that? There are lots of references that should stay absolute but the vast majority should be relative within the document. Mass replace of this http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html within the inside XML of the docx should do the trick for vast majority of crosslinks, just a handful would need switching back to absolute manually.. Also this is a multipart product and we need to send along also the schemas and ctalogue. Cheers and thanks dF  Cheers dF Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 On Wed, Mar 23, 2016 at 7:28 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Well, close but TOC links still didn't work. Your copy looks better too.  On Wed, Mar 23, 2016 at 2:30 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi David,  I noticed that the TOC links in the file don't work. Since the HTML was pasted into the document, the HTML links remained pointing to docs.oasis-open.org . I'm trying a couple of utilities right now to see if we can get that fixed. If they work, I'll send you the file.  I'll let Jamie handle procedural questions.  Best,  /chet On Wed, Mar 23, 2016 at 1:49 PM, David Filip < david.filip@adaptcentre.ie > wrote: Bryan, all, I uploaded onto the TC SVN a docx version of XLIFF 2.0 that Peter Reynolds produced by copy pasting the HTML (authoritative version). http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/%21Admin/SubmissionToISO/xliff-2-0.docx It is a requirement of the ISO fast track process that we submit the standard in the docx format. @Jamie, Chet, any advice how to go about this? Would a simple call for dissent do? We jumped all the hoops and produced the OASIS standard and then approved the letter asking OASIS Leadership to submit the standard to ISO. So this should be considered just a technicality? It should be noted that this is a verbatim copy of the authoritative HTML version of the published standard. Anyways, whatever procedure Jamie or Chet advise on this, I'd like to address this in the April 5 TC meeting. Cheers and thanks dF  Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 ---------- Forwarded message ---------- From: < workgroup_mailer@lists.oasis-open.org > Date: Wed, Mar 23, 2016 at 5:27 PM Subject: [xliff] Version Control Commit by DavidFilip To: xliff@lists.oasis-open.org Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added:    trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process. --------------------------------------------------------------------- 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 -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  Attachment: xliff-core-v2.0-os.zip Description: Zip archive

Hi Chet,   I just looked at the Word doc and all the links work. I think this is good. Thank you! ISO are very good at checking a standard for formatting so I would not worry about that unless there is some reason I don’t know.   I think this should go to Bettina soon. She has to change the heading and forwards and then send it to ISO central secretariat who submit it as an Draft International Standard. Yesterday we forgot about the French translation. All ISO standards are published in English and French and I think this happens at the DIS stage. Let us wait and see if that is the case.   Thanks again to you and Jamie for your support for this and for attending yesterdays meeting.   Thanks,   Peter.     From: Chet Ensign [mailto:chet.ensign@oasis-open.org] Sent: Thursday 24 March 2016 14:45 To: David Filip <david.filip@adaptcentre.ie>; Peter Reynolds <p.reynolds@maart.com> Cc: XLIFF Main List <xliff@lists.oasis-open.org>; Schnabel, Bryan S <bryan.s.schnabel@tektronix.com>; Jamie Clark <jamie.clark@oasis-open.org> Subject: Re: [xliff] Version Control Commit by DavidFilip   Also, as far as packaging, take a look at the attached zip file.    I downloaded the zip file from XLIFF OS folder. I unzipped it, added the .docx file I just sent to you, and zipped it back up again.    This way, Bettina would get the schemas and catalog, the .docx file as well as the .xml, .html and .pdf files of the standard.    Jamie, there would be no problem in giving her *more* than she asked for, correct?    Best,    /chet     On Thu, Mar 24, 2016 at 9:39 AM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi David, hi Peter,    Have a look at the attached. I saved xliff-core-v2.0-os.html from the server, opened it locally in Word and saved it as a .docx file.    It has other problems. The formatting doesn't exactly match - it was originally Times but I changed the fonts over to Arial so that looks more like a regular OASIS spec. The line breaks in examples and schemas disappeared. So there is some clean up needed. BUT all the TOC and internal links appear to work now.    See what you think - maybe with a bit more clean up this will work?    Best,    /chet   On Thu, Mar 24, 2016 at 8:52 AM, David Filip < david.filip@adaptcentre.ie > wrote: Chet, this is a bigger issue than just the TOC. The standard contains hundreds of internal cross-references that all point back to the authoritative html version from the copy-pasted docx. I don't know maybe Bettina (ISO TC37 SC5 Secretary) has ways to deal with that? There are lots of references that should stay absolute but the vast majority should be relative within the document. Mass replace of this http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html within the inside XML of the docx should do the trick for vast majority of crosslinks, just a handful would need switching back to absolute manually..   Also this is a multipart product and we need to send along also the schemas and ctalogue.   Cheers and thanks dF    Cheers dF Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122     On Wed, Mar 23, 2016 at 7:28 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Well, close but TOC links still didn't work. Your copy looks better too.    On Wed, Mar 23, 2016 at 2:30 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi David,    I noticed that the TOC links in the file don't work. Since the HTML was pasted into the document, the HTML links remained pointing to docs.oasis-open.org . I'm trying a couple of utilities right now to see if we can get that fixed. If they work, I'll send you the file.    I'll let Jamie handle procedural questions.    Best,    /chet   On Wed, Mar 23, 2016 at 1:49 PM, David Filip < david.filip@adaptcentre.ie > wrote: Bryan, all,   I uploaded onto the TC SVN a docx version of XLIFF 2.0 that Peter Reynolds produced by copy pasting the HTML (authoritative version). http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/%21Admin/SubmissionToISO/xliff-2-0.docx It is a requirement of the ISO fast track process that we submit the standard in the docx format.   @Jamie, Chet, any advice how to go about this? Would a simple call for dissent do? We jumped all the hoops and produced the OASIS standard and then approved the letter asking OASIS Leadership to submit the standard to ISO. So this should be considered just a technicality? It should be noted that this is a verbatim copy of the authoritative HTML version of the published standard.   Anyways, whatever procedure Jamie or Chet advise on this, I'd like to address this in the April 5 TC meeting.   Cheers and thanks dF  Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122     ---------- Forwarded message ---------- From: < workgroup_mailer@lists.oasis-open.org > Date: Wed, Mar 23, 2016 at 5:27 PM Subject: [xliff] Version Control Commit by DavidFilip To: xliff@lists.oasis-open.org Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added:    trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process. --------------------------------------------------------------------- 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     -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393     -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393       -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393     -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 

    Thanks for that, David.  It seems to me that this is a production process, not a change to the approved standard -- so unless Chet objects, and once his link-fixing changes (noted in this thread) are included, I believe it should be sufficient for you to post the artifact, and then ask if the committee has any objections to your conversion being used as the ISO working document.  That gives anyone who wishes to examine it the opportunity to confirm its fidelity.      I defer to Chet on any further rule issues; it looks in order from my end.     Cordially  Jamie James Bryce Clark, General Counsel OASIS: Advancing open standards for the information society https://www.oasis-open.org/staff www.twitter.com/JamieXML http://www.slideshare.net/jamiexml Recent:  http://j.mp/EURollingPlan2016 (European ICT standards plan) Recent:  http://j.mp/IdesgReqts (US NSTIC IDESG identity requirements) Recent:  http://j.mp/UBLisoiec (UBL approved by ISO/IEC)    On Wed, Mar 23, 2016 at 10:49 AM, David Filip < david.filip@adaptcentre.ie > wrote: Bryan, all, I uploaded onto the TC SVN a docx version of XLIFF 2.0 that Peter Reynolds produced by copy pasting the HTML (authoritative version). http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/%21Admin/SubmissionToISO/xliff-2-0.docx It is a requirement of the ISO fast track process that we submit the standard in the docx format. @Jamie, Chet, any advice how to go about this? Would a simple call for dissent do? We jumped all the hoops and produced the OASIS standard and then approved the letter asking OASIS Leadership to submit the standard to ISO. So this should be considered just a technicality? It should be noted that this is a verbatim copy of the authoritative HTML version of the published standard. Anyways, whatever procedure Jamie or Chet advise on this, I'd like to address this in the April 5 TC meeting. Cheers and thanks dF  Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 ---------- Forwarded message ---------- From: < workgroup_mailer@lists.oasis-open.org > Date: Wed, Mar 23, 2016 at 5:27 PM Subject: [xliff] Version Control Commit by DavidFilip To: xliff@lists.oasis-open.org Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added:    trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process. --------------------------------------------------------------------- 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

No problems on my part. On Wed, Mar 23, 2016 at 5:40 PM, Jamie Clark < jamie.clark@oasis-open.org > wrote:     Thanks for that, David.  It seems to me that this is a production process, not a change to the approved standard -- so unless Chet objects, and once his link-fixing changes (noted in this thread) are included, I believe it should be sufficient for you to post the artifact, and then ask if the committee has any objections to your conversion being used as the ISO working document.  That gives anyone who wishes to examine it the opportunity to confirm its fidelity.      I defer to Chet on any further rule issues; it looks in order from my end.     Cordially  Jamie James Bryce Clark, General Counsel OASIS: Advancing open standards for the information society https://www.oasis-open.org/staff www.twitter.com/JamieXML http://www.slideshare.net/jamiexml Recent:  http://j.mp/EURollingPlan2016 (European ICT standards plan) Recent:  http://j.mp/IdesgReqts (US NSTIC IDESG identity requirements) Recent:  http://j.mp/UBLisoiec (UBL approved by ISO/IEC)    On Wed, Mar 23, 2016 at 10:49 AM, David Filip < david.filip@adaptcentre.ie > wrote: Bryan, all, I uploaded onto the TC SVN a docx version of XLIFF 2.0 that Peter Reynolds produced by copy pasting the HTML (authoritative version). http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/%21Admin/SubmissionToISO/xliff-2-0.docx It is a requirement of the ISO fast track process that we submit the standard in the docx format. @Jamie, Chet, any advice how to go about this? Would a simple call for dissent do? We jumped all the hoops and produced the OASIS standard and then approved the letter asking OASIS Leadership to submit the standard to ISO. So this should be considered just a technicality? It should be noted that this is a verbatim copy of the authoritative HTML version of the published standard. Anyways, whatever procedure Jamie or Chet advise on this, I'd like to address this in the April 5 TC meeting. Cheers and thanks dF  Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 ---------- Forwarded message ---------- From: < workgroup_mailer@lists.oasis-open.org > Date: Wed, Mar 23, 2016 at 5:27 PM Subject: [xliff] Version Control Commit by DavidFilip To: xliff@lists.oasis-open.org Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added:    trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process. --------------------------------------------------------------------- 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 -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393 

Thanks, Jamie, so once we have resolved the crossreferencing issues this should be a simple matter of calling for dissent in the TC teleconference after the members had some time to examine the word document. Cheers and thanks dF Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 On Wed, Mar 23, 2016 at 9:40 PM, Jamie Clark < jamie.clark@oasis-open.org > wrote:     Thanks for that, David.  It seems to me that this is a production process, not a change to the approved standard -- so unless Chet objects, and once his link-fixing changes (noted in this thread) are included, I believe it should be sufficient for you to post the artifact, and then ask if the committee has any objections to your conversion being used as the ISO working document.  That gives anyone who wishes to examine it the opportunity to confirm its fidelity.      I defer to Chet on any further rule issues; it looks in order from my end.     Cordially  Jamie James Bryce Clark, General Counsel OASIS: Advancing open standards for the information society https://www.oasis-open.org/staff www.twitter.com/JamieXML http://www.slideshare.net/jamiexml Recent:  http://j.mp/EURollingPlan2016 (European ICT standards plan) Recent:  http://j.mp/IdesgReqts (US NSTIC IDESG identity requirements) Recent:  http://j.mp/UBLisoiec (UBL approved by ISO/IEC)    On Wed, Mar 23, 2016 at 10:49 AM, David Filip < david.filip@adaptcentre.ie > wrote: Bryan, all, I uploaded onto the TC SVN a docx version of XLIFF 2.0 that Peter Reynolds produced by copy pasting the HTML (authoritative version). http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/%21Admin/SubmissionToISO/xliff-2-0.docx It is a requirement of the ISO fast track process that we submit the standard in the docx format. @Jamie, Chet, any advice how to go about this? Would a simple call for dissent do? We jumped all the hoops and produced the OASIS standard and then approved the letter asking OASIS Leadership to submit the standard to ISO. So this should be considered just a technicality? It should be noted that this is a verbatim copy of the authoritative HTML version of the published standard. Anyways, whatever procedure Jamie or Chet advise on this, I'd like to address this in the April 5 TC meeting. Cheers and thanks dF  Dr. David Filip =========== OASIS XLIFF OMOS TC Chair OASIS XLIFF TC Secretary, Editor, Liaison Officer Spokes Research Fellow ADAPT Centre KDEG, Trinity College Dublin Mobile: +420-777-218-122 ---------- Forwarded message ---------- From: < workgroup_mailer@lists.oasis-open.org > Date: Wed, Mar 23, 2016 at 5:27 PM Subject: [xliff] Version Control Commit by DavidFilip To: xliff@lists.oasis-open.org Author: DavidFilip Date: 2016-03-23 17:27:34 +0000 (Wed, 23 Mar 2016) New Revision: 610 Web View: https://tools.oasis-open.org/version-control/browse/wsvn/xliff/?rev=610&sc=1 Added:    trunk/xliff-20/!Admin/SubmissionToISO/xliff-2-0.docx Log: Added a docx version of XLIFF 2.0 that is needed for the ISO fast track process. --------------------------------------------------------------------- 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