Minor changes to release notes and alignment documents

OpenPEPPOL · Oct 10, 2018 · cfddedd · cfddedd
1 parent 41c452c
commit cfddedd
Show file tree

Hide file tree

Showing 5 changed files with 19 additions and 29 deletions.
diff --git a/guides/changes/main.adoc b/guides/changes/main.adoc
@@ -9,18 +9,18 @@
 :sectanchors:
 :sectnums:
 
-The following list give a general overview of the changes made to the BIS2 specifications as part of the alignment with the EN 16931 invoice. This list does not address the additional RFC that were approved and adopted.
+The following list give a general overview of the changes made to the specifications as part of the alignment with the EN 16931 invoice. This list does not address the additional RFC that were approved and adopted.
 
 = Business terms
 
 * Qualified reference elements added to Order.
 * Removed type and date from contract references
-* All addresses changed to include 3 lines insted of two.
+* All addresses changed to include 3 lines instead of two.
 * Added address information for tax representatives, where appropriate.
 * Use of business terms aligned across BIS specifications.
 * Use of label elements aligned between Order agreement and Punch Out.
 * Contact information aligned across BIS.
-* Allownce and charge classes aligned in terms of use of percentage, reason code and VAT.
+* Allowance and charge classes aligned in terms of use of percentage, reason code and VAT.
 
 = VAT
 
@@ -31,9 +31,8 @@ The following list give a general overview of the changes made to the BIS2 speci
 = Code and identifiers
 
 * Customization and profile identifiers made mandatory in all BIS.
-* Endpoint identifiers restricted to CEF code lists (ICD).
 * Party and item identifiers restricted to ICD code list.
-* Allowance and charge code lists aligned with EN by using 5189 and 7161.
+* Aligning use of code lists, examples are the allowance/charge lists and VAT category codes.
 * Assigning fixed code lists and removing requirements for code attributes.
 * Action code lists aligned between BIS's.
 
@@ -50,14 +49,13 @@ The following list give a general overview of the changes made to the BIS2 speci
 = UBL syntax bindings
 
 * Alignment of syntax bindings.
-* Party name remapped to party legal name in UBL and made mandatory.
+* Party name remapped to party legal name.
 * "Your reference" remapped to Customer reference from Buyer/Contact/Id
 
 = Documentation
 
-* All documentation moved to Ascii Doc or XML form and maintained as code in GitHub.
+* All documentation moved to AsciiDoc or XML form and maintained as code in GitHub.
 * BIS specifications moved from Word to browsable website.
 * Data model and syntax bindings moved from BIS document to browsable data model.
 * Code lists for all BIS maintained jointly and hyperlinked where used.
 * Traceability of changes improved by linking between Jira issues and GitHub updates.
-
diff --git a/guides/releasenotes/alignoverview.adoc b/guides/releasenotes/alignoverview.adoc
@@ -1,16 +1,13 @@
 = Overview of alignments
 
-The alignment of the BIS specification to the EN has been done with referenct to the EN 16931 electronc invoice in line with the adoption of that standard into BIS5A Billing. The work is based on the following documents and decisions:
+The alignment of the BIS specification to the EN has been done with reference to the EN 16931 electronic invoice in line with the adoption of that standard into PEPPOL BIS Billing 3.0. The work is based on the following documents and decisions:
 
 * https://openpeppol.atlassian.net/wiki/download/attachments/180125738/Gap%20analysis.xlsx?api=v2[Peppol invoice to EN 16931 gap analysis] that formed basis for the BIS5A Billing.
-* https://openpeppol.atlassian.net/wiki/download/attachments/180125738/BIS3%20Scope%20and%20disposition.docx?api=v2[BIS3 Scope and disposition] addressing how gaps identified for the invoice should be adopted into other specifications. 
+* https://openpeppol.atlassian.net/wiki/download/attachments/180125738/BIS3%20Scope%20and%20disposition.docx?api=v2[BIS3 Scope and disposition] addressing how gaps identified for the invoice should be adopted into other specifications.
 * Agreements made by the BIS3 work team members and documented in the team minutes.
 
