Post on 28-Dec-2015
National Information Exchange Model Briefing for FGDC HSWG
David Li, Ph.D.
Geospatial Management Office, DHSFeb 16, 2006
NIEM Briefing for FGDC HSWG 2
GMOGMO
Introduction National Information Exchange Model (NIEM) was launched in
February 2005 by U.S. Department of Justice (DOJ) and U.S. Department of Homeland Security (DHS) Chief Information Officers (CIO).
Authority and Motivation for NIEM comes from the Homeland Security Presidential Directive-5 (HSPD-5) and the Homeland Security Act of 2002.
NIEM Focuses on Cross-Domain Information Exchange Package (IEP) Standards for Data Exchanged among Agencies as part of their Current or Intended Business Practices.
NIEM will Standardize the Information Exchange Package Contents, Provide tools, and Manage Processes.
NIEM Briefing for FGDC HSWG 3
GMOGMO
Significance of NIEM NIEM is Envisioned to be the Data
Model to facilitate the Information Exchange Package (IEP) Development in the Federal Enterprise Architecture (FEA) Data Reference Model (DRM).
IEP is a set of data that is shared for a specific business purpose; the actual transmitted XML instance that delivers the payload or information (on the wire).
NIEM is Proposed as the Basis of the DHS Enterprise Logical Data Model (ELDM).
DHS ELDM is Identified as the Prerequisite of the Implementation of the DHS Enterprise Service Oriented Architecture (SOA) in the DHS Enterprise Architecture (EA).
NIEM will facilitate Information Exchange among DHS components and Between DHS and States and Locals to Improve Situation Awareness Capability.
NIEM Briefing for FGDC HSWG 4
GMOGMO
NIEM Core (a collection of namespaces)
JusticeJusticeEmergency MgtEmergency Mgt
ImmigrationImmigration
IntelligenceIntelligence
NIEM Architecture
UniversalUniversal
CommonCommon
StructuresStructures
Governed by NIEM Technical Architecture Group (NTAG)
that coordinate and cooperate with the NIEM governing body
NIEM Participants: (1) Bring domain content to NIEM.(2) Conform to NIEM NDR.(3) Agree to NIEM governance
policies and procedures.(4) Participate in NIEM governance.
Core: jointly governed through the NIEM governing body
Requires joint governance and reconciliation; but relatively stable
The minimally supported set for all participating domains;universally understood; very
stable; minimal or no subsetting
Where NIEM tiger teams operate
Domains
Core
Int’l TradeInt’l Trade
GeospatialGeospatial
NIEM Briefing for FGDC HSWG 5
GMOGMO
Tools, methods, mapping, process, training,
etc.
New IEPDs
IEP
Ds
New IEPDs
New reusablecomponents
NIEM IEP Concept
HomelandSecurity
Justice
Universal
Transportation
Geospatial
Intelligence
AmberAlert<AmberAlert>
AmberAlert<AmberAlert>
Transport<Transport>
Transport<Transport>
EDXL_MsgEDXL_Msg
Virtual Object Reuse Repository – types, properties, business containers,
message constructs, service metadata, …
EmergencyManagement
IEPDTemplate
IEPDTemplate
Information ExchangePackage Descriptions (IEPDs)
GovernanceBodiesExchange
Requirements
CollaborativeTools
(for distributedconsensus)
CollaborativeTools
(for distributedconsensus)
New components
Semanticallyconsistentacross alldomains
reusable components
CommonStructures
Core
NIEM Briefing for FGDC HSWG 6
GMOGMO
2005 2006 Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
NIEM
0.2 IEPDT 1.0
Formal governance in place governance planning
IEPDT 1.n
Interim NIEM governance
0.3 1.0bNIEM 0.1
Based on refactoredGJXDM 3.0.3
Based on refactoredGJXDM 3.0.3
NIEM workshops (in Jan and May) digest feedback collected by conference calls and NIEM
Configuration Control Tool
NIEM workshops (in Jan and May) digest feedback collected by conference calls and NIEM
Configuration Control Tool
RC = Release Candidate
0.2 NIEM 1.1 RC.xls
Spreadsheet marks GJXDM for NIEM partitioning
Spreadsheet marks GJXDM for NIEM partitioning
Begin to buildtest msgs
Begin to buildtest msgs
SSGT 0.1
New features in NIEM 0.2 based on GJXDM 3.1(NOT dependent on
XSTF approval of 3.1)
New features in NIEM 0.2 based on GJXDM 3.1(NOT dependent on
XSTF approval of 3.1)
Tools IEPD Tool 0.3
feedback feedback0.4 public comment
NIEM 1.0 Operational
NIEM 1.0-beta for public comment
0.4
NIEM Schedule NOW
Geospatial NIEM Insertion
DHS Geospatial Management Office
NIEM Briefing for FGDC HSWG 8
GMOGMO
Background ~ 80% of ALL data can be related to a geographic location or
feature on the earth’s surface. There are significant existing investments on geospatial standards,
encoding schema for information exchange and interoperability, and related vendor implementations.
Standards organizations and consortia, including ISO/TC211, the Open Geospatial Consortium (OGC), the U.S. Federal Geographic Data Committee (FGDC), the Urban and Regional Information Systems Association (URISA), the Organization for the Advancement of Structured Information Systems (OASIS), the Open Mobile Alliance (OMA), and the Emergency Interoperability Consortium (EIC), have invested years, and in some cases more than a decade of effort in developing consensus standards for geospatial information and technology, and promoting the commercial adoption of those standards.
The DHS Geospatial Management Office (GMO) has a Mandate to Manage DHS Geospatial Assets.
NIEM Briefing for FGDC HSWG 9
GMOGMO
Approach Geospatial NIEM Proposed Insertion takes a Standard-Based Approach:
Incorporate Significant ISO, FGDC, OGC and Other Geospatial Standards Promote Interoperability though International and National Standards Leverage Existing Geospatial Investments
is U.S. member body of
Participates instandards
development
Accredits U.S. TAG to
is an advisory member ofis a voting member of
Other StandardsDevelopmentOrganizations
Accredited StandardsDevelopment Organization
FederalStandards
Open GeospatialConsortium (OGC)
Consortia andAcademia
International Committeeon Information
Technology Standards(INCITS)
American NationalStandards Institute (ANSI)
ISO TechnicalCommittee(TC) 211
ISO
NIST
OMB
FGDCStates
Municipalities
INCITS TechnicalCommittee L1
is strategic member of
W3COASIS
etc.
is liason with
is Technical Committee of
is accredited by
is a Subcommittee of
MOU
reports to
sets policy for
State/Local Standards
NIEM Briefing for FGDC HSWG 10
GMOGMO
Core Geospatial Data Types and Associated Geospatial StandardsType Standards
Feature ISO Geography Markup Language (GML) [2], and OGC GML simple feature profile [3]
Location (Object)
ISO GML [2], Open Location Services (OpenLS®) [4], and FGDC Street Address Data Standard [5]
Coverage ISO GML [2]
Observation OGC Observations and Measurements [6]
Route[1] Open Location Services (OpenLS®) [4], andISO Location Based Services – Multimodal routing and navigation [7]
Map ISO Web Map Server interface [8]
Mobile Object
ISO GML [2], and ISO Schema for moving features [9]
Alert OASIS Common Alert Protocol (CAP) [10], and ISO GML [2]
Structure LandXML [11] and ifcXML [12]
HSIP FGDC Homeland Security Infrastructure Protection (HSIP) Geospatial Data Content [13] and the types: Feature, Location, and Address
1. U.S. Department of Homeland Security (DHS) and U.S. Department of Justice (DOJ), “National Information Exchange Model, version 0.2,” December, 2005. http://niem.gov/niem02.php
2. International Standards Organization, "ISO 19136: Geographic information - Geography Markup Language (GML)," February, 2004. This document is equivalent to following document.
1. Open Geospatial Consortium, Inc., "OpenGIS® Geography Markup Language (GML) Encoding Specification, version 3.1.1," OGC Document Number 03-105r1, http://portal.opengeospatial.org/files/?artifact_id=4700
3. Open Geospatial Consortium, Inc., "GML simple features profile, version 0.0.28," OGC Document Number 05-033r18, not yet publicly available.
4. Open Geospatial Consortium, Inc., "OpenGIS® Location Service (OpenLS) Implementation Specification: Core Services, version 1.1," OGC Document Number 05-016, http://portal.opengeospatial.org/files/?artifact_id=8836
5. Federal Geographic Data Committee, Address Standards Working Group, "Street Address Data Standard, Working Draft 2.0," November 2005, http://www.urisa.org/FGDC_addr_standard/05-11.2ndDraft.CompleteDoc.pdf
6. Open Geospatial Consortium, Inc., "Observations and Measurements, version 0.11.0," OGC Document Number 05-087r1, not yet publicly available.
7. International Standards Organization, "ISO 19134: Geographic information – Location Based Services – Multimodal routing and navigation,” April, 2004.
8. International Standards Organization, "ISO 19128: Geographic information – Web Map Server interface,” November, 2005.
9. International Standards Organization, "ISO 19141: Geographic information – Schema for moving features,” May, 2005.
10. Organization for the Advancement of Structured Information Standards (OASIS), “OASIS Standard CAP-V1.1,” October, 2005. http://www.oasis-open.org/committees/download.php/14759/emergency
11. LandXML.org, “LandXML-1.1 Schema,“ December, 2005. http://www.landxml.org/schema/LandXML-1.1/LandXML-1.1.xsd
12. International Alliance for Interoperability (IAI), “Industry Foundation Classes (IFC)2x2, Addendum 1“ July, 2004. http://www.iai-international.org/Model/IFC(ifcXML)Specs.html
13. Federal Geographic Data Committee, Homeland Security Working Group, "Guidelines for Homeland Security Infrastructure Protection Geospatial Data Content, Version 1.0 (FOUO)," December 2005. Contact gmo@dhs.gov to request access.
NIEM Briefing for FGDC HSWG 11
GMOGMO
Recommendations Add Geospatial Types to NIEM within a Separate Geospatial
Namespace from those that currently exist. Add Geospatial Standard-Based Definitions from the provided
schema (see the associated proposed insertion package) under a target geospatial namespace for use in all NIEM Information Exchange Packages (IEP) if geospatial types are needed.
Existing NIEM processes can continue to use existing NIEM definitions for geospatial components, such as location type, but those definitions should be deprecated in favor of the standards-based, industry-compatible types described in the associated geospatial schema package.
Future NIEM processes should be designed and constructed to use the Geospatial Standard-Based Definitions for NIEM Geospatial Core Types.
NIEM Briefing for FGDC HSWG 12
GMOGMO
Recommendations – Geospatial Schema PackageFile Contents
hsip.xsd The schema for the Homeland Security Infrastructure Protection (HSIP) IEP. This was drafted as a separate schema under the assumption that it is for the NIEM HSIP domain, not part of the NIEM core. If that assumption is incorrect, the definitions in this schema can be moved to geoSpatial4niem.xsd and edited to share the core NIEM geospatial target namespace and prefix.
geoSpatial4niem.xsd The schema of core geospatial types for NIEM, including Feature, Location, Coverage, and Observation types. It is a GML Application Schema that defines types following NIEM conventions for identity, associations, roles and metadata by extending XML types from geospatial standards.
gml4niem.xsd A profile of Open Geospatial Consortium Geography Markup Language (GML) version 3.1.1 schemas for NIEM version 0.2. Deprecated GML3.1.1 types like gid are eliminated because they will not be included in the ISO TC/211 19136 version of the GML standard.Includes support for Feature, Location, Coverage, and Observation types.
xls4niem.xsd A profile of Open Geospatial Consortium OpenLS schema for NIEM. Supports the Location and Route types
om4niem.xsd Support for Observation type.
StreetAddressDataStandard.xsd The schema for the FGDC Address Data Content Standard, used by the Location type.
context4niem.xsd Adaptation of OGC Web Map Context schema, that imports version 1.0.20 definitions from the StyledLayerDescriptor schema instead of the version 1.0.0 ones used by the standard. Used by the Map type.
StyledLayerDescriptor4niem.xsd Supporting Styled Layer Description (SLD) schema for Web Map Context. Used by the Map type.
filter4niem.xsd Supporting schema for SLD. Used by the Map type.
xlinks.xsd Supporting schema for Observations, Context, and SLD.
hsipSample.xml Sample instance document for HSIP IEP.
NIEM Briefing for FGDC HSWG 13
GMOGMO
Some Technical Design Considerations Adopt the GML type/property element naming convention that uses
[LeadingUpperCamelCase] names for elements of XML complex types derived from gml:AbstractGMLType, and [leadingLowerCamelCase] names for attributes, attribute groups, elements of simple type and for gml property types that follow the design pattern of gml:AssociationType, gml:_association element, gml:FeaturePropertyType, and gml:featureProperty element.
Geospatial Namespace: targetNamespace="http://niem.gov/niem/gs" Follow NIEM conventions, it uses substitution groups and roles
rather than XML/Schema choice model groups to offer alternative definitions of an object where one type would not satisfy all use case requirements.
Use abstract address type serves as the head of a substitution group that includes elements of a variety of different address types from different sources, including OpenLS, the URISA/FGDC StreetAddressDataStandard, and NIEM. An application schema can define a complex type that includes a reference to this element when any element in the substitution group may occur in an instance document.
NIEM Briefing for FGDC HSWG 14
GMOGMO
An Example – LocationType<complexType name="LocationType">
<complexContent> <extension base="u:SuperType"> <sequence>
<element ref="gs:RoleOfPoint" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfLineString" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfPolygon" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfMultiGeometry" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfMultiPoint" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfMultiCurve" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfMultiSurface" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfCircleByCenterPoint" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfArcByCenterPoint" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfFeature" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfEllipse" minOccurs="0" maxOccurs="unbounded"/> <element ref="gs:RoleOfMultiPolygon" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfPosition" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfPointOfInterest" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfAreaOfInterest" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfXLSAddress" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUrisaSiteAddress" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUrisaLandmarkSiteAddress" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUrisaIntersectionAddress" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUrisaTwoNumberAddressRange" minOccurs="0“ maxOccurs="unbounded"/><element ref="gs:RoleOfUrisaFourNumberAddressRange" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUrisaUnnumberedThoroughfareAddress" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUrisaSingleSiteLandmarkAddress" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUrisaMultiSiteLandmarkAddress" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUrisaCommunityAddress" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUrisaUSPSPostalDeliveryBox" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUSPSPostalDeliveryRoute" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUSPSGeneralDeliveryAddress" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfUSPSGeneralAddress" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfNiemAddress" minOccurs="0" maxOccurs="unbounded"/><element ref="gs:RoleOfNiemGeographicCoordinate" minOccurs="0" maxOccurs="unbounded"/>
</sequence> </extension></complexContent>
</complexType>
NIEM Briefing for FGDC HSWG 15
GMOGMO
Data File
• Data pulled from a database• Modeled with an XML schema• Transport data in valid XML instance• Can transform w/ XSL for display• Data loaded into receiving database
Database
• Data pulled from a structured data file • Modeled with an XML schema• Transport data in valid XML instance• Can transform w/ XSL for display
DB
DocXML
XMLXSL
DB
Exchange XML Documents
NIEM Briefing for FGDC HSWG 16
GMOGMO
An Exchanged XML Instance Example<HSIPFeatureCollection xmlns="http://niem.gov/niem/hsip" xmlns:addr="http://wfs.co.fulton.ga.us/urisa/addr_std/addr" xmlns:gml="http://www.opengis.net/gml" xmlns:gs="http://niem.gov/niem/gs" xmlns:i="http://niem.gov/niem/appinfo/0.2" xmlns:s="http://niem.gov/niem/structures/0.2" xmlns:u="http://niem.gov/niem/universal/0.2" xmlns:x="http://www.w3.org/1999/xhtml" xmlns:xls="http://www.opengis.net/xls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://niem.gov/niem/hsip hsip.xsd" gml:id="ID000000"> <gml:description>SampleHSIPFeatureCollection</gml:description> <gml:name codeSpace="http://www.niem.gov">Sample</gml:name> <gml:boundedBy>
<gml:Envelope srsName="urn:EPSG:geographicCRS:4326" srsDimension="2"><gml:lowerCorner>-74.35 34.58</gml:lowerCorner><gml:upperCorner>-74.31 34.77</gml:upperCorner>
</gml:Envelope> </gml:boundedBy> <hsipFeatureMember>
<PrivateBankingAndCreditInstitution gml:id="Citibank47" s:metadata="Citibank47Address Citibank47Point“ s:linkMetadata="Citibank47Location Citibank47POC">
<gs:addressProperty><gs:SiteAddress s:id="Citibank47Address">
<addr:CompleteAddressNumber><addr:Number>234</addr:Number>
</addr:CompleteAddressNumber><addr:CompleteStreetName>
<addr:StreetNamePreDirectional>NORTH</addr:StreetNamePreDirectional><addr:StreetName>Main</addr:StreetName><addr:StreetNamePostType>STREET</addr:StreetNamePostType>
</addr:CompleteStreetName><addr:PlaceName>
<addr:MunicipalJurisdiction>Rockville</addr:MunicipalJurisdiction></addr:PlaceName>
</gs:addressProperty><gml:geometryProperty>
<gs:Point gml:id="Citibank47Point"><gml:pos>-74.312345 34.678901</gml:pos>
</gs:Point></gml:geometryProperty><gs:locationProperty>
<gs:Location s:id="Citibank47Location"> <gs:RoleOfPoint s:id="Citibank47PointLocation" s:ref="Citibank47Point"/> <gs:RoleOfUrisaSiteAddress s:id="Citibank47AddressLocation" s:ref="Citibank47Address"/></gs:Location>
</gs:locationProperty></PrivateBankingAndCreditInstitution>
</hsipFeatureMember>
……
NIEM Briefing for FGDC HSWG 17
GMOGMO
For More Information To Learn More on NIEM Concept of Operations and
NIEM Schema: http://niem.gov To Get a Copy of DHS GMO Geospatial NIEM Insertion
Package, Please Contact Mike Lee at Michael.P.Lee@dhs.gov (Comments and Suggestions are Highly Appreciated)
For All Other Questions, Contact Dr. David Li at david.li@associates.dhs.gov (telephone: 202-205-5467)