Copyright © OASIS, 2000 Onwards OASIS Customer Information Quality Technical Committee – Overview...

Copyright © OASIS, 2000 Onwards

OASIS Customer Information Quality Technical Committee –Overview

Ram KumarFounding Chairman

October 2008October 2008

[email protected]

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


OASIS Customer Information Quality Technical Committee (OASIS CIQ TC)

The Name “Customer Information Quality” is just the operating name of the Technical Committee. The scope of the TC is much broader than “Customer Information”. This Committee concentrates on developing global and generic industry specifications for “Party Centric Information”. “Customer” is a type of “Party”.


Background about CIQ TC

“Officially” founded at XML 2000 Conference in Washington DC, USA

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 a 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 or groups in year 2000 that concentrated on defining standards for consistent representation of party data and for sharing party data between the groups, processes, and applications/systems involved in business transactions associated with a party

Therefore, it was decided to fill this gap through CIQ TC that would focus on developing XML industry specifications for party centric data representation and exchange

A group called Customer Profile Exchange (CPExchange) under IDE Alliance commenced similar work in 2000, but the committee was closed down in 2001-02


PARTY CENTRIC

DATA

PARTY CENTRIC

DATA

Dat a Qual it y (Data Parsing, Data Matching/De-duping, Data Validation andVerification, Data Profiling, Data Migration, Data Standardization, Data Enhancement)

Dat a Qual it y (Data Parsing, Data Matching/De-duping, Data Validation andVerification, Data Profiling, Data Migration, Data Standardization, Data Enhancement)

Unique Par t y Ident ifi cat ion andRecognit ion

Unique Par t y Ident ifi cat ion andRecognit ion

Indust r y Spec ifi cAppl icat ions (Health, Tax, Finance, Justice, Retail,Human Resources, Travel, Manufacturing, Billing, Purchasing, etc)

Indust r y Spec ifi cAppl icat ions (Health, Tax, Finance, Justice, Retail,Human Resources, Travel, Manufacturing, Billing, Purchasing, etc)

Par t y Views, Cust omer Views,MDM, CDM, CDI, ODS, Sour ce Of Tr ut h

Par t y Views, Cust omer Views,MDM, CDM, CDI, ODS, Sour ce Of Tr ut h

E-Business,E-Commer ce

E-Business,E-Commer ce

Par t y Anal yt ics.Par t y Segment at ion,Par t y P r ofi l ing,Par t y Int er ac t ionchannel s

Par t y Anal yt ics.Par t y Segment at ion,Par t y P r ofi l ing,Par t y Int er ac t ionchannel s

Geo-c oding,Geo-Spat ial

Geo-c oding,Geo-Spat ial

Post al Ser vices

Post al Ser vices

F r aud, Ident it y Management , Ter r or ism,emer gency

F r aud, Ident it y Management , Ter r or ism,emer gency

Par t y / Cust omerRel at ionships

Par t y / Cust omerRel at ionships

Some Key Applications of Party Centric Data



CIQ TC Goals/Objectives Develop global party specifications to represent party data Application independent specifications Platform independent specifications Vendor neutral specifications Industry 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 "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 Mission Statement

Delivering royalty free, open, international, industry and application neutral XML specifications for representing, interoperating, and managing Party (Person/Organisation) Centric Information (Name, Address, Party Profile and Party Relationships)

Open Industry Specifications developed by the Public for the Public


Why CIQ Standards – An Example

If there are many business systems in a organisation, party data are often captured in each of these systems independently with different formats, contexts, and quality. This leads to serious party data integration issues and therefore, poor visibility of the party and the dealings with the party within the enterprise. As a result, Party oriented initiatives becomes a challenge.

If “standards” are introduced for different domains such as billing, sales, marketing, loans, insurance, etc, often you end up defining party models for each of these standards independently as advocated by these domain models (e.g. IAA, ACORD, xBRL).

CIQ provides a common base specification to represent party data in a consistent way across the organisation, and this can then be extended to support specific business requirements

Source: Acxiom Corporation 2001

LoansDeposits Mortgage Brokerage Insurance

CIF

Line of Business

Silo’s

DeliveryChannels

Where’s the Party (customer)?What do I know about the Party (customer)?

Credit Cards


CIQ TC’s definition of Interoperability