-An important part of the alignment work was to adopt the documentation of the BIS5A Billing to other specifications by using a browsable format instead of Word documents and spreadsheets.
+An important part of the alignment work was to adopt the documentation of the PEPPOL BIS Billing 3.0 to other specifications by using a browsable format instead of Word documents and spreadsheets.
 
 Minutes and further details can be found in the https://openpeppol.atlassian.net/wiki/spaces/PB3UWG/overview[project space in Confluence] .
 
 Further details of the the changes made can be found in http://test-docs.peppol.eu/poacc/upgrade-3/changes/[Overview of Alignments].
-
-
-
diff --git a/guides/releasenotes/explaindocument.adoc b/guides/releasenotes/explaindocument.adoc
@@ -2,7 +2,7 @@
 
 For each Business Interoperability Specification (BIS) there are the following parts:
 
-== Business Ineroperability Specifications.
+== Business Interoperability Specifications.
 
 === BIS document
 The specification of a business process. The document describes the business process that it supports and provides details on how individual elements that are exchanged in transactions are to be used and understood. It provides business examples and syntax examples where needed. Defines rules that govern the data as well as code list that must be used.
@@ -38,21 +38,15 @@ There are business rules that can not be automatically generated from the data m
 Each business rule has an identifier that include the transaction id and a sequential number starting with a R. As example "PEPPOL-T01-R001"
 
 === Downloads
-These contain two type. 
+These contain two type.
 
-* Schematron files that can be used for validating a transactions. 
-* Example files that can be used in tests and as reference in implementations.
+* Schematron files that can be used for validating a transactions.
+** Schematron files for all transactions are provided in a single zip file.
 
-Schematron files for all transactions are provided in a single zip file. Example files for all transaction are also provided in a single zip file.
+* Example files that can be used in tests and as reference in implementations.
+** Example files for all transaction are also provided in a single zip file.
 
 == Codes
 The documentation includes a listing of all code lists used in one or more transactions. The code lists are fully populated with information on where they are used, what their code values are and their definitions.
 
 NOTE: When a BIS specification defines how a code is used that definition overrules the general definition in the code list.
-
-
-
-
-
-
-
diff --git a/guides/releasenotes/main.adoc b/guides/releasenotes/main.adoc
@@ -8,7 +8,7 @@
 :sectanchors:
 :sectnums:
 
-This is a release candidate for a new, non-backwards compatible, major upgrade of all OpenPEPPOL BIS specifications, other than the BIS3 Billing. It is **open for review comments until October 26**. 
+This is a release candidate for a new, non-backwards compatible, major upgrade of all OpenPEPPOL BIS specifications, other than the BIS3 Billing. It is **open for review comments until October 26**, see <<review>> for further details.
 
 The OpenPEPPOL BIS3 Upgrade project was started in January 2018. Project was mandated to to upgrade the PEPPOL BIS specifications so that they are aligned with the PEPPOL BIS Billing 3.0 specification that is based on the CEN/EN 16931 eInvoicing standard.
 

diff --git a/guides/releasenotes/reviewtimeline.adoc b/guides/releasenotes/reviewtimeline.adoc
@@ -1,3 +1,4 @@
+[[review]]
 = Review instructions
 
 The deadline for submitting comments to the review is end of Friday October 26.
@@ -10,7 +11,7 @@ Following types of comments are accepted.
 ** syntax
 ** rules
 ** spelling and edits
-* Comments on the accepted RFC's
+* Comments on the accepted Requests for change (RFC)
 * General comments on the BIS3 upgrade projec including migration plan.
 
-This review does not open up for new RFC's that modify current business requirements or add new ones. Such RFC's will be addressed later as part of the first version upgrade of the BIS3, version 1.1 that can be expected in first half of 2019.
+This review does not open up for new RFC's that modify current business requirements or add new ones. Such RFC's will be addressed later as part of the first version upgrade of the BIS3, version 1.1 that can be expected in first half of 2019.