ANSI/NIST Fingerprint and Biometric standard.
Motor vehicle administration codes from ANSI D20, the Data Dictionary for Traffic Record Systems, maintained by AAMVA, the American Association of Motor Vehicle Administrators.
Association of Public-Safety Communications Officials (APCO) - International, Inc.
Bureau of Alcohol, Tobacco, and Firearms
Province codes for Canada.
Common Alerting Protocol (CAP) is a simple but general format for exchanging effective warning messages based on best practices identified in academic research and real-world experience.
Chemical, Biological, Radiological, and Nuclear Domain
Radiological and Nuclear Code List
Employment codes from the U.S. Census Bureau.
This Distribution Element specification describes a standard message distribution framework for data sharing among emergency information systems using the XML-based Emergency Data Exchange Language (EDXL). This format may be used over any data transmission system, including but not limited to the SOAP HTTP binding.
Drug Enforcement Administration
Intelligence discipline codes from the U.S. Department of Defense (DoD) Joint Publication 2.01.
Emergency Data Exchange Language
Common Alerting Protocol
Distribution Element
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.
Emergency Management
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).
Countries, dependencies, areas of special sovereignty, and their principal administrative divisions from the Federal Information Processing Standards (FIPS) 10-4.
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.
Counties and equivalent entities of the U.S., its possessions, and associated areas from the Federal Information Processing Standards (FIPS) 6-4.
Family Services
This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:00:05 ======
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.
This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:40:03 ======
Geography Markup Language (GML) version 3.2.1 schemas. See http://www.opengeospatial.org OGC document 07-036 for documentation: "The Geography Markup Language (GML) was originally developed within the Open Geospatial Consortium, Inc. (OGC). ISO 19136 was prepared by ISO/TC 211 jointly with the OGC." See http://schemas.opengis.net/gml/ for schemas.
This file was generated from ISO TC/211 UML class diagrams == 04-27-2005 17:16:11 ====== Handcrafted
This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:24:48 ======
This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:14:37 ====== The geometry packages (Figure 4) contain the various classes for coordinate geometry. All of these classes through the root class GM_Object inherit an optional association to a coordinate reference system. All direct positions exposed through the interfaces defined in this standard shall be in the coordinate reference system of the geometric object accessed. All elements of a geometric complex, composite, or aggregate shall be associated to the same coordinate reference system. When instances of GM_Object are aggregated in another GM_Object (such as a GM_Aggregate, or GM_Complex) which already has a coordinate reference system specified, then these elements are assumed to be in that same coordinate reference system unless otherwise specified. - The geometry package has several internal packages that separate primitive geometric objects, aggregates and complexes, which have a more elaborate internal structure than simple aggregates. Figure 4 shows the dependencies between the geometry packages as well as a list of classes for each package - Figure 5 shows the basic classes defined in the geometry packages. Any object that inherits the semantics of the GM_Object acts as a set of direct positions. Its behavior will be determined by which direct positions it contains. Objects under GM_Primitive will be open, that is, they will not contain their boundary points; curves will not contain their end points, surfaces will not contain their boundary curves, and solids will not contain their bounding surfaces. Objects under GM_Complex will be closed, that is, they will contain their boundary points. This leads to some apparent ambiguity. A representation of a line as a primitive must reference its end points, but will not contain these points as a set of direct positions. A representation of a line as a complex will also reference its end points, and will contain these points as a set of direct positions. This means that identical digital representations will have slightly different semantics depending on whether they are accessed as primitives or complexes. - This difference of semantics is most striking in the GM_CompositeCurve. Composite curves are used to represent features whose geometry could also be represented as curve primitives. From a cartographic point of view, these two representations are not different. From a topological point of view, they are different. This distinction appears in the inheritance diagram (Figure 5) as an inheritance relationship between GM_CompositeCurve and GM_OrientableCurve. The primary semantics of a GM_CompositeCurve (see 6.6.5) is as a closed GM_Object, but it may also act as an open GM_Object under GM_Primitive operations (see 6.3.10). Interface protocols depending upon the topological details of this object will have to be distinguished as to whether they have been inherited from GM_Primitive or GM_Complex, where the distinction first occurs. Even though these protocols have been inherited from the same operations defined at GM_Object, they will act differently depending upon the branch of the inheritance tree from which they have inherited semantics. Creators of implementation profiles may take this into account and use a proxy mechanism for realization relationships that cause semantic dissonance. Such a procedure will be necessary in object-oriented programming and databases in systems that disallow multiple inheritance or make limiting assumptions about method binding.
This file was generated from ISO TC/211 UML class diagrams == 01-26-2005 12:18:09 ======
Hospital Availability Exchange (HAVE)
EDXL Hospital AVailability Exchange (HAVE) code sets
Pipeline and Hazardous Materials Safety Administration - Office of Hazardous Materials Safety.
Immigration
Intelligence
Infrastructure Protection
Codes for the representation of names of countries and their subdivisions from the International Organization for Standardization (ISO) 3166-1:1997.
Codes for the representation of currencies and funds from the International Organization for Standardization (ISO) 4217:2001.
Codes for the representation of names of languages - Part 3: Alpha-3 code for comprehensive coverage of languages.
International Trade
Integrated Transportation Information System
Justice
Los Angeles County Sheriff's Department
Maritime
Model Minimum Uniform Crash Criteria
Statute and offense codes from the state of Minnesota.
NIEM Core includes both Universal (U) and Common (C) components. The identities for U and C components in Core are maintained with metadata.
National Geospatial Agency
Proxy types that carry dictionary metadata and have XML data type simple contents.
NLETS - The International Justice and Public Safety Information Sharing Network
Non-authoritative codes for the direction of a person's pose in an image.
Suspicious Activity Reporting
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.
Terrorist Watchlist Person Data Exchange Standard
Crime reporting codes from Uniform Crime Reporting.
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.
U.S. state and possession abbreviations from the U.S. Postal Service (USPS).
Plea and military discharge codes from the Utah Offender Tracking Database, version 2.03.
The Extensible HyperText Markup Language, a family of current and future document types and modules that reproduce, subset, and extend HTML 4.
GML 3.0 candidate xlinks schema. Copyright (c) 2001 OGC, All Rights Reserved.
A profile of OpenGeospatialConsortium (OpenGIS, OGC) OpenLS (Location Services) version 1.1 schemas. A profile of OpenGeospatialConsortium (OpenGIS, OGC) OpenLS (Location Services) version 1.1 schemas that have been edited to use GML version 3.2.1 schemas instead of the GML version 3.0 schemas that were current when OpenLS version 1.1 was promulgated. See http://www.opengeospatial.org for documentation, http://schemas.opengis.net/ols/ for schemas.
The XML Schema definition language, which offers facilities for describing the structure and constraining the contents of XML documents.