Hello,
using just the SWIFT/BIC code you should be able to express ABA as well
as they have been included in BIC.
Anyway the USA case could be not the only one... do we require a
separate RoutingNumber (e.g. ABA in US) ???
IBAN and BIC are sufficient for Europe... but we should be sure to
include other countries as well.
Any opinion ?
---
Tim McGrath ha scritto:
4BC03CBB.7020106@documentengineeringservices.com"
type="cite">i agree with Oriol. as design policy (and practice) we
dont want unbounded BBIEs (except for language version of text BBIEs)
Oriol Bausà Peris wrote:
Hi Ken,
Reading your mail, it reminds me to the identification of parties,
having a cac:PartyIdentification/cbc:ID, where the PartyIdentification
ABIE is unbounded. Shouldn't we try to use the same approaches?
Best regards, Oriol
El 08/04/2010, a las 20:37, G. Ken Holman escribió:
Hello PSC members!
I'm creating a UBL invoice for my company from my paper copy and I note
that my financial institution has two global identifiers: a Swift ID
and an ABA ID.
The cardinality of cbc:ID for cac:FinancialInstitution is 0..1, so I
arbitrarily picked the Swift one:
<cac:FinancialInstitution>
<cbc:ID
schemeAgencyName="Swift">AAAAAAAAA</cbc:ID>
</cac:FinancialInstitution>
... but that means I am not conveying the ABA identifier and I must
have needed it at one point to add it to the paper invoice. Not being
a banker, I'm guessing the Swift identifier will be more useful than
the ABA identifier.
All 88 cbc:ID elements in UBL 2.1 have a maxOccurs of 1.
Does it make sense to make maxOccurs="unbounded" for some identifiers
such as the financial institution?
I know it does not make sense for items being identified within the
document, such as line items ... those should only have a single
identifier. But we might consider this for items external to the
document.
Recently I argued that since <cbc:ID> is based on CCTS
IdentifierType and that that type implies uniqueness. Thankfully the
uniqueness indicated is only within a particular identification scheme:
A character string to identify and distinguish uniquely, one
instance of an object in an identification scheme from all
other objects in the same scheme together with relevant
supplementary information.
Thus, even with that definition, the following would not be out of line
because of the different identification schemes:
<cac:FinancialInstitution>
<cbc:ID
schemeAgencyName="Swift">AAAAAAAAA</cbc:ID>
<cbc:ID schemeAgencyName="ABA">BBBBBBBB</cbc:ID>
</cac:FinancialInstitution>
This implies a new unwritten UBL rule of each use of more than one
cbc:ID should (must?) be distinguished by supplementary scheme
metadata.
I don't know off hand if there are other uses of cbc:ID that would
qualify.
Does this make sense, or have I missed something?
Thanks!
. . . . . . . . . . . . Ken
--
XSLT/XQuery training: San Carlos, California 2010-04-26/30
Principles of XSLT for XQuery Writers: San Francisco,CA 2010-05-03
XSLT/XQuery training: Ottawa, Canada 2010-05-10/14
XSLT/XQuery/UBL/Code List training: Trondheim,Norway 2010-06-02/11
Vote for your XML training: http://www.CraneSoftwrights.com/o/i/
Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/
G. Ken Holman mailto:gkholman@CraneSoftwrights.com
Male Cancer Awareness Nov'07 http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers: http://www.CraneSoftwrights.com/legal
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
Nessun virus nel messaggio in arrivo.
Controllato da AVG - www.avg.com
Versione: 8.5.437 / Database dei virus: 271.1.1/2800 - Data di rilascio: 04/09/10 06:32:00
--
JAVEST by Roberto Cisternino
* Document Engineering Services Ltd. - Alliance Member
* UBL Italian Localization SubCommittee (ITLSC), co-Chair
* UBL Online Community editorial board member (ubl.xml.org)
* Italian UBL Advisor
Roberto Cisternino
PPlease consider the environment before
printing this email.
|