1 / 30

OASIS – Customer Information Quality Technical Committee (CIQ TC)

OASIS – Customer Information Quality Technical Committee (CIQ TC). January 2003 Ram Kumar Chairman, OASIS CIQ TC. Organisation for Advancement in Structured Information Standards (OASIS).

jelani-holloway
Download Presentation

OASIS – Customer Information Quality Technical Committee (CIQ TC)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OASIS – Customer Information Quality Technical Committee (CIQ TC) January 2003Ram KumarChairman, OASIS CIQ TC

  2. Organisation for Advancement in Structured Information Standards (OASIS) “OASIS provides a framework for XML interoperability that is critical to the future success of electronic business. OASIS puts the control of XML specifications firmly in the hands of those who will use them” Jon Bosak, Sun Microsystems “Father of XML” Organizer of the Working Group that Created XML Chair of “Universal Business Language” TC of OASIS

  3. OASIS - Overview • OASIS is a member consortium dedicated to building systems interoperability specifications • Focuses on industry applications of structured information standards, such as XML, SGML, and CGM. Founder of ebXML • Members of OASIS are providers, users and specialists of standards-based technologies and include organizations, individuals and industry groups. • International, Not-for-profit, Open, Independent. Runs XML.org • Successful through industry-wide collaboration • Works relationships with International Standard Bodies such as ISO, UN/CEFACT, IEC, ITU and UN/ECE

  4. Access360 Adobe Systems, Inc. AND Data Solutions B.V. Arbortext, Inc. Auto-trol Technology Corporation Aventail Corp. Baltimore Technologies B-Bop Associates BEA Systems Inc. Bentley Systems Boeing Commercial Airplanes Bowstreet Bridge Chrystal Software Cohesia Corporation Commerce One Critical Path DataChannel, Inc. Dataloom, Inc. Deutsche Post AG Documentum EADS Airbus SA empolis Enigma Incorporated Excelergy Corporation eXcelon Corporation Extensibility Extricity Software First Call Corporation Hewlett-Packard Company IBM Corporation Informix Software, Inc. Infoteria Inc. Innodata Corporation Interwoven, Inc. IPNet Solutions ITEDO Software GmbH Jamcracker Logistics Mgmt Institute Mediaplex Mercator Software Microsoft Corporation MSI Business Solutions Netegrity, Inc. Netfish Technologies Netscape/AOL NextPage, LC NII Enterprise Prom. Assoc. Nimble Technology NIST Novell ObjectSpace Oracle Pearson Education Planet 7 Technologies Popkin Software & Systems Reuters Limited Sabre SAP Sequoia Software Corporation Silverstream Software SoftQuad Software Inc. Software AG Sterling Commerce StreamServe, Inc. Sun Microsystems Synth-Bank The Tamalpais Group, Inc. Thomas Technology Solutions U. S. Defense Information Systems Agency Virtual Access Networks Visa International Wavo, Inc. webMethods, Inc. Whitehill Technologies, Inc. Xerox Corporation XML Global XMLSolutions Corporation Xyvision Enterprise Solutions Inc. OASIS Members – 600+Membership grew by 41% in 2001

  5. Background about CIQ TC • “Officially” founded in late 2000 at XML 2000 Conference in Washington DC • Work on CIQ standards started “informally” in early 2000 • Technical Committee Members from Asia-Pacific, Europe, UK, and USA • Over 600 members of OASIS have a say on the work of the committee • Founding Chairman, Ram Kumar of MSI Business Systems Pty. Ltd, Australia

  6. CIQ TC Goals/Objectives • The CIQ standards will be open, vendor neutral, application independent and “global” • The CIQ TC will not concentrate on building standards in the areas of Privacy, Security, Messaging, Transporting, Routing, etc. including domain specific applications of customer data as many other groups are working on this • The CIQ TC will advocate and establish relationships with other groups working on similar activities to do joint work in an “open” process in order to avoid duplicity • The CIQ TC will be open to public for feedback, criticisms, comments, and suggestions • The CIQ will work in a truly “open” process environment to build the customer information standards

  7. CIQ TC Goals/Objectives

  8. CIQ TC Customer Information Standards • Extensible Name and Address Language (xNAL) • Extensible Name Language (xNL) to define a customer’s name (person/company) • Extensible Address Language (xAL) to define a customer’s address(es) • Extensible Customer Information Language (xCIL) for defining a customer’s unique information (tel, e-mail, account, url, identification cards, etc. in addition to name and address) • Extensible Customer Relationships Language (xCRL) to define customer relationships namely, person to person, person to organisation and organisation to organisation relationships • “x” in xNAL, xCIL, and xCRL means “extensibility” of the standards

  9. Name and Address: What is the big deal about it? • The most complex “customer” data, but the most important data for customer identification • 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 geography, culture, race, religion, language, etc • Addresses of 241+ Countries • Represented in 5,000+ languages • With about 130+ Address Formats • With about 36+ Personal Name formats

  10. xNAL : Goals • Application/Domain Independent • Truly “Global” international standard • Flexiblity in design to help any simple application (eg. Simple user registration) to complex application (eg. Address parsing and validation) to use xNAL to represent customer name and address data • Follow and adopt XML industry standards (eg. XML 1.0, W3C Schema, W3C DTD, etc) and not vendor specific XML standards (eg. XDR Schema) • Open and vendor neutral

  11. xNAL: Application Independency • The CIQ standards will not be specific to any application/domain, say, Postal services, Mailing, CRM, Address Validation, etc • The CIQ Standards will provide the customer 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 standards and build their own standards on top of it that is specific to its postal business • Any domain specific application can use CIQ standards and build applications around it that meets its business requirements

  12. xNAL: “Global” Standard • 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

  13. 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) • Initially used the Name and Address XML Standard of MSI Business Systems and Global Address XML Standard of AND Solutions • 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 (eg. 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 xNAL took about 2 years and is still evolving

  14. xNAL: How different is it from other similar efforts? Other Efforts: GCA-ADIS, CEN WG331, ECCMA/UN-PROLST* • Other efforts in defining name and address standards are application or domain specific (eg. Postal services, specific to a country’s names and addresses) • xNAL is the world’s first truly global, open, vendor neutral and application/domain independent standard for name and address language • 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) • Supports Postal Service specific elements also (eg. ECCMA Code Tables)

  15. xNAL: Flexibility in Design 23 Archer Street Chatswood, NSW 2067 Australia Option 1: <AddressDetails> <AddressLines> <AddressLine>23 Archer Street</AddressLine> <AddressLine>Chatswood, NSW 2067</AddressLine> <AddressLine>Australia</AddressLine> </AddressLines> </AddressDetails> Example: Adhoc/Simple user registration, etc

  16. Option 2: <AddressDetails> <AddressLine Type=“Country”>Australia</AddressLine> <AddressLine Type=“AdministrativeArea”>NSW</AddressLine> <AddressLine Type=“Locality”>Chatswood</AddressLine> <AddressLine Type=“Thoroughfare”> Level 12, 67 Albert Avenue</AddressLine> <AddressLine Type=“Postal Code”>2067</AddressLine> </AddressDetails> Example: Call Centre, user registration on web, etc

  17. Option 3: <AddressDetails> <Country> <CountryName>Australia</CountryName> <Locality> <LocalityName>NSW</LocalityName> <DependentLocality> <DependentLocalityName>Chatswood</DependentLocalityName> <Thoroughfare> <ThoroughfareName>23 Archer Street</ThoroughfareName> </Thoroughfare> </DependentLocality> <PostalCode> <PostalCodeNumber>2067</PostalCodeNumber> </PostalCode> </Locality> </Country> </AddressDetails> Example: Address Database Indexing and Searching, etc

  18. Option 4: <AddressDetails Address Type= “Postal”> <Country> <CountryName>Australia</CountryName> <Locality> <LocalityName NameType="Abbreviation">NSW</LocalityName> <DependentLocality Type="Suburb"> <DependentLocalityName>Chatswood</DependentLocalityName> <Thoroughfare Type=“Street” NumberType=“single”> <ThoroughfareNumber NumberNameOccurrence=“Before”>23</ThoroughfareNumber> <ThoroughfareName>Archer</ThoroughfareName> <ThoroughfareTrailingType>Street</ThoroughfareTrailingType> </Thoroughfare> </DependentLocality> <PostalCode> <PostalCodeNumber>2067</PostalCodeNumber> </PostalCode> </Locality> </Country> </AddressDetails> Example: Address Parsing/Validation, Data Quality, etc

  19. xNAL: Examples More international address examples using xNAL is available at http://www.oasis-open.org/committees/ciq Different types of international addresses are covered by xNAL: 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, tracks address changes, etc

  20. xNAL: Status • xNAL V1.0 (includes xNL V1.0 and xAL V1.0) released in March 2001 • Ratified as “OASIS Committee Spec.” in September 2001 • Available as DTD and W3C Schema implementations • Current Version: xNLV2.0, xALV2.0, xNALV2.0 • Version 2.0 released in July 2002

  21. xCIL • Represents Other Customer Information – extends xNAL • Customer : A Person or an Organisation (Organisation: Company, not for profit, Consortiums, Groups, Government, Clubs, Institutions, etc) • Only concentrates on customer-centric information that helps to uniquely identify a customer (NOT data such as transactions) • Does not concentrate on privacy issues, security, messaging, transportation, etc. • Application independent, open and vendor neutral • Flexibility for simple representation of data to detailed representation of the data depending upon the need

  22. xCIL : Supported Customer-Centric Information • - Name details - Occupation details • - Address details - Qualification details • - Customer Identifier - Passport details • - Organisation 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

  23. xCIL Standards – Status • xCIL V1.0 released in June 2001 • Ratified as “OASIS Committee Spec.” in July 2002 • Available as DTD and W3C Schema implementations • Current Version: xCILV2.0 using xNLV2.0 and xALV2.0 • Version 2.0 released in July 2002

  24. xCRL • Extends xCIL and xNAL by defining relationships between two or more customers • First XML Standard in industry for managing Customer Relationships • Helps ease existing complex integration between CRM systems/software and with back-end systems • Only concentrates on Customer to Customer Relationships • Does not concentrate on privacy issues, messaging, transportation, security, etc. • Application independent, open and vendor neutral • Flexibility for simple representation of data to detailed representation of the data depending upon the need

  25. xCRL – Types of Relationships • Person to Person Relationships • Household relationships, Contact/Account Management, Personal and Business relationships, Organisation structure, etc • Person to Organisation/Group Relationships • Business relationships (eg. “Doing Business As”, member of, employee-employer, business contacts, etc) • Organisation/Group to Organisation/Group Relationships • Parent-Subsidiary relationships, Head office-Branch relationships, Partnership relationships(eg. Alliance, Channel, Dealer, Supplier, etc), “member of” relationships, “Trading As”, “In Trade for” type relationships, etc

  26. xCIL Standards – Status • xCILV1.0 released in December 2001 • Ratified as “OASIS Committee Spec.” in July 2002 • Available as DTD and W3C Schema implementations • Current Version: xCRLV1.1 using xNLV2.0, xALV2.0 and xCILV2.0 • Version 1.1 released in July 2002

  27. MSI’s Universal Name and Address Standard (UNA) + Name and Address Markup Language (NAML) AND Solution’s Global Address XML Standard xNL xAL MSI’s Customer Identity Markup Language (CIML) MSI’s Customer Relationships Markup Language (CRML) xCRL Evolution of CIQ Standards xNAL xCIL

  28. CIQ Standards - Customers (Implemented/Implementers/Interested) • Vendors (eg. Information Quality, XML, CRM) • Consortiums • XML Standards Groups (eg. UBL, Election Services, etc) • Governments (eg. e-government) • Publications Industry • Solution Providers • Telecommunications Industry

  29. For further information about CIQ TC(specs., schemas, examples, publications, press releases, presentations, etc – All free downloads) http://www.oasis-open.org/committees/ciq About OASIS :http://www.oasis-open.org CIQ TC Chair Contact: rkumar@msi.com.au

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

More Related