This technical overview document provides a quick practical introduction into high level technical details of CIQ Technical Committee (TC) specification family version 3.0.

Status:

This document was last revised or approved by the OASIS CIQ TC on the above date. The level of approval is also listed above. Check the current location noted above for possible later revisions of this document. This document is updated periodically on no particular schedule.

Technical Committee members should send comments on this specification to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at www.oasis-open.org/committees/ciq.

For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page (www.oasis-open.org/committees/ciq/ipr.php.

The non-normative errata page for this specification is located at www.oasis-open.org/committees/ciq.

Notices

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification.

OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so.

OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.

The names "OASIS", “CIQ”, “xNL”, “xAL”, xNAL”, “xPIL”, “xPRL”, “xCIL”, “xCRL” , “Genericode”, and “UBL” are trademarks of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/who/trademark.php for above guidance.

Table of Contents

1 Introduction.. 5

2 CIQ TC Family Version 3.0. 6

2.1 The Need for a New Version.. 6

2.2 What is in scope in this version.. 6

2.3 What is out of scope in this version.. 6

3 CIQ TC Specifications Version 3.0. 7

3.1 Extensible Name Language (xNL) 7

3.1.1 Example – Simple Person Name Representation. 7

3.1.2 Example – Complex Person Name Representation. 8

3.2 Extensible Address Language (xAL) 8

3.2.1 Example – Simple Address Representation. 9

3.2.2 Example – Semi Complex Address Representation. 10

3.2.3 Example – Complex Address Representation. 10

3.3 Extensible Name and Address Language (xNAL) Version 3.0. 10

3.3.1 Example Simple Name and Address Representation. 11

3.3.2 Example – Complex Name and Address Representation. 12

3.4 Extensible Party Information Language (xPIL) 13

3.5 Extensible Party Relationships Language (xPRL) 14

4 Implementing CIQ TC specifications – Practical Guidelines.. 15

4.1 Where to Start.. 15

4.2 Don’t get confused – keep it simple. 15

4.3 Data Exchange. 15

4.4 Output Formatting.. 16

4.5 Customising Schema.. 16

4.5.1 Schema Extensions. 16

4.5.2 Restricting Schema. 16

4.6 Data Mapping Challenges. 17

4.6.1 Application Diversity. 17

4.6.2 Cultural Diversity. 17

4.6.3 CIQ TC Solution. 17

A. Acknowledgements.. 19

B. Intellectual Property Rights, Patents, Licenses and Royalties.. 20

C. Revision History.. 21

1 Introduction

This document is a brief technical overview of version 3.0 of OASIS CIQ TC specifications family namely:

· xNL : extensible Name Language

· xAL: extensible Address Language

· xNAL: extensible Name and Address Language (combines xNL and xAL)

· xPIL: extensible Party Information Language (formerly known as extensible Customer Information language (xCIL)

· xPRL: extensible Party Relationships Language (formerly known as extensible Customer Relationships Language (xPRL) – Release data for this specification not set yet

The purpose of this document also is to give software developers and solution architects a quick snapshot of CIQ TC specifications and help decide if the specifications are suitable for a particular application.

2 CIQ TC Family Version 3.0

2.1 The Need for a New Version

The CIQ TC’s XML Name and Address languages define universal structures for name and address entities.

It is a trivial exercise to define name and address structures for a particular locale, but on the international scale it is much harder due to cultural and lingual differences. Previous versions of xNAL defined the name and address structures to a great level of detail providing very hierarchical XML structures to express names and addresses in a consistent way.

However, the previous versions were:

· ambiguous by providing multiple options for representing the same information

· offering a complex model for simple representation of name and address data

· difficult to implement as an object model

· perceived as being complex for many applications that required minimal representation

· semantically incorrect for many country name and address data that are bound by its culture and geographical boundaries

In many cases the xNAL family of specifications were used as a basis for a localised standards that were much simpler, but not truly interoperable on a global scale. The derived standards were mainly about scaling it down to a simpler and lighter version that would meet the local requirements.

CIQ TC recognised the need for simplifying the specifications while keeping them locale-independent and interoperable on a global scale, and importantly, ensuring that the capabilities of the earlier versions are not compromised.

2.2 What is in scope in this version

· Ensure all the overall expressive power of version 2.0 is not lost

· The specification will include W3C XML schemas

· All examples defined using version 2.0 will be represented in version 3.0

· High level UML models of the schemas

2.3 What is out of scope in this version

· DTDs

· Privacy and security issues connected to exchanging and storing personal information

· Data exchange methods and procedures for party information

· Messaging protocol for exchange of party information

· Validation/verification of party information

· Formatting, labeling, or sorting of party information

· API specifications

· Backward compatibility with previous versions

3 CIQ TC Specifications Version 3.0

This section provides a brief overview of the CIQ TC specifications (Version 3.0).

3.1 Extensible Name Language (xNL)

xNL defines an XML structure to represent party name data. An example of a Party is “customer”. A party could be a “Person” or an “Organisation”. An “Organisation” could be educational institutions namely, school, university or college, clubs, associations, industry groups, not-for-profit bodies, consortiums, etc.

xNL was designed to handle international name data that is culturally and geographically specific. For example, the concept of given names and family names do not exist in some cultures, e.g. in some regions of India.

xNL can represent names in over 36 formats and it is extendable. The diagram below illustrates a high level UML model of xNL.

3.1.1 Example – Simple Person Name Representation

Dr Jeremy Apatuta Johnson III PhD

<n:PartyName>

<n:PersonName>

<n:NameLine>Dr Jeremy Apatuta Johnson III PhD</n:NameLine>

</n:PersonName>

</n:PartyName>

3.1.2 Example – Complex Person Name Representation

Dr Jeremy Apatuta Johnson III Phd

<n:PartyName>

<n:PersonName>

<n:NameElement Abbreviation="true" ElementType="Title">Dr</n:NameElement>

<n:NameElement ElementType="FirstName">Jeremy</n:NameElement>

<n:NameElement ElementType="MiddleName">Apatuta</n:NameElement>

<n:NameElement ElementType="LastName">Johnson</n:NameElement>

<n:NameElement ElementType="GenerationIdentifier">III</n:NameElement>

<n:NameElement ElementType="Title">PhD</n:NameElement>

</n:PersonName>

</n:PartyName>

3.2 Extensible Address Language (xAL)

xAL defines an XML structure to represent address data. An address could include but not limited to any of the following types that are supported by xAL:

· Airport

· Business/Commercial Parks

· Caravan Parks

· Community Developments

· Dual (Primary and Secondary)

· Educational institutions

· Entertainment/Recreation Parks

· Hospitals

· Large Mail Users

· Marinas

· Military

· Ports

· Retirement Villages

· Resorts

· Royal Highness

· Rural (with land, air and water access)

· Sporting Venues

· Territories

· Tribal

· Simple Urban

· Complex Urban

· Utility Urban

· Ranged Urban

· Villages

· Canals

· Banks

· etc

xAL can represent addresses of 245+ countries in over 130 formats. The diagram below illustrates a high level UML model of xAL.

3.2.1 Example – Simple Address Representation

16 Patterson Street, OCEAN REEF, WA

<a:Address>

<a:FreeTextAddress>

<a:AddressLine>16 Patterson Street</a:AddressLine>

<a:AddressLine>OCEAN REEF</a:AddressLine>

<a:AddressLine>WA</a:AddressLine>

</a:FreeTextAddress>

</a:Address>

3.2.2 Example – Semi Complex Address Representation

16 Patterson Street, OCEAN REEF, WA

<a:Address>

<a:FreeTextAddress>

<a:AddressLine>16 Patterson Street</a:AddressLine>

</a:FreeTextAddress>

<a:AdministrativeArea a:Type=”State”>

<a:NameElement>WA</a:NameElement>

</a:AdministrativeArea>

<a:Locality a:Type=”Suburb”>

<a:NameElement>OCEAN REEF</a:NameElement>

</a:Locality

</a:Address>

3.2.3 Example – Complex Address Representation

16 Patterson Street, OCEAN REEF, WA

<a:Address>

<a:AdministrativeArea a:Type=”State”>

<a:NameElement>WA</a:NameElement>

</a:AdministrativeArea>

<a:Locality a:Type=”Suburb”>

<a:NameElement>OCEAN REEF</a:NameElement>

</a:Locality>

<a:Thoroughfare a:Type=”Street”>

<a:Name>Patterson</a:Name>

<a:Number>16</a:Number>

</a:Thoroughfare>

</a:Address>

3.3 Extensible Name and Address Language (xNAL) Version 3.0

xNAL defines an XML strucutre to represent name and address data bound together. xNAL utilises XML structures from xNL and xAL specifications. The diagram below illustrates a high level UML model of xNAL version 3.0.

3.3.1 Example Simple Name and Address Representation

Mr H G Guy, 9 Uxbridge Street, Redwood, Christchurch

<nal:Record>

<n:PartyName>

<n:NameLine>Mr H G Guy</n:NameLine>

</n:PartyName>

<a:Address>

<a:FreeTextAddress>

<a:AddressLine>9 Uxbridge Street</a:AddressLine>

<a:AddressLine>Redwood</a:AddressLine>

<a:AddressLine>Christchurch</a:AddressLine>

</a:FreeTextAddress>

</a:Address>

</nal:Record>

3.3.2 Example – Complex Name and Address Representation

Mr H G Guy, 9 Uxbridge Street, Redwood, Christchurch

<xnal:Record>

<n:PartyName>

<n:PersonName>Mr H G Guy

<n:NameElement n:ElementType=”Title>Mr</n:NameElement>

<n:NameElement n:ElementType=”FirstNameInitial”>H</n:NameElement>

<n:NameElement n:ElementType=”MiddleNameInitial”>G</n:NameElement>

<n:NameElement n:ElementType=”LastName”>Guy</n:NameElement>

</n:PersonName>

</n:PartyName>

<a:Address>

<a:AdministrativeArea>

<a:NameElement>Christchurch</a:NameElement>

</a:AdministrativeArea>

<a:Locality>

<a:NameElement>Redwood</a:NameElement>

</a:Locality>

<a:Thoroughfare>>

<a:Name>Uxbridge Street </a:Name>

<a:Number>9</a:Number>

</a:Thoroughfare>

</a:Address>

</xnal:Record>

3.4 Extensible Party Information Language (xPIL)

xPIL defines an XML structure to represent party-centric data. Party-centric data includes name, address, e-mail address, telephone numbers, identification details (e.g. passport, license number, identification card, etc), vehicle details, account details, etc. These unique attributes of a party assist in uniquely identifying a party. The diagram below illustrates a high-level UML view of xPIL version 3.0

3.5 Extensible Party Relationships Language (xPRL)

xPRL defines a consistent way of using xLink to represent party relationships. Party relationships could be:

· Person to Person relationships

· Person to Organisation relationships, and

· Organisation to Organisation relationships

Release date for version 3.0 of this specification not set yet at the time of releasing OASIS CIQ Party, Name and Address Specifications v3.0.

4 Implementing CIQ TC specifications – Practical Guidelines

Some readers may find it hard to get to grips with the CIQ TC specifications family. This section is an informative guide to help you get started.

4.1 Where to Start

Consider doing the following:

· Clearly define your requirements and goals of using CIQ Specifications

· Complete reading this document (30 minutes)

· Study the XML examples of the schemas (30 minutes). Examples are provided in the same download as the schemas.

· Study the schema diagrams (15 minutes). You can browse the schemas using an XML editor or use HTML documentation provided as part of every CIQ TC specification

· Decide whether you want to use Option 1 or Option 2 of Code List (15 minutes)

· If you want to use OASIS Codelist specification in your work, understanding the specification and how to use the specification as part of CIQ Specifications (provided as an option) could be time consuming, but a worthy exercise. Enough work has already been done by the TC to keep this process simple by providing all required files and test cases in the CIQ Specification package (1 hour)

· Try to build valid structures you need using the schemas and your sample data (20 minutes). You may want to use an XML editor that provides information from schema xs:annotation elements to help you understand the meaning of the elements and attributes.

· If you want to customise the base/default CIQ schemas provided without modifying them to meet your application specific requirements, use Schematron patterns as part of the UMCLVV approach used by OASIS Code List Specification. To be able to use this option, you need to have some basic knowledge of xPath and Schematron languages.

4.2 Don’t get confused – keep it simple

xNL, xAL and other CIQ TC specifications provide the flexibility to deal with different types of applications. Flexibility could lead to breaking interoperability unless the implementation is managed effectively. If you are interoperating the data with other parties, ensure that you and the other parties implement the specifications in identical fashion. To enforce this, the parties should have an agreement in place and ensure that the agreement is implemented and governed.

Version 3.0 allows you to customise the specifications to meet your requirements without affecting the structure of the schemas through enumeration lists. However, please ensure that what you have customised is agreeable with the other party that exchanges data with you (e.g. applications, end users, external parties) to achieve interoperability between parties involved in data exchange.

4.3 Data Exchange

CIQ TC specifications can be used to organise data exchange of party information or just names and addresses. It is likely that CIQ TC specifications on their own are not enough to organise such an exchange as it requires some messaging mechanisms and additional information such as metadata.

CIQ TC recommends that reusable elements from the CIQ TC schemas are used inside other namespaces or wrappers. This will ensure that the original namespaces remain intact while additional information is still provided.

CIQ TC re-iterates here that agreements should be in place between parties involved in the data exchange process on how the specifications will be implemented to ensure consistency in implementations and how the agreement will be managed/ governed. This is very important to achieve interoperability of data between parties involved in data exchange.

Given that CIQ Specifications provide many optional elements and attributes, implementation of the specifications for data exchange require agreement in place between parties that use the CIQ specifications based data formats to ensure interoperability.

4.4 Output Formatting

CIQ TC specifications do not have any means to specify the formatting of the data. It is up to the application to decide which formatting suits best. It is recommended to preserve the original order of elements to assist with correct output formatting. Remember, that addresses, for example, may begin with the finest details (e.g. flat number) in some locales or with country name in the other. Preserving the original order is important.

4.5 Customising Schema

CIQ XML Schemas (xNL.xsd, xAL.xsd, xNAL.xsd, and xPIL.xsd) have been designed to be application and industry independent thereby allowing different applications to use them. Users have been provided with the following choices to customise CIQ Schema to meet their specific application requirements.

Further details on this subject are described in “Name, Address and Party Specifications Document” of CIQ TC.

4.5.1 Schema Extensions

It is possible to extend CIQ XML schemas within some allocated boundaries to meet specific application or locale requirements. The extensions can be of four types:

· Any element can have any number of attributes from the non-target namespace, which means you can include some other attributes not specified by the schema.

· Enumerations can be changed and they are intentionally placed in a separate “include” xml schema file.

· Enumerations can also be changed with genericode approach from OASIS Code List Representation Technical Committee and the enumeration lists are placed in separate files (.gc extension)

· Adding new elements to the schema is not permitted to ensure interoperability– use wrappers instead. This is shown in the figure below the elements of xNAL are wrapped using an XML Schema that has “Records” as its root element.

4.5.2 Restricting Schema

Restricting the use of the CIQ XML Schemas as part of implementation can be done by two ways:

· All elements and attributes in the CIQ XML Schemas are optional. This provides users the flexibility to customise the schemas to meet their application specific requirements.

· Deleting new elements in the CIQ XML schemas are not permitted to ensure interoperability – use UMLCVV (approach from OASIS Code List Representation TC and OASIS UBL TC) that is proposed to restrict the schema without modifying it. This allows customisation of the schema by defining business rules using Schematron language, an open industry standard, to meet application specific requirements, but at the same time ensures that the XML document is compatible with the base/core schema. This capability for example, allows xAL schema to be customised to meet country specific address structure requirements. An example would be a country like Singapore where there are no states, cities, post towns and Rural Areas. In this case, a business rule can be written not to use AdministrativeArea, SubAdministrativeArea, PostTown, and RuralDelivery elements of xAL.xsd schema.

A working example of this is provided as part of the CIQ V3.0 package.

4.6 Data Mapping Challenges

The main challenge in standardising name and address and even party data structures is in a potentially infinite number of ways they can be presented for different applications, different cultures and locales.

4.6.1 Application Diversity

For example a simple e-commerce database may have name as one field, address as a free-text 3-field set and other party information in a dozen of other fields. It may be sufficient for that particular data usage scenario.

A larger bank may be interested in a more detailed name and address structure to allow business intelligence applications to do their analysis.

The differences in complexity between these two examples present a great challenge finding a common form of representing the data so that it is attractive to all parties participating in data exchange.

4.6.2 Cultural Diversity

Name and address presentation formats vary between cultures elevating the importance of breaking down the structure and preserving the original meaning of the elements so that the name or address can be correctly restored at a later time. It is virtually impossible to fit all these diverse views into a single name and address specification that is also specific to a particular culture. Some balanced approach is required to meet the semantic and presentation variations and requirements in one specification. It is the goal of CIQ TC to achieve such a balance.

India is a good example of cultural diversity with people from different ethnic backgrounds, languages (officially 14 national languages) and religions. In some Indian locales there is no concept of family name or given name or surname or first name or middle name or last name. They have the following name types that can be used as part of a person’s name:

Grand father name, Great grand father name, Father’s name, Mother’s name, Native Place name, Tribal name, Caste name, Husband’s name, Birth name, etc.

Addresses are culture and locale specific too. There is typically a great degree of freedom as to how one writes an address with information that is specific to the geographic location/locale. Yet it still reaches the destination. For example, in countries like Thailand, addresses include the names of the river banks, or canals instead of streets. The concept of neither the postal code nor the locality applies to some countries. In certain countries an address is attached to the number of a postal van that delivers the mail to the destination as the van driver is responsible for delivering mail to a certain area/streets in an area.

4.6.3 CIQ TC Solution

CIQ TC provides a solution that can absorb and persist with the information in the form it was originally provided without any loss of semantics. The information can then be mapped to some target structure with a minimal effort.

However, CIQ TC does not provide a solution for mapping a simple source structure to a more complex target as it would require parsing and “understanding” the information carried in the structure itself. Any solution to this problem is out of scope for CIQ TC.

The diagram below shows how a simple one-field data model can be mapped to another complex data model through xNL, but with help of “smart name parsing/scrubbing data quality software” (and there are plenty in the market) to separate a full name into name, middle name and surname:

A. Acknowledgements

The following individuals have participated in the creation of version 3.0 of CIQ specifications and are gratefully acknowledged:

Participants:

Colin Wallis	New Zealand Government	Voting Member, CIQ TC
David Webber	Individual	Voting Member, CIQ TC
Fulton Wilcox	Colts Neck Solutions LLC	Voting Member, CIQ TC
Graham Lobsey	Individual	Voting Member, CIQ TC
Joe Lubenow	Individual	Voting Member, CIQ TC
John Glaubitz	Vertex, Inc	Voting Member, CIQ TC
Michael Roytman	Vertex, Inc	Voting Member, CIQ TC
Ram Kumar	Individual	Chair and Voting Member, CIQ TC
George Farkas	XBI Software, Inc	Former Member, CIQ TC
Hidajet Hasimbegovic	Individual	Former Member, CIQ TC
John Putman	Individual	Former Member, CIQ TC
Mark Meadows	Microsoft Corporation	Former Member, CIQ TC
Max Voskob	Individual	Former Member, CIQ TC
Robert James	Individual	Former Member, CIQ TC

OASIS CIQ Technical Committee (TC) sincerely thanks the public (this includes other standard groups, rganizations and end users) for their continuous feedback and support that helps the TC to work toward improving the CIQ specifications.

Special thanks to Mr.Ken Holman, Chair of OASIS Code List TC (http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=codelist) for his support, guidance and genericode implementation assistance to the TC in releasing the OASIS Code List version of CIQ V3.0 XML Schemas.

Special thanks to Mr.Hugh Wallis, Director of Standards Development of extensible Business Reporting Language (xBRL) International Standards Group (http://www.xbrl.org) for working closely with the CIQ TC in jointly implementing W3C xLink specification that is now used by both xBRL and CIQ Specifications to enable interoperability between the two specifications.

Special thanks to Mr.Carl Reed, Chief Technology Officer of Open Geospatial Consortium (OGC – http://www.opengeospatial.org) for his guidance and assistance to the TC in referencing the work of OGC on GeoRSS and Geo-Coordinates for addresses/locations as part of CIQ Address Specifications.

OASIS CIQ TC also acknowledges the contributions from other former members of the TC since its inception in 2000.

B. Intellectual Property Rights, Patents, Licenses and Royalties

CIQ TC Specifications (includes documents, schemas and examples^{1 and 2}) are free of any Intellectual Property Rights, Patents, Licenses or Royalties. Public is free to download and implement the specifications free of charge.

¹xAL-AustralianAddresses.xml

Address examples come from AS/NZ 4819:2003 standard of Standards Australia and are subject to copyright

²xAL-InternationalAddresses.xml

Address examples come from a variety of sources including Universal Postal Union (UPU) website and the UPU address examples are subject to copyright.

xLink-2003-12-31.xsd

This schema was provided by the xBRL group in December 2006.

C. Revision History

Revision	Date	Editor	Changes Made
V3.0 PRD 01	13 April 2006	Ram Kumar and Max Voskob	Prepared 60 days public review draft from Committee Draft 01
V3.0 PRD 02	15 June 2007	Ram Kumar	Prepared second round of 60 days public review draft from Committee Draft 02 by including all public review comments from PRD 01. Also included is implementation of OASIS Code list specification
V3.0 PRD 02 R1	18 September 2007	Ram Kumar	Inclusion of comments from Public Review 02
V3.0	15 November 2007	Ram Kumar	Final Version
V3.0 CS02	20 September 2008	Ram Kumar	Final Version