OASIS – Customer Information Quality (CIQ) January 2004 John Glaubitz Member, OASIS CIQ TC.

Slides:



Advertisements
Similar presentations
1 An Update on XML.org Registry and Repository Una Kearns Documentum, Inc.
Advertisements

Who am I? Senior Researcher of The National Library of Korea (2007 ~ )
XML in the Emerging U.S. Federal Information Architecture Presented by Eliot Christian, USGS April 30, 2003.
Copyright © OASIS, 2000 Onwards OASIS Customer Information Quality Technical Committee – Overview Ram Kumar Founding Chairman October 2008
OASIS Customer Information Quality Technical Committee – Overview Ram Kumar Founding Chairman Ram Kumar Founding Chairman March 2008
Co-Registration.  Industry’s Most Advanced System  Real-Time Data Hygiene Dynamic Offer Targeting/Optimization Secondary Questions & B2B Support XML.
UDDI v3.0 (Universal Description, Discovery and Integration)
INTER-OPERABILITY IN THE NEW ZEALAND EDUCATION SECTOR USING A SECTOR DATA MODEL DRIVEN METHODOLOGY Presented on April at the New Zealand State.
SPML Core Identity Schema A discussion document. Agenda What is the core identity schema? Source materials Proposed schema.
OASIS – Customer Information Quality Technical Committee (CIQ TC) January 2003 Ram Kumar Chairman, OASIS CIQ TC.
Copyright © Open Applications Group, Inc. All rights reserved 1 OAGi XML Schema User Report June 21, Michael.
3/5/2009Computer systems1 Analyzing System Using Data Dictionaries Computer System: 1. Data Dictionary 2. Data Dictionary Categories 3. Creating Data Dictionary.
TC3 Meeting in Montreal (Montreal/Secretariat)6 page 1 of 10 Structure and purpose of IEC ISO - IEC Specifications for Document Management.
Database Features Lecture 2. Desirable features in an information system Integrity Referential integrity Data independence Controlled redundancy Security.
System Integration (Cont.) Week 7 – Lecture 2. Approaches Information transfer –Interface –Database replication –Data federation Business process integration.
A Use Case for SAML Extensibility Ashish Patel, France Telecom Paul Madsen, NTT.
OCLC Online Computer Library Center A Global OpenURL Resolver Registry Phil Norman OCLC Dlsr4lib Workshop March 23 rd, 2006 Arlington VA.
Overview What are the provisioning methods used in the Australian registry system? How are these provisioning systems secured?
Procedures to Develop and Register Data Elements in Support of Data Standardization September 2000.
Just a collection of WS diagrams… food for thought Dave Hollander.
Copyright OASIS, 2001 OASIS Election & Voter Services Technical Committee John Borras Office of e-Envoy Cabinet Office UK Government May 2002.
ICS – FORTH, August 31, 2000 Why do we need an “Object Oriented Model” ? Martin Doerr Atlanta, August 31, 2000 Foundation for Research and Technology -
WG2 Tutorial ISO/JTC1/SC32 Larry Fitzwater (202) SDC JE-4029.
AIXM 5.1 Seminar 12 – 13 December 2011
Addressing Metadata in the MPEG-21 and PDF-A ISO Standards NISO Workshop: Metadata on the Cutting Edge May 2004 William G. LeFurgy U.S. Library of Congress.
CompuBase Data for CRM / PRM Integration How compuBase fits to an existing CRM / PRM system? Last review 25/03/2007.
U.S. Department of the Interior U.S. Geological Survey NWIS, STORET, and XML National Water Quality Monitoring Council August 20, 2003.
Larry Fitzwater, U.S. EPA Judith Newton, NIST Lois Fritts, SAIC January 17, 2000 Open Forum on Metadata Registries Santa Fe, NM SDC JE-2026.
Copyright OASIS, 2002 OASIS Topic Maps Technical Committees Standards Update Presentation Knowledge Technologies Conference Seattle , March 11 Bernard.
Sharing Your Data – An Update on AIRS XML and Helpful Tools Marianne Galleon – 211 LA County (626) x2122,
Facility Registry System and the Exchange Network Pat Garvey OEI/OIC May 2000.
Health information that does not identify an individual and with respect to which there is no reasonable basis to believe that the information can be.
Introduction to the Controlled Trade Markup Language (CTML) Technical Committee May, 2002.
SDC JE-Matsue May 1999 Bruce Bargmeyer U.S. Environmental Protection Agency Tel: (202) WWW URL:
Interoperability Standards at Levels of Syntax and Semantics Presented by Eliot Christian at the First Meeting of WMO / CBS / ISS / ET-ADRS (Expert Team.
New Member Orientation Boston Quarterly April 2003 Kim Bartkus.
Possible elements of the technical standards Pre-sessional consultations on registries Bonn, 2-3 June 2002 Andrew Howard UNFCCC secretariat
Dr. Bhavani Thuraisingham October 2006 Trustworthy Semantic Webs Lecture #16: Web Services and Security.
SDC JE-8019 February 16, 1999 Bruce Bargmeyer EPA/OIRM/EIM Division Tel: (202) WWW URL:
Metadata and Geographical Information Systems Adrian Moss KINDS project, Manchester Metropolitan University, UK
U.S. Department of the Interior U.S. Geological Survey NWIS, STORET, and XML Advisory Committee on Water Information September 10, 2003 Kenneth J. Lanfear,
Cooperating Registries Draft Content for OASIS/ebXML Reg/Rep f2f November 1, 2001 Bruce Bargmeyer (510)
Address Levels Business Use Alignment. Introduction Objective is to provide layers of address granularity tailored to business use Address use levels.
1 Global Address Verification Overview Bud Walker, Admound Chou.
CS370 Spring 2007 CS 370 Database Systems Lecture 4 Introduction to Database Design.
FEA Data and Information Reference Model (DRM): the Interoperability Message Presented by Eliot Christian, USGS based on work of ISO/IEC JTC1/SC32 Data.
Luxembourg, 13 October 2008 ITDG Giuseppe Sindoni, Istat, Italy 2011 Census innovations, the 2009 pilot Census and some technological implications.
XML Engr. Faisal ur Rehman CE-105T Spring Definition XML-EXTENSIBLE MARKUP LANGUAGE: provides a format for describing data. Facilitates the Precise.
OASIS CIQ TC ServiceStream CIQ Product Briefing. Journée Software Journée recognized as an “early mover” in the customer data management market Journée.
Overview of SC 32/WG 2 Standards Projects Supporting Semantics Management Open Forum 2005 on Metadata Registries 14:45 to 15:30 13 April 2005 Larry Fitzwater.
SDC JE-2027 January 18, 2000 Bruce Bargmeyer Chair, SC 32 – Data Management and Interchange U.S. Environmental Protection Agency Telephone: (202)
Data Registry to support HIPAA standards The Health Insurance Portability and Accountability Act of 1996 Title II - Subtitle F Administrative Simplification.
SDC JE-xxxx September 1999 Bruce Bargmeyer U.S. Environmental Protection Agency Tel: (202) WWW URL:
2003 © SWITCH Authentication and Authorisation Infrastructure - AAI Christoph Graf Project Leader AAI SWITCH.
Concept Proposal Sixth Open Forum on Metadata Registries Semantic Interoperability between Registries To be held January 20-24, 2003 Bruce Bargmeyer
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
Silverstein Group Presenter Moshe Silverstein A Content Assembly Mechanism Technology Overview Context & Integration A Content Assembly Mechanism Technology.
International/Interagency Collaboration – IT for Environmental Information & Environmental Data Exchange Network Copenhagen, Denmark April 25, 2002 Bruce.
Part of the Cronos Group 4C/kZen 4 th EcoTerm meeting, Vienna, April 18, 2007 Jef Vanbockryck Research & Development “Risk Assessment ontologies and data.
OASIS Customer Information Quality Technical Committee – Overview Ram Kumar Founding Chairman Ram Kumar Founding Chairman February 2007.
Metadata Schema Registries: background and context MEG Registry Workshop, Bath, 21 January 2003 Rachel Heery UKOLN, University of Bath Bath, BA2 7AY UKOLN.
Chief Security Officers List
Concept Presentation Sixth Open Forum on Metadata Registries To be held January 20-24, 2003 Bruce Bargmeyer
Florida Department of Business and Professional Regulations Ken Lawson Juana Watkins Secretary Director Division of Real Estate.
Geospatial metadata Prof. Wenwen Li School of Geographical Sciences and Urban Planning 5644 Coor Hall
ISO/IEC Past, Present, Future -- A Thumbnail Sketch
Ecoinformatics Technical Projects Workgroup
Data Model.
Legal Entity Identifier Standard and Global LEI System Implementation
CDC SOFTWARE CRM USERS & MAILING DATABASE
Presentation transcript:

OASIS – Customer Information Quality (CIQ) January 2004 John Glaubitz Member, OASIS CIQ TC

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, , 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

Name and Address Complexity 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

xNAL: Goals Application/Domain Independent Truly “Global” international specification 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

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

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 Solutions 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

Address Use Level Defined –Level 0 = handwritten postal address – machine parsed –Level 1 = “last line” - city, state, zip+ (postal code) or foreign country –Level 2 = in country simple postal address – concatenated delivery address line(s) –Level 3 = extended postal address – advanced features »3A = Non-address - business volume (bulk) »3B = delivery address field s (atomic) –Level 4 = Rendering only - external or business to business use, e.g., shipping / delivery/bill to/marked for/in care of –Level 5 =management – advanced features »5A = internal management »5B = international management

Address Horizontal and Vertical Authoritative Source & Use Matrix A = Government (Domestic) B = Vendor C = International Organization D = Customer E = Consortiums D A B, D, E A C & A Top = Authoritative source Bottom = User and Implementers A, B D B, E A, B, C, E A, C, E

xNAL: Flexibility in Design 23 Archer Street Chatswood, NSW 2067 Australia Option 1: 23 Archer Street Chatswood, NSW 2067 Australia Example: Adhoc/Simple user registration, etc

Option 2: Australia NSW Chatswood Level 12, 67 Albert Avenue 2067 Example: Call Centre, user registration on web, etc

Option 3: Australia NSW Chatswood 23 Archer Street 2067 Example: Address Database Indexing and Searching, etc

Option 4: Australia NSW Chatswood <Thoroughfare Type=“Street” NumberType=“single”> 23 Archer Street 2067 Example: Address Parsing/Validation, Data Quality, etc

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

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 - /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

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

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

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

Ontological Registry Concept Geographic Area Geographic Sub-Area Country Country Identifier Country NameCountry Code Short Name ISO Character Code ISO Character Code Long Name Distributor Country Name Mailing Address Country Name ISO Numeric Code FIPS Code

Example of Common Content Country Identifier Data Elements DZ BE CN DK EG FR... ZW ISO 3166 English Name ISO Numeric Code ISO Alpha Code Algeria Belgium China Denmark Egypt France... Zimbabwe Name: Context: Definition: Unique ID: 4572 Value Domain: Maintenance Org. Steward: Classification: Registration Authority: Others ISO 3166 French Name L`Algérie Belgique Chine Danemark Egypte La France... Zimbabwe DZA BEL CHN DNK EGY FRA... ZWE ISO Alpha Code Algeria Belgium China Denmark Egypt France... Zimbabwe Name: Country Identifiers Context: Definition: Unique ID: 5769 Conceptual Domain: Maintenance Org.: Steward: Classification: Registration Authority: Others Data Element Concept

CIQ Specifications - Customers (Implemented/Implementers/Interested) Vendors (e.g. Information Quality, XML, CRM) Consortiums XML Standards Groups (e.g. UBL, Election Services, Human Markup, etc) Governments (e.g. UK/NZ/AUS e-government, Defense) Publications Industry Solution Providers Telecommunications Industry Standard Groups Private/Public Organisations Partial list of users of the CIQ specifications:

A Message from the CIQ Chairman The important thing is the true "global" nature of the schemas. Organisations use name and address and other customer data for various purposes and this includes tax. For true interoperability to occur, the customer data has to be represented on a single "standard" that can be used as the basis to cover various applications that use the customer data. CIQ specifications have been designed to precisely do this. CIQ specs have been used by various applications ranging from simple web site registration to e-government. In addition, CIQ specs have been used by UBL. Rather than looking at the short term view of using a customer spec that is very specific and is not truly global, TaxXML should look at the long term usefulness of its specs, that will hopefully be "the" specs for Tax around the world. This is where CIQ specs fit very well with the tax XML goals. - Ram Kumar

Further Information about CIQ (specs., schemas, examples, publications, press releases, presentations, etc – All free downloads)