OASIS XML Localisation Interchange File Format (XLIFF) TC

Per the TC's submission request [1], please find the attached starter documents for:  XLIFF Version 2.1 WP-abbrev: xliff-core The attached ZIP file contains examples for csd01 and csprd01 (Public Review) in HTML, PDF, and a source word processor format (Microsoft Word .doc) PLEASE NOTE - DocBook template updates expected in conformance with 2014 OASIS templates: - use of sentence case in section headings for "Related work" and "Declared XML namespaces" (as opposed to earlier "Related Work" and "Declared XML Namespaces") - use of https: (instead of http:) for all OASIS URIs except the OASIS Library ( http://docs.oasis-open.org/.. .) Note particularly three instances in EACH of the "Status" and "Notices" sections, as well as the single occurrence in the "Technical Committee" section. - inclusion of the names of Editors in the "Citation format", and the preferred use of "v2.1" instead of "2.1" in the citation label. When the TC first votes [5] to publish this Work Product in the OASIS Library, we expect it to be published at: http://docs.oasis-open.org/xliff/xliff-core/v2.1/csd01/xliff-core-v2.1-csd01.html The permanent "Latest version" URI will be: http://docs.oasis-open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.html . Please let me know if anything here fails to meet your expectations. (Some of the guidance below may not apply to the use of DocBook.) Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the OASIS TC Administration How-to Guide [2]. Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Subversion (SVN) repository, if SVN has been activated for your TC [3].  TCs are encouraged to use ZIP packaging when the WD releases contain multiple files (and directories). For each WD revision, you will need to: 1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in the document identifier within the page footer. 2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the  prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier, Working Draft ##) and in the page footer. 3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc. 4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision. 5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed URIs/namespaces [4]. When the TC votes [5] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests Page [6].   Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library ( http://docs.oasis-open.org/ ) as a Committee Draft, including addition of the requisite cover page metadata and other boilerplate information. =========== References: [1] https://tools.oasis-open.org/issues/browse/TCADMIN-1762 [2] Developing Committee Specifications and Notes     https://www.oasis-open.org/resources/tcadmin/developing-committee-specifications-and-notes     Starting a Working Draft     https://www.oasis-open.org/resources/tcadmin/starting-a-working-draft [3] SVN Version control, via Tools     https://tools.oasis-open.org/ [4] OASIS Naming Directives     http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html [5] Approval of a WD as a CD (CSD or CND)     https://www.oasis-open.org/resources/tcadmin/approving-a-committee-specification-or-note-draft     https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft [6] TC Administration Requests Page, see Committee Specification Draft Creation / Upload Request     https://www.oasis-open.org/resources/tc-admin-requests Best wishes, Paul -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst Attachment: xliff-core-v2.1-templates.zip Description: Zip archive

Thanks, Paul, looks good. I may be in touch when I get to cloning our DocBook template to conform with your model. That will be probably later in June. Best regards and thanks again for a quick response dF Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Tue, May 27, 2014 at 4:21 PM, Paul Knight < paul.knight@oasis-open.org > wrote: Per the TC's submission request [1], please find the attached starter documents for:  XLIFF Version 2.1 WP-abbrev: xliff-core The attached ZIP file contains examples for csd01 and csprd01 (Public Review) in HTML, PDF, and a source word processor format (Microsoft Word .doc) PLEASE NOTE - DocBook template updates expected in conformance with 2014 OASIS templates: - use of sentence case in section headings for "Related work" and "Declared XML namespaces" (as opposed to earlier "Related Work" and "Declared XML Namespaces") - use of https: (instead of http:) for all OASIS URIs except the OASIS Library ( http://docs.oasis-open.org/.. .) Note particularly three instances in EACH of the "Status" and "Notices" sections, as well as the single occurrence in the "Technical Committee" section. - inclusion of the names of Editors in the "Citation format", and the preferred use of "v2.1" instead of "2.1" in the citation label. When the TC first votes [5] to publish this Work Product in the OASIS Library, we expect it to be published at: http://docs.oasis-open.org/xliff/xliff-core/v2.1/csd01/xliff-core-v2.1-csd01.html The permanent "Latest version" URI will be: http://docs.oasis-open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.html . Please let me know if anything here fails to meet your expectations. (Some of the guidance below may not apply to the use of DocBook.) Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the OASIS TC Administration How-to Guide [2]. Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Subversion (SVN) repository, if SVN has been activated for your TC [3].  TCs are encouraged to use ZIP packaging when the WD releases contain multiple files (and directories). For each WD revision, you will need to: 1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in the document identifier within the page footer. 2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the  prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier, Working Draft ##) and in the page footer. 3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc. 4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision. 5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed URIs/namespaces [4]. When the TC votes [5] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests Page [6].   Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library ( http://docs.oasis-open.org/ ) as a Committee Draft, including addition of the requisite cover page metadata and other boilerplate information. =========== References: [1] https://tools.oasis-open.org/issues/browse/TCADMIN-1762 [2] Developing Committee Specifications and Notes     https://www.oasis-open.org/resources/tcadmin/developing-committee-specifications-and-notes     Starting a Working Draft     https://www.oasis-open.org/resources/tcadmin/starting-a-working-draft [3] SVN Version control, via Tools     https://tools.oasis-open.org/ [4] OASIS Naming Directives     http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html [5] Approval of a WD as a CD (CSD or CND)     https://www.oasis-open.org/resources/tcadmin/approving-a-committee-specification-or-note-draft     https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft [6] TC Administration Requests Page, see Committee Specification Draft Creation / Upload Request     https://www.oasis-open.org/resources/tc-admin-requests Best wishes, Paul -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst --------------------------------------------------------------------- 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