1 / 26

USGS XML in the Emerging U.S. Federal Information Architecture

This presentation by Eliot Christian from USGS provides an overview of XML in the emerging U.S. Federal Information Architecture, including reference models and principles for data and information management.

carolcraig
Download Presentation

USGS XML in the Emerging U.S. Federal Information Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Presented by Eliot Christian, USGS April 30, 2003 XML in the Emerging U.S. Federal Information Architecture

  2. Federal Enterprise Architecture (FEA) Performance Reference Model (PRM) • Government-wide Performance Measures & Outcomes • Line of Business-Specific Performance Measures & Outcomes Business Reference Model (BRM) • Lines of Business • Agencies, Customers, Partners Business-Driven Approach Service Component Reference Model (SRM) • Service Layers, Service Types • Components, Access and Delivery Channels Data Reference Model (DRM) • Business-focused data standardization • Cross-Agency Information exchanges Technical Reference Model (TRM) • Service Component Interfaces, Interoperability • Technologies, Recommendations

  3. FEA Reference Models Performance Reference Model (PRM) Outcomes, Measurements, Metrics Business Reference Model ( BRM ) Service Component Reference Model ( SRM ) Technical Reference Model ( TRM ) Rule Publication Support Delivery of Services Technologies Platforms J2EE .NET Windows NT Knowledge Mgmt CRM Content Mgmt Collaboration Search Portal Personalization Regulatory Management Policy and Guidance Devel. Public Comment Tracking Regulatory Development Rule Publication Data Mgmt ODBC JDBC Business Logic Enabling capabilities, components, and services Business lines and functions Supporting technology and standards Data and Information Reference Model (DRM) Classification, Categorization, XML, Sharing

  4. Level of Granularity / Re-Use Level of Context FEA Data Reference Model (DRM) Overview of Framework Recreational Resource Management & Tourism Conceptual FEA Business Reference Model (BRM) Camping Classification Campsite Permit Object Class Data Element Concept Data Element Name Location Facility Trail Fee Use Request Identifier Property Name Location Text Amount Text Name Representation Campsite Name (Name) Permit Fee Amount

  5. Information Architecture Principles 1. Avoid non-standard data syntaxesStandard: XML or ASN.1 2. Register the semantics of shared data elementsStandard: ISO 11179 3. Document service interfaces in a standard wayStandard: CORBA IDL, ebXML, Web Services, UDDI 4. Implement standard for information discoveryStandard: Information Retrieval, ISO 23950/GILS 5. Implement standard interfaces for geospatial dataStandard: GILS/GEO, OpenGIS Consortium

  6. Information Architecture Principle 1:Avoid non-standard data syntaxes • Need to agree on a small number of robust data representation syntaxes that handle all data types required to traverse the shared interfaces • Agreement to use either ASN.1 (Abstract Syntax Notation) or XML (Extensible Markup Language • Both are interconvertible and both are compatible with Web Services

  7. Information Architecture Principle 2:Register the semantics of shared data elements • Need a common understanding of the meaning of data elements traversing the interface • ISO 11179 (Information Technology--Metadata Registries) supports registration of data using virtually any syntax

  8. Registries as Applied to Data/ Information/ Knowledge Management • Several types of “registries” commonly used in data / information/ knowledge management • Various registries have related content, extended and utilized in different ways • The registries vary according to: • intended purpose • granularity of contents • the level of semantics management.

  9. Software Component Registries ISO 11179Registries Common Content OASIS/ebXMLRegistries UDDIRegistries Common Content Common Content Common Content OntologicalRegistries Common Content Database Catalogs CASE Tool Repositories Common Content Common Content Types of Registries

  10. Database Catalogs Common Content Types of Registries:Database Catalogs/Data Dictionaries/ Repositories • Registers schema, integrity & operational information • Includes all elements of database schemas: data elements, relations, integrity constraints • Emphasis on information required to make database systems work for queries, etc., not semantic management

  11. UDDIRegistries Common Content Types of Registries:Universal Description, Discovery, and Integration (UDDI) Registries • Registers Web-based Business Services • A White page directory of the business activities of firms • Emphasis on interface specifications

  12. CASE Tool Repositories Common Content Types of Registries:Case Tool (Encyclopedias/Repositories) • Registers data models and application program logic • Includes information needed to create a database and potentially the program code for a system, including database schemas • Emphasis not on semantic management

  13. OntologicalRegistries Common Content Types of Registries: Ontological Registries • Registers Concept Structures • Includes relations among concepts (subsumption, inheritance,…) and axioms for inference among concepts, e.g., temporal/spatial reasoning, etc. • Emphasis is on semantics

  14. Software Component Registries Common Content Types of Registries:Software Component Registries • Registers reusable software components built on specific vendor platforms such as EJB, COM, CORBA IDL etc. • Includes basic common elementary objects and object patterns • Emphasis on reusability of software component to build flexible and standardized business systems.

  15. OASIS/ebXMLRegistries Common Content Types of Registries:OASIS/ebXML XML Registries • Registers XML Artifacts • Includes schemas and DTDs (XML schemata typically relate to a paper form, EDI document, or reporting requirement) • Emphasis on syntactic (structure) information

  16. ISO 11179Registries Common Content Types of Registries:ISO 11179 Metadata Registries • Registers Data Elements, components of data elements and groups of data elements (e.g., country codes for customer place of residence) • Includes data element concepts, data elements (including representation), value domains, and (multiple) taxonomies • Emphasis on semantic information such as definitions of data elements and value meanings, and stewardship responsibilities

  17. Software Component Registries Common Content Example of Common Content across Registry Types Database Catalogs Common Content ISO 11179Registries UDDIRegistries Common Content Common Content Country Name OASIS/ebXMLRegistries CASE Tool Repositories Common Content Common Content OntologicalRegistries Common Content

  18. Software Component Registries Common Content RegistriesExample of Common Content Database Catalogs Common Content ISO 11179Registries UDDIRegistries Table Column Data Element Common Content Common Content Business Specification Country Name OASIS/ebXMLRegistries CASE Tool Repositories XML Tag Attribute Common Content Common Content TermHierarchy OntologicalRegistries Business Object Common Content

  19. <?xml version="1.0"?> <shipTo > <name>Alice Wilson</name> <street>161 North Street</street> <city>Happy Valley</city> <state>MO</state> <zip>63105</zip> <country code>USA</country code> </shipTo> OASIS/ebXML XML Registry Repository VI304 Dollars X12 UnitPrice EDIFACT ListPrice Collaboration Partner #1 Collaboration Partner #2 Currency <Rep href= “http://www.disa.mil”>DISA</Rep> <ELEMENTrep= ‘DISA’name=‘Country’Biz =‘VI304’ > Schema or Template <Rep href= “http://www.disa.mil”>DISA</Rep> <ELEMENTrep= ‘DISA’name=‘CntryCode’Biz =‘VI304’ > Schema or Template XML Instance XML Instance <Country>JPN</Country> <CntryCode>JPN</CntryCode>

  20. UDDI Registry <?xml version="1.0"?> <shipTo> <name>Alice Wilson</name> <street>161 North Street</street> <city>Happy Valley</city> <state>MO</state> <zip>63105</zip> <country code>USA</country code> </shipTo> Business-to-Business

  21. Case Tool Repository

  22. Database Catalog

  23. Concept Concept Concept Concept Geographic Area Geographic Sub-Area Country Country Identifier Country Name Country Code ISO 3166 2-Character Code ISO 3166 3- Character Code Short Name Long Name Mailing Address Country Name ISO 3166 3-Numeric Code FIPS Code Distributor Country Name Ontological Registry

  24. An Example of Software Component Registry

  25. Data Element List – Address Group 33c Name Street Address City, State Postal Code Country ISO 11179 Registry <?xml version="1.0"?> <shipTo > <name>Alice Wilson</name> <street>161 North Street</street> <city>Happy Valley</city> <state>MO</state> <zip>63105</zip> <country code>USA</country code> </shipTo>

  26. Name: Country Identifiers Context: Definition: Unique ID: 5769 Conceptual Domain: Maintenance Org.: Steward: Classification: Registration Authority: Others DataElementConcept Algeria Belgium China Denmark Egypt France . . . Zimbabwe Example of Common ContentCountry Identifier Data Elements Algeria Belgium China Denmark Egypt France . . . Zimbabwe L`Algérie Belgique Chine Danemark Egypte La France . . . Zimbabwe DZ BE CN DK EG FR . . . ZW DZA BEL CHN DNK EGY FRA . . . ZWE 012 056 156 208 818 250 . . . 716 Name: Context: Definition: Unique ID: 4572 Value Domain: Maintenance Org. Steward: Classification: Registration Authority: Others ISO 3166 3-Alpha Code ISO 3166 English Name ISO 3166 French Name ISO 3166 2-Alpha Code ISO 3166 3-Numeric Code

More Related