FAQs
The NIEM Release history timeline:
Release Candidate (RC) - August 2013
NIEM 3.0 Beta - May 2013
NIEM 3.0 Alpha 2 - March 2013
NIEM 3.0 Alpha 1 - February 2013
NIEM Pre-Alpha - September 2012
NIEM 3.0 Kick-Off - August 29, 2012
NIEM 2.1 Production Release - September 2009
NIEM 2.0 Production Release – July 31, 2007
NIEM 2.0 Release Candidate 2 - June 2007
NIEM 1.0 Production Release – November 1, 2006
NIEM 1.0 Release Candidate 1 – September 30, 2006
NIEM 1.0 Beta 3 – September 11, 2006
NIEM 1.0 Beta 2 – August 8, 2006
NIEM 1.0 Beta 1 – June 30, 2006
NIEM 0.3 – April 12, 2006
NIEM 0.2.1 – February 24, 2006
NIEM 0.2 – December 23, 2005
NIEM 0.1 – October 11, 2005
By default the national community is highly encouraged to develop IEPDs using NIEM 2.0. In the case that the project is critical, under strict time constraints, and staff is well-educated and well-versed in GJXDM but has no exposure to the NIEM it would be a viable choice to instead develop IEPDs using GJXDM 3.0.3.
Although it is difficult to list pros and cons of each model it is worth mentioning that NIEM introduces new concepts that remedy shortcomings identified in the GJXDM. These concepts are called associations, roles, and metadata.
Associations
GJXDM 3.0.3 relies on element inclusion and referencing for representing relationships between objects. As the GJXDM has become more heavily used it has been determined that there are several issues with these methods of data association. In response NIEM introduced a new mechanism for data object associations, simply coined "associations". The new association concept closely resembles a relational model. NIEM associations accommodate n-ary associations whereas the GJXDM does not. Also, with the GJXDM it is not possible to apply metadata to a data association; the new NIEM association mechanism makes this possible.
[Reference articles #235 and #236 ]
Roles
GJXDM 3.0.3 was not designed with the concept of "roles" in mind; instead inheritance is used to apply role-specific properties to a base object. NIEM only uses inheritance in the seldom case that an object is truly a specialized type of the base object; therefore roles in the NIEM do not use inheritance. NIEM has adopted the idea that a role represents a certain function of a base object. The NIEM role mechanism allows a base object to take on several roles, the GJXDM does not easily accommodate this.
[Reference article #239]
Metadata
GJXDM 3.0.3 relies on inheritance from the SuperType class for the distribution metadata information throughout the model. Because the NIEM has addressed this as misuse of inheritance it does not rely on inheritance from a base structure for the application of metadata throughout the model. NIEM introduces a new independent structure specifically for the application of metadata. NIEM makes it very simple to apply metadata to roles, associations, and basic properties. This structure allows sets of metadata to be extended and applied to only those objects requiring the extended set of metadata. Metadata properties can also be repeated (cardinality set to 0..*), this was not possible in the GJXDM. Metadata structures can be created and applied to multiple different objects; also an object may be related to multiple metadata structures.
[Reference article #238]
*Web Site Link: |
http://niem.gtri.gatech.edu/niemtools/iepdt/display/container.iepd?ref=Y9MPHRjRYsI |
|
Description: |
This package includes NIEM 2.0 artifacts supporting the exchange of prescription monitoring program (PMP) data between state PMP systems. |
|
*Exchange Partners: |
|
|
Other Exchange Partners: |
||
*NIEM Version: |
2.0 |
|
*Project Start Date: |
||
Last Revision Date: |
||
Next Revision Date: |
||
*Status: |
Draft |
|
Status Description: |
Being updated as part of the IJIS Phase III Hub Pilot Project |
|
Schedule: |
Through December, 2009 |
|
*Participating Organizations: |
IJIS Institute, Ohio State Board of Pharmacy, Kentucky Cabinet for Health and Family Services, Nevada Board of Pharmacy, New York Bureau of Narcotic Enforcement |
|
*Contact Name: |
||
*Contact E-mail: |
||
*Contact Phone: |
||
Contact Fax: |
||
*Contact Organization: |
||
Organization Web Site: |
||
Street Address: |
||
City: |
||
State: |
||
Country: |
||
Zip Code: |
43215-6126 |
NIEM is the National Information Exchange Model. This is an interagency initiative to provide the foundation and building blocks for national-level interoperable information sharing and data exchange. The NIEM project was initiated on 28 February 2005 as a joint venture between the U.S. Department of Homeland Security (DHS) and the U.S. Department of Justice (DOJ) with outreach to other Government departments and agencies. The NIEM leverages both the Global Justice XML Data Model (GJXDM) reference model and the GJXDM XML-based framework and support infrastructure.
This package contains the NIEM reference schemas (Core, code lists, domains, type adapters for external standards, as well as the schemas, schema profiles, or adaptations for those standards.) It also contains a cumulative change log and the spreadsheet. NIEM provides practitioners and developers with a baseline set of XML Schema components for building Information Exchange Package Documentation (IEPDs).
NIEM release 2.1 is based on the NIEM Naming and Design Rules (NDR) 1.3 and the Type Augmentation Supplement to NDR 1.3 (version 1.0, 24 September 2009).
Release Package
NIEM 2.1 - The release package includes all NIEM schemas for this release as well as the changelog, spreadsheet, and schema index.
Documentation
- Catalog - Catalog of files; the file you are viewing now.
- Schemas - A complete list of schemas included in this distribution.
- Spreadsheet - A hyperlinked, textually oriented model and dictionary of the NIEM content.
- Change Log - List of changes since last release.
- Alternative data formats - Alternative to XSD format; contains metadata for all 2.1 data components in three formats: CSV, MS Access, and MS Excel.
- Index to data components by namespace - Links to HTTP URIs and associated documentation pages for each 2.1 data component.
NIEM Core Schemas
- niem-core: NIEM Core includes both Universal (U) and Common (C) components. The identities for U and C components in Core are maintained with metadata.
NIEM Domain Schemas
- cbrn: Chemical, Biological, Radiological, and Nuclear Domain
- emergencyManagement: Emergency Management
- familyServices: Family Services
- immigration: Immigration
- infrastructureProtection: Infrastructure Protection
- intelligence: Intelligence
- internationalTrade: International Trade
- jxdm: Justice
- maritime: Maritime
- screening: The People Screening domain provides harmonized information sharing content within the Screening Portfolio of DHS. The Screening namespace is initially being populated with person screening information for immigrant and non-immigrant person types who have been encountered and identified by the Screening Portfolio Components. Screening expands on encounter-related NIEM elements currently included in the Immigration and Intelligence domains.
NIEM Conformant Schemas (code lists and adaptations of external standards)
- ansi_d20: Motor vehicle administration codes from ANSI D20, the Data Dictionary for Traffic Record Systems, maintained by AAMVA, the American Association of Motor Vehicle Administrators.
- ansi-nist: ANSI/NIST Fingerprint and Biometric standard.
- apco: Association of Public-Safety Communications Officials (APCO) - International, Inc.
- atf: Bureau of Alcohol, Tobacco, and Firearms
- cbrncl: Radiological and Nuclear Code List
- census: Employment codes from the U.S. Census Bureau
- dea: Drug Enforcement Administration
- dod_jcs-pub2.0-misc: Intelligence discipline codes from the U.S. Department of Defense (DoD) Joint Publication 2.01.
- edxl: Emergency Data Exchange Language
- edxl-cap: Common Alerting Protocol
- edxl-de: Distribution Element
- edxl-have: EDXL-HAVE specifies an XML document format that allows the communication of the status of a hospital, its services, and its resources. These include bed capacity and availability, emergency department status, available service coverage, and the status of a hospital's facility and operations.
- fbi: FBI code lists for National Crime and Information Center (NCIC-2000), National Incident-Based Reporting System (NIBRS), and National Law Enforcement Data Exchange (N-DEx).
- fips_10-4: Countries, dependencies, areas of special sovereignty, and their principal administrative divisions from the Federal Information Processing Standards (FIPS) 10-4.
- fips_5-2: Codes for the identification of the states, the District of Columbia and the outlying areas of the U.S., and associated areas from the Federal Information Processing Standards (FIPS) 5-2.
- fips_6-4: Counties and equivalent entities of the U.S., its possessions, and associated areas from the Federal Information Processing Standards (FIPS) 6-4.
- geospatial: Defines NIEM adapter types for external geospatial components defined by OGC and ISO. It references local copies of unmodified schemas from external standards in local directory tree fragments that mirror the directory structures of the cannonical schema sources on the world wide web, and a profile of the OGC Open Location Services (XLS) schema that is based on GML version 3.2.1.
- have-codes: EDXL Hospital AVailability Exchange (HAVE) code sets
- hazmat: Pipeline and Hazardous Materials Safety Administration - Office of Hazardous Materials Safety
- iso_3166: Codes for the representation of names of countries and their subdivisions from the International Organization for Standardization (ISO) 3166-1:1997.
- iso_4217: Codes for the representation of currencies and funds from the International Organization for Standardization (ISO) 4217:2001.
- iso_639-3: Codes for the representation of names of languages - Part 3: Alpha-3 code for comprehensive coverage of languages.
- itis: Integrated Transportation Information System
- lasd: Los Angeles County Sheriff's Department
- mmucc_2: Model Minimum Uniform Crash Criteria
- mn_offense: Statute and offense codes from the state of Minnesota.
- nga: National Geospatial Agency
- nlets: NLETS - The International Justice and Public Safety Information Sharing Network
- nonauthoritative-code: Non-authoritative codes for the direction of a person's pose in an image.
- post-canada: Province codes for Canada.
- sar: Suspicious Activity Reporting
- twpdes: Terrorist Watchlist Person Data Exchange Standard
- ucr: Crime reporting codes from Uniform Crime Reporting.
- unece_rec20-misc: Miscellaneous unit of measure codes from the United Nations Economic Commission for Europe Recommendation No. 20, Codes for Units of Measure used in International Trade.
- usps_states: U.S. state and possession abbreviations from the U.S. Postal Service (USPS).
- ut_offender-tracking-misc: Plea and military discharge codes from the Utah Offender Tracking Database, version 2.03.
NIEM Proxy Schemas
- xsd: Proxy types that carry dictionary metadata and have XML data type simple contents.
Special NIEM Schemas
- appinfo: Elements for use within xsd:appinfo to indicate information supporting the data model underlying NIEM.
- appinfo: This appinfo schema provides support for augmented types and augmented elements in NIEM domain schemas. It was written to work in tandem with the NIEM appinfo v2.0 schema.
- structures: Schema constructs for use by NIEM-conformant schemas to provide consistent definitions and functionality.
Source: http://release.niem.gov/niem/2.1/schemas.html
Documents
NIEM 3.0 will be a major release, building on the current active release NIEM version 2.1.
Please click on this link to download the NIEM BETA-1 version: http://reference.niem.gov/.3b1/niem-3.0-beta1.zip
NIEM 3.0 changes include model harmonization at both the core and domain levels. See below for specific updates and enhancements.
NIEM Core Updates
Through harmonization and content submission, NIEM Core has been updated as follows:
· Added some elements previously contained in domain content to NIEM Core
· Modified existing definitions for data elements in NIEM Core based on community input
· Added substitution group placeholders for code lists used in core, which makes plugging in updated code sets into information exchanges (i.e., IEPDs) much easier
· Updated 33 code lists in NIEM Core ensuring more timely and relevant data
NIEM Domain Content Updates
The following domains have submitted new and/or updated content for incorporation in NIEM 3.0:
· Biometrics (this domain community content marks their first input into the model)
· Chem Bio Rad Nuc (CBRN)
· Children, Youth, and Family Services (CYFS)
· Justice
· Maritime
· Immigration and Screening.
Technical Architecture Enhancements
· Augmentation: Type Augmentation is a complex concept that is often misunderstood. The NIEM 3.0 design makes type augmentation easier to understand and implement within information exchanges.
· Updating of Code Lists Independent from Releases: This enhancement allows NIEM communities to use and maintain up-to-date code lists without waiting for a future release.
· Intelligence Community Information Security Marking (IC-ISM) standard: NIEM 3.0 includes enhancements that better support the IC-ISM standard and provide the ability to leverage IC-ISM updates based on its rapid version cycle.
· Enhancements to Reference and Content-Bearing Elements: This enhancement significantly reduces complexity and duplication of NIEM elements by allowing a single element declaration to serve as a reference element or a content-bearing element.
NIEM.gov tools will be updated along with the launch of Version 3.0 to reflect architectural changes to the model.
Updated tools include:
· Schema Subset Generation Tool (SSGT): Enables users to search through the NIEM data model and build a NIEM subset.
· Conformance Testing Assistant (ConTesA): Assists developers by automatically identifying potential locations of non-conformance within IEPD artifact using the NIEM NDR 1.3 and IEPD specifications.
· Code List Generator: Provides the ability to build an XML Schema file for code sets from an Excel spreadsheet.
· NIEM-UML for v3.0: The UML Profile for NIEM (NIEM-UML) will be updated to align to 3.0. We will accommodate requests by current and prospective NIEM-UML tool vendors to incorporate NIEM 3.0 capabilities into their services.
Tool Link: http://tools.niem.gov/niemtools/home.iepd
A NIEM release represents a stable, harmonized, and production-ready data model, updated specifications, and potentially enhanced tools. NIEM supports a range of release types that are described in the NIEM High Level Versioning Architecture (HLVA) and categorized by the following release types: Micro, Minor, and Major. NIEM 3.0 will be a major release, building on the current active release NIEM version 2.1. For more information on the HLVA please refer to High-Level Version Architecture.
No. The rationale for elements vs. attributes in NIEM remains the same: The NIEM release will use elements to model NIEM properties, unless this is not possible (usually due to a type having simple content), in which case it will use attributes.
The appinfo.xsd to employ attributes (instead of element properties) was changed for several reasons. The appinfo schema defines metadata about the model, schemas, and terminology, and does not contain payload content components. Appinfo is part of NIEM infrastructure that is designed to be relatively fixed, and does not require the flexibility that users/developers need for IEPD extension and corresponding model semantics. And finally, attributes tend to make appinfo annotations simpler and cleaner.
Yes, the NIEM-UML Profile will be updated to align to 3.0. The NIEM PMO also plans to support requests by current and prospective NIEM-UML tool vendors to incorporate NIEM 3.0 capabilities into their services.
For more information on NIEM-UML, please click on this link: https://www.niem.gov/technical/Pages/niem-uml.aspx
NIEM 3.0 will be a major release, building on the current active release NIEM version 2.1. All the information that relate to the 3.0 can be found in the link below.
Please click on this link to download the NIEM 3.0 that just released: https://www.niem.gov/technical/Pages/current-release.aspx.
Click on the attachment file below to download all the release schemas for NIEM 3.0.
Documents
https://bja.ojp.gov/media/document/29976
NIEM 3.0
Description
The National Information Exchange Model (NIEM) is an interagency initiative that provides the foundation and building blocks for national-level interoperable information sharing and data exchange. Initiated in February 2005, NIEM was originally a joint venture between the U.S. Departments of Justice (DOJ) and Homeland Security (DHS) with outreach to other Government departments and agencies.
This package contains the NIEM 3.0 reference schemas (Core, code lists, domains, type adapters for external standards, as well as the schemas, schema profiles, or adaptations for those standards). It also contains a spreadsheet of the model, a spreadsheet for all code lists, a change log, and an XML catalog. NIEM provides practitioners and developers with a baseline set of reusable XML Schema components for building Information Exchange Package Documentation (IEPDs).
NIEM 3.0 contains significant architectural improvements and content changes over the last NIEM release. This version conforms to NIEM Naming and Design Rules (NDR) v3.0.
Release Package
NIEM 3.0 - The release package includes all NIEM schemas for this release as well as the changelog and spreadsheet.
Documentation
- Index - Index of files; the file you are viewing now.
- Schema list - A complete list of schemas included in this distribution.
- Component spreadsheet - A hyperlinked, textually oriented model and dictionary of the NIEM content.
- Code spreadsheet - A hyperlinked dictionary of codes in NIEM.
- Change log XML - A log identifying components that changed from 2.1 to 3.0 in XML.
- Change log spreadsheet - A log identifying components that changed from 2.1 to 3.0. Also identifies what values changed.
- Alternate data formats - Alternatives to the XSD format; contains content and metadata for all 3.0 data components in three formats: CSV, MS Access, and MS Excel.
NIEM Core Schemas
- niem-core: NIEM Core.
NIEM Domain Schemas
- biom: Biometric Schema Version 1.0
- cbrn: Chemical, Biological, Radiological, and Nuclear Domain
- cyfs: Children, Youth, and Family Services
- emergencyManagement: Emergency Management
- immigration: Immigration
- infrastructureProtection: Infrastructure Protection
- intelligence: Intelligence
- internationalTrade: International Trade
- jxdm: Justice
- maritime: Maritime
- screening: The People Screening domain provides harmonized information sharing content within the Screening Portfolio of DHS. The Screening namespace is initially being populated with person screening information for immigrant and non-immigrant person types who have been encountered and identified by the Screening Portfolio Components. Screening expands on encounter-related NIEM elements currently included in the Immigration and Intelligence domains.
NIEM Conformant Schemas (code lists and adaptations of external standards)
- ansi_d20: Motor vehicle administration codes from ANSI D20, the Data Dictionary for Traffic Record Systems, maintained by AAMVA, the American Association of Motor Vehicle Administrators. Publication: ANSI-D20 Data Dictionary Release 5.0.0; Version: May 2009; http://www.aamva.org/ANSI-D20-Standard-for-Traffic-Records-Systems
- apco_event: Association of Public-Safety Communications Officials (APCO) - International, Inc.Publication: APCO ANS 2.103.1-2012 Public Safety Communications Common Incident Types for Data Exchange; Version: 2012; http://www.apco911.org
- atf: Bureau of Alcohol, Tobacco, and FirearmsDate: 2008
- cbrncl: Radiological and Nuclear Code ListPublication: CBRN domain; Version: 3.0; Date: Oct 2013; http://release.niem.gov/niem/3.0/
- census_commodity: Census and Dept of Transportation.Publication: CFS-1200 - SCTG COMMODITY CODES; Date: 11-15-2011
- census_uscounty: County codes from US Census and ANSI. Publication: INCITS 31:2009; Version: 2009; http://www.census.gov/geo/www/ansi/download.html
- core_misc: Non-authoritative codes for the direction of a person's pose in an image.Source: NIEM 3.0; Publication: NIEM 3.0; Version: 3.0; Date: Oct 2013; http://release.niem.gov/niem/3.0/
- dea: Drug Enforcement Administration (DEA).Publication: Controlled Substances - by DEA Drug Code Number; Date: 6 Sep 2012; http://www.deadiversion.usdoj.gov/schedules/orangebook/d_cs_drugcode.pdf
- dod_jcs-pub2.0: Intelligence discipline codes.Source: DoD Joint Staff; Publication: Joint Publication 2.0 - Joint Intelligence; Date: 22 Jun 2007; http://www.dtic.mil/doctrine/new_pubs/jp2_0.pdf
- dol_soc: US Department of Labor occupation codes.Publication: Standard Occupational Classification (SOC); Version: 2010; http://www.bls.gov/SOC/
- dot_hazmat: Source: US Department of Transportation (DoT)Pipeline and Hazardous Materials Safetey Administration (PHMSA); Publication: Title 49 CFR 172.101 Table (List of Hazardous Materials); Date: 18 Jan 2012; Source Updats: 18 Jan 2012; http://www.phmsa.dot.gov/portal/site/PHMSA/menuitem.ebdc7a8a7e39f2e55cf2031050248a0c/?vgnextoid=d84ddf479bd7d110VgnVCM1000009ed07898RCRD&vgnextchannel=4f347fd9b896b110VgnVCM1000009ed07898RCRD&vgnextfmt=print
- edxl_rm: Source: EDXL Resource Messaging (RM) Standards Working Group (SWG); Publication: Emergency Data Exchange Language Resource Messaging (EDXL-RM) specification; Version: 1.0; Date: 22 Dec 2009; http://docs.oasis-open.org/emerge
- edxl-cap: Common Alerting Protocol
- edxl-de: Distribution Element
- edxl-have: EDXL-HAVE specifies an XML document format that allows the communication of the status of a hospital, its services, and its resources. These include bed capacity and availability, emergency department status, available service coverage, and the status of a hospital's facility and operations.
- fbi_ncic: FBI code lists for the National Crime and Information Center (NCIC-2000).Source: FBI Crminal Justice Information Systems (CJIS) Division; Publication: leo.gov database; https://www.leo.gov
- fbi_ndex: Source: FBI Crminal Justice Information Systems (CJIS) Division; Publication: National Data Exchange (N-Dex) Specification (a NIEM IEPD); Version: 2.2; Date: 2013; http://www.it.ojp.gov/framesets/iepd-clearinghouse-noClose.htm
- fbi_ucr: Crime reporting codes from Uniform Crime Reporting.Source: FBI Crminal Justice Information Systems (CJIS) Division; Publication: CJIS Div UCR Program - NIBRS Technical Specification; Version: 1.0; Date: 16 April 2012; http://www.fbi.gov/about-us/cjis/ucr/nibrs_technical_specification_version_1.0_final_04-16-2012.pdf
- fips_10-4: Countries, dependencies, areas of special sovereignty, and their principal administrative divisions.Source: National Geospatial-Intelligence Agency (NGA); Publication: Geopolitical Entities and Codes (formerly FIPS 10-4); Date: Apr 2010; Source Updates: 14+; http://earth-info.nga.mil/gns/html/GEOPOLITICAL_CODES.pdf
- fips_5-2: Source: National Institute for Standards and Technology (NIST); Publication: Codes for the Identification of the States, the District of Columbia, and the Outlying Areas of the U.S., and Associated Areas; Date: 28 May 1987; Source Updates: 1 Jan 1988; http://www.itl.nist.gov/fipspubs/fip5-2.htm
- fips_6-4: Source: National Institute for Standards and Technology (NIST); Publication: Counties and Equivalent Entities of the U.S., its Possesions, and Associated Areas; Date: 31 Aug 1990; Source Updates: 7 (7 Jul 2001); http://www.itl.nist.gov/fipspubs/fip6-4.htm
- geospatial: Defines NIEM adapter types for external geospatial components defined by OGC and ISO. It references local copies of unmodified schemas from external standards in local directory tree fragments that mirror the directory structures of the cannonical schema sources on the world wide web, and a profile of the OGC Open Location Services (XLS) schema that is based on GML version 3.2.1.
- have-codes: Source: OASIS Emergency Data Exchange Language (EDXL); Publication: Emergency Data Exchange Language (EDXL) Hospital AVailability Exchange (HAVE) Version 1.0; Version: 1.0; Date: 22 Dec 2009; http://docs.oasis-open.org/emergency/edxl-have/v1.0/errata/edxl-have-v1.0-os-errata-os.html
- hl7: Source: Health (HL-7); Publication: Religion-HL7 Table 0006_VD; Date: 19 Jul 2004; http://ushik.ahrq.gov/dr.ui.drConceptualDomain_View?System=mdr&ConceptualDomainID=74288000&ViewDownFile=yes&DownFile=Co
- iso_3166-1: Source: International Standards Organization (ISO); Publication: Codes for the representation of names of countries -- Part 1: Country codes; Date: 2 Aug 2012; Source Updates: VI-13; http://www.iso.org/iso/country_codes.htm
- iso_4217: Source: International Standards Organization (ISO); Publication: Codes for the representation of currencies and funds; Version: ISO 4217:2008; Date: 30 Jun 2008; http://www.iso.org/iso/en/prods-services/popstds/currencycodeslist.html
- iso_639-3: Source: International Standards Organization (ISO); Publication: Codes for the representation of names of languages -- Part 3: Alpha-3 code for comprehensive coverage of languages; Version: ISO 639-3:2007; Date: 2007; Source Updates: 5 Feb 2007; http://www.sil.org/iso639-3/
- it_codes: IT Codes
- mmucc: Source: Model Minimum Uniform Crash Criteria (MMUCC); Publication: MMUCC Guideline - Model Minimum Uniform Crash Criteria - 3rd Edition; Version: 3.0; Date: 2012; Source Updates: 31 Oct 2006;
- nga_datum: Source: National Geospatial-Intelligence Agency; Publication: Temporal Spatial Positioning Information (TSPI) ; Version: 2.0; Date: 1 Mar 2012; http://metadata.ces.mil/dse/ns/GSIP/tspi/2.0.0/tspi-core.xsd
- nga_genc: The Geopolitical Entities, Names, and Codes (GENC) Standard, the US Government implementation of ISO 3166.Source: NGA; Publication: GENC Standard; Version: Ed 1.0; Date: 27 Nov 2012; https://nsgreg.nga.mil/genc/discovery
- nlets: Source: The International Justice & Public Safety Information Sharing Network; Publication: NLETS User and Technical Guide; Date: 2006; http://www.nlets.org/
- occs_facility: OmniClass; Publication: OCCS Table 11; Date: 30 Oct 2012; http://www.omniclass.org/tables.asp
- post-canada: Province codes for Canada.Publication: Canada Post Addressing Guidelines; Date: 14 Jan 2013; http://www.canadapost.ca/tools/pg/manual/PGaddress-e.asp#1380608
- sar: Source: PM Information Sharing Environment (ISE); Publication: SE-FS-200-version-1.5 Suspicious Activity Reporting (SAR); Version: 1.5; Date: 25 Aug 2009; http://niem.gtri.gatech.edu/niemtools/iepdt/display/container.iepd?ref=ntsXeIX7M6Q%3D
- unece_rec20-misc: Miscellaneous unit of measure codes.Source: UN Economic Commission for Europe (UNECE); Publication: UNECE Recommendation No. 20 Revision 8; Version: Revision 8; Date: 2012; http://www.unece.org/tradewelcome/areas-of-work/un-centre-for-trade-facilitation-and-e-business-uncefact/outputs/cefactrecommendationsrec-index/list-of-trade-facilitation-recommendations-n-16-to-20.html
- usps_states: Source: U.S. Postal Service (USPS); Publication: Official USPS Abbreviations, Appendix B; Date: 2012; http://pe.usps.com/text/pub28/28apb.htm
- xCard: vCard XML representation, IETF RFC 6351
NIEM Proxy Schemas
- xs: Proxy types that carry dictionary metadata and have XML data type simple contents.
Special NIEM Schemas
- appinfo: Elements for use within xsd:appinfo to indicate information supporting the data model underlying NIEM.
- structures: Schema constructs for use by NIEM-conformant schemas to provide consistent definitions and functionality.
The release schemas can be downloaded here: http://release.niem.gov/niem/3.0/niem-3.0.rel.zip
NIEM 3.0 will be a major release, building on the current active release NIEM version 2.1. For more information on the HLVA please refer to High-Level Version Architecture. In the NIEM 3.0 zip file below, it will included all the new namespaces, schema index, summary for NIEM 3.0, alternated data format, and more....
To download all the NIEM version from 1.0 to 3.0, please click HERE.
To download only the NIEM 3.0 version package, please click on the file below.
Documents
https://bja.ojp.gov/media/document/29981
In September 2013, the Object Management Group (OMG) Board of Directors officially finalized the Unified Modeling Language (UML) Profile for NIEM (or NIEM-UML) as an OMG specification. NIEM-UML for Version 2.1 is now available!
NIEM-UML is an extension of a subset of UML that is specific to NIEM. NIEM-UML, when implemented in a tool, generates 100% NIEM-conformant information exchanges and provides a visual representation of those exchanges that is understandable to both technical and business users. This enables organizations to align their information exchanges with their business requirements.
We invite you to join the submission team as a contributor or reviewer. We expect to have conference calls every other week to discuss updates and items that require a decision. If you'd like to be added to the team distribution list, please reach out to us here.
Final approval is expected in the April 2015 timeframe.
More information, please click on this link: https://github.com/NIEM/NIEM-UML
NIEM 3.1 Alpha-1 Version is a test version of NIEM 3.1. This minor upgrade version will associate with our NIEM NDR 3.0 and MPD 3.0. There will be no changes to NDR 3.0 and MPD 3.0 in this upgrade. The final version of NIEM 3.1 will be released in 2015, and the date is not yet finalized due to the workflows and decision making from NIEM PMO. We recommend all NIEM users who want to stay informed on NIEM updates go to the link below, download the zip file, and test out the new version.
Please click on the link below to download the NIEM 3.1 Alpha-1 version package for test. We welcome any comments or recommendations to our help desk about this version.
NIEM 3.1 Alpha-1 Version: http://release.niem.gov/niem/3.1/