2004/05/04
Form required
http://docs.oasis-open.org/ubl/cd-UBL-1.0/ - Universal Business Language OASIS
http://www.oasis-open.org/committees/ciq/ciq.shtml - XML STANDARDS FOR "GLOBAL" CUSTOMER
INFORMATION MANAGEMENT
"If an address database contains errors - for example the same address is entered in
two different varieties the retrieval of information becomes extremely complex and
unreliable.
The fact that elements of a customer name are not unique can lead to unexpected
duplication of information. Storing the same information in different ways makes
de-duplication more difficult. Database search and query functions may give ambiguous
or confusing information, or not locate all matching records. Online searches can
result inlong drop down lists of choices on the screen and a degradation in the
performance rate during retrieval.
Managing customer information has a number of problems that can be improved through
the application of open standards to this type of data. There are, however, a number
of name and address standards available throughout the world. To a large extent,
these standards have been designed with a particular business requirement in mind,
for example, the expedient delivery of a piece of mail. This has generally meant that
while the particular standard is appropriate for the purpose for which it was designed,
it is frequently not suitable for a variety of other purposes.
The challenge for xNAL is to provide the ability to handle the following:
- About 36+ customer name formats
- Addresses of 241+ Countries
- About 130+ Address Formats
- Represented in 5,000+ languages (dialects)
- Should be application independent, ie., capable of being used for a variety of
applications ranging from simple user profiling to name and address parsing, matching,
validation and postal services
- Should be Platform independent
- Should be open, and
- Should be vendor neutral.
"
INFORMATION MANAGEMENT
"If an address database contains errors - for example the same address is entered in
two different varieties the retrieval of information becomes extremely complex and
unreliable.
The fact that elements of a customer name are not unique can lead to unexpected
duplication of information. Storing the same information in different ways makes
de-duplication more difficult. Database search and query functions may give ambiguous
or confusing information, or not locate all matching records. Online searches can
result inlong drop down lists of choices on the screen and a degradation in the
performance rate during retrieval.
Managing customer information has a number of problems that can be improved through
the application of open standards to this type of data. There are, however, a number
of name and address standards available throughout the world. To a large extent,
these standards have been designed with a particular business requirement in mind,
for example, the expedient delivery of a piece of mail. This has generally meant that
while the particular standard is appropriate for the purpose for which it was designed,
it is frequently not suitable for a variety of other purposes.
The challenge for xNAL is to provide the ability to handle the following:
- About 36+ customer name formats
- Addresses of 241+ Countries
- About 130+ Address Formats
- Represented in 5,000+ languages (dialects)
- Should be application independent, ie., capable of being used for a variety of
applications ranging from simple user profiling to name and address parsing, matching,
validation and postal services
- Should be Platform independent
- Should be open, and
- Should be vendor neutral.
"
http://citeseer.ist.psu.edu/padget98picalculus.html - pi-calculus model of a Spanish fish market Preliminary Report (1998)
http://www.med.govt.nz/irdev/el_com.html - Electronic Commerce New Zealand
Web Service Choreography Interface (WSCI) 1.0 - WSCI is dead according to the mailing list at W3.org: "WSCI is dead. It is not used commercially but it was an input and a
valid input to the W3C Web Services WG."
valid input to the W3C Web Services WG."
Qatar