“Get the right data to the right place at the right time in the right format, with the right quality, in the right context, and with the right governance” for processing by processes, applications and users.”


CIQ TC’s Data Interoperability Success Formula

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


What is special about CIQ TC and its Specifications?

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

The “only set of international specifications in industry” that concentrates exclusively on defining Party information specifications 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

Developed by experts who have implemented Information and Data Management Strategies in many organisations


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


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 “Global” international specifications capable of handling

any party names and addresses of the world 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, global, application, industry and vendor neutral


xNAL: Application and Industry Independency

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

The CIQ Specifications will provide the party data in a standard model 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, industry 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, Party Relationships Management, Parsing, matching, validation, DW, DM, Single Party View, Party Information Systems, 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 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


xNAL: How different is it from other similar efforts?

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

xNAL is the world’s first global, open, vendor neutral and application/domain, and industry 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


An Open Challenge to existing groups that develop Person Name Models in Industry

Can existing party models in industry other than OASIS xNL V3.0 be able to represent the following name of a living person?

Full Name : William Street Rajan United States Virginia IndianName used to address the person : WRUVI First Name, Middle Name, Last Name categorisation of the above name is invalid (they

only represent the position of the name in a name string) as each name has a meaning associated with it that has to be preserved. This person’s cultural background does not have the concept for first name, given name, surname, family name, Christian name, last name, etc:

William Street : Name of the street where the person was born Rajan : The person’s father’s name at birth United States : Country where the person was born Virginia : State where the person was born Indian : Country of origin of the person OASIS xNL Specification can represent the above name as it provides capability to users

to add “semantics” to a name string that helps to preserve the exact meaning of a name.


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


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, application, industry, and vendor neutral Global 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


+ Country

+ FreeTextAddress

+ Locality



+ Postcode

+ PostOffice

+ Premises

+ RuralDelivery

+ Thoroughfare


Name


+ Organisation Name

+ PartyName

+ PartyNameType

+ Person Name

+ Subdivision


Person Info

+ Birth information

+ Country of residence

+ Favourite

+ Habit

+ Hobby

+ Key Event

+ Language

+ Nationality

+ Occupation

+ Person Info

+ Physical details

+ Qualification

+ Travel visa


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 and

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

Relationships with supporting roles Helps ease existing complex integration between Party

information systems/software (e.g. CRM) and with back-end systems

Only concentrates on Party to Party Relationships and associated party roles

Open, Application, industry and vendor neutral Global 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) Relationships

Business relationships (e.g. “Doing Business As”, member of, employee-employer, business contacts, etc)

• Organisation(s)/Group(s) to Organisation(s)/Group(s) Relationships

Parent-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)


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


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


Address

+ Address

+ Address


+ Country

+ FreeTextAddress

+ Locality



+ Postcode

+ PostOffice

+ Premises

+ RuralDelivery

+ Thoroughfare


Name


+ Organisation Name

+ PartyName

+ PartyNameType

+ Person Name

+ SubDivision


«uses» «uses»

<<isoftype>><<isoftype>>

1..*0..*


Status of CIQ Specifications(As of October 2008)

V3.0-CS02 of Name (xNL) V3.0-CS02 of Address (xAL) V3.0-CS02 of Name and Address (xNAL) V3.0-CS02 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 (Genericode) from

OASIS Context Value Association Methodology 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 (e.g. OGC) OASIS Technical committees (e.g. DITA, Tax, Emergency, Election) Open Source Communities Postal Companies Manufacturing companies Financial Service Providers (e.g. credit cards) Automotive industry Justice Sector Health


Single Party View Party Recognition/Identification Enterprise Party Data Management Data Quality (e.g. parsing, matching, de-duping, verification,

validation and enhancement) Party Profiling Purchase orders, invoicing and shipping Party Relationships Management Party Services Postal Services Election Services Justice, Legal and Corrective Services Business Intelligence Party Data Interoperability Frameworks Front End Data Quality Capture Emergency Management Geospatial (e.g. Google Earth/Map)

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 and user registration) 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, OASIS CIQ TC

[email protected]


Thank You

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

Copyright © OASIS, 2000 Onwards OASIS Customer Information Quality Technical Committee – Overview...

Documents

Transcript of Copyright © OASIS, 2000 Onwards OASIS Customer Information Quality Technical Committee – Overview...