Version .81  -  12 May 2001

CHANGES IN AGGREGATE ELEMENTS (OBJECTS)

- the "docRef" class now has an additional, optional element "docUri" 
optionally, link to the whole document on filesystem or network. Needed 
a pressure relief valve to maintain information without having to 
accomodate an unconstrained variety of document formats.

- within the "code" class "codeListUri" is now an address which returns 
the record format, interface methods, access rules, etc. in human 
readable format.

- within the "code" class is added a new element, "getRecordUri" --the 
address which returns the whole record associated with a code, from the 
codeList agency, repository, network, application, filesystem, etc.

CHANGES IN TRANSACTIONSET

- within transactionSet "controlTotal" now allows unbounded number of 
account control totals.  This is a correction of an oversight.  It would 
have been relatively useless to allow only one control total, of one 
account. ("controlTotal" is intended to support broad subtotals such as 
assets, liabilities etc. or if no account is present, simply the total 
debits in the transactionSet.)

- within transactionSet "Ledger" element is changed to lowercase.

- within transaction "transactionJournalType" is changed from a string
to a code.  The diverse BSPs will create diverse transaction types.

CHANGES IN TRANSACTION

- within transaction "isSummary" added.  a boolean, indicates this 
transaction is an aggregate or sum of other ledger transactions. 
"isSummary" is dropped from the entry level.

- within transaction "postedStatus" is changed to "isPosted" to 
conform with naming standards for a boolean.  This element is vital
to the unposted transaction batch within untrusted choreographies.


CHANGES IN ENTRY

- entryId is now optional.  transactionId has been optional since v. 70. 
Not every A2A and B2B doc. has entry Ids at the row level, any more than 
they did at the transaction level.  Some systems are anchored around 
document numbers.  ArapXML is intended to be a universal schema.  When
users wish to disambiguate the schema further they can do so by editing
it, or by applying the ledgerDefinitionXML accompanying  arapXML to
specify their usage of the schema.

- within entry "entryJournalType" is changed from a string to a code. 
The diverse BSPs will create diverse transaction types.

- within entry "settlementMethod" is now a code.  A settlement method 
that is a xsd:uriReference is unusable by most applications and users.


NEW ELEMENTS IN ENTRY

- entry now has "tax" element, unbounded.  One or more sales or VAT tax 
codes is nearly universal in 3rd party transactions.  It may be a 
function of other things in the schema such as party location or 
implicitly known by company location, but quite often the code is burned 
into the row at creation, and/or subject to later correction.

- "location" element.  Location where the transaction was executed.
- "project" --another code.
- "job" --another code.
- "costCenter" --another code.
- "employee" --another code.
- "fund" --another code.