Help


[permalink] [id link]
+
Page "National Information Exchange Model" ¶ 15
from Wikipedia
Edit
Promote Demote Fragment Fix

Some Related Sentences

NIEM and .
In the United Kingdom, for example, there is an eGovernment-based interoperability initiative called e-GIF while in the United States there is the NIEM initiative.
GML can also be included in version 2. 1 of the United States National Information Exchange Model ( NIEM ).
The National Information Exchange Model ( NIEM, pronounced as ' Neam ' similar to ' Team ') is an XML-based information exchange framework from the United States.
NIEM represents a collaborative partnership of agencies and organizations across all levels of government ( federal, state, tribal, and local ) and with private industry.
NIEM is designed to develop, disseminate, and support enterprise-wide information exchange standards and processes that will enable jurisdictions to automate information sharing.
NIEM is an outgrowth of the United States Department of Justice's Global Justice XML Data Model ( GJXDM ) project.
NIEM is now being expanded to include other federal and state agencies such as the Office of the Director of National Intelligence, Federal Bureau of Investigation, Texas, Florida, New York, Pennsylvania, and others.
NIEM is not a software program, database, network, or computer system.
NIEM is designed to facilitate the creation of automated enterprise-wide information exchanges which can be uniformly developed, centrally maintained, quickly identified and discovered, and efficiently reused.
The following key concepts are essential to understanding the purpose, architecture, processes, and other capabilities of NIEM, as well as to establish a common knowledge base with which to develop the ability to use NIEM effectively.
The fundamental building block of NIEM is the data component.
Components that are frequently and uniformly used in practice are specified in NIEM and can then be reused by practitioners for information exchanges, regardless of the nature of their business or the operational context of their exchanges, provided they are semantically consistent.
NIEM Core.
The set of NIEM universal components is stable ( once established ) and relatively small.
For purposes of NIEM, a domain refers to a business enterprise broadly reflecting the agencies, units of government, operational functions, services, and information systems which are organized or affiliated to meet common objectives.
NIEM domains are organized to facilitate governance, and each has some measure of persistency.
COIs reuse data components and artifacts found in NIEM to document their information exchanges.
NIEM Conformance.
There are NIEM conformance rules that serve as guidelines for agencies utilizing NIEM to implement their information sharing exchanges.
Grantees developing inter-agency XML-based exchanges must comply with the special condition language contained in the grant, and follow the associated NIEM implementation guidelines.
NIEM is a continually evolving program, and new agencies and COIs are joining the effort all the time.
As new stakeholders come on board, they need to receive information to gain understanding and knowledge of the core capabilities of NIEM and how to engage in NIE information exchanges.

NIEM and gov
* The official NIEM. gov website

NIEM and provides
Training provides the knowledge and know-how stakeholders need to use the tools and other capabilities provided by NIEM.
The naming and design rules for NIEM are documented in the NIEM NDR, which specifies the data model, XML components, and XML data for use with NIEM and provides a basis for NIEM conformance.
NIEM is based on several concepts from the International Organisation for Standardisation ( ISO ) 11179, which provides guidelines for the naming and definition of data elements, as well as information about the metadata captured about data elements.
NIEM provides a reference set of tools freely available with each NIEM release.
The Wayfarer tool provides an alternative to the SSGT for designers to select existing components from the NIEM dictionary and assemble want lists for use in NIEM subset schema generation.

NIEM and training
NIEM tools and training opportunities are further described below.

NIEM and such
NIEM adopts standard XML Schema constructs and methods, such as roles, associations, and augmentation from industry standards, such as the World Wide Web Consortium ( W3C ) XML Schema language.
The NIEM schemas may import additional schemas, such as code table schemas, as needed.
The following are samples of Representation Terms that have been used for the exchange of electronic messages in systems such as NIEM or GJXDM 3. 0: the restrictions expressed here are limited to those specifications and do not represent universal consensus

NIEM and documentation
The NIEM Web site serves as a primary means by which NIEM can provide the latest documentation and downloads to those interested in NIEM.
3rd Party IEPD tool support includes automatic generation of NIEM cross-reference, wantlist. xml, exchange and subset schema, XML examples, rules documentation and NDR evaluation.

NIEM and resources
As related projects, tools, and support resources develop around NIEM, the Web site will expand as the hub for these supplemental resources.

NIEM and National
The NISS Help Desk assists users in finding answers to technical questions regarding the content, principles, and best practices for using the National Information Exchange Model ( NIEM ) and Global Justice XML Data Model ( GJXDM ).
* National Information Exchange Model ( NIEM )
* US National Information Exchange Model NIEM

NIEM and Information
* Global JXDM & NIEM: Moving Toward Seamless Information Sharing
NIEM has introduced the concept of Enterprise Information Exchange Model ( EIEM ) dictionaries to allow NIEM implementers to position local collections of components specific to their own enterprise.
The Information Exchanges Mapping Tool allows the user to specify metadata and upload XMI domain models associated with NIEM IEPDs, map components within domain models to NIEM components, and generate artifacts based on mappings, including mapping reports, wantlist, exchange schemas, extension schemas, and subset schemas.

0.751 seconds.