XML Web Services Working Group May 14, 2003

1
XML Web Services Working GroupMay 14, 2003

• Brand Niemann, Chair
• National Science Foundation, Stafford II
  Building, 4121 Wilson Blvd., Room 555
• Ballston, Virginia
• 2 p.m. 5 p.m.

2
Agenda

• 1. Introduction
• Updates.
• Some Coming Attractions and Announcements.
• Special Recognition and Introductions.
• 2. Business
• Report on State and Homeland Security Practices
  and Federal Working Group Coordination Database
  Web Service, James Mackison, GSA Office of
  Citizen Services.
• Report on Discussions of Topic Maps, RDF, and
  Semantic Web, Ralph Hodgson, TopQuadrant, Inc.
  and others.
• 3. Presentations
• Organizations Justice XML Data Model and Data
  Dictionary, Ken Gill, Department of Justice.
• Pilot Project The MetaMatrix System for
  Model-driven Integration with Enterprise
  Metadata, Ed Fakler, MetaMatrix.
• Pilot Project XML Web Services Content
  Authoring the State of the Chesapeake Bay Report
  (XMetal and Smart Graphics Studio), Scott
  Edwards, Corel.
• Pilot Project Client-Side XML Web Services for
  the Chesapeake Bay Program, Joe Brophy, Object
  Builders.

3
1. Introductions

• Updates
• Federal Enterprise Architecture
• Data and Information Reference Model (DRM) In
  Process
• Third All-day Offsite May 19th. See Suggestions
  for Strengthening the Federal Enterprise
  Architecture (FEA) Data and Information Reference
  Model (DRM) (see slides 4-11).
• CIO Council
• Architecture and Infrastructure Committee
• Presentation on Components Activities of the
  Emerging Technology Subcommittee to the
  Governance and Components Subcommittees and the
  full Committee, April 17th. (See slides 12-19).
• Discussion of Budgets and Funding Options (see
  slide 20).
• Emerging Technology Subcommittee
• Finalized Work Plan and Budgets on April 11th.
  Discussion of next steps, scope, etc. on May 2nd.

4
Strengthening the Federal Enterprise Architecture
(FEA) Data and Information Reference Model (DRM)

• Overview
• The Data and Information Reference Model needs
  to
• (1) Specify the use of XML for universal access.
• (2) Specify XML Web Services to link content
  across multiple registries and repositories.
• (3) Provide the basis for integration across all
  five Reference Models.
• (4) Provide for a collaboration platform for XML
  data exchange as well as process collaboration
  and free-form interaction.

5
Strengthening the Federal Enterprise Architecture
(FEA) Data and Information Reference Model (DRM)

• Specifics
• (1) Rendering Data and Information in Six Ways to
  Meet Citizen Expectations and Preferences.
• (2) Registries and Repositories with Common
  Content Linked by XML Web Services.
• (3) Creating Taxonomies in Registries and
  Repositories that Integrate the Five Reference
  Models.
• (4) CollabNet Enabling collaborative software
  development strategies and communities.

6
(1) Rendering Data and Information in Six Ways to
Meet Citizen Expectations and Preferences.

• The six ways that content is rendered is
• 1. Electronic Braille
• 2. Digital Talking Book (including data tables!)
• 3. Captioning
• 4. Electronic Large Print
• 5. Virtual Sign Language
• 6. Foreign Language
• Source Dave Schleppenbach, GH Braille Player,
  Collaboration Expedition Workshop 23,
  Presentation at the National Science Foundation,
  Ballston, VA, April 15, 2003.

7
(2) Registries and Repositories with Common
Content Linked by XML Web Services

• Types of Registries(1)
• ISO 11179Registries
• OASIS/ebXMLRegistries
• UDDIRegistries
• OntologicalRegistries
• Database Catalogs
• Software Component Registries
• CASE Tool Repositories

• Pilot Projects with Registries
• XML Design Collaboration and Registry Platform
• XML Design Collaboration and Registry Platform
• XML Design Collaboration and Registry Platform
  and Tamino
• Open Standard Ontology Tool and Platform (Topic
  Maps)
• Various (MetaMatrix, etc.)
• Various (CollabNets SourceCast, etc.
• Various (GIDS, etc.)

(1) Source Eliot Christian, USGS, based on work
of ISO/IEC JTC1/SC32 Data Management Subcommittee
chair, Bruce Bargmeyer (NIST, EPA, LBL).
8
(3) Creating Taxonomies in Registries and
Repositories that Integrate the Five Reference
Models

• Example Show me all the data structures that
  have been classified as part of the Business
  Compliance One-Stop Initiative and as a work
  product of the IRS
• DRM the data structures themselves (e.g. data
  dictionary)
• SCRM expressed as a reusable component (e.g.
  XML Schema)
• TRM provided in an interoperable way (e.g. an
  XML Web Service) .
• BRM classified according to a taxonomy (e.g.
  Business Reference Model Version 2).
• PRM Doing all this demonstrates performance!

Source Kevin Williams, Creating Taxonomies in
XML Collaborator, Presentation to the XML Web
Services Working Group, April 15, 2003.
9
(3) Creating Taxonomies in Registries and
Repositories that Integrate the Five Reference
Models
Classifying a structure
Creating a taxonomy
Source Kevin Williams, Creating Taxonomies in
XML Collaborator, Presentation to the XML Web
Services Working Group, April 15, 2003.
10
(4) CollabNet Enabling collaborative software
development strategies and communities

• CollabNet
• Roots in the Apache Software Foundation and Open
  Source.
• SourceCast Enterprise collaboration platform
  targeting software development deployment.
• Integrates Structured Exchange (XML), Process
  Collaboration, and Free-form Interaction.
• Value proposition to the FEA Benefits of Open
  Source Process.
• Pilots
• DISA (Dawn Meyerriecks)
• About 100 participants collaborating on about 30
  projects to produce Horizontal Fusion across
  the organization.
• Canadian Government Pilot (Joseph Potvin)
• Users never know what they want .. until they
  can see what they will get.

11
(4) CollabNet Enabling collaborative software
development strategies and communities

Effective Collaborative Software Development
Environments
project workspace
software development applications
technical communication
knowledge management

• - mailing lists
• - discussion
• forums
• document
• and file
• management

- scm - issue tracking - ide integration

• knowledge
• archive
• (lists, forums, code)
• - power search
• - news
• - notification

project administration
application security, role-based permissions
12
1. Introductions

• Updates (continued)
• Components Activities of the Emerging Technology
  Subcommittee presented to the Governance and
  Components Subcommittees and the full Committee,
  April 17th (excerpts)
• (1) AIC Guidance, Work Plan, Tools
• (2) Target Next 3-6 months
• (3) Pilot Selection Criteria
• (4) Pilot Graduation Criteria
• (5) Pilot Process
• (6) XML Web Services Pilot Projects Titles
• (7) XML Web Services Pilot Projects Schedule

13
(1) AIC Guidance, Work Plan, Tools

• AIC Guidance
• The Subcommittee needs a plan for evolution to
  meet near and longer term expectations and for
  working with vendors.
• An Enterprise Architecture component is defined
  as a self-contained business process or service
  with predefined functionality that may be exposed
  through a business or technology interface.
• Work Plan
• Baseline October 2002 to present.
• Transition Next 1-3 months.
• Target Next 3-6 months.
• Pilot Selection and Graduation Criteria and
  Process
• Tools
• Collaboration (with other Subcommittees).
• Clearinghouse.
• Registries and Repositories.

14
(2) Target Next 3-6 months
Working Group
Deliverables

• XML
• XML Web Services
• Universal Access
• Technology Life-Cycle Process

• XML Registry becomes part of Components SC.
• Graduate additional successful pilots to the
  Governance and Components SCs.
• Regular Workshops and Technology Conferences.
• Initiate process and tools.

15
(3) Pilot Selection Criteria

• Inherited from previous work
• E.g., Digital Talking Books, VoiceXML, and
  Content Networking.
• Working Group priorities
• E.g., 5 of the top 9 priorities given to the new
  XML Web Services Working Group were to develop a
  registry and collaboration facility for Web
  Services in support of e-Gov.
• Formal request from OMB, FEA-PMO, AIC and
  Subcommittees, etc.
• E.g., Eforms for E-Gov, XML Data Exchange
  Across Multiple Levels of Government Using Native
  XML Databases, etc.
• IAC Web Services SIG recommendation
• E.g., User Customization and Dynamic Discovery.
• Proposed and Vetted in the Working Group
• E.g., Cognitive Topic Map Web Sites.

16
(4) Pilot Graduation Criteria

• The AIC Leadership decides it is ready.
• E.g., Federal PKI Steering Committee.
• The Governance and Components Subcommittees
  request a specific component with a specific
  schedule.
• E.g., XML Registry.
• The Emerging Technology Subcommittee Co-Chairs
  and Working Group Leaders agree it is ready.
• E.g., The Technology Life Cycle process.
• The Working Group leaders set a schedule for the
  pilots.
• E.g., XML Web Services Working Group.

17
(5) Pilot Process

• OMB wants IAC to lead by example by
  implementing enterprise architecture principles
  in their own businesses and open standards in
  their own products, but OMB cannot fund IAC.
• IAC wants to influence the FEA process and market
  implementation of component-based architectures
  in their products and services.
• IAC has mirrored the AIC structure and wants to
  do pilots which have the following benefits to
  both IAC and the AIC
• Vendors are indoctrinated in the FEA and their
  pilot proposals are vetted within their own SIGs.
• The proposed pilots represent a consensus
  recommendation from the SIGs.
• The proposed pilots are ready to be matched to
  real needs and demonstrated more rapidly than
  just solutions in search of problems.
• Usually, proposed pilots need to be attached to
  either the IAC, an E-Gov Initiative, agency, or
  sponsoring organization to be viable since
  unattached pilots are difficult to foster and
  resource.

18
(6) XML Web Services Pilot Projects Titles

• 1. Digital Talking Books on CD-ROM and the Web as
  VoiceXML.
• 2. XML Collaborator.
• 3. VoiceXML for Universal Access and Homeland
  Security Applications.
• 4. Geospatial Interoperability.
• 5. XML Web Services Content Authoring,
  Management, and Dissemination.
• 6. Military Systems-Federation of Registries,
  Native XML Databases, etc.
• 7. E-Forms for e-Gov The Use of XML
  Standards-based Applications.
• 8. The MetaMatrix System for Model-driven
  Integration with Enterprise Metadata.
• 9. Cognitive Topic Map Web Sites-Aggregating
  Information Across Individual Agencies and E-Gov
  Initiatives.
• 10. Collaboration and CoSourcing Designing
  Intergovernmental Services and Sharable
  Components.
• 11. The Potential of Semantic Technologies for
  E-Gov.
• 12. XML Data Exchange Across Multiple Levels of
  Government Using Native XML Databases.
• 13. Others to be added.

19
(7) XML Web Services Pilot Projects Schedule

• Pilot Status
• 1. Graduating to GPO/GSA
• 2. Planned Public Release
• 3. Ready for EPA and DHS
• 4. Just Beginning
• 5. Well Underway
• 6. Just Beginning
• 7. Pilot Sub-teams Formed
• 8. Ready for DHS
• 9. Just Beginning
• 10. Just Beginning
• 11. Just Beginning
• 12. Just Beginning

• Planned Date
• April 15th Workshop Report
• May 5th Conference
• April May Presentations
• TBA
• May June Presentations
• TBA
• Interim-June, Final-October
• May 14-15th Presentations
• April 15th Workshop Report
• At Technology Conference
• May 14th Workshop Report
• June 17th Workshop Report

20
1. Introductions

• Updates (continued)
• The pilot funding options are as follows
• (1) AIC Budget (limited)
• (2) Industry Advisory Council (IAC)
• (3) Participating Agencies and
• (4) Venture Capitalists.
• Explanation Over the near term, the IAC is going
  to review the Work Plans of all three
  Subcommittees to determine what it can do to help
  the AIC complete its work plans (including the
  pilots) and then the participating agencies will
  see what they can do to help with what is left
  over. Over the longer term, the quarterly
  Components Technology Conferences being planned
  will bring together government requirements,
  vendor capabilities, and venture capital
  interests to foster investment in innovation that
  meets e-government needs.

21
1. Introductions

• Updates (continued)
• The second meeting of the "Eforms for E-Gov"
  Pilot Team, March 19th, at EPA West was another
  outstanding success with over 30 in attendance
• See new Web Site and ListServ
• http//www.fenestra.com/eforms
• One-Stop Business Compliance (SBA)
• Support from four pilot project teams in process.
• Topic Map Web Service Pilot for E-Gov Conference
  Proceedings has been produced.
• XML Data Exchange Across Multiple Levels of
  Government Using Native XML Databases
• MITRE XML SIG, April 22nd and EPA, April 28th.
  Report on June 17th.
• ITIPS-II (Information Technology Investment
  Portfolio System http//www.itips.gov).
• Support from three pilot project teams being
  provided.

22
1. Introductions

• Updates (continued)
• Opportunity for Vendors Participating in the
  "E-Forms for E-Gov" Pilot to Pilot the Use of XML
  Web Services in E-Gov Initiatives (e.g. e-Grants,
  etc.) to Support an "Assessment of Readiness" by
  the Working Group for the Solutions Architects
  Working Group (SAWG) and the "QuickWin" Task of
  the Components Subcommittee of the AIC. All
  Vendors were invited to participate.
• 1. Microsoft - Susie Adams
• 2. Adobe - Melonie Warfel
• 3. Soltex - Matthew Garst
• 4. Digital Evolution - Al Lang
• 5. Sand Hill Systems - Krishna Srinivasan
• 6. SeeBeyond - Mike Sinisgalli
• 7. Object Builders - Joe Brophy
• 8. SiloSmashers - Ken Sall (observing)
• 9. Conclusive Technology - Matthew McKennirey
• 10. ITM Associates - Steve Katz
• 11. Pure Edge - Greg O'Connell

See http//listserv.gsa.gov/cgi-bin/wa?A2ind0305
Lcioc-web-servicesFSP232
23
1. Introductions

• Some Coming Attractions and Announcements
• May 21, 2003, E-Forms for E-Gov Pilot Team
  Meeting, 10-12 noon, Department of Commerce, Room
  6029. See http//www.fenestra.com/eforms for
  details.
• May 21, 2003, Information Management Subcommittee
  of the Chesapeake Bay Program, 1105-1145 a.m.,
  Pilot Project Reports XML Authoring the State
  of the Chesapeake Bay Report (Corels' XMetal and
  Smart Graphic Studio) and Client-Side XML Web
  Services for the Chesapeake Bay Program (Object
  Builders).
• June 2, 2003, Piloting the Use of XML Web
  Services in E-Gov Initiatives, scheduled for June
  2nd, 830 a.m.- 5 p.m., Truman Room, White House
  Conference Center. Attendance by invitation to
  the SAWG (Federal), E-Gov Initiative Portfolio
  and Program Managers, etc. More information to
  follow.
• June 17, 2003, in conjunction with the Universal
  Access Collaboration Workshop 25 at the National
  Science Foundation (Ballston, VA Orange Line
  Metro Station). Agenda in process. Focus
  Consolidated Health Informatics Intersecting with
  the OASIS E-Gov and the Open Source E-Gov.
• June 26, 2003, Components Technology Conference,
  8 a.m. - 430 p.m., GSA Auditorium at 18th and F
  Street, NW, Washington, DC, in cooperation with
  The Cyberspace Security Policy and Research
  Institute (Tony Stanco, Associate Director),
  George Washington University. Participation in
  planning and production invited. Fact Sheet
  Template to be available soon.

24
1. Introductions

• Federal CIO Council, Architecture and
  Infrastructure Committee, FEA Component
  Technology Conference, June 26, 2003, General
  Services Administration, 1800 F ST NW, Wash.,
  D.C.
• 800 AM Registration and Coffee
• 845 AM Welcome and Introductions
• 900 AM Envisioning the Possibilities Plenary
• Congressional, OMB, Software Industry, Venture
  Capital
• 1030 AM Break
• 1100 AM Framing Principles for Coordinated
  Action Building Components that Work Together
• CIO Council, Agency, Industry, Collaborative
  Communities
• 1230 PM Lunch
• 130 PM FEA Components Open Dialogue
• 200 PM Bringing Whats Needed to Light!
• 5 minute highlights from current and emerging
  component development teams one page fact
  sheets available.
• 315 PM Break
• 330 PM Lightning Rounds Open Dialogue
• 430 PM Adjourn

25
1. Introductions

• Special Recognition
• To be announced at the meeting.
• Special Recognition to Kevin Williams and Anne
  Yastremski, Blue Oxide Technologies, For
  exceptional creativity and performance on the
  XML Collaborator Pilot Project, presented at
  the XML Web Services Working Group Meeting, May
  14, 2003, by Brand Niemann, Chair.

26
1. Introductions

• Participants
• Need two volunteers for minutes.
• Acknowledge Brand Niemann, Jr..
• Who you are
• Your name.
• Your affiliation.
• Your interests in XML Web Services.

27
2. Business

• Report on State and Homeland Security Practices
  and Federal Working Group Coordination Database
  Web Service, James Mackison, GSA Office of
  Citizen Services.
• Report on Discussions of Topic Maps, RDF, and
  Semantic Web, Ralph Hodgson, TopQuadrant, Inc.
  and others.

28
3. Presentations

• Organizations Justice XML Data Model and Data
  Dictionary, Ken Gill, Department of Justice.
• Pilot Project The MetaMatrix System for
  Model-driven Integration with Enterprise
  Metadata, Ed Fakler, MetaMatrix.
• Pilot Project XML Web Services Content
  Authoring the State of the Chesapeake Bay Report
  (XMetal and Smart Graphics Studio), Scott
  Edwards, Corel.
• Pilot Project Client-Side XML Web Services for
  the Chesapeake Bay Program, Joe Brophy, Object
  Builders.