Global Justice XML Data Model 3.0.3

The Global Justice XML Data Model.

Proxy types that carry dictionary metadata and extend the Common Alerting Protocol (CAP).

Proxy types that carry dictionary metadata and extend security classification codes from Presidential Executive Order 12958.

Proxy types that carry dictionary metadata and extend security level codes from the Department of Defense (DoD).

Proxy types that carry dictionary metadata and extend the Federal Information Processing Standards (FIPS) 5-2 codes - codes for state identification, District of Columbia, and other outlying areas of the United States and associated areas.

Proxy types that carry dictionary metadata and extend codes for the representation of names of countries and their subdivisions from the International Organization for Standardization (ISO) 3166-1:1997.

Proxy types that carry dictionary metadata and extend codes for the representation of names of languages from the International Organization for Standardization (ISO) 639-2/T (terminology codes).

Proxy types that carry dictionary metadata and extend statute and offense codes from the state of Minnesota.

Proxy types that carry dictionary metadata and extend miscellaneous crime-reporting codes from the National Incident-Based Reporting System (NIBRS).

Proxy types that carry dictionary metadata and extend Canadian province codes.

Proxy types that carry dictionary metadata and extend United States state and possession abbreviations from the United States Parcel Service (USPS).

Proxy types that carry dictionary metadata and have XML data type simple contents.

Employment codes from the U.S. Census Bureau.

Intelligence discipline codes from the Department of Defense (DoD) Joint Chiefs of Staff (JCS) Publication 2.0, Appendix A.

Countries, dependencies, areas of special sovereignty, and their principal administrative divisions from the Federal Information Processing Standards (FIPS) 10-4.

Counties and equivalent entities of the United States, its possessions, and associated areas from the Federal Information Processing Standards (FIPS) 6-4.

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 from the International Organization for Standardization (ISO) 639-2/T (terminology codes).

Statute and offense codes from the state of Minnesota.

Miscellaneous crime-reporting codes from the National Incident-Based Reporting System (NIBRS).

Province codes for Canada.

Miscellaneous unit of measurement code from the United Nations Economic Commission for Europe Recommendation No. 20, "Codes for Units of Measure used in International Trade".

Plea codes and military discharge codes from the Utah Offender Tracking Database, version 2.03.

See http://www.w3.org/XML/1998/namespace.html and
http://www.w3.org/TR/REC-xml for information about this namespace.
 This schema document describes the XML namespace, in a form
 suitable for import by other schema documents.
 Note that local names in this namespace are intended to be defined
 only by the World Wide Web Consortium or its subgroups.  The
 following names are currently defined in this namespace and should
 not be used with conflicting semantics by any Working Group,
 specification, or document instance:
 base (as an attribute name): denotes an attribute whose value
      provides a URI to be used as the base for interpreting any
      relative URIs in the scope of the element on which it
      appears; its value is inherited.  This name is reserved
      by virtue of its definition in the XML Base specification.
 id   (as an attribute name): denotes an attribute whose value
      should be interpreted as if declared to be of type ID.
      The xml:id specification is not yet a W3C Recommendation,
      but this attribute is included here to facilitate experimentation
      with the mechanisms it proposes.  Note that it is _not_ included
      in the specialAttrs attribute group.
 lang (as an attribute name): denotes an attribute whose value
      is a language code for the natural language of the content of
      any element; its value is inherited.  This name is reserved
      by virtue of its definition in the XML specification.
 space (as an attribute name): denotes an attribute whose
      value is a keyword indicating what whitespace processing
      discipline is intended for the content of the element; its
      value is inherited.  This name is reserved by virtue of its
      definition in the XML specification.
 Father (in any context at all): denotes Jon Bosak, the chair of
      the original XML Working Group.  This name is reserved by
      the following decision of the W3C XML Plenary and
      XML Coordination groups:
          In appreciation for his vision, leadership and dedication
          the W3C XML Plenary on this 10th day of February, 2000
          reserves for Jon Bosak in perpetuity the XML name
          xml:Father

This schema defines attributes and an attribute group
        suitable for use by
        schemas wishing to allow xml:base, xml:lang, xml:space or xml:id
        attributes on elements they define.
        To enable this, such a schema must import this schema
        for the XML namespace, e.g. as follows:
        <schema . . .>
         . . .
         <import namespace="http://www.w3.org/XML/1998/namespace"
                    schemaLocation="http://www.w3.org/2001/xml.xsd"/>
        Subsequently, qualified reference to any of the attributes
        or the group defined below will have the desired effect, e.g.
        <type . . .>
         . . .
         <attributeGroup ref="xml:specialAttrs"/>
         will define a type which will schema-validate an instance
         element with any of those attributes

In keeping with the XML Schema WG's standard versioning
   policy, this schema document will persist at
   http://www.w3.org/2005/08/xml.xsd.
   At the date of issue it can also be found at
   http://www.w3.org/2001/xml.xsd.
   The schema document at that URI may however change in the future,
   in order to remain compatible with the latest version of XML Schema
   itself, or with the XML namespace itself.  In other words, if the XML
   Schema or XML namespaces change, the version of this document at
   http://www.w3.org/2001/xml.xsd will change
   accordingly; the version at
   http://www.w3.org/2005/08/xml.xsd will not change.