The CIO Councils XML Web Services Working Group Kickoff Presentation at the XMLWeb Services Technica - PowerPoint PPT Presentation

1 / 24
About This Presentation

The CIO Councils XML Web Services Working Group Kickoff Presentation at the XMLWeb Services Technica


... given the task of taking the lead in the development of an integrated ... 'Eforms for E-Gov' Pilot Rick Rogers, Fenestra, Team Lead. Education/Analysts: ... – PowerPoint PPT presentation

Number of Views:96
Avg rating:3.0/5.0
Slides: 25
Provided by: Niem


Transcript and Presenter's Notes

Title: The CIO Councils XML Web Services Working Group Kickoff Presentation at the XMLWeb Services Technica

The CIO Councils XML Web Services Working
GroupKickoff Presentation at the XML/Web
Services Technical Exchange Meeting/Conference,MI
TRE Langley, Virginia
  • Brand Niemann
  • XML and Web Services Specialist, US EPA and
  • Chair, XML Web Services Working Group
  • January 28, 2003
  • http//

  • 1. Kickoff Presentation
  • 2. CIO Councils Architecture and Infrastructure
    Committee (AIC)
  • 3. XML Web Services Working Group
  • 4. Eforms for E-Gov Pilot Project
  • 5. Military Pilot Projects
  • 6. Questions and Answers

1. Kickoff Presentation
  • Football
  • A place kick from the 40-yard line of the kicking
    team that puts the ball into play at the
    beginning of each half or after a touchdown or
    field goal.
  • Other
  • A beginning, as of a campaign or drive.
  • Here
  • A new activity at the highest levels of
    government to help us all (individually and
    cooperatively) score a touchdown with XML Web
  • So here goes, and I look forward to your
    returns in the QA time at the end of my
    presentation and in the special Breakout
    Session this afternoon.

2. CIO Councils Architecture and Infrastructure
Committee (AIC)
  • In the News - Federal Computer Week, Architecture
    forms e-gov foundation, December 20, 2002
  • John Gilligan, Air Force CIO and CIOC/AIC
  • Individual commanders have been given the task of
    taking the lead in the development of an
    integrated architecture for each of their
    commands as part of the CIOC/AIC.
  • The architecture has to be relevant and has to be
    relevant immediately. In the past, we have
    developed stuff and it has become shelfware.
  • Interoperability is extremely important -
    architecture is an essential part of Air Force
    operations and we have to define security and
    other attributes of the architecture to allow us
    to have a dialog between the services and our
  • See http//

2. CIO Councils Architecture and Infrastructure
Committee (AIC)
  • AIC Leadership
  • John Gilligan, Air Force CIO, Co-Chair.
  • Debra Stouffer, EPA CTO, Co-Chair (resigning
    January 31st).
  • Norm Lorentz, Federal CTO, OMB, Advisor (and
    acting Co-Chair on February 1st).
  • Jonathan Smith, Chief of Staff, Booz Allen
  • AIC Objectives
  • Integrate OMB and CIOC Architecture Efforts.
  • Develop (simplier) and Consistent Taxonomy and
  • Facilitate Cross-agency Efforts (common meta
    data, tools, etc.).
  • Oversee Operationalization of Architecture

2. CIO Councils Architecture and Infrastructure
Committee (AIC)
  • A Subcommittee Structure Has Been Developed to
    Support These Objectives
  • Governance John Przysucha, ACIO, DOE, and Bob
    Haycock, FEAPMO.
  • Components Reynolds Cahoon, CIO NARA, and Bob
    Haycock, FEAPMO.
  • Emerging Technologies Dawn Meyerriecks, CTO,
    DISA, and Mark Day, DCIO, EPA.
  • Move from Ad-Hoc Efforts to Priority and
    Schedule-Driven Efforts with Committed Staff.
  • Emerging Technologies Working Groups
  • XML Owen Ambur, DOI, and Marion Royal, GSA
  • PKI Judith Spencer, GSA
  • XML Web Services Brand Niemann, EPA
  • Universal Access Susan Turnbull, GSA
  • Directory Services Martin Smith, USITC
  • Standards Barbara Guttman, NIST

2. CIO Councils Architecture and Infrastructure
Committee (AIC)
  • CIO Council Executive Committee Expectations for
    Federal Agency Participation in the AIC
  • Agencies will have senior-level representatives
    to Governance and Components Subcommittees (about
    25 time).
  • Volunteer opportunities exist in the Emerging
    Technologies Subcommittee.
  • Subcommittee participation contributes to
    executive development objectives of CIOC.
  • AIC products will benefit all agencies and
    accelerate movement to CIOC goals.
  • Some Deliverables
  • Update of the FEAF to be the single framework for
    agencies the FEA.
  • Development and support for a Federal
    Government-wide Component Registry.
  • Incubator-funded process of EA Components
    Technologies for very small proof of concept

2. CIO Councils Architecture and Infrastructure
Committee (AIC)
  • FEA Models
  • The Federal Enterprise Architecture is a
    business-focused framework for cross-agency,
    Government-wide improvement.
  • The FEA is being constructed through a collection
    of inter-related reference models designed to
    facilitate cross-agency collaboration, and
    horizontal / vertical information sharing.
  • Collectively, the FEA reference models support
    investment and e-Government planning by providing
    frameworks in which agencies can leverage
    existing services, technologies, and components
    across the Federal Government and provide a
    framework to support the creation and integration
    of cross-agency initiatives and business
  • Governance Performance Reference Model (PRM) and
    the Business Reference Model (BRM).
  • Components Service Component Reference Model
    (SCRM), Data (and Information) Reference Model
    (DRM), and Technical Reference Model (TRM)
  • See http// and http//www.ichnet.or

3. XML Web Services Working Group
  • Chartered by the Federal CIO Council under its
    Architecture and Infrastructure Committee
  • Works with the CIOC/AIC, the OMB Solution
    Architects Working Group (SAWG), and the Industry
    Advisory Council (IAC) to produce incubator pilot
    projects in support of the e-Gov Initiatives that
    use XML Web Services to demonstrate increased
    accessibility and interoperability.
  • See http// for definitions and
  • Recent Press
  • Government Computer News, Working group tests
    tools for Web services, 12/16/02 Vol. 21 No. 34.
  • http//

3. XML Web Services Working Group
  • XML Working Group (started June 2002)
  • Facilitate the efficient and effective use of XML
    through cooperative efforts among government
    agencies, including partnerships with commercial
    and industrial organizations.
  • XML Web Services Working Group (started August
  • Facilitate the use of this emerging technology in
    the e-Government initiatives and in the
    development of the Federal Enterprise
    Architecture in conjunction with the development
    of architectural governance and component
    architectures for the Federal enterprise.

3. XML Web Services Working Group
  • January 14th Meeting
  • 1. Introduction
  • E-Gov Act, CIO Council, and AIC Updates
  • XML 2002 Conference WG Meeting and Exhibit
  • Recent Press
  • 2. Business
  • Web Site
  • ListServ
  • Collaboration Place (Karl Habenstreit and Martin
  • Initial and Proposed Pilots and Priorities
  • Draft IAC/SAWG White Paper
  • Some Coming Attractions
  • Other
  • 3. Presentations
  • a. XML 2002 Conference Video Highlights-Antoinette
    Purdon, Instant Index.
  • b. Priorities/Pilots-Kevin William, Blue Oxides
    Technologies, The XML Collaborator - Industry
    Standards Interoperability (see Next Session).
  • c. Vendors-Jeff Harrison, OpenGIS Consortium, OWS
    1.2 Demonstration and Geospatial One-Stop Portal
  • d. Education/Analysts-Uttam Narsu, Giga
    Information Group, e-Gov Secure Transactions
    Scenario (via telephone at 5-530 p.m.).

3. XML Web Services Working Group
  • 4 of the top 9 priorities of the new XML Web
    Services Working Group are to develop a registry
    and collaboration facility for Web Services in
    support of e-Gov
  • 1. Provide direct support on implementing Web
    Services to 24 e-Gov initiatives.
  • 2. Maintain registry of WS-related projects or
    efforts, to avoid duplication and promote
    information sharing.
  • 3. Implement a registry of available Web Services
    (a loose registry of human-researchable
    information at first, but later supporting
    automated services location).
  • 9. Provide on-line collaboration facility for
    exchange of sample business cases, templates, and
    other info related to Web Services.

3. XML Web Services Working Group
The XML Collaborator ArchitectureA Distributed
Web Service to Build Distributed Web Services
See http// for White Paper and
forthcoming online version.
3. XML Web Services Working Group
  • Next Meeting, February 18th (DRAFT)
  • Business
  • Eforms for E-Gov Pilot Rick Rogers, Fenestra,
    Team Lead.
  • Education/Analysts
  • The Business Case for XML Web Services Scott
    Christiansen, Seattle Pacific University and
    Boeing Company
  • Organizations
  • Integrated XML Topic Map Web Services David
    Brown, IRS, and Michel Biezunski, Coolheads
  • Vendors
  • Office 11 XDocs Web Services for OMB/FEA and
    eForms, Susie Adams, Microsoft
  • Pilots/Priorities
  • E-Forms for E-Gov The Use of XML-based Standards
    Applications, to be announced.
  • XML Data Exchange Across Multiple Levels of
    Government Using Native XML Databases (Tamino 4.1
    with UDDI), Joel Patterson, SoftwareAG.

3. XML Web Services Working Group
Story and Suggestion Number 1
  • Working Nine to Five on Enterprise Architecture
  • The IAC EA-SIG has prepared nine White Papers to
    help implement the five models of the FEA-PMO.
  • Making Web Services a Ten
  • The new IAC WS-SIG is working with the new
    CIOC/XML WS WG to produce a tenth White Paper,
    some best practice examples for the nine White
    Papers, and incubator pilot projects in support
    of the e-Gov Initiatives.
  • Moving It All To the New Three
  • The CIOC/AIC has three new subcommittee where all
    the work will be operationalized.
  • Suggestion Participate in the IAC WS-SIG White
    Papers and the CICO/XML WS WG incubator pilot

3. XML Web Services Working Group
Story and Suggestion Number 2
  • Performing with Agility
  • A service-oriented architecture has components
    that can be loosely-coupled and bound
    just-in-time to produce new applications and
  • Eating Our Own Dog Food
  • Vendors and agencies have to be willing to
    support open standards and open collaboration to
    make this a reality.
  • The Collaboration Environment and Network
  • The XML Collaborator, one of our first incubator
    pilot projects, supports the collaborative
    building and integration of components in a
  • Suggestion Participate in the XML Collaborator
    Pilot by registering your Web Services, hosting a
    distributed node, and/or integrating your Web
    Service components with those of agencies and
    other vendors.

4. Eforms for E-Gov Pilot Project
  • OMB Request to SAWG, December 20, 2002
  • There are too many agency eforms products being
    purchased with a lot of similar problems and a
    lot of redundancy. Are there any products out
    there that can be used to meet Section 508 and
    GPEA and products that we could use for little or
  • CIO Council Vision, Karen Evans, Vice Chair,
    December 2002
  • We will consider publishing a taxonomy for
    government so we can use the same language to
    describe the same concepts and will develop
    standards for XML data definitions so the
    information we create can be shared and accessed
    easily regardless of its origins. (Sent
    endorsement on 12/16/02)

4. Eforms for E-Gov Pilot Project
  • Federal Enterprise Architecture Data and
    Information Reference Model
  • The Data and Information Reference Model (DRM)
    will describe, at an aggregate level, the data
    and information that support program and business
    line operations. The model will aid in describing
    the types of interaction and exchanges that occur
    between the Federal Government and its various
    customers, constituencies, and business partners.
    The DRM will categorize the government's
    information along general content areas and
    decomposes those content areas into greater
    levels of detail.
  • Genesis of the XML Working Group, February 2000,
    and part of budget justification for the XML
    Registry, September 2002
  • With reference to GPEA and the President's E-Gov
    Directive 2, it would also be good to explore
    the use of DTDs and XML schemas to render
    Standard and Optional Forms not only for ready,
    non-proprietary exchange of data with databases,
    but also for preservation as records (preferably
    in DoD-certified ERMSs) for the appropriate
    periods of time.

4. Eforms for E-Gov Pilot Project
  • Paperwork Reduction Act of 1995 and the
    Government Paperwork Elimination Act of 1998
  • GPEA requires Federal agencies, by October 2003,
    to allow individuals or entities that deal with
    the agencies the option to submit information or
    transact with the agency electronically, when
    practicable, and to maintain records
    electronically, when practicable. The Act
    specifically states that electronic records and
    their related electronic signatures are not to be
    denied legal effect, validity, or enforceability
    merely because they are in electronic form, and
    encourages Federal government use of a range of
    electronic signature alternatives.

4. Eforms for E-Gov Pilot Project
  • Some Recent Developments
  • XML 2002 Conference, December 8-13, 2002
  • XML for the masses
  • Bringing the XML Vision to the Desktop With
    'Office 11.
  • XML For The Masses - An XML Based File Format for
    Office Documents (OpenOffice).
  • XML in Adobe Document and Data Publishing
    (Acrobat 6 XML).
  • Latest News on XForms and XHTML.
  • Air Force rolling out XML-based e-forms, Federal
    Computer Week, November 18, 2002.
  • See http//
  • XML Working Group, February 19, 2003 USAF Forms
    Automation Project Abraham Coy, USAF Bruce
    Lyman, EIM Steve Jacek, PureEdge.
  • Microsofts Ballmer Welcomes XDocs to Office
    Family, ComputerWorld, October 9, 2002.
  • http//

4. Eforms for E-Gov Pilot Project
  • A Joint SAWG/XML and XML Web Services WG Pilot
    Project with High Priority
  • Involve the major players
  • XML Working Group (Owen Ambur and Marion Royal)
  • GSA (Jan Wendler)
  • Microsoft XDocs (Jean Paoli and Susie Adams)
  • Sun OpenOffice (Daniel Vogelheim)
  • W3C XForms (Micah Dubinko) and Accessibility
    Initiative (Janina Sajka and Al Gilman)
  • Adobe (Peter Kacandes)
  • US Agencies and e-Gov Initiatives (Charles
    Havekost, e-Grants, Diane Lewis, DOJ, etc.)
  • OASIS E-Government Technical Committee (John
    Borras) and Universal Business Language Technical
    Committee (Jon Bosak)
  • Industry Advisory Council (IAC) WS-SIG (John
  • More to come.

4. Eforms for Egov Pilot Project
  • Update
  • Many comments were received and were used to
    design the initial pilot (see ListServ).
  • Rick Rogers, CEO of Fenestra, was selected to
    lead the initial pilot and he may select a
  • The basic steps are
  • (1) selection of about 6-12 forms.
  • (2) production of the XML Markup and Schema for
    those forms.
  • (3) distribution of the pilot forms to the
    participants and their registration in the XML
  • (4) review and scheduling of proposed
    presentations using the pilot forms.
  • (5) periodic meetings to discuss the process,
    results, and next steps.
  • A status report and at least one presentation
    will be made at the next WG meeting on February
  • The OMB/SAWG and the CIOC/AIC will be kept
    abreast of this high priority pilot project.

5. Military Pilot Projects
  • One of six initial pilot projects at the
    suggestion of John Gilligan, Air Force CIO and
    Co-chair, CIOC/AIC
  • October 23, 2002, Military Systems Air Force
  • Paul Kim, Chief Technologist, MITRE, Bedford, MA.
  • See http// Web
  • January 28, 2003, MITRE XML/Web Services Meeting,
    Special Breakout Session, 315-445, Room 108.
  • January 15, 2003, XML Working Group,
    Registry/Repository Team Meeting Suggestion
    Integration of the Three DOD/DLA Registries and
    the DOD XML Registry with the XML Collaborator.

6. Questions and Answers
  • Your turn to let me know how I and the new WG can
    help you score a touchdown with XML Web
Write a Comment
User Comments (0)