1. OASIS Customer Information Quality Technical Committee – Overview Ram Kumar Founding Chairman Ram Kumar Founding Chairman February 2007

2. Who is OASIS? O rganization for the A dvancement of S tructured I nformation S tandards www.oasis-open.org

3. OASIS drives the development, convergence and adoption of e-business standards. of e-business standards. OASIS Mission

4. n OASIS is a member-led, international non-profit standards consortium concentrating on structured information and global e-business standards. n Over 5,000 Members from 100+ countries of OASIS include: l Vendors, users, academics and governments l Organizations, individuals and industry groups n Best known for web services, e-business, security and document format standards. n Supports over 65 committees producing royalty- free and RAND standards in an open process.

5. Current Members n Software vendors n User companies n Industry organisations n Governments n Universities and Research centres n Individuals n And co-operation with other standards bodies

6. OASIS Relationships n Cooperate and liaise with other standards organizations l Working to reduce duplication, promote interoperability l Gaining sanction/authority & adoption for OASIS Standards n Formal working relationships with many: l ISO, IEC, ITU, UN-ECE MoU for E-Business l ISO/IEC JTC1 SC34, ISO TC154 (Cat. A Liaison) l ITU-T A.4 and A.5 Recognition l IPTC, LISA, SWIFT, UPU l ABA, ACORD, HL7, HR-XML, ISM, MBAA, NASPO, NIGP, VCA l European ICTSB, CEN/ISSS, EC SEEM, PISCES, LRC l Asia PKI, CNNIC, EA-ECA, ECIF, KIEC, PSLX, Standards- AU l BPMI, CommerceNet, GGF, IDEAlliance, OAGi, OGC, OMA, OMG, RosettaNet/UCC, W3C, WfMC, WSCC, WS-i

7. Current Scope of Work n Web Services n e-Commerce n Security n Law & Government n Supply Chain n Computing Management n Application Focus n Document-Centric Applications n XML Processing n Conformance/Interop n Industry Domains

8. 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/organization) centric information

9. 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

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

11. 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

12. 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

13. CIQ TC Goals/Objectives

14. 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, e-mail, account, url, identification cards, etc. in addition to name and address) n Extensible Party Relationships Language (xPRL) to define party relationships namely, person to person, person to organization and organization to organization relationships

15. What is special about CIQ TC Specifications? n The “only set of specifications in industry” that concentrates exclusively on defining Party information standards without any specific industry or applications in mind

16. Applications using Party related data (a sample)

17. 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

18. 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 n Open and vendor neutral

19. 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

20. 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

21. 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

22. 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)

23. Evolution of xNAL Specifications

24. xNAL (xNL + xAL) Model

25. xNL Model

26. xAL Model

27. 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

28. 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

29. 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 Information details - Nationality details- Parent/Spouse/Child details - Visa details - Reference Check details - Habits- Qualification details - Occupation details

30. Evolution of xPIL Specifications

31. xPIL Model

32. 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

33. xPRL – Types of Relationships Person to Person Relationships Household relationships, Contact/Account Management, Personal and Business relationships, Organization structure, etc Person to Organization/Group Relationships Business relationships (e.g. “Doing Business As”, member of, employee-employer, business contacts, etc) Organization/Group to Organization/Group 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

34. Evolution of xPRL Specifications

35. 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

36. 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)

37. 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 for the public and by the pubic

38. Interested to contribute to CIQ TC? n CIQ TC is constantly looking for more members to join this important committee n If you are interested to contribute, please contact l Ram Kumar, Chair, CIQ TC n kumar.sydney@gmail.com

39. OASIS – Customer Information Quality Technical Committee (CIQ TC) http:// www.oasis-open.org/committees/ciq Thank You