OASIS Customer Information Quality Technical Committee – Overview Ram Kumar Founding Chairman Ram Kumar Founding Chairman March 2008

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 n “Officially” founded in late 2000 at XML 2000 Conference in Washington DC n Work on CIQ specifications started “informally” in early 2000 n Technical Committee Members from Asia- Pacific, Europe, UK, and USA n Founding Members l Ram Kumar, Mastersoft, Australia (Chairman) l Vincent Buller, AND Data Solutions, The Netherlands l John Bennett, Parlo.com, USA

Why was CIQ TC formed? n In customer driven world, party information is the “key piece of data” used in any business transaction and in particular, global e- business n However, there were no XML industry standards to define and share party information between the groups involved in business transactions n Therefore, it was decided to develop XML industry specifications for party centric data representation and exchange

Applications using Party related data (a sample)

CIQ TC Goals/Objectives n Develop global party specifications to represent party data n Application independent specifications n Platform independent specifications n Vendor neutral specifications n Truly “open” specifications, meaning l free of royalties l free of patents l free of licenses l free of Intellectual Property Rights (IPRs) l freely available for public to download and implement the specifications without any restrictions n Specifications developed in an open process environment n Specifications independent of language, cultural and geographical boundaries n Specifications have the ability and flexibility to represent global party data

Out of Scope activities of CIQ TC n Data Privacy n Data Security n Message Structure n Data Transport n Data Routing n Data Formatting n International Name and Address Templates n Data Transformation n Transactional "customer/party information" such as recent purchases, payment history, etc. n 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 n “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 n Data Interoperability = l Open Data Architecture + l Data Integration + l Data Quality + l Open Data Standards + l Data Semantics + l Data Governance

CIQ TC Party Information Specifications n Extensible Name and Address Language (xNAL) l Extensible Name Language (xNL) to define a Party’s name (person/company) l Extensible Address Language (xAL) to define a party’s address(es) n Extensible Party Information Language (xPIL) for defining a Party’s unique information (tel, , account, url, identification cards, etc. in addition to name and address) n 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? n 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 n 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? n Developed by experts dealing with “international party data” (includes international names and addresses) for use in various applications for over a decade n Developed by experts with XML and XML based interoperability expertise n 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? n The most complex “party” data, but the most important data for party identification and for any business dealing with parties (person/organizations) n Can be represented in many ways, but still could mean the same n Very volatile - names and addresses change often n Often cluttered when recorded n Varies from country to country as it is closely associated with the geographical location, culture, race, religion and language l Addresses of 241+ Countries l Represented in 5,000+ languages l With about 130+ Address Formats l With about 36+ Personal Name formats

xNAL Goals n Application/Domain Independent n Truly “Global” international specifications n 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 n Follow and adopt W3C XML industry standards and ensure it is 100% open n Open and vendor neutral

xNAL: Application Independency n The CIQ specifications will not be specific to any application/domain, say, Postal services, Mailing, CRM, Party Profile, Address Validation, etc n 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 n 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 n Any domain specific application can use CIQ specifications and build applications around it that meets its business requirements

xNAL: “Global” Specification n The objective is to provide the ability to handle the following: l Addresses of 241+ Countries l Represented in 5,000+ languages l With about 130+ Address Formats l With about 36+ Personal Name formats n and at the same time, should be application independent, open and vendor neutral

xNAL: Design Approach/Methodology n 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) n Collected and used valuable inputs from other name and address standard initiatives around the world n Collected and used inputs from real world users, applications and experts (e.g. Graham Rhind of Global Address Database) of name and address data n Conducted a detailed analysis and modeling of international name and address data n 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? n 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) n xNAL is the world’s first truly global, open, vendor neutral and application/domain independent specification for name and address language n First and the only international standards committee dedicated to developing global XML specifications for name and address n 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. n 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) Model

xNL Model

xAL Model

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

xPIL ( formerly called as “xCIL”) n Represents Other Party Information – extends xNAL n Party : A Person or an Organization ( Organization: Company, not for profit, Consortiums, Groups, Government, Clubs, Institutions, etc ) n Only concentrates on party-centric information that helps to uniquely identify a party n Application independent n Open n Vendor neutral n 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 - /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 Model

xPRL (formerly called as “xCRL”) n Extends xPIL and xNAL by defining relationships between two or more parties n First XML Specification in industry for managing Party Relationships n Helps ease existing complex integration between CRM systems/software and with back-end systems n Only concentrates on Party to Party Relationships n Application independent n Open n Vendor neutral n 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) Relationships Household 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

xPRL Data Model

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

Open Industry Specifications used by CIQ Specifications V3.0 n xLink from W3C (Jointly implemented with xBRL Group to enable interoperability between CIQ and xBRL) n GeoRSS/GML Profile from OGC n Schematron from ISO n Code List Representation from OASIS n XML Schema from W3C n xPath from W3C n XSL from W3C

Key Features of CIQ V3.0 n Allows users to define semantics to the data that reflect their business requirements n 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 n Allows users to add/delete/change code list values without changing the CIQ XML Schemas n 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 n 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 n More international address examples represented in CIQ n Option to use xLink from W3C or key reference to link parties n Option to use GeoRSS from OGC to represent address locations

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

n Single Customer View n Customer recognition/identification n Enterprise customer data management n Data Quality (e.g. parsing, matching, de-duping, verification, validation and enhancement) n Party profiling n Purchase orders, invoicing and shipping n Customer/Party relationships management n Customer services n Postal services n Election services n Justice, Legal and Corrective services n Business Intelligence n Customer/Party data interoperability frameworks n Front end data capture CIQ Specifications (Industry Applications - Sample)

n Any Intellectual Property Rights? l NONE n Any Licensing agreements/terms/conditions? l NONE n Any Royalties? l NONE n Any Patents? l NONE n Any restrictions (e.g. cost) to download? l NONE n Any restrictions (e.g. cost) to implement? l NONE n Any restrictions (e.g. cost) to modify? l NONE CIQ Specifications – Restrictions to use CIQ Specifications are developed by the Public for the Public

Interested to contribute/contact CIQ TC? n CIQ TC is constantly looking for more members to join this important committee n If you are interested to contribute or provide feedback, please contact l Ram Kumar, Chair, CIQ TC n

OASIS – Customer Information Quality Technical Committee (CIQ TC) Thank You