PRD3 corrections

[Jon Bosak <bosak@pinax.com>]

Hello UBL TC,

A couple of PRD3 corrections:

1. Not all of the row number references in one paragraph of C.4 have been
   updated correctly.  The current version reads as follows:

   <para>Next in order in the Invoice come two required pieces, the
   ASBIEs <literal>AccountingSupplierParty</literal> and
   <literal>AccountingCustomerParty</literal>. As shown in Column M of
   the Invoice spreadsheet, <literal>AccountingSupplierParty</literal>
   (line 36) derives from the <literal>SupplierParty</literal> ABIE and
   <literal>AccountingCustomerParty</literal> (line 37) derives from the
   <literal>CustomerParty</literal> ABIE. Checking in the Common
   Library, it is seen that both <literal>SupplierParty</literal> (line
   1899 of the Common Library spreadsheet) and
   <literal>CustomerParty</literal> (line 552 of the Common Library
   spreadsheet) can contain an ASBIE named <literal>Party</literal> (as
   shown in lines 1891 and 546, respectively) and that each
   <literal>Party</literal> ASBIE is an instantiation of the
   <literal>Party</literal> ABIE (line 1312). Therefore both parties
   have the same structure (lines 1247 through 1265). Thus
   <literal>AccountingSupplierParty</literal> and
   <literal>AccountingCustomerParty</literal> share the information
   components common to parties in general and differ in the information
   specific to suppliers and customers. Parties commonly have a
   <literal>PartyName</literal> (line 1320) that derives (Column M) from
   the ABIE <literal>PartyName</literal> (line 1349), which is a wrapper
   for the BBIE <literal>Name</literal> (line 1350). A conforming piece
   of the document instance might therefore look like this:</para>

   Here it is with corrections:

   <para>Next in order in the Invoice come two required pieces, the
   ASBIEs <literal>AccountingSupplierParty</literal> and
   <literal>AccountingCustomerParty</literal>. As shown in Column M of
   the Invoice spreadsheet, <literal>AccountingSupplierParty</literal>
   (line 36) derives from the <literal>SupplierParty</literal> ABIE and
   <literal>AccountingCustomerParty</literal> (line 37) derives from the
   <literal>CustomerParty</literal> ABIE. Checking in the Common
   Library, it is seen that both <literal>SupplierParty</literal> (line
   1899 of the Common Library spreadsheet) and
   <literal>CustomerParty</literal> (line 552 of the Common Library
   spreadsheet) can contain an ASBIE named <literal>Party</literal> (as
   shown in lines 1903 and 556, respectively) and that each
   <literal>Party</literal> ASBIE is an instantiation of the
   <literal>Party</literal> ABIE (line 1312). Therefore both parties
   have the same structure (lines 1313 through 1331). Thus
   <literal>AccountingSupplierParty</literal> and
   <literal>AccountingCustomerParty</literal> share the information
   components common to parties in general and differ in the information
   specific to suppliers and customers. Parties commonly have a
   <literal>PartyName</literal> (line 1320) that derives (Column M) from
   the ABIE <literal>PartyName</literal> (line 1349), which is a wrapper
   for the BBIE <literal>Name</literal> (line 1350). A conforming piece
   of the document instance might therefore look like this:</para>

2. Column R of the common library spreadsheet looks very doubtful in the
   neighborhood of lines 1132 and 1133.

Jon