The OASIS Customer Information Quality (CIQ) standard for global-customer information
- management contains the definition of the
The objective of xNAL is to describe a common structure for Personal/Organization Names and - Addresses that would enable any applications that want to represent customer names - and addresses in a common standard format. The applications could be CRM/e-CRM, - Customer Information Systems, Data Quality (Parsing, Matching, Validation, - Verification, etc.), Customer Data Warehouses, Postal services, etc.
-However, any party for its own purposes and applications can use xNAL grammar or parts of - it.
-The DITA xNAL specialization is based on the OASIS extensible Name and Address Language - metadata elements. Due to differences between the two processing architectures, the DITA - xNAL domain does not incorporate all of the definitions from the OASIS xNAL standard - directly. Instead, there is a transformational equivalence between the DITA and OASIS - xNAL definitions for names and addresses. This equivalence enables XML-aware tools in - workflow systems to capture and manipulate names and addresses in a standard manner.
-The xNAL domain is available for use in the
DITA bookmaps use a set of
- elements associated with a subset of the
-
While the elements share element names, and the
- expectation is that content written using this type of metadata
The examples shown after the - table provide sample tagging methods for name and address information, using - the DITA elements associated with xNAL.
-The set of bookmap elements
- associated with elements from the
-
This example shows a way to - tag the following personal name and description.
-This example shows a way to - tag the following address.
-This example shows two ways to - tag a fairly complex collection of personal, organizational, and address - information.
-This method tags all the - organizational information as associated with the identified person.
-The following method separates - the person and organization information. It might be used if it were necessary - to associate address information with organizations rather than persons.
-The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The
The following code sample shows how the
The XNAL information is all metadata, so it generally does not - need to be translated. Exceptions might be needed when selections - from this metadata are used for display purposes. The standard - behavior might need to change based on local business rules. For - example, in some cases it might be appropriate to translate the - honorific, country, or organizationname elements. There are no - translatable attributes
-