1. 19 January 2005Plans for Derived XML Registry Prototype 1 Plans for Derived XML Registry Prototype Problem: l Proliferation of Narrowly-Focused Standards, Policies, Legislation, Registries, Portals, etc. l Adoption Uneven Across Federal Government Departments & Agencies. l Reaction TO vs. Setting Requirements FOR IT Standards.

2. 19 January 2005Plans for Derived XML Registry Prototype 2 XML & XML-based Standards Offer Solution, but No Panacea l XML Salvages Legacy Databases, Applications, Crosses Platforms, but … n XML Schema Standard is Complex. n Inconsistent Validation Remains. n Work-arounds for Toolsets cause Backward Compatibility Issues when Standards are Refined and Toolsets Improved. n Lack of Best Practices & Risks of Duplicate Terms in Vocabularies Possible. l Still, Improvement Continues.

3. 19 January 2005Plans for Derived XML Registry Prototype 3 Needs Drive Rush for Domain-Specific Standards l Similar Concerns Breed Similar Standards. l Overlap & ‘Scope Creep’ Inevitable. l Specialization Standards Can be Separate from the Generalized Standards in the Same Domain, such as Optometry in Healthcare. l Key Terms can have many Standards, such as ‘Person.’

4. 19 January 2005Plans for Derived XML Registry Prototype 4 Government Cross Department, Cross Agency Effort Small, Voluntary but Growing. l Presidential Management Agenda for ‘Citizen-Centric Government’ Emphasizes Importance of E- Government, Continues Second Decade of IT Efficiency Effort. l Transition Underway from ‘Early Adoption’ to ‘Leadership’ in Open Standards Adoption Post Y2K.

5. 19 January 2005Plans for Derived XML Registry Prototype 5 Interrelated Legislation, Policy Mandates Continue... l Government Performance & Results Act-1993. n Requires Strategic Plan with Periodic Reviews. n Requires ‘Outcome-Related’ Goals & Objectives. l Government Paperwork Reduction Act-1995. n Office of Information & Regulatory Affairs (OIRA) in OMB Reviews ALL Governmental Agency Information Collection. n Requires ONLY Information Collection ‘Necessary for Proper & Practical Utility for Agency.’

6. 19 January 2005Plans for Derived XML Registry Prototype 6 Interrelated Legislation, Policy Mandates Continue... l Clinger-Cohen Act-1995. n Information Technology Management Reform Act Repeals 1949 Brooks Act Section 111-- GSA No Longer Responsible for Government-Wide Automated Data Processing Purchasing. n Requires Agencies to use Capital Planning & Investment Control Policies (GPIC). l Government Paperwork Elimination Act-1998. n Allows ‘Electronic Information Submission & Transmission’ in Government Agency Interactions. n Agencies Allowed Electronic Records Maintenance.

7. 19 January 2005Plans for Derived XML Registry Prototype 7 Interrelated Legislation, Policy Mandates Continue... l Federal Enterprise Architecture (FEA) n Clinger-Cohen-Based FEA Framework Formed-1999- CIO Council (CIOC), Program Management Office (FEAPMO)-2002 under OMB, Returning to CIOC. n Zachman-Based, Promotes Interoperabilty, Sharing Common Federal Processes, Information. n Aids Capital Planning & Investment Control Policies (CPIC). n Common Federal Reference Models Provided-2002 u Performance Reference Model (PRM) u Business Reference Model (BRM) u Service Component Reference Model (SRM) u Data Reference Model (DRM) u Technical Reference Model (TRM)

8. 19 January 2005Plans for Derived XML Registry Prototype 8 Interrelated Legislation, Policy Mandates Continue... l OMB Circular A-11 Part 7 - 2002 n Planning, Budgeting, Acquisition, and Management of Capital Assets for Reaching Strategic Results-Based Goals at Lowest Life- Cycle Cost and Least Risk. n Section 300 Requires: u CPIC & FEA-Based Documentation of Business Case Justification for IT Investments. u Performance Measurements. u Using FEA Reference Models in Relation to Specific Lines of Business (Implied. Not Explicit). u Identifying Cross-Agency Resources to Share.

