Notes
Slide Show
Outline
1
History, Charter & Challenges Facing the XML Community of Practice (xmlCoP)
  • Owen Ambur, Co-Chair Emeritus
  • xmlCoP/XBRL CoP Forum @FOSE
  • March 20, 2007
2
Presentation Outline
  • xmlCoP History
    • Original Motivations
    • 1st Charter
    • 2nd Charter
    • 3rd Charter
    • 4th Charter
    • Accomplishments
  • Recent ET Submissions
  • I411 & BTS Prototype
3
History
  • Chartered by CIO Council in 2000
  • 1st Charter Expired on September 30, 2002
  • Now Operating under 4th two-year Charter
    • Expiring November 30, 2008
  • New Co-Chairs:
    • Ed Coia, Treasury’s Financial Management Service
    • Kirk Keller, Missouri’s Department of Conservation


    • http://xml.gov/documents/completed/history.htm
4
Original Motivations
  • Render all .gov forms in XML & gather the data from them in XML
  • Specify a core set of XML metatags for the classification & management of records governmentwide


  • My E-mail message:
  • http://xml.gov/documents/completed/genesis.htm
5
Originally Chartered Activities
  • Develop XML Best practices and Recommended Standards
  • Develop Partnerships with Key Industry and Public Groups Developing XML Standards and Specifications
  • Develop Partnerships with Existing Federal "Vertical" Communities to Accelerate the Delivery of XML Benefits
  • Conduct "Results-Oriented" Education and Outreach


  • http://xml.gov/documents/completed/charter1st.htm


6
Additional Activity in 2nd Charter
  • Propose for consideration by the AIC specific projects and products benefiting stakeholders of multiple Federal agencies


  • CIOC intended to take more “operational” role
  • Subsequently found resources lacking
  • Congress cut cross-agency funding
    • Including $2.1 million requested by the President for the XML Registry
      • Business Case estimated ROI ranging from 500 – 1400%
      • http://xml.gov/documents/completed/bah/registryBusinessCase.htm#_Toc19694635
7
Additions in 3rd Charter
  • Continue previously authorized activities while focusing on:
  • Assisting with implementation of the emerging technology (ET) life-cycle management process
  • Facilitating collaboration on and review of XML-based "components" within that process


  • The XML Working Group (XML WG) was renamed as the XML Community of Practice (xmlCoP)


  • http://xml.gov/documents/completed/charter3rd.htm


8
Addition in 4th & Current Charter
  • Continue previously chartered activities while:
  • Coordinating with and supporting the activities of the Data Architecture Subcommittee (DAS) and Services Subcommittee, as well as the Governance Subcommittee of the AIC


  • The CIOC/AIC
  • Created the DAS to emphasize data architecture as a priority, and
  • Renamed the Services S/C to focus on services already available for reuse


  • http://xml.gov/documents/completed/charter.htm
9
Accomplishments
  • Education & Outreach
    • xml.gov site
    • Meetings/briefings virtually every month for 6 years
      • See Agendas, Minutes & Presentations
  • ET.gov Site/Process
    • About 80 components/specifications so far
      • See search results screen & i411 & BTS prototype
    • 14 CoPs at Stage 2
    • 5 at Stage 3
    • 2 have “graduated” at Stage 4
      • PDF-A & X3D included in the FEA TRM







10
Most Recent ET.gov Submissions
11
I411 Prototype
12
Stage 2 ET CoPs
13
Stage 3 CoPs
14
Remaining Challenges
  • XML Registry Services
  • Emerging Technology Process Enhancements
  • XML Schema for Data Reference Model
  • XML Naming & Design Rules & Guidelines
  • Original Motivations:
    • XML schemas & data from all .gov forms
    • XML metatags for records management/sharing


15
XML Registry Services
  • Collaborative development/use of XML schemas
  • Still too hard to discover & reuse
    • Centralized registry has highest ROI
    • Distributed set of interoperating registries preferred
    • Posting XSDs on Web with appropriate metadata may be best alternative
      • Build registries from the bottom-up
    • See Registries page on xml.gov site

16
ET.gov Site/Process Enhancements
  • More effective & well-coordinated consideration of ET by .gov agencies
    • Dampen hype cycle
    • Accelerate maturation & adoption
  • Enhancement of ET.gov site & process
    • See proposed enhancement requirements

17
XSD for DRM
  • One of “Key Indicators” in CIO Council’s Strategic Plan is:
    • All of the e-Gov and Lines of Business (LoB) project management offices have fully documented data architectures in conformance with the XML schema for DRM 2.0
  • Problem:
    • XSD for DRM is merely in draft form
      • http://xml.coverpages.org/FEA-DRM-SchemaDraftV04-20060103.xsd
    • Not yet “authoritative”
18
XML NDRG
  • Various groups specifying own XML naming & design rules (NDR)
  • Not all make sense in all contexts
  • Guidelines may be more appropriate than rules in some instances
  • Difficult & complex to apply
  • Tool support required
    • NIST & XML Schema Interoperability Work Group
      • https://collab.core.gov/CommunityBrowser.aspx?id=2234
19
XML for Forms & Records
  • A couple hopeful signs:
  • FIRM’s forum this morning
    • http://xml.gov/documents/completed.asp#20070320pechakucha
  • XBRL/XForms presentation at this meeting
    • http://xml.gov/presentations.asp#20070320
20
Contact Information
  • My E-mail Address:
    • Owen.Ambur@verizon.net
  • Web Sites:
    • http://xml.gov
    • http://et.gov/
    • http://mysite.verizon.net/ambur/
  • This Presentation:
    • http://xml.gov/presentations/xmlCoPhistory.htm
    • http://xml.gov/presentations/xmlCoPhistory.ppt