OASIS Customer Information Quality Technical Committee –Overview

Ram KumarRam Kumar

Founding ChairmanFounding ChairmanRam KumarRam Kumar

Founding ChairmanFounding Chairman

March 2008March 2008

kumar.sydney@gmail.com

OASIS Customer Information Quality Technical Committee (OASIS CIQ TC)

Delivering royalty free, open, international, industry and application neutral XML specifications for representing, interoperating and managing PARTY (person/organisation) INFORMATION

Industry Specifications developed by the Public for the Public

Background about CIQ TC

“Officially” founded in late 2000 at XML 2000 Conference in Washington DC

Work on CIQ specifications started “informally” in early 2000

Technical Committee Members from Asia-Pacific, Europe, UK, and USA

Founding Members Ram Kumar, Mastersoft, Australia (Chairman) Vincent Buller, AND Data Solutions, The

Netherlands John Bennett, Parlo.com, USA

Why was CIQ TC formed? In customer driven world, party information is

the “key piece of data” used in any business transaction and in particular, global e-business

However, there were no XML industry standards to define and share party information between the groups involved in business transactions

Therefore, it was decided to develop XML industry specifications for party centric data representation and exchange

Par ty Rel ated

Data

Data Quality (Data Parsing, Data Matching / de-duping, data standardization, data migration, data validation, data enhancement)

Data Quality (Data Parsing, Data Matching / de-duping, data standardization, data migration, data validation, data enhancement)

Customer Segmentation

Customer Segmentation

Party Identification/ Recognition

Party Identification/ Recognition

Postal ServicesPostal Services

Customer Profiling

Customer Profiling

Customer Relationships

Customer Relationships

Customer ViewsCustomer Views e-business/ e-commercee-business/ e-commerce

Other Specific Applications (e.g.

Health, Tax, manufacturing, retail, finance, automotive,

justice, etc)

Other Specific Applications (e.g.

Health, Tax, manufacturing, retail, finance, automotive,

justice, etc)

Customer Analytics, Interaction ChannelsCustomer Analytics, Interaction Channels

Applications using Party related data (a sample)

CIQ TC Goals/Objectives Develop global party specifications to represent party data Application independent specifications Platform independent specifications Vendor neutral specifications Truly “open” specifications, meaning

free of royalties free of patents free of licenses free of Intellectual Property Rights (IPRs) freely available for public to download and implement the specifications

without any restrictions Specifications developed in an open process environment Specifications independent of language, cultural and geographical

boundaries Specifications have the ability and flexibility to represent global party

data

Out of Scope activities of CIQ TC Data Privacy Data Security Message Structure Data Transport Data Routing Data Formatting International Name and Address Templates Data Transformation Transactional "customer/party information" such as

recent purchases, payment history, etc. Not a quality enhancing process as commonly

understood or akin to a certificate of test results against some objective specification

CIQ TC Goals/Objectives

CIQ TC’s definition of Interoperability

“Getting the right data to the right place at the right time in the right format and in the right context”

CIQ TC’s Data Interoperability Success Formula

Data Interoperability = Open Data Architecture + Data Integration + Data Quality + Open Data Standards + Data Semantics + Data Governance

CIQ TC Party Information Specifications Extensible Name and Address Language (xNAL)

Extensible Name Language (xNL) to define a Party’s name (person/company)

Extensible Address Language (xAL) to define a party’s address(es)

Extensible Party Information Language (xPIL) for defining a Party’s unique information (tel, e-mail, account, url, identification cards, etc. in addition to name and address)

Extensible Party Relationships Language (xPRL) to define party relationships namely, person(s) to person(s), person(s) to organisation(s) and organisation(s) to organisation(s) relationships

What is special about CIQ TC and its Specifications?

The “only standards group in industry” that is dedicated to developing XML standards for representing Party Centric Data that is truly international and is independent of specific application or industry

The “only set of international specifications in industry” that concentrates exclusively on defining Party information standards without any specific industry or applications or any geographic location or culture in mind

CIQ Specifications – Who developed them? Developed by experts dealing with “international

party data” (includes international names and addresses) for use in various applications for over a decade

Developed by experts with XML and XML based interoperability expertise

Developed by experts dealing with data quality, data integration and interoperability of party centric data for many years

Name and Address: What is the big deal about it?