9. 19 January 2005Plans for Derived XML Registry Prototype 9 Interrelated Legislation, Policy Mandates Continue... l OMB Identified Lines of Business-2004 n Lines of Business for CPIC & FEA-Based Reports u 2004-2005 ?Financial Management. ?Data & Statistics. ?Human Resources. ?Monetary Benefits. ?Criminal Investigations. ?Public Health Monitoring. u 2006 ?Financial Management. ?Human Resources Management. ?Grants Management. ?Federal Health Architecture. ?Case Management.

10. 19 January 2005Plans for Derived XML Registry Prototype 10 Interrelated Legislation, Policy Mandates Continue... l OMB Circular A-119 n Federal Participation in the Development & Use of Voluntary Consensus Standards & in Conformity Assessment Activities. n National Technology Transfer & Advancement Act-1995: u NIST Coordinates Conformity Assessment. u OMB Revised Circular “Directing Agencies to use Voluntary Consensus Standards in lieu of Government- Unique Standards Except Where Inconsistent with Law or Otherwise Impractical. n Purpose: Reduce to Minimum Government Reliance on Government-Unique Standards.

11. 19 January 2005Plans for Derived XML Registry Prototype 11 Legislation & Policy Results: l Well-Intended, very Smart in some Specifics, Overly Specific in others. l Creates Confusion-What to do First? l Duplicated Provisions, Restated Objectives, Unstated Implications. l Specifies Process and Outcomes such as Sharing Resources among Agencies without Clear Priorities & Criteria. l Overall: Normal, Improving.

12. 19 January 2005Plans for Derived XML Registry Prototype 12 A Start: XML Registry of Existing Standards & Specifications l Using Firstgov.gov: n Evaluate Methods to Automate or Assist in Populating an XML Registry of Governmentally- Used or -Related Documents, Standards. n Evaluate Making the Registry Selectively Available using ebXML Registry and eXtensible Access Control Markup Language (XACML) to Restrict Access by Identity Authentication and Role-Based Permissions. n Evaluate the Extent of the Task of Using a Prototype Process to Develop a Centralized and Federated XML Standards Registry to Support the IT Investment Tasks of Governmental Agencies.

13. 19 January 2005Plans for Derived XML Registry Prototype 13 A Start: XML Registry of Existing Standards & Specifications l Using Firstgov.gov: n Method 1: WSRP Standard- Plumtree Web Crawler Portlet Makes Results Available by Web Browser in Humanmarkup.org Public Service Portal. n Method 2: Use OWL to Search site by Ontological Rules to identify and sort.xml and.xsd files by Relationships to Criteria Keywords or Phrases, such as Healthcare Services or Emergency Event Types. n Method 3: Use Strawman Search Standard(s) to Discover Requirements for an XML-Specific Search Standard from this Registry Use-Case to be used in a Prototype Government XML Standards Registry.

14. 19 January 2005Plans for Derived XML Registry Prototype 14 A Start: XML Registry of Existing Standards & Specifications l Using Firstgov.gov: How many & which documents? n Are or Refer to XML? n Are or Refer to XSD? l Identify, Sort, Index. n XSDs that are Standards. n XSDs that are Agency- or Company-Specific. n Extract XSD Elements, Attributes, complexTypes, simpleTypes, etc. n Check for Duplicate Terms & Definitions- Compare and Contrast.

15. 19 January 2005Plans for Derived XML Registry Prototype 15 A Start: XML Registry of Existing Standards & Specifications l What does Our Search Tell Us? l Apply Ontological Categorization n Make Ontology of Lines of Business. n Make Ontology of Cabinet Departments and their constituent Agencies. n Search by Ontological Criteria for Terms. n Identify Similar or Identical Terms. n Identify Number of Occurrences of Terms. n Identify Departments & Agencies using Specific Terms.