xml in the emerging u.s. federal information architecture presented by eliot christian, usgs april...
TRANSCRIPT
XML in the Emerging U.S. Federal
Information Architecture
Presented by Eliot Christian, USGS
April 30, 2003
2
Business Reference Model (BRM)• Lines of Business• Agencies, Customers, Partners
Service Component Reference Model (SRM)
Technical Reference Model (TRM)
Data Reference Model (DRM)
Busin
ess-D
riven A
ppro
ach
Performance Reference Model (PRM)
• Government-wide Performance Measures & Outcomes• Line of Business-Specific Performance Measures & Outcomes
• Service Layers, Service Types• Components, Access and Delivery Channels
• Service Component Interfaces, Interoperability• Technologies, Recommendations
• Business-focused data standardization • Cross-Agency Information exchanges
Federal Enterprise Architecture (FEA)
3
Regulatory Management
Support Deliveryof Services
Policy and Guidance Devel.Public Comment TrackingRegulatory DevelopmentRule Publication
Knowledge MgmtCRMContent MgmtCollaborationSearchPortalPersonalization
BusinessReference Model
( BRM )
Rule Publication
Service ComponentReference Model
( SRM )
Technologies
Platforms J2EE .NET Windows NTData Mgmt ODBC JDBCBusiness Logic
TechnicalReference Model
( TRM )
Performance Reference Model (PRM)Outcomes, Measurements, Metrics
Business lines and functions
Supporting technologyand standards
Enabling capabilities, components, and
services
Data and Information Reference Model (DRM)Classification, Categorization, XML, Sharing
FEA Reference Models
4
FEA Data Reference Model (DRM) Overview of Framework
Recreational Resource
Management & Tourism
Level o
f Gra
nu
larity
/ Re-U
se
Level o
f Con
text
FEA Business ReferenceModel (BRM)
Classification
Object Class
Property
Representation
Data Elemen
t ConceptData
Element
Camping
Campsite Permit
Name Location FacilityTrail
Fee Use Request Identifier
NameLocationText
AmountTextName
Campsite Name (Name) Permit Fee Amount
Conceptual
5
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
Information Architecture Principles
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 purposegranularity of contentsthe level of semantics management.
9
Types of Registries
Common Content
OASIS/ebXMLRegistries
Common Content
ISO 11179Registries
Common Content
OntologicalRegistries
Common Content
DatabaseCatalogs
Common Content
CASE ToolRepositories
Common Content
UDDIRegistries
SoftwareComponentRegistries
Common Content
10
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
Common Content
DatabaseCatalogs
11
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
Common Content
UDDIRegistries
12
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
Common Content
CASE ToolRepositories
13
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
Common Content
OntologicalRegistries
14
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.
SoftwareComponentRegistries
Common Content
15
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
Common Content
OASIS/ebXMLRegistries
16
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
Common Content
ISO 11179Registries
17
Example of Common Content across Registry Types
Common Content
OASIS/ebXMLRegistries
Common Content
ISO 11179Registries
Common Content
OntologicalRegistries
Common Content
CASE ToolRepositories
Common Content
UDDIRegistries
CountryName
SoftwareComponentRegistries
Common Content
Common Content
DatabaseCatalogs
18
RegistriesExample of Common Content
Common Content
OASIS/ebXMLRegistries
Common Content
ISO 11179Registries
Common Content
OntologicalRegistries
Common Content
CASE ToolRepositories
Common Content
UDDIRegistries
CountryName
DataElement
XML Tag
TermHierarchy
Attribute
BusinessSpecification
TableColumn
SoftwareComponentRegistries
Common Content
Common Content
DatabaseCatalogs
BusinessObject
19
OASIS/ebXML XML Registry
<Country>JPN</Country>
Repository
VI304
ListPriceCurrency
Dollars
XML Instance
UnitPrice
XML Instance
<CntryCode>JPN</CntryCode>
CollaborationPartner #1
X12
EDIFACT
<Rep href= “http://www.disa.mil”>DISA</Rep>
<ELEMENT rep= ‘DISA’ name=‘Country’ Biz =‘VI304’ >
<Rep href= “http://www.disa.mil”>DISA</Rep>
<ELEMENT rep= ‘DISA’ name=‘Country’ Biz =‘VI304’ >
Schema or Template<Rep href= “http://www.disa.mil”>DISA</Rep>
<ELEMENT rep= ‘DISA’ name=‘CntryCode’ Biz =‘VI304’ >
<Rep href= “http://www.disa.mil”>DISA</Rep>
<ELEMENT rep= ‘DISA’ name=‘CntryCode’ Biz =‘VI304’ >
Schema or Template
CollaborationPartner #2
<?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>
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
Ontological Registry
Concept Concept
ConceptConcept Geographic Area
Geographic Sub-Area
Country
Country Identifier
Country Name Country Code
Short Name ISO 31662-Character
Code
ISO 31663- Character
Code
Long Name
DistributorCountry Name
Mailing AddressCountry Name ISO 3166
3-Numeric CodeFIPS Code
24
An Example of Software Component Registry
25
Data Element List – Address Group
<?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>
ISO 11179 Registry
33c
NameStreet AddressCity, State Postal CodeCountry
26
Data Elements
DZ
BE
CN
DK
EG
FR
. . .
ZW
ISO 3166English Name
ISO 31663-Numeric Code
012
056
156
208
818
250
. . .
716
ISO 31662-Alpha Code
Algeria
Belgium
China
Denmark
Egypt
France
. . .
Zimbabwe
Name:Context:Definition:Unique ID: 4572Value Domain:Maintenance Org.Steward:Classification:Registration Authority:Others
ISO 3166French Name
L`Algérie
Belgique
Chine
Danemark
Egypte
La France
. . .
Zimbabwe
DZA
BEL
CHN
DNK
EGY
FRA
. . .
ZWE
ISO 31663-Alpha Code
Example of Common ContentCountry Identifier
Algeria
Belgium
China
Denmark
Egypt
France
. . .
Zimbabwe
Name: Country IdentifiersContext:Definition:Unique ID: 5769Conceptual Domain:Maintenance Org.:Steward:Classification:Registration Authority:Others
DataElementConcept