The most complex “party” data, but the most important data for party identification and for any business dealing with parties (person/organizations)

Can be represented in many ways, but still could mean the same

Very volatile - names and addresses change often Often cluttered when recorded Varies from country to country as it is closely associated

with the geographical location, culture, race, religion and language

Addresses of 241+ Countries Represented in 5,000+ languages With about 130+ Address Formats With about 36+ Personal Name formats

xNAL Goals Application/Domain Independent Truly “Global” international specifications Flexibility in design to help any simple

application (e.g. Simple user registration using address lines 1,2,3, etc) to complex application (e.g. Name and Address parsing and validation by breaking name and address into atomic elements) to use xNAL to represent party name and address data

Follow and adopt W3C XML industry standards and ensure it is 100% open

Open and vendor neutral

xNAL: Application Independency

The CIQ specifications will not be specific to any application/domain, say, Postal services, Mailing, CRM, Party Profile, Address Validation, etc

The CIQ Specifications will provide the party data in a standard format that can be used by any application to do further work with the data

Any domain specific standard group, say, Postal services, can use CIQ specifications and build their own standards by extending it to make it specific to its postal business

Any domain specific application can use CIQ specifications and build applications around it that meets its business requirements

xNAL: “Global” Specification The objective is to provide the

ability to handle the following: Addresses of 241+ Countries Represented in 5,000+ languages With about 130+ Address Formats With about 36+ Personal Name formats

and at the same time, should be application independent, open and vendor neutral

xNAL: Design Approach/Methodology Designed by people with several years of experience in

International Name and Address data management and its applications (Postal services, CRM, Parsing, matching, validation, DW, DM, Single Customer View, CIS, etc)

Collected and used valuable inputs from other name and address standard initiatives around the world

Collected and used inputs from real world users, applications and experts (e.g. Graham Rhind of Global Address Database) of name and address data

Conducted a detailed analysis and modeling of international name and address data

The development of original xNAL (ver.1.0) took about 2+ years and is still evolving

xNAL: How different is it from other similar efforts?

Other efforts in defining name and address standards are application or domain specific (e.g. Postal services, specific to a country’s names and addresses, Health, Human Resources, etc)

xNAL is the world’s first truly global, open, vendor neutral and application/domain independent specification for name and address language

First and the only international standards committee dedicated to developing global XML specifications for name and address

xNAL can be used in any application/domain such as user registration, postal services, name and address parsing, name and address matching, name and address validation, etc.

xNAL is well set to meet the current business challenges of conducting businesses globally (thanks to e-business)

Evolution of xNAL Specifications

xNAL (xNL + xAL) Modelcd xNAL

xNAL

Record Postal label

Address

+ Address

+ Address

+ AdministrativeArea

+ Country

+ FreeTextAddress

+ Locality

+ Location Coordinates

+ PostalDeliveryPoint

+ Postcode

+ PostOffice

+ Premises

+ RuralDelivery

+ Thoroughfare

(from CIQ Data Model)

Addressee

XOR

Name

- Free Text Name Line

+ Organisation Name

+ PartyName

+ PartyNameType

+ Person Name

+ Subdivision

(from CIQ Data Model)

1..*1..*

1..*

xNL Modelcd Name

«type»PartyNameType

+ Names connector:

Free Text Name Line Person Name

- FirstName: - LastName: - MiddleName: - GivenName1: - GivenName2: - Title:

Organisation Name

- Name: - Type:

Subdiv ision

- Name:

«hierarchy»

0..* 0..*0..*

xAL Modelcd Address

«type»Address

- Type: - Usage: - Date Valid From: - Date Valid To: - Postal ID:

FreeTextAddress

Country

- Name: - Code:

Administrativ eArea

- Name: - Type: Locality

- Name: - Type:

Thoroughfare

- Name: - Number: - Type:

Premises

- Name: - Number: - Type:

Postcode

- Identifier:

RuralDeliv ery

- Identifier:

PostalDeliveryPoint

- Identifier: PostOffice

- Identifier:

Location Coordinates

- Identifiers:

«hierarchy»

«hierarchy»

«hierarchy»

0..1

0..1

0..1

0..1

0..1

0..1

0..1

0..1

0..10..1

0..1

xAL: Types of addresses coveredAirport, 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, Location based references, vacant lands, Hills, banks, canals, rivers, etc

xPIL (formerly called as “xCIL”)

Represents Other Party Information – extends xNAL Party : A Person or an Organization (Organization: Company,

not for profit, Consortiums, Groups, Government, Clubs, Institutions, etc) Only concentrates on party-centric information that

helps to uniquely identify a party Application independent Open Vendor neutral Flexibility for simple representation of data to detailed

representation of the data depending upon the need

xPIL : Supported Party-Centric Information

- Name details - Address details

- Customer Identifier - Passport details

- Organization details - Religion/Ethnicity details

- Birth details - Telephone/Fax/Mobile/Pager details

- Age details - E-mail/URL details

- Gender - Account details

- Marital Status - Identification card details

- Physical Characteristics - Income/tax details

- Language details - Vehicle details

- Nationality details - Parent/Spouse/Child details

- Visa details - Relationship details

- Habits - Qualification details

- Occupation details - Hobbies

- Preferences - Key Events

- Membership details

Evolution of xPIL Specifications

xPIL Modelcd Party

«type»Party

Name

Address

FreeTextInformation

Account

- ID: - type of account/reg: - issuer: - date of issue: - place of issue:

Coutact Number

- country code: - area code: - local number: - extenstion:

Contact

- Person: - Address: - Contact Number: - Electronic Address Identifier:

Document

- Number: - Issuer: - Valdity:

Electronic Address Identifier

- Type:

Vehicle

- Type: - Make: - Model: - Registration Number:

PersonDetails OrganisationDetails

- Size: - Revenue: - Registration ID: - Formation date: - Industry Code: - Nature of Business:

XOR

Address

+ Address

+ Address

+ AdministrativeArea

+ Country

+ FreeTextAddress

+ Locality

+ Location Coordinates

+ PostalDeliveryPoint

+ Postcode

+ PostOffice

+ Premises

+ RuralDelivery

+ Thoroughfare

(from CIQ Data Model)

Name

- Free Text Name Line

+ Organisation Name

+ PartyName

+ PartyNameType

+ Person Name

+ Subdivision

(from CIQ Data Model)

Person Info

+ Birth information

+ Country of residence

+ Favourite

+ Habit

+ Hobby

+ Key Event

+ Language

+ Nationality

+ Occupation

+ Person Info

+ Physical details

+ Qualification

+ Travel visa

(from CIQ Data Model)

Membership

- Number: - Organisation:

«is of type»

0..*

0..1

0..*

0..*

«is of type»

0..*

0..1

0..*

0..*

0..*

0..*

«is of type»

0..*

xPRL (formerly called as “xCRL”) Extends xPIL and xNAL by defining relationships

between two or more parties First XML Specification in industry for managing Party

Relationships Helps ease existing complex integration between

CRM systems/software and with back-end systems Only concentrates on Party to Party Relationships Application independent Open Vendor neutral Flexibility for simple representation of data to

detailed representation of the data depending upon the need

xPRL – Types of Relationships• Person(s) to Person(s) RelationshipsHousehold relationships, Contact/Account Management, Personal and Business relationships, Organisation structure, etc

• Person(s) to Organisation(s)/Group(s) RelationshipsBusiness relationships (e.g. “Doing Business As”, member of, employee-employer, business contacts, etc)

• Organisation(s)/Group(s) to Organisation(s)/Group(s) RelationshipsParent-Subsidiary relationships, Head office-Branch relationships, Partnership relationships (e.g. Alliance, Channel, Dealer, Supplier, etc), “member of” relationships, “Trading As”, “In Trade for” type relationships, etc

Evolution of xPRL Specifications

OASIS ExtensibleName Language

(xNL)

OASIS ExtensibleAddress Language

(xAL)

OASIS ExtensibleName and Address

Language(xNAL)

OASIS ExtensibleCustomer

RelationshipsLanguage

(xCRL)

OASIS ExtensibleCustomer

RelationshipsLanguage

(xCRL)

Input from Industry

OASIS PartyRelationships

Language (xPRL)

Input from IndustryxLink Specification

from W3C

2001 2002 2005-08

VERSION 1.1VERSION 1.0 VERSION 3.0

Input from Industry

OASIS ExtensibleCustomer

InformationLanguage

(xCIL)

Name Change

CustomerRelationships Markup

Language (CRML)from Mastersoft,

Australia

EVOLUTION OF OASIS xCRL/xPRL SPECIFICATION SINCE 1999

Code ListRepresentation

Specification fromOASIS

xPRL Data Modelcd Party Relationships

Relationship

- RelationshipID: - RelationshipIDType: - ID: - RelationshipType: - RelationshipCategory: - RelationshipStatus: - RelationshipStartDate: - RelationshipEndDate: - RelationshipRelativityWithOtherParty: - RelationshipStartReason: - RelationshipEndReason: - RelationshipRole: - OtherPartyRelationshipRole: - RelationshipPriority:

Party Party

Party

+ Account

+ Address

+ Contact Number

+ Document

+ Electronic Address Identifier

+ Event

+ FreeTextInformation

+ Identifier

+ Membership

+ Name

+ OrganisationDetails

+ Party

+ PersonDetails

+ Relationship

+ Vehicle

(from CIQ Data Model)

Address

+ Address

+ Address

+ AdministrativeArea

+ Country

+ FreeTextAddress

+ Locality

+ Location Coordinates

+ PostalDeliveryPoint

+ Postcode

+ PostOffice

+ Premises

+ RuralDelivery

+ Thoroughfare

(from CIQ Data Model)

Name

- Free Text Name Line

+ Organisation Name

+ PartyName

+ PartyNameType

+ Person Name

+ SubDivision

(from CIQ Data Model)

«uses» «uses»

<<isoftype>><<isoftype>>

1..*0..*

Status of CIQ Specifications V3.0 of Name (xNL) V3.0 of Address (xAL) V3.0 of Name and Address (xNAL) V3.0 of Party Information (xPIL) V3.0 of Party Relationships (xPRL)

Open Industry Specifications used by CIQ Specifications V3.0

xLink from W3C (Jointly implemented with xBRL Group to enable interoperability between CIQ and xBRL)

GeoRSS/GML Profile from OGC Schematron from ISO Code List Representation from OASIS XML Schema from W3C xPath from W3C XSL from W3C

Key Features of CIQ V3.0 Allows users to define semantics to the data that reflect their business

requirements Allows users to apply constraint on CIQ XML Schemas (e.g. only using the

elements they want to meet their business requirements) without changing the CIQ XML Schemas

Allows users to add/delete/change code list values without changing the CIQ XML Schemas

Can perform one pass validation (structure and code list value validation) of CIQ XML document instances against the CIQ XML Schemas if the code lists are defined as part of CIQ XML Schemas

Can perform two pass validation (pass 1 – structure validation and pass 2 – code list value validation and business rules validation) of CIQ XML document instances against the CIQ XML Schemas by defining code lists outside of the CIQ XML Schemas

More international address examples represented in CIQ Option to use xLink from W3C or key reference to link parties Option to use GeoRSS from OGC to represent address locations

CIQ Specifications (Adoption by Industry Types - Sample)

Governments, including e-Government Insurance Companies Banks Solution providers Telecommunication companies Product Vendors Retail companies Standard Bodies/Groups/Consortiums OASIS Technical committees Open Source Community for CRM Postal Companies Manufacturing companies Financial Service Providers (e.g. credit cards) Automotive industry Justice Sector Health

Single Customer View Customer recognition/identification Enterprise customer data management Data Quality (e.g. parsing, matching, de-duping,

verification, validation and enhancement) Party profiling Purchase orders, invoicing and shipping Customer/Party relationships management Customer services Postal services Election services Justice, Legal and Corrective services Business Intelligence Customer/Party data interoperability frameworks Front end data capture

CIQ Specifications (Industry Applications - Sample)

Any Intellectual Property Rights? NONE

Any Licensing agreements/terms/conditions? NONE

Any Royalties? NONE

Any Patents? NONE

Any restrictions (e.g. cost) to download? NONE

Any restrictions (e.g. cost) to implement? NONE

Any restrictions (e.g. cost) to modify? NONE

CIQ Specifications – Restrictions to use

CIQ Specifications are developed by the Public for the Public

Interested to contribute/contact CIQ TC? CIQ TC is constantly looking for more

members to join this important committee

If you are interested to contribute or provide feedback, please contact Ram Kumar, Chair, CIQ TC

kumar.sydney@gmail.com

OASIS – Customer Information Quality Technical

Committee (CIQ TC)

http://www.oasis-open.org/committees/ciq

Thank YouThank You