SPEEDING UP THE STANDARDS DEVELOPMENT PROCESS Standards Coordination

SPEEDING UP THE STANDARDS DEVELOPMENT PROCESS Standards Coordination Conference Don Deutsch, Vice President Standards Strategy & Architecture Oracle Corporation 10 July 2002

SETTING THE STAGE Ÿ QUESTION – How is the IT standards community dealing with the need for speed in standards development? Ÿ CONTEXT – De Jure (formal) standards process Ÿ Domestic US: ANSI/INCITS Ÿ International: ISO/IEC JTC 1 – SQL database language Ÿ PERSPECTIVE – – Not a Standards Development Organization (SDO) Process participant/Technical committee chair

USING A DE JURE FORUM Ÿ PROS – – – Open/Level playing field Low cost of entry Due process Recognized results Ÿ ANSI/INCITS Ÿ ISO/IEC JTC 1 Life-cycle process Ÿ Maintenance Ÿ Interpretations Record of Success (e. g. SQL) Ÿ CONS – – – Too open Money is no problem Too bureaucratic Ÿ Slow Ÿ Want to retain control De jure brand not necessary Want “standard” ASAP and will “turn over” to formal body when done Major failures (e. g. , OSI)

INCITS: ANSI ACCREDITED SDO Three Paths to IT Standards 1. Technical Committee Development Technical experts collaborate within groups dedicated to one or more projects to develop an American National Standard. 2. Entry into the International Standards Arena INCITS experts form U. S. delegations to the international committees developing IT standards 3. "Fast Track" Externally Developed Standards INCITS accepts candidate standards that were developed by external bodies for adoption as American National Standards. Mix and Match Depending on Situation/Needs

INCITS TECHNICAL COMMITTEE PROCESS IMPROVEMENTS Ÿ Eliminated or reduced times for – – Ballots Internal process reviews Ÿ Parallel Processing Ÿ TC Officer Empowerment – – – TC can establish new project TC Chair can create sub-group TC Chair can appoint sub-group chair Ÿ Reduced Number of Steps from 19 to 8 Ÿ Best Case to ANS: Reduced from 22 to 9 Months

INCITS: TECHNICAL COMMITTEE DEVELOPMENT PROCESS Ÿ Traditional Multi-step Process 1: Project Proposal Approval – 2: Public Notification – 3: Technical Development – 4: Public Review(s) – 5: Management Review ----------------– 6: INCITS Approval – 7: ANSI Approval – 8: Publication –

INCITS FAST TRACK PROCESS Ÿ 1: Fast Track Submission – – – Proposal Memorandum of Understanding INCITS vote to accept Ÿ 2: Public Review of Specification ---------------------Ÿ 3: INCITS Approval Ballot Ÿ 4: ANSI Approval Ÿ 5: Publication

INCITS/H 2 Database Committee Ÿ SQL is the Lingua Franca for Database Access Ÿ SQL Database Language Standards – – – 1986 1989 1992 Various Addenda + New Parts 1993 -1998 SQL 1999 Working toward SQL 2003 Ÿ Parallel (and different) Multi-step Processes Used Within ANSI/INCITS & ISO/IEC JTC 1

SQLJ: Using Java™ & SQL Together Ÿ SQLJ-Part 0: Embedding SQL Statements in Java™ – – – Just one more language binding (e. g. , Fortran, C) Multi-step development process Approved as Part 10 of SQL standard in 1998 Ÿ Vendor Consensus Re: Need for New Capabilities – – SQLJ-Part 1: SQL Routines Using Java™ SQLJ-Part 2: SQL Types Defined Using Java™ Ÿ Decision to Progress via INCITS Fast Track – – All vendors were/would be implementing SOON Single specifications preferred to vendor specific interfaces

Timeline for SQLJ-Part 1: SQL Routines using the Java™ Programming Language Ÿ September 25, 1998 - Submission to INCITS of Proposal for both Parts 1 & 2 Ÿ April 1999 - SQLJ-Part 1 specification submitted (7 months late) Ÿ April 2, 1999 - INCITS meeting vote to accept for processing Ÿ April 23 - June 7, 1999 - 45 -day Public Review (1 comment received and responded to by SQLJ) Ÿ July 7, 1999 - INCITS Management Review and document preparation for final publication Ÿ August 11 - September 10, 1999 - INCITS 30 -Day Ballot Ÿ September 1999 - Approval and Publication as an American National Standard

SQLJ-Part 1: Retrospective Evaluation Good/Bad/Ugly Ÿ Good – Industry consensus – INCITS H 2 willing to accept maintenance Ÿ Bad – Process had to wait (7 Months) for specification developers Ÿ Ugly – Comment came from specification developer Approved/Published ANSI Standard - 12 Months from initiation, 5 months from specification submission

Timeline for SQLJ-Part 2: SQL Types Defined Using the Java™ Programming Language Ÿ September 25, 1998 - Submission to INCITS of Proposal for both Parts 1 & 2 Ÿ April 1999 - SQLJ-Part 1 specification submitted (7 months late) --------------------------------Ÿ July 9, 2000 - SQLJ Part 2 specification submitted Ÿ August 11 - September 25, 2000 - 45 -day Public Review Ÿ September 27 - October 27, 2000 - INCITS 30 -Day Ballot Ÿ November 1 - Approval as an American National Standard Ÿ November 22 – Available for Sale (Published)

SQLJ-Part 2: Retrospective Evaluation Fast Track is Better the Second Time Around Ÿ Continued the Good – Industry Consensus – H 2 in loop and willing to maintain Ÿ Eliminated Ugly – No comments from specification developers Ÿ Better Understanding of Process by – Specification developers – Technical committee (H 2) 5 Months from specification submission to Approved/Published ANSI Standard

INCITS FAST TRACK FOR SQLJ: SUMMARY Ÿ Fast Track Works: – Industry Consensus – Complete Specification – TC Willing to Maintain – Demand/Marketplace Pull Ÿ ANSI/INCITS Standard BEFORE Submit to ISO/IEC Ÿ Loose Coupling with TC: – Facilitates concentrated work by small group – Opens process to those with focused interest Ÿ Model for Future Focused Efforts

MY UNSOLICITED RESPONSES TO SYMPOSIUM QUESTIONS Ÿ Does the IT industry face special challenges that impair its ability to compete domestically or internationally? – – Short product cycles Need to maintain world-wide industry leadership Ÿ Should the IT industry shift more towards using consortia-developed standard? – It’s NOT a question of should; the industry IS using a spectrum of standards development mechanisms increasingly including consortia, joint-development agreements, etc. as well as formal SDOs

MY UNSOLICITED RESPONSES TO SYMPOSIUM QUESTIONS (Continued) Ÿ Does the recognition of consortia-developed standards present difficulties for businesses outside IT-related fields? – Possibly, YES. Consortia may NOT include ALL interested parties from both within and outside IT. Ÿ How is the IT standards community dealing with the need for speed in standards development? – See my presentation & those from other accredited SDOs Ÿ How are Federal agencies using IT standards? – They MAY be using but they are LESS active/visible in consortia and standards development forums

MY UNSOLICITED RESPONSES TO SYMPOSIUM QUESTIONS (Continued) What will it take to get the Standards Developer Organizations and consortia to work together? Demand pull – from technology users and providers “We have met the enemy and he is us!” Walt Kelly, Comic Strip POGO