Justice Information Sharing: GJXDM

The Global Justice Extensible Markup Language Data Model (GJXDM) is an XML standard designed to create a uniform method for law enforcement and judicial agencies to exchange criminal justice information in a timely manner.

GJXDM removes the burden from agencies to independently create exchange standards. Its extensibility allows for flexibility to deal with unique agency requirements and changes. GJXDM is an object-oriented data model for organizing the content of a data dictionary, the Global Justice XML Data Dictionary (GJXDD), in a database. From this database, an XML schema specification can be generated that consistently represents the semantics and structure of common data elements and types required for information exchange within the justice and public safety communities. There are three primary parts to the GJXDM: the Data Dictionary (identifying content and meaning), the Data Model (defining structure and organization), and the Component Reuse Repository (a database).

The work accomplished to date, based on participation by practitioners from the justice and public safety communities, has resulted in the creation of a data model that can be used to generate data schema which will facilitate information sharing among the various jurisdictions of those communities. This was done in a manner that reduced the cost of developing the technical solutions required, simplified the process and associated products, and enhanced the interoperability quotient of the end product. The approach combines successful practices in data modeling with recent technology standards for XML schema.

Proactive information sharing promotes public safety by allowing users to make accurate and rapid decisions. GJXDM lets users share critical information better and faster, and reduce costs and overcome delays in case management. GJXDM provides for electronic data sharing in a simple automatic process between previously incompatible systems.

The automation revolution led to piecemeal interoperability, individual software applications that were programmed to only serve a single agency or a group of agencies. This approach did not take into account the need to share information between agencies with different applications. Yet the need to share information is now important as ever.

Exchange of information can be accomplished between different applications by using a uniform standard, regardless of computer system or platform. Luckily, this is exactly what XML allows. Global Justice XML Data Model is an XML markup-language that serves this purpose for law enforcement and related agencies. GJXDM has a standard Justice specific vocabulary and agreed to objects that all agencies can use to describe information. Below is a scenario which illustrates how the useof GJXDM yields the best possible result for lawenforcement.

A local police officer conducts a routine traffic stop for speeding. When the police officer approaches the car, he discovers that there is a young female passenger alongside the male driver. Thereafter, the police officer enters the driver's information into his mobile data computer. Immediately the system queries all participating neighboring jurisdictions and agencies, besides his local district, for any information concerning the driver. Information is returned from a state Sex Offender Registry that the driver is a registered sex offender who is prohibited from being the company of any child under the age of 16. Further, the officer also receives information from the Department of Corrections that there is a warrant for the driver's arrest because he is wanted for not registering with them. It turns out that the passenger is actually a 12 year old girl, so the driver is arrested based on both pieces of information obtained using GJXDM. Without GJXDM, the driver might have just received a speeding ticket. Luckily the XML technology, GJXDM, allowed for the quick and easy transfer of information between the local police officer's computer and the systems of all the other appropriate agencies.

The scenario provided is only one of many examples of how the exchange of information is crucial in ensuring justice. The XML enhanced data sharing provides for a common framework to improve data and information sharing. And as XML is increasingly being adapted as the IT standard globally, more tools will become available to work with XML. Also, XML is a very adaptable language, since it works on top of most existingservers (nothing needs to be replaced to work withXML).

US Dept. of Justice GJXDM Website: https://bja.ojp.gov/program/it/national-initiatives/gjxdm

US Dept. of Justice Information Sharing Initiative: https://bja.ojp.gov/program/it/national-initiatives

Yes, there is. The GJXDM User Guide can be located via the following URL:
https://bja.ojp.gov/program/it/national-initiatives/gjxdm/documentation

Another good source of information is the GlJXDM Developer's Workshop Online Training Materials Website that contains all of the presentations, training materials, and recorded audio/video streams from the workshop held at Georgia Tech in Atlanta May 11-12, 2004.

The GJXDM consists primarily of object classes and properties. The Object classes are converted into XML Schema types. They eache represent a specific syntax and structure for a set of values. The properties are converted into XML Schema attributes and elements. They each represent characteristics, or values of things.

The GJXDM is a reference model that is based on a class hierarchy of many specific objects (xsd:type) derived from one very general object (SuperType). Each object contains any number of properties (xsd:element or xsd:attribute). These properties may be simple or complex elements (containing sub-elements). The highest level object classes (under the SuperType) are PersonType, OrganizationType, PropertyType (i.e., things), LocationType, ContactInformationType (i.e., electronic means of contact), ActivityType, DocumentType, and other smaller supporting types.

There is also a special class of RelationshipType used to specify meaning to a link between two object instances. On many of these objects, there are metadata properties (xsd:element or xsd:attribute) that supplement meaning. For example, all properties of MeasureType have a mandatory "units" attribute.

The components were chosen from a variety of legal and technical sources that preceded Global Justice XML Data Model (GJXDM). Data components were built from approximately 35 data dictionaries, XML schema documents, and XML data models under development or in use by various law enforcement and judicial organizations.

These sources yielded approximately 16,000 data components (elements, attributes, and types). Through study and analysis of the similarities and differences among these components, approximately 2,200 properties (xsd:element, xsd:attribute) and 550 types (xsd:type) were synthesized to represent a common set of elements and types, the GJXDM.

It is important to realize that the authors did not invent the content. Instead, the GJXDM tries to capture the requirements of the 35 data sources as completely and accurately as possible. However, compromises were necessary in order to follow the basic design principles and criteria set forth by the XML Structure Task Force (XSTF).

The source data requirements analyzed by the XML Structure Task Force (XSTF) were not consistent in their use of codes. For components with the same meaning, some sources used codes; others used literals. When codes were used, they were not always drawn from the same code table, and some code tables are specific to local jurisdictions.

In order to provide maximum flexibility, the GJXDM usually provides both a code type element and a text type element (that may contain a literal). There are particular code tables that are always common; for example National Criminal Information Center (NCIC)-2000 and the American Association of Motor Vehicle Administrators (AAMVA). Therefore, the XSTF provided a mechanism to use codes from other namespaces. This enables the use of standards without restriction to a single internal set of values.

This also does not require a change to the GJXDM namespace every time external standards change. For example, the XSTF has created an NCIC-2000 schema in its own namespace that contains the NCIC code tables. Temporarily, the XSTF refers to this as the NCIC-2000 proxy schema because it is external to the GJXDM namespace and can be updated without causing the GJXDM to change. The XSTF anticipates that local jurisdictions will want to create their own proxy schemas for their local code tables as well.

NISS Clearinghouse

Reference elements exist to allow schema designs with multiple occurrences of the same information object or instance to reference a single content-filled object rather than to repeat it in different locations.

This ensures that the same information object does not repeat multiple times and mislead the receiver into thinking there are multiple (different) objects. If an object is recorded once and referenced from everywhere else it is used, then there is a lower risk of misunderstanding or inconsistency. This requires one XML element of type ReferenceType for each element in the model. That is, for every element named "X" in GJXDM, there is a second element named "XReference" that is intended to reference, or "point to", an element named X appearing elsewhere in the instance.

While this technique makes the GJXDM somewhat redundant, the use of separate elements for bearing content and content references makes it easier for applications to know immediately if and when they are looking at the information object itself or a reference to it.

A GJXDM or NIEM reference Information Exchange Package Documentation (IEPD) is a specification for a model document or transaction that has been derived from and uses the GJXDM / NIEM. It is currently considered a suggested model for a particular kind of document.

For example, an Arrest Warrant reference Information Exchange Package Documentation (IEPD) uses the GJXDM, is specified in XML Schema, and is a reference for building an Arrest Warrant. This means that it can be used as is, or extended for a more specific or local purpose, or to guide construction of another similar document specification. There also some examples of reference IEPDs that use the NIEM such as, SAR for Local and State Entities IEPD v1.1.

A "reference" is a starting point for a standard, not a rigid, fixed standard. For more information on reference Information Exchange Packages, see Reference Information Exchange Package Schemas.

GJXDM versions are numbered by three integers X, Y, and Z delimited by periods (X.Y.Z).

Each integer represents a particular class of change:

X = Major revisions to the model or representations of the model as rendered in a schema (as XML or other markup)
Y = Minor changes that do not maintain forward compatibility
Z = Minor changes that maintain forward compatibility
A version number should NOT be confused with decimal numbers. X, Y, and Z are integers, not digits, and may become greater than 9. For example, 4.89.113 is a legitimate release number (though not likely to ever be used).

GJXDM version 3.0 is the first operational release. Version 3.0 instances will be forward compatible with and validate using the version 3.0.2 schema or appropriate 3.0.2 schema subsets. See the question on compatibility for more details. Prereleases used four numbers to designate versions. There were only four prereleases: 3.0.0.0, 3.0.0.1, 3.0.0.2, and 3.0.0.3. Except for 3.0.0.2, prereleases are still available, but are no longer maintained or supported.

Note that specific person role types (like CaseOfficialType) extend PersonType, and so automatically inherit all of the properties of PersonType. Since element sequence follows the inheritance hierarchy, in an XML instance, the PersonType information would appear first, followed by the CaseOfficialType information.

The Global Justice XML Data Model (GJXDM) Bugzilla Feedback site will continue to be the primary mechanism for identifying urgent bug fixes and requests for additions, deletions, and modifications. The XML Structure Task Force (XSTF) will continue to authorize all fixes and changes. Thus, all bug reports (feedback) will be reviewed and approved/disapproved by the XSTF. All approved additions, deletions, and modifications will be applied to the next release whenever possible. A cumulative change log will be published with each release to maintain an audit trail. Changes will be linked to appropriate bug reports in the feedback history.

GJXDM Support can be obtained by contacting National Information Sharing Standards Help Desk via:

GJXDM Knowledge Base and Help Desk can be accessed via:
Web: http://it.ojp.gov/gjxdm/helpdesk

GJXDM Help Desk can be contacted via:

Telephone:

1-877-333-5111

703-726-1919

Email: [email protected]

This GJXDM listserv exists to support community-wide announcements, comments, discussions, and exchanges that are relevant to the GJXDM but not directly relevant to the feedback site.

Finally, the organizations utilizing the GJXDM can be contacted directly for further information .

Information Sharing Listserv: https://bja.ojp.gov/program/it/policy-implementation/practitioners

The GJXDM schema is a list of commonly used data elements that were compiled from actual data requirement sources and narrowed down and refined to result in a set of precise and well-defined data components. The GJXDM schema is one functional representation of those components and the product of the GJXDM specification that application developers use for programming.

The GJXDM is also dependent on schemas that represent code tables taken from specifications and publications created by other groups and organizations. The GJXDM base schema references these code tables by importing external schemas in an effort to maintain the independence of the various specifications.

Information in regards to full schemas for GJXDM releases :https://bja.ojp.gov/program/it/national-initiatives/gjxdm

The following design criteria were applied in the development of the Global Justice Extensible Markup Language (XML) Data Model (GJXDM):

Design a common set of reusable, extendable XML data components for the Global Justice XML Data Dictionary (GJXDD) that facilitates standard information exchange.
The GJXDM will be over-inclusive and optional.
Requirements, solutions, and time constraints will be established from rational compromises.
The International Organization for Standardization (ISO) 11179 – Specification and Standardization of Data Elements will be used, as well as other applicable standards.
The GJXDD will evolve, facilitating change and extension.
Extension methods should minimize impact on prior schema and code investments.
Domain relationships will be implemented and represented so that they are globally understood.
Develop reference architecture and namespaces for a standard GJXDM schema specification.
The GJXDM will be an object-oriented model using named types and extensions.
Value constraints will be enabled: codes/enumerations and special semantics. Primary (IS-A, HAS-A) and secondary (domain) relationships will be utilized.
The GJXDM will be built from functional requirements, reference documents, use cases, business context components, and containers.
The GJXDM will provide migration paths for evolving to new technologies.

The GJXDM was designed as a data model to be used as the basis for information exchanges, not as a data model for data warehouses (or databases). A data warehouse is a copy of transaction data specifically structured for querying and reporting. In essence, a data warehouse is designed for the storage of data, not the exchange data with other applications.

On the other hand, GJXDM was inherently designed to allow information exchange. For example, building a GJXDM 'compliant' data warehouse to store the data in a case management system might be problematic and requires adapting the GJXDM schema. In this case, one would want to use GJXDM components to represent the set of data used by an application (the case management system). Yet, since it is unlikely the GJXDM exactly models the business data for this particular application, one should expect to have to use certain GJXDM components, adding your own components, and combining them in additional or different ways than they are in the GJXDM to suit the particular business purpose of the application.

It is possible for a data warehouse modeled after the GJXDM to work; although it may not be optimal for a particular application, it could make it easier to send and receive IEPs. It's just that this use of the GJXDM for data warehouses was not considered in the development of the GJXDM.

The GJXDM Instance Validation Tool is a simple tool built on top of the Apache Xerces parser, and can be used to test whether an XML instance is valid against a GJXDM-conformant schema.

GJXDM Validator: https://bja.ojp.gov/program/it/national-initiatives/niem

Currently, there are four methods to define a relationship (or a ''link'') between two components that do not already have a relationship with each other in the Global Justice XML Data Model (GJXDM). (To demonstrate the methods, as an example the component Citation will be linked to Charge. A citation ID is represented in the GJXDM as j:Citation/j:ActivityID (j:ActivityID is inherited from j:ActivityType, the parent of j:CitationType). However, j:ChargeType does not contain j:Citation or a parent of j:Citation, and there is no relationship between the two in the GJXDM. So one has to define that relationship.

The first method, referred to as inclusion, is to simply define a new type that extends the type of one component (which is a complex type) to include the other component (which can be either a complex type or a simple type). To use the first method, one would define their own charge type that is an extension of j:ChargeType. Then one would have to add j:Citation to the sequence. If there were any other GJXDM properties not in j:ChargeType that one wants, those could be added as well. If one only wants the citation ID (and not the whole citation), since it is so trivial, one could consider defining their own CitationID element of type IDType. This method might be most appropriate, since extending j:ChargeType to include j:Citation (or your:CitationID) is analogous to including the citation ID in your charge table.

The second method, referred to as reference, is to include in one component a reference to the other component using ID/IDREF . For this method, one would define a new type that extends j:ChargeType to add j:CitationReference to the sequence (instead of j:Citation). This can be used if the citation information is already represented elsewhere as j:Citation and the purpose is to just reference that existing citation information instead of duplicating it in the charge information.

The third method, referred to as association, is to use the j:Relationship element. It has the attributes name, subject, and object. For our example, one would give it the name attribute -- say ''ChargeCitationID''. The subject attribute would be j:ChargeReference and the object attribute would be j:CitationReference. This method is used to define some relationship between two properties without extending one to include the other (as in the first method) or a reference to the other (as in the second method).

The fourth method is to define your own association type and element, similar to the third method, but enabling additional relationship content beyond the name, subject, and object.

The GJXDM schema itself does NOT provide query capabilities. The two alternatives are to build queries that return GJXDM compliant ''types'' or to use web services. There is anobject model with method names to provide such query: IMHO, it is very academic in nature with minimal business analysis for practical usage; i.e., it is more of a ''controlled vocabulary'' than a real model for implementation with modern tools.

It is possible to build queries that return GJXDM compliant ''types''. One should use a naming convention for SOAP queries that follow standard camel case, using the actionTypeConstraintType convention: getPersonByID; returns Person getCourtAppearanceActorPersonByPersonName; return CourtAppearanceActorPerson (drop the dot notation), etc. Regarding the source of the input parameters, it is not possible to directly use the GJXDM naming as input parameters due to the contextual nature of the typing (complexTypes). Specifically, some of the names used in the attributes and elements are TOO GENERIC to be able to pass them as SOAP parameters. You need the entire XPATH notation to be able to define the full context / semantic definition of the parameter. Therefore, the requests are often home spun.

The second option is to use web services (WS-I conformant SOAP and WSDL) to implement the exchange. To use GJXDM in a web services context with WSDL, your schemas (subset/constraint and extension) become a source of types for the input and output parameters for each operation, as well as for faults (errors). This tends to provide a lot of flexibility in reusing these structures in the input (request) and output (reply) messages. That way, one does not need to try to figure out how to fit this all into one document schema, since the WSDL really takes on that role. The other advantage of web services and WSDL is that in most cases one can generate both requestor and service endpoint stub/skeleton code, which invokes an interface that you implement to wire up the endpoints to business logic on each end. It is also possible to choose to parse the XML, or have it de-serialized into an object graph. (This is well-supported on both the Java 2 and .NET platforms.)

The JXDM-Query-Options file in the attachment contains recommendations, best practices and lessons about query generation for the model.

Documents
https://bja.ojp.gov/sites/bja/files/media/document/JXDM-query-options-v…

When considering the Global Justice Extensible Markup Language (XML) Data Model (GJXDM), the government and industry experts, technical managers, and engineers responsible for its development formed the following assumptions that guided them in their design of the GJXDM.

The GJXDM:

Be reusable, with extensible data components that facilitate standard information exchange in XML within the justice, courts, public safety, and homeland security communities.
Generalize for the community at large, rather than specific document instances.
Provide referenceable schema components for schema developers.
Have a Global Justice XML Data Dictionary (GJXDD) and Global Justice XML Data Dictionary Schema (JXDDS) that will evolve, change, and require extensions, using extension methods that minimize the impact on prior investments.
Represent and implement domain relationships.
Have time, technical, and requirement constraints that mandate rational trade-offs—no silver bullets! The design criteria discussed above were developed in accordance with the following goals:
To enable forms-based maintenance/reconfiguration of the GJXDM.
To automatically generate XML schema for the GJXDD schema specification.
To automatically generate equivalent Resource Description Framework (RDF) schema.
To store and map data element requirements from any data source (schema, Document Type Definition [DTD], data table, or data dictionary) to GJXDM components.
To enable measurement by source of the number of data requirements covered and the number of data left to implement.
To provide search filters, forms, and tools to quickly analyze data requirements and build initial draft object models for vetting.

NLETS, which serves as the International Justice and Public Safety Information Sharing Network for state owned system connecting all 50 states, territories along with every federal agency with a justice component, has found great success in its embrace of the Global Justice XML Data Model (GJXDM) standard. As a result there are over 500,000 access points.

The network has for 38 years provided sharing of data – the hub for interstate exchange. NLETS has always “dictated” the data format for use of the system. And until recently the format was proprietary, but fortunately a decision was made to adapt GJXDM as the standard. In the past, NLETS did not hold any data. Proprietary data formats were used to connect disparate state and federal systems. This forced extensive custom programming for each NLETS interface user. NLETS -FBI and the states all have the same "customers." Yet the proprietary format and the different specifications all made the different users design different applications for the different interfaces. This severely drove up costs and maintenance issues.

GJXDM offered a chance for NLETS to simply exchange of information. They are still supporting proprietary data formats, but no new services will be offered in legacy. All NLETS transactions and responses were transitioned to GJXDM 3.0.x. Currently, NLETS are accepting nearly 1 million FBI-CJIS-III CCH transactions per month in XML. They are doing hundreds of thousands of bidirectional transformations (Legacy – XML – Legacy) daily. The success of the transformation to GJXDM has expanded the role of NLETS. Kentucky, Maine and Wisconsin are sending and receiving XML rap sheets across NLETS. And there is a pilot to standardize driver's license records across state lines over NLETS is underway using GJXDM XML. The Amber Alert Consortium for interstate Amber notification for justice enterprise also uses GJXDM.

There are over 40 projects that are using or are committed to using the Global Justice XML Data Model (GJXDM) for their data exchange applications.

The organizations include:

1. Administrative Office of the Courts, Georgia  (Georgia Judicial Exchange)

2. Arizona Supreme Court, Administrative Office of the Courts  (Justice Integration-Electronic Citations Import)

3. Arizona Supreme Court, Administrative Office of the Courts/Arizona Criminal Justice Information System (ICJIS)  (Adult Probation Data Exchange)

4. Arkansas Integrated Justice Information Systems Program  (Arkansas IJIS Pilot Project)

5.         Association of Motor Vehicle Administrators (AAMVA)  (CANDLE : Standardization of Driver's License records across NLETS – The International Justice & Public Safety Information Sharing Network)

6.         California Administrative Office of the Courts  (Data Exchange Standards Initiative)

7.         California Department of Justice (DOJ)  (Statewide Investigative Networking System (SINS))

8.         Coconino County, Arizona  (Criminal Justice Integration Project)

9.      Colorado Integrated Criminal Justice Information System (CICJIS)  (CICJIS Online Presentation System (COPS))

10.      CriMNet - Minnesota Department of Public Safety  (CriMNet EAI Backbone)

11.      Criminal Information Sharing Alliance, Incorporated (CISAnet: Sharing, organizing, and analyzing of criminal information (intelligence, CJIS, investigative, etc.) across local, state, and federal boundaries for investigative and analytical purposes)

12.      Florida Law Enforcement Data Sharing Consortium  (FINDER – Florida Integrated Network for Data Exchange and Retrieval)

13.      Maine State Police  (Bureau of Motor Vehicles Interface)

14.      Maine State Police  (Criminal History Record System - Justice Data Broker)

15.      Maine State Police  (Criminal History Record System - Provision of Criminal History Records (RAP Sheets))

16.      Maine State Police  (Violations Bureau Interface)

17.      Missouri Office of State Courts Administrator (OSCA) (Missouri Court Automation Project)

18.      NLETS  (Standardized XML Transactions)

19.      North Carolina Criminal Justice Network (CJIN)  (DOJ, SBI, DCI Batch Updates to ACIS)

20.      North Carolina Criminal Justice Network (CJIN)  (Driver License Photo Transmission)

21.      North Carolina Criminal Justice Network (CJIN)  (Facial Image Transmission)

22.      North Carolina Criminal Justice Network (CJIN)  (Sex Offender Data Sharing)

23.      Ohio Association of Chiefs of Police  (OLLEISN - Ohio Local Law Enforcement Information Sharing Network)

24.      Orange County Florida  (Integrated Criminal Justice Information Systems)

25.      Pennsylvania Justice Network (JNET)  (GJXDD 3.0-Based Driver History Record)

26.      Pennsylvania Justice Network (JNET)  (Criminal History Records Disposition System Update Project)

27.      Pennsylvania Justice Network (JNET)  (Warrants Project)

28.      Pennsylvania Justice Network (JNET)  (Sentencing Guidelines Project)

29.      Pennsylvania Justice Network (JNET)  (Electronic Citation Filing Project)

30.      RISS Application Development Group  (RISSApps)

31.      Seattle, Washington  (Seattle Justice Information System (SeaJIS))

32.      Southwest Alabama Integrated Criminal-Justice System  (Law Enforcement Tactical System (LETS))

33.      State of New Hampshire - Department of Safety  (J-ONE (One Network Environment for Justice) - Bail Conditions)

34.      State of New Hampshire - Department of Safety  (J-ONE (One Network Environment for Justice) - Warrant Requests)

35.      State of New Hampshire - Department of Safety  (J-ONE (One Network Environment for Justice)- Criminal Complaints)

36.      State of New Hampshire - Department of Safety  (J-ONE (One Network Environment for Justice)- Dispositions)

37.      State of New Hampshire - Department of Safety  (J-ONE (One Network Environment for Justice)- Protection Orders)

38.      Supreme Court of Georgia  (Supreme Court E-filing Project)

39.      Syracuse Police Department  (CNYLEADS: Electronic reporting with RMS.)

40.      United States Department of Justice (DOJ), Executive Office for United States Attorneys (EOUSA) and United States Postal Inspection Service (USPIS) (Victim Notification System (VNS)

41.      University of Maryland Center for Advanced Transportation Technology (UMD-CATT)  (Capital Wireless Integrated Network (CapWIN))

42.      University of Southern Mississippi  (Automated System Project)

43.      State of Vermont Agency of Digital Services - formerly Department of Innovation and Information  (Vermont Criminal Justice Integration Services)

44.      Washington State Administrative Office for the Courts  (Data Exchanges)

45.      Whatcom County, Washington  (Whatcom Exchange Network (WENET))

46.      Wisconsin Department of Justice  (eTIME Server to Server)

47.      Wisconsin's Justice Information Sharing Program (WIJIS) (The Justice Gateway)

Organizations Using GJXDM: http://it.ojp.gov/default.aspx?area=nationalInitiatives&page=1227

How GJXDM is being used: http://www.idealliance.org/proceedings/xml04/papers/150/How-US-Govt-Using-XML-1YL.html#S7.9

GJXDM prereleases have four integers in their version numbering schemes, and include 3.0.0.0, 3.0.0.1, 3.0.0.2, and 3.0.0.3. All were released in 2003. For transitional reasons, prereleases 3.0.0.0, 3.0.0.1, and 3.0.0.3 will remain available in their respective namespaces for an undetermined period of time. GJXDM prereleases are no longer updated or supported.

The XML Structure Task Force (XSTF) found a bug in XMLSpy that prevented refinement of the simple content of a complex type by restricting an existing complex type with simple content. It was decided that, in deference to XMLSpy users, schemas that use this capacity of XML Schema will be avoided.

The common principles for using GJXDM are as follows:

* Design and synthesize common, reusable, extensible data components that facilitate standard information exchange in Extensible Markup Language (XML).
* Requirements-based: Build content from existing data models, dictionaries, and specifications.
* Object-oriented: Maximize efficiency through extension and consistent reuse of properties and types.
* Generalize the Global JXDM for the justice community at-large. Do NOT target specific applications or systems.
* Provide referenceable schema components primarily for schema developers.
* Facilitate the evolution of the Global JXDM and its schema by providing change management and extension.
* Extendable: Enable local additions of data components, but preserve the semantic relationships when they exist, and minimize the impact on prior schema and code investments.
* Implement and represent domain relationships so they are globally understood.
* Preserve global semantics.
* Build to evolve with emerging technologies (e.g. OWL, Web Services, etc.).
* In view of time constraints, national priorities, requirements conflicts, and technical limitations, apply rational compromises to these criteria to achieve solutions.

The following sequence describes compatibility within the GJXDM 3.0 release series: 3.0(.0) instances validate with 3.0.2, 3.0.3, ..., 3.0.n schemas 3.0.2 instances validate with 3.0.3, 3.0.4, ..., 3.0.n schemas 3.0.3 instances validate with 3.0.4, 3.0.5, ..., 3.0.n schemas ... (Note: 3.0.1 was removed from service.) We say that within the 3.0 series, forward compatibility is maintained.

However, when 3.1.0 (a new series) is released, 3.0.n instances are NOT guaranteed to validate against 3.1.m schemas. However, 3.1.0 instances will validate with 3.1.1, 3.1.2, ..., 3.1.n schemas, etc. (if/when they are released). In other words, forward compatibility within the 3.1 series will be maintained.

Caveats:

If you want a 3.0.0 instance to validate against the 3.0.2 GJXDM schema, then you must change the namespace reference in the instance to 3.0.2 (and in your schema, as well if you are using one between the instance and the GJXDM schema).
Depending on which GJXDM components you are using, you may find that a 3.0.0 instance validates against the 3.1.0 GJXDM schema (when available). DO NOT assume that every 3.0.0 instance will validate. NO guarantees of validation will exist between 3.0 and 3.1.

Not at the moment. However, the ultimate intent of the XML Structure Task Force (XSTF) is to establish a Global Justice Data Registry capability. This would provide a single logical point of access to all GJXDM artifacts, including the GJXDM content, the schema releases, reference document schemas, tools, and additional capabilities.

These may be stored in a local repository or in multiple distributed networked repositories. The registry would be standards-based and present multiple interfaces (e.g. browser, Web services) to enable both users and other servers to access, navigate, view, and retrieve metadata from the GJXDM. The data registry may be implemented with commercial registry software, depending upon requirements and cost-effectiveness. The XSTF and the Office of Justice Programs (OJP) are evaluating requirements and alternatives

OJP Website: http://www.ojp.usdoj.gov/

There is a draft mapping of the 53 data elements of the National Incident Based Reporting System (NIBRS) to the GJXDM, Version 3.0, release. While many of the elements have a direct mapping, some elements are not a one-to-one match. Furthermore, in a few cases a mapping is either too complex or does not exist, and was therefore omitted.

NIBRS was created by the FBI's Uniform Crime Reporting (UCR) program, which began in 1929, collects information about crimes reported to the police. In 1982, BJS and the FBI sponsored a study of the UCR Program with the objective of revising it to meet law enforcement needs into the 21st century. A 5-year redesign effort to provide more comprehensive and detailed crime statistics resulted in the National Incident-Based Reporting System (NIBRS) which collects data on each reported crime incident.

The UCR Program is currently being expanded to NIBRS. Currently under the Summary system, law enforcement authorities aggregate the number of incidents by offense type monthly and report these totals to the FBI. Under incident-based reporting, agencies will provide an individual record for each crime reported. The Summary UCR Program collects offense information on the 8 Part I crimes of homicide, forcible rape, robbery, aggravated assault, burglary, larceny-theft, motor vehicle theft, and arson. It provides limited information about offenses, victims and offenders, and includes reported arrests for 21 additional crime categories.

Under NIBRS, law enforcement authorities provide information to the FBI on each criminal incident involving 46 specific offenses, including the 8 Part I crimes, which occur in their jurisdiction. Details about each incident include information about multiple victims and offenders. Arrest information on the 46 offenses plus 11 lesser offenses is also provided in NIBRS. Since NIBRS place such a crucial role in the activities of FBI, it is very important that the link between the NIBRS elements and GJXDM elements are clearly defined.

Spreadsheet of Mapping: https://bja.ojp.gov/sites/bja/files/media/document/NIBRS-GJXDM.xls

Note that the Incident Reporting Reference IEPD, created by SEARCH, has been validated to map all 53 NIBRS elements.

Ultimately, XML and the Global Justice XML Data Model can help to make criminal justice information sharing easier, quicker, and less expensive for agencies by offering standard tools, techniques, and data structures.

With the help of XML and the Global Justice XML Data Model, the opportunity for proactive justice information sharing is enhanced, arming everyone across the justice and public safety communities with the most accurate and up-to-date data to make the very best decisions possible—increasing law enforcement and criminal justice agency efficiency, public safety, and national security.

Refer to the article "Extensible Markup Language (XML) and Its Role in Supporting the Global Justice XML Data Model": https://bja.ojp.gov/sites/bja/files/media/document/What_is_XML_article…

The Global Justice Extensible Markup Language (XML) Data Model (GJXDM) is an XML standard designed specifically for criminal justice information exchanges, providing law enforcement, public safety agencies, prosecutors, public defenders, and the judicial branch with a tool to effectively share data and information in a timely manner. The GJXDM removes the burden from agencies to independently create exchange standards, and because of its extensibility, there is more flexibility to deal with unique agency requirements and changes.

A long long-term goal is to provide a baseline model for the data dictionary that can be represented in advanced technologies beyond XML Schema.

The first step to getting started with GJXDM is learning about XML (Extensible Markup Language).The next major step is familiarizing one self with all the tags in the data model that are expected to be used with the GJXDM standard.

The tags are presented in an easy to navigate schema, in the format of an Excel Document.All the tags represented in the schema are easy to understand because their purpose is clearly and fully defined in their name. The Excel Document also provides information about what type of data is a tag, including inheritance links, and a brief description.

For Example (using the tag name "Biometric ID") : The tag BiometricID clearly refers to "an identifier used to uniquely refer to a biometric." Therefore it is under the Biometric heading. Biometric is in the part of the file under the person tab, because Biometric clearly defines property of a person. The type of BiometricId is provided as inheritance of IDType. And a quick link to IDtype is provided to allow the user to know what sub-tags one should use within the BiometricID tag. An identifier used to uniquely refer to a biometric.

Some useful links:
XML Tutorial: http://www.w3schools.com/xml/xml_whatis.asp
GJXDM Website: https://bja.ojp.gov/program/it/national-initiatives/gjxdm
GJXDM Version 3.0.3 Schema: https://bja.ojp.gov/program/it/national-initiatives/gjxdm
GJXDM User's Guide: https://bja.ojp.gov/sites/bja/files/media/document/GJXDMUserGuide.pdf

Bugzilla is a "Defect Tracking System" or "Bug-Tracking System" to submit questions, change suggestions and requests, and problems about the Global JXDM/JXDD and its products. It facilitates the management and evolution of the model by enabling Georgia Tech Research Institute (GTRI) to track, manage, and respond to comments by the XML Structure Task Force (XSTF). It is very important before submitting a new bug or issue, to “Query existing bug reports” to determine if the bug/issue has already been reported. Ensure that you are not confusing bugs reported for a pre-release as they are no longer supported or maintained.

GJXDM Bugzilla website: https://niem.gtri.gatech.edu/ncct/

The Office of Justice Programs (OJP) assigned the Bureau of Justice Assistance (BJA) to develop a training and technical assistance capability to support implementation of the Global Justice Extensible Markup Language (XML) Data Model (Global JXDM). The result was the formation of the GJXDM Training and Technical Assistance Committee (GTTAC). Today, GTTAC represents several organizations that have volunteered to play a leadership role assisting jurisdictions across the country needing training and technical assistance, specifically for Global JXDM. It is through the collective efforts of the GTTAC members that BJA is able to provide a coordinated, efficient, and effective delivery of a wide range services and resources to meet the needs of the field. GTTAC's vision is to make available to all who require assistance a consistent, high quality, and complete set of resources and materials sufficient to ensure that GJXDM implementations are developed in such a way as to ensure true interoperability.

The Committee was established in January 2004 as an outreach effort for Global JXDM. It is related to, but external from, the Global Justice Information Sharing Initiative (Global) and is an operating entity on behalf of Global JXDM to assist the justice community's need to better understand and implement Global JXDM.

Office of Justice Programs: https://www.ojp.gov/

Global Justice Information Sharing Initiative: https://bja.ojp.gov/program/it/global/resources

Global Advisory Committee: https://bja.ojp.gov/program/it/global/resources

Global Infrastructure/Standards Working Group: https://bja.ojp.gov/program/it/giswg

SEARCH is involved with GJXDM through participation in a variety of justice XML committees and task forces.

SEARCH has also developed a conceptual framework to:
• present the flow of justice information between criminal justice agencies,
• define the key events that trigger the need to share information,
• identify the agencies involved in the exchange, and
• describe the nature of the information exchange.

Project staff developed the JIEM Modeling Tool, a web-based modeling tool and a methodology to capture detailed information regarding the processes, events, agencies, information, and conditions associated with justice information integration. In January 2004, SEARCH released version 3.0 of the JIEM Modeling Tool, which was a vast improvement over the prior versions and provided greatly enhanced functionality and outputs. The new version 3.0 incorporates the JIEM Reference Model version 1.0.1, which supplies jurisdictions with 663 reference exchanges developed from 5 years of research conducted in nearly two-dozen jurisdictions. In addition, the new tool interfaces with the Global Justice XML Data Model (GJXDM), which is another important nationally-supported model that facilitates integration of justice information systems.

SEARCH: http://www.search.org/
SEARCH Justice XML Projects: http://www.search.org/programs/info/

The Global Justice XML Data Model (GJXDM) is a data reference model for the exchange of information within the justice and public safety communities. The Global JXDM is sponsored by the U.S. Department of Justice (DoJ) Office of Justice Programs (OJP), with development supported by the Global Justice Information Sharing Initiative's (Global) XML Structure Task Force (GXSTF). It is a body of rules and concepts that provides a common language with which these agencies can describe, structure, and share information on justice/public safety matters and offenders. It integrates the data names and structures from the Global Justice XML Data Dictionary into a database. From this database, an XML schema specification can be generated that consistently represents the semantics and structure of common data elements and types required for exchanging information within the justice and public safety communities.

Global Justice XML Data Model Introduction: https://bja.ojp.gov/program/it/national-initiatives/gjxdm

Justice practitioners and the private sector have been working for a number of years in the United States to develop standards for justice data exchange through various coordinated and collaborative efforts, including an early grassroots effort known as “LegalXML”. The achievements of “LegalXML” include initial drafts of XML schemas for a standard arrest warrant, incident report, prosecution charging document, and sentencing order, as well as an XML standard for electronic court filing. Input from these parallel Justice XML initiatives provided important source requirements, which supported the development of GJXDM as it exists today.

The GJXDM is sponsored by U.S. Department of Justice's (DOJ) Office of Justice Programs (OJP), with development supported by the Global XML Structure Task Force (GXSTF) which works closely with researchers at the Georgia Tech Research Institute (GTRI). New releases are issued by the GXSTF, which reviews and evaluates each version of the GJXDM.

There has been some confusion among users regarding what is described as the data model (GJXDM) versus the data dictionary (GJXDD). One way to describe the Justice XML architecture is that the data dictionary (GJXDD) is a well-defined vocabulary of data names and structures assembled in an object-oriented data model (GJXDM) from which consistent XML schemas are generated to be used as templates for valid XML instances that carry data payload (actual data content).

GJXDM refers to the body of concepts and rules that underlie the data dictionary and the schema. The rules behind the data model are fundamental to the structure of the data dictionary and are used to generate the XML schemas.

The data model and dictionary are combined together into one database, a component repository, which allows the consistent generation of several products in support of the justice community:

1. The GJXDD schema.
2. Numerous external code table schemas.
3. A GJXDD documentation spreadsheet.

It is recommended that new users acquaint themselves with the GJXDD documentation spreadsheet (https://bja.ojp.gov/sites/bja/files/media/document/jxdm-3.0.3.xls), which is provided in a Microsoft Excel format for easy navigation. The spreadsheet is a tangible representation of the data dictionary.

Global Justice XML Data Model (GJXDM): https://bja.ojp.gov/program/it/national-initiatives/gjxdm

The Global Justice XML Data Model (GJXDM) employs the following rules for rendering elements vs. attributes:

1.      Employ elements whenever possible.

Attributes are used as the exception, and only with reasonable justification based on XML limitations or significant avoidance of complexity.

Justification: Elements are much more flexible than attributes. Attributes cannot be complex and cannot occur multiple times. Federal guidelines and best practices suggest the avoidance of attribute use.

2.      SuperType properties are always attributes.

Justification: The “SuperType” contains properties that are applicable to all components of the GJXDM. Therefore, all fields will include the properties of “SuperType”. All GJXDM components are derived from “SuperType”, so that all components inherit all the “SuperType” properties. At the same time, “SuperType” has neither complex nor simple content. In fact, it has no content; it's empty. Thus, objects with simple content can still be derived from “SuperType”, because it cannot contain any subordinate elements. And finally, one can consider “SuperType” properties generic enough to be metadata (such as, “probabilityNumeric”, “distributionText”, “reportedDate”, “expirationDate”, etc.) on all GJXDM components.

3.      DocumentType properties are always elements.

Reason: In view of rule (1), a justification is unnecessary. However, we provide the following explanation because of the special nature of “DocumentType” as the root of all reference document types. “DocumentType” is derived from “SuperType”. In the GJXDM, reference document types derived from “DocumentType” are the primary basis for information exchange transactions. As such, “DocumentType” has a set of metadata properties that are common to all documents derived from it. We render these properties as elements for several reasons:

4.      Use attributes for metadata that simply qualify the format or representation of a data value, but are not a required part of that data value, and when such use will avoid complexity.

Justification: Sometimes metadata qualifiers are not an essential part of the data itself. The data can stand alone and still be understood, or in other words, the qualifiers can be ignored without harm to understanding. The qualifier simply clarifies or focuses the meaning of the data or its representation. Furthermore, use of attributes for such qualifiers avoids unnecessary content complexity. Example:

<PersonName personNameTypeCode="aka"/>

5. Properties of simple numeric types are attributes.

Justification: Type Measure, Numeric, Quantity, Rate, and several other types that require qualifiers such as unit of measure or tolerance will be handled with attributes to maintain simple content. These qualifiers are simple and have stable values. The data value and qualifiers cannot be separated without almost total loss of meaning. Furthermore, use of attributes for such qualifiers avoids unnecessary content complexity. Example:

<VehicleSpeedMeasure speedUnit="mph" tolerance="5">37</VehicleSpeedMeasure>

6.      Mixed content is NOT supported.

Justification: Mixed content models are confusing and extremely difficult to implement and parse. Example:

<VehicleSpeedMeasure>37<SpeedUnit>mph</SpeedUnit></VehicleSpeedMeasure>

NOTE: The rules above will require modifications to: “PropertyStatusType”, “PropertyStatusCode”, “DrivingJurisdictionAuthorityCode”, and “IDType” – reconsider the design and replace attributes with elements, if possible, as “IDType” is overused.  In addition, use a complex type with complex content to simplify the derivatives.  For example, “DriversLicense” requires more structure than a number (e.g. issuing state, date, etc.); and should be captured in elements not attributes.

It is important to recognize that the scope of the GJXDM is to provide a basis for standardized electronic sharing of justice (courts, corrections, law enforcement, etc.) information between information systems. (The GJXDM does not specify how the systems internally store exchanged data or what business rules the systems apply to process or generate an information exchange.) The particular information shared is implementation dependent – it varies depending on the function of each participating system and the agreements between organizations exchanging the information.

Generally, a system should not be expected or required to exchange all of the data elements (and attributes) in the GJXDM – only those that are relevant to its function. Therefore, an implementation does not have to support or use all GJXDM components to be compliant. It must simply use the GJXDM components – where practical – for the particular information exchanges required by the organization’s business process.

Recognizing that the GJXDM components are not expected to completely address all information exchanges for all implementations, the GJXDM is designed to be extensible. Therefore, an implementation may include components that are not in the GJXDM and still be GJXDM compliant (as long as the guidelines for extension are followed). These guidelines include defining new elements, defining new types that are extensions of existing GJXDM types, and creating and documenting new elements that reuse existing GJXDM types. Extensions are specified in an Extension Schema that imports the GJXDM or a subschema of the GJXDM (see the GJXDM User's Guide  for a complete set of guidelines).

For an implementation to be GJXDM compliant, the following criteria must be considered:

• The implementation must provide and/or accept justice information exchanges using XML documents that validate to XML Schemas that import the GJXDM or a subschema of the GJXDM
• Any subschemas of the GJXDM used must follow the guidelines for generating a valid subschema.
• Any extensions used must follow the guidelines for extending the GJXDM
• Any other schemas imported (in addition to the GJXDM) must not conflict with, and must be consistent with, the GJXDM.

Following is the list of all the GJXDM Elements and Types (see note at the bottom regarding descriptions):

Elements:

j:Activity
j:ActivityAbstracter.Organization
j:ActivityAbstracter.Person
j:ActivityApprovalPerson
j:ActivityAssistingPerson
j:ActivityClearer.Organization
j:ActivityClearer.Person
j:ActivityCollectedEvidence
j:ActivityCommentText
j:ActivityComplainantAttorney
j:ActivityComplainantPerson
j:ActivityCompletedIndicator
j:ActivityCourt
j:ActivityCrimeCase
j:ActivityCrimePotentialCharge
j:ActivityDate
j:ActivityDefenseAttorney
j:ActivityDescriptionText
j:ActivityDetainedLocation
j:ActivityDispatcher
j:ActivityDispatchLocation
j:ActivityDisposition
j:ActivityDistrictAttorney
j:ActivityDocket
j:ActivityDocument
j:ActivityDocumentIssuerOrganization
j:ActivityDocumentServer.Organization
j:ActivityDocumentServer.Person
j:ActivityDocumentValidator.Organization
j:ActivityDocumentValidator.Person
j:ActivityEndDate
j:ActivityEndTime
j:ActivityEvidenceLedger
j:ActivityID
j:ActivityInformant
j:ActivityInitiatingInstrument
j:ActivityInvestigator
j:ActivityIssuingJudge
j:ActivityItemObtainer
j:ActivityLabReceipt
j:ActivityNarrativeDocument
j:ActivityOfficial.Enforcement
j:ActivityOfficial.Judicial
j:ActivityOriginatingDocument
j:ActivityOwner
j:ActivityPhoneOperator
j:ActivityPreviousActivity
j:ActivityPreviousCase
j:ActivityPreviousCourt
j:ActivityPreviousIncident
j:ActivityPrimaryOrganization
j:ActivityPrimaryWorker
j:ActivityReasonText
j:ActivityRegistration
j:ActivityReleaser
j:ActivityReporter
j:ActivityReportingOrganization
j:ActivityRequestedEvidence
j:ActivityResponsibleOrganization
j:ActivityResultDate
j:ActivityResultText
j:ActivityResultTime
j:ActivitySecondaryServiceAgency
j:ActivitySeizedProperty
j:ActivitySeverestInjury
j:ActivityStatus
j:ActivitySupervisingOrganization
j:ActivitySupplementalDocument
j:ActivitySuspect
j:ActivityTime
j:ActivityTypeText
j:ActivityUnknownAffiliate
j:ActivityUpdateIndicator
j:ActivityUsedForce
j:ActivityVehicleOperator
j:ActivityVictim
j:ActivityWitness
j:Actor.Organization
j:Actor.Person
j:Actor.Property
j:Address
j:AddressComponentDescriptionText
j:AddressComponentText
j:AddressFullText
j:AddressGrid
j:AddressGridID
j:AddressGridText
j:AddressMailDeliveryUnitText
j:AddressOther
j:AddressPrivateMailboxText
j:AddressRecipientName
j:AddressRegionFullText
j:AddressRouteName
j:Affiliate
j:AffiliateDescriptionText
j:AffiliateName
j:AffiliateParty.Organization
j:AffiliateParty.Person
j:AffiliateRoleText
j:AffiliateStartDate
j:AffiliateTypeText
j:AgeMeasure
j:Agency
j:ageUnitCode
j:Aircraft
j:AircraftAirportID
j:AircraftAirportName
j:AircraftEngineQuantity
j:AircraftFuselageColorCode
j:AircraftFuselageColorText
j:AircraftMakeCode
j:AircraftModelCode
j:AircraftStyleCode
j:AircraftTailID
j:AircraftWingColorCode
j:AircraftWingColorText
j:AircraftYearDate
j:Alert
j:AlertAudienceDescriptionText
j:AlertAudioURLID
j:AlertCertaintyCode
j:AlertCertaintyText
j:AlertContactInformation
j:AlertContactText
j:AlertEffectiveDate
j:AlertEffectiveTime
j:AlertEventCategoryCode
j:AlertEventCategoryText
j:AlertEventDescriptionText
j:AlertEventTypeText
j:AlertExpiresDate
j:AlertExpiresTime
j:AlertHeadlineText
j:AlertImageURLID
j:AlertInformationURLID
j:AlertInstructionText
j:AlertOnsetDuration
j:AlertParameterCodeText
j:AlertSenderDescriptionText
j:AlertSeverityCode
j:AlertSeverityText
j:AlertTargetCodeText
j:AlertUrgencyCode
j:AlertUrgencyText
j:AmendedSentence
j:Amount
j:AppellateCase
j:AppellateCaseBrief
j:AppellateCaseDecision
j:AppellateCaseDecisionDate
j:AppellateCaseDecisionDescriptionText
j:AppellateCaseDecisionID
j:AppellateCaseDecisionIssuingJudge
j:AppellateCaseDecisionName
j:AppellateCaseDecisionOpinionIndicator
j:AppellateCaseDecisionPrecedenceIndicator
j:AppellateCaseDecisionReliefEffectiveDate
j:AppellateCaseDecisionReliefIndicator
j:AppellateCaseDecisionText
j:AppellateCaseDecisionTypeText
j:AppellateCaseJudgePanel
j:AppellateCaseNotice
j:AppellateCaseNoticeDefendantActor.Organization
j:AppellateCaseNoticeDefendantActor.Person
j:AppellateCaseNoticeDefendantActor.Property
j:AppellateCaseNoticeDefendingAgency
j:AppellateCaseNoticeFilingCourt
j:AppellateCaseNoticeOriginalCourt
j:AppellateCaseNoticeProsecutingAgency
j:AppellateCaseNoticeProsecutingAttorney
j:AppellateCaseNoticeReasonText
j:AppellateCaseOriginalCase
j:AppellateCaseRelatedCase
j:AppellateCaseSanction
j:applicationVersionText
j:Area
j:AreaCircularRegion
j:AreaCircularText
j:AreaDescriptionText
j:AreaGeographicCodeText
j:AreaPolygonGeographicCoordinate
j:AreaPolygonText
j:Arrest
j:ArrestAgency
j:ArrestAgencyRecordID
j:ArrestApprehensionDetentionOrder
j:ArrestArraignmentDate
j:ArrestArraignmentTime
j:ArrestBailRecommendationText
j:ArrestBloodAlcoholContentNumberText
j:ArrestCharge
j:ArrestIntoxicantInvolvedIndicator
j:ArrestInvolvedOrganization
j:ArrestInvolvedProperty
j:ArrestInvolvedWeapon
j:ArrestLocation
j:ArrestOfficial
j:ArrestProbableCauseText
j:ArrestRelease
j:ArrestResistedIndicator
j:ArrestSequenceID
j:ArrestSubject
j:ArrestSubjectCountCode
j:ArrestSubjectCustodyTransfer
j:ArrestSubjectRightsReadIndicator
j:ArrestSubjectRightsReadResponseText
j:ArrestSummonsIndicator
j:ArrestTypeCode
j:ArrestWarrant
j:Assessment
j:AssessmentAdministrator.Organization
j:AssessmentAdministrator.Person
j:AssessmentBillRecipient.Organization
j:AssessmentBillRecipient.Person
j:AssessmentFee
j:AssessmentProgram
j:AssessmentRecommendationText
j:AssessmentReferral
j:AssessmentScoreText
j:AssessmentSubject
j:AssessmentSupervisor.Organization
j:AssessmentSupervisor.Person
j:Attorney
j:Bail
j:BailConditionDescriptionText
j:BailHearingDate
j:BailPostedAmount
j:BailPostedBond
j:BailPostedDate
j:BailRequirementText
j:BailRevokedDate
j:BailSetAmount
j:BailSetAmountText
j:BailSetCourt
j:BailSubject
j:Binary
j:BinaryAvailableAtText
j:BinaryAvailableIndicator
j:BinaryCaptureDate
j:BinaryCaptureOrganization
j:BinaryCapturePerson
j:BinaryCaptureTime
j:BinaryDescriptionText
j:BinaryFormatText
j:BinaryFormatTypeText
j:BinaryID
j:BinaryObject.Base64
j:BinaryObject.Hex
j:BinaryReferenceID
j:BinarySizeValue
j:BinaryTypeText
j:Biometric
j:BiometricAccuracyDescriptionText
j:BiometricBinary
j:BiometricCaptureDate
j:BiometricCaptureDescriptionText
j:BiometricCaptureOrganization
j:BiometricCapturePerson
j:BiometricCaptureSourceText
j:BiometricCaptureTime
j:BiometricDescriptionText
j:BiometricEncodingMethodText
j:BiometricID
j:BiometricImage
j:BiometricLabAnalysisText
j:BiometricRepositoryDescriptionText
j:BiometricRepositoryOrganization
j:BiometricStatus
j:BiometricTestDate
j:BiometricTestDescriptionText
j:BiometricTestMethodText
j:BiometricTestOrganization
j:BiometricTestPerson
j:BiometricTestTime
j:BiometricValueText
j:Boat
j:BoatColorCode
j:BoatHullID
j:BoatHullMaterialCode
j:BoatHullMaterialText
j:BoatHullShapeCode
j:BoatHullShapeText
j:BoatMakeCode
j:BoatPropulsionCode
j:BoatPropulsionText
j:BoatRegistrationID
j:BoatTrailerMakeCode
j:BoatTrailerMakeName
j:BoatTypeCode
j:Bond
j:BondAmount
j:BondConditionDescriptionText
j:BondIssuer.Organization
j:BondIssuer.Person
j:BondPaymentDescriptionText
j:BondRevokeDate
j:BondSuretyName
j:BondTerminationDate
j:BondTerminationTypeText
j:Booking
j:BookingAdditionalChargesIndicator
j:BookingAgency
j:BookingAgencyRecordID
j:BookingArraignmentDate
j:BookingArraignmentTime
j:BookingCourtCaseID
j:BookingDepositedProperty
j:BookingDetentionFacility
j:BookingDocumentControlID
j:BookingEmployee
j:BookingFacility
j:BookingFileID
j:BookingRelease
j:BookingReleaseCorrectionsAnalyst
j:BookingReportingDistrictText
j:BookingRetainedProperty
j:BookingSealedIndicator
j:BookingSearchOfficial
j:BookingSeizedProperty
j:BookingSubject
j:BookingSubjectCustodyTransfer
j:BookingTelephoneCall
j:BookingTelephoneCallDate
j:BookingTelephoneCallSupervisingOfficial
j:BookingTelephoneCallTime
j:BookingTransportOfficial
j:BranderID
j:BranderTypeCode
j:BuildingFullText
j:BuildingName
j:BuildingNumberText
j:BuildingSubUnitText
j:CanadianProvinceCode
j:CapabilityCategoryText
j:CapabilityDescriptionText
j:CapabilityIsLimitationIndicator
j:CapabilityTypeText
j:Case
j:CaseAmendedCharge
j:CaseCapiasDate
j:CaseCategoryText
j:CaseCharge
j:CaseClassification
j:CaseContinuanceDate
j:CaseConvictionReportingRequirements
j:CaseCourt
j:CaseCourtEvent
j:CaseDefendantParty.Organization
j:CaseDefendantParty.Person
j:CaseDefendantParty.Property
j:CaseDefendantQuantityText
j:CaseDefendantSelfRepresentationIndicator
j:CaseDefenseAttorney
j:CaseDetails
j:CaseDisposition
j:CaseDispositionDecision
j:CaseDispositionDecisionText
j:CaseDispositionDecisionTypeText
j:CaseDispositionFinalDate
j:CaseDocketID
j:CaseDomesticViolenceIndicator
j:CaseDrivingImpairedIndicator
j:CaseDrivingIntoxicatedIndicator
j:CaseExhibit
j:CaseFiling
j:CaseHearing
j:CaseInformationAdmissibleIndicator
j:CaseInformationAdmissibleText
j:CaseInformationUnadmissibleText
j:CaseInitiatingParty.Organization
j:CaseInitiatingParty.Person
j:CaseInitiatingParty.Property
j:CaseJudge
j:CaseJuror
j:CaseLineageCase
j:CaseOfficial
j:CaseOfficialCaseID
j:CaseOfficialCaseStatusText
j:CaseOfficialEndDate
j:CaseOfficialRoleDescriptionText
j:CaseOfficialRoleText
j:CaseOfficialStartDate
j:CaseOfficialTerminationIndicator
j:CaseOfficialTerminationReasonText
j:CaseOriginalCourt
j:CaseOtherActor.Organization
j:CaseOtherActor.Person
j:CaseOtherActor.Property
j:CaseOtherID
j:CaseOtherOfficial
j:CaseParticipants
j:CasePendingCourtEvent
j:CaseProceedingTypeText
j:CaseProsecutionAttorney
j:CaseProtectionOrderIndicator
j:CaseRelatedCase
j:CaseResolutionText
j:CaseRespondentParty.Organization
j:CaseRespondentParty.Person
j:CaseRespondentParty.Property
j:CaseRestrictionDate
j:CaseRestrictionText
j:CaseSecurityText
j:CaseSeverityText
j:CaseStatus
j:CaseSubtypeText
j:CaseTerminationStageText
j:CaseTerminationTypeText
j:CaseTitleText
j:CaseTrackingID
j:CaseTrial
j:CaseTypeText
j:CaseVerdictGivenIndicator
j:CaseVictimNotProsecutingIndicator
j:CaseWitness
j:CaseYearDate
j:Caveat
j:CaveatIssuingAuthorityName
j:CaveatReferenceDate
j:CaveatText
j:Charge
j:ChargeAccidentRelatedIndicator
j:ChargeApplicabilityText
j:ChargeArrestReasonIndicator
j:ChargeCategoryDescriptionText
j:ChargeClassification
j:ChargeCountQuantity
j:ChargeDegreeText
j:ChargeDescriptionText
j:ChargeDisposition
j:ChargeDispositionCondition
j:ChargeDispositionDate
j:ChargeDispositionDescriptionText
j:ChargeDispositionOtherText
j:ChargeDispositionPlea
j:ChargeDispositionReasonText
j:ChargeDispositionSanction
j:ChargeDispositionVerdict
j:ChargeEmploymentRelatedIndicator
j:ChargeEnhancingAllegationCharge
j:ChargeEnhancingFactor
j:ChargeEnhancingFactorDescriptionText
j:ChargeEnhancingFactorReferenceDate
j:ChargeEnhancingFactorStatusText
j:ChargeEnhancingFactorText
j:ChargeEnhancingPriorConviction
j:ChargeFelonyIndicator
j:ChargeFiler.Organization
j:ChargeFiler.Person
j:ChargeFilingDate
j:ChargeHighestIndicator
j:ChargeID
j:ChargeInstrument
j:ChargeLegalDescriptionText
j:ChargeLocalCode
j:ChargeMACRDispositionText
j:ChargeMACRIndicationLevelText
j:ChargeMACRJuvenileLevelText
j:ChargeMACRStatusText
j:ChargeModificationInstrument
j:ChargeModifier.Organization
j:ChargeModifier.Person
j:ChargeNarrative
j:ChargeNCICCode
j:ChargeOriginator.Organization
j:ChargeOriginator.Person
j:ChargePlea
j:ChargeQualifierText
j:ChargeRecommendedBailAmount
j:ChargeReducingFactorText
j:ChargeReporting
j:ChargeSanction
j:ChargeSentence
j:ChargeSentenceRangeText
j:ChargeSequenceID
j:ChargeSeriousViolentIndicator
j:ChargeSeverityLevel
j:ChargeSeverityText
j:ChargeSpecialAllegationText
j:ChargeStatus
j:ChargeStatute
j:ChargeSubject
j:ChargeText
j:ChargeTrackingID
j:ChargeUCRCode
j:ChargeUCRCrimeTypeText
j:ChargeVerdict
j:ChargeVictim
j:CircularRegionCenterCoordinate
j:CircularRegionRadiusLengthMeasure
j:Citation
j:CitationAgency
j:CitationDismissalConditionIndicator
j:CitationDismissalConditionText
j:CitationFineAmount
j:CitationIssuedLocation
j:CitationIssuingOfficial
j:CitationSubject
j:CitationViolation
j:Classification
j:ClassificationAgencyName
j:ClassificationDerivationText
j:ClassificationEffectiveDate
j:ClassificationInstructionText
j:ClassificationNonUSText
j:ClassificationPersonName
j:ClassificationReasonText
j:ClassificationReviewAgencyName
j:ClassificationReviewDate
j:ClassificationReviewPersonName
j:ClassificationTerminationActualDate
j:ClassificationTerminationSetDate
j:ClassificationText
j:ClassificationUSCode
j:ClothingCategoryText
j:ClothingColorText
j:ClothingDescriptionText
j:ClothingStyleText
j:commentText
j:CommercialStructure
j:CommercialVehicle
j:Condition
j:ConditionalRelease
j:ConditionalReleaseCondition
j:ConditionalReleaseOppositionText
j:ConditionalReleaseProjectedDate
j:ConditionalReleaseRevokedDate
j:ConditionalReleaseRevokedReasonText
j:ConditionalReleaseSupportText
j:ConditionDisciplinaryAction
j:ConditionGroup
j:ConditionGroupID
j:ConditionGroupParentID
j:ConditionMandatoryIndicator
j:ConditionSetDate
j:ConditionViolatedIndicator
j:ConditionViolationDate
j:ConditionViolationText
j:confidenceNumeric
j:ContactEmailID
j:ContactFacsimileNumber
j:ContactInformation
j:ContactInformationDescriptionText
j:ContactMailingAddress
j:ContactMobileTelephoneNumber
j:ContactOrganization
j:ContactOtherID
j:ContactPagerNumber
j:ContactPerson
j:ContactPersonDescriptionText
j:ContactRadio
j:ContactRadioCallSignID
j:ContactRadioChannelText
j:ContactRadioTypeText
j:ContactResponder
j:ContactTelephoneNumber
j:ContactWebsiteID
j:Conviction
j:ConvictionCharge
j:ConvictionChargeCountQuantity
j:ConvictionCountQuantity
j:ConvictionCourt
j:ConvictionLocatorReferenceID
j:ConvictionOffense
j:ConvictionPlea
j:ConvictionReportingProfessionName
j:ConvictionReportingRequirementText
j:ConvictionSanction
j:ConvictionSentence
j:ConvictionSubject
j:ConvictionVerdict
j:CorrectionalFacility
j:Corrections
j:Court
j:CourtActivity
j:CourtActivityCondition
j:CourtActivityCourtOrder
j:CourtActivityScheduleDay
j:CourtActivitySupervisingAgency
j:CourtAdministrativeUnitText
j:CourtAppearance
j:CourtAppearanceActor.Organization
j:CourtAppearanceActor.Person
j:CourtAppearanceActor.Property
j:CourtAppearanceCase
j:CourtAppearanceCourt
j:CourtAppearanceDate
j:CourtAppearanceReasonText
j:CourtAppearanceTime
j:CourtAppearanceTypeText
j:CourtCharge
j:CourtDivisionText
j:CourtEvent
j:CourtEventAction
j:CourtEventActivity
j:CourtEventAppearance
j:CourtEventCase
j:CourtEventCourt
j:CourtEventJudge
j:CourtEventMotion
j:CourtEventSchedule
j:CourtEventSequenceID
j:CourtName
j:CourtOrder
j:CourtOrderCondition
j:CourtOrderDesignatedLocation
j:CourtOrderDesignatedOrganization
j:CourtOrderDesignatedProperty
j:CourtOrderDesignatedSubject
j:CourtOrderEnforcementAgency
j:CourtOrderIssuingCourt
j:CourtOrderIssuingDate
j:CourtOrderIssuingJudicialOfficial
j:CourtOrderJurisdiction
j:CourtOrderRecallDate
j:CourtOrderRecallReasonText
j:CourtOrderRequestActor.Organization
j:CourtOrderRequestActor.Person
j:CourtOrderRequestActor.Property
j:CourtOrderRequestDate
j:CourtOrderRequestReasonText
j:CourtOrderServiceAttemptedDate
j:CourtOrderServiceCautionText
j:CourtOrderServiceDate
j:CourtOrderServiceDescriptionText
j:CourtOrderServiceOfficial.Enforcement
j:CourtOrderServiceOfficial.Judicial
j:CourtOrderServiceReceivedDate
j:CourtOrderServiceRestrictionText
j:CourtOrderSignatureMethodText
j:CourtOrderSpecialInstructionText
j:CourtOrderStatus
j:CourtOrderSupervisingAgency
j:CourtSupervisingAgency
j:CourtTypeCode
j:criminalInformationIndicator
j:CriminalOrganization
j:CriminalOrganizationCautionText
j:CriminalOrganizationMembershipHighQuantityText
j:CriminalOrganizationMembershipInitiationText
j:CriminalOrganizationMembershipLowQuantityText
j:CriminalOrganizationNCICID
j:CriminalOrganizationObjectiveText
j:CriminalOrganizationTraitDetails
j:CriminalTraitAction
j:CriminalTraitActivityDescriptionText
j:CriminalTraitColorText
j:CriminalTraitCommunicationDescriptionText
j:CriminalTraitDescriptionText
j:CriminalTraitDetails
j:CriminalTraitDressText
j:CriminalTraitEthnicityCode
j:CriminalTraitEthnicityText
j:CriminalTraitGraffitiDescriptionText
j:CriminalTraitGraffitiImage
j:CriminalTraitHandSignalText
j:CriminalTraitModusOperandiText
j:CriminalTraitTargetDescriptionText
j:CriminalTraitTattooDescriptionText
j:CriminalTraitTattooImage
j:CriminalTraitTurfText
j:CrossStreet
j:CrossStreetDescriptionText
j:CrossStreetRelativeLocation
j:currencyCode
j:currencyText
j:CustodyTransfer
j:CustodyTransferActionText
j:CustodyTransferLocation
j:CustodyTransferProperty
j:CustodyTransferReceivingEnforcementAgency
j:CustodyTransferReceivingEnforcementFacility
j:CustodyTransferReceivingEnforcementOfficial
j:CustodyTransferReleasingEnforcementAgency
j:CustodyTransferReleasingEnforcementFacility
j:CustodyTransferReleasingEnforcementOfficial
j:CustodyTransferSubject
j:DecalColorText
j:DecalID
j:DecalMonthDate
j:DecalPeriodCode
j:DecalPeriodText
j:DecalYearDate
j:Detention
j:DetentionFacility
j:DisciplinaryAction
j:DisciplinaryActionAssigner.Organization
j:DisciplinaryActionAssigner.Person
j:DisciplinaryActionCommunityService
j:DisciplinaryActionCounseling
j:DisciplinaryActionEnforcer.Organization
j:DisciplinaryActionEnforcer.Person
j:DisciplinaryActionFacility
j:DisciplinaryActionFee
j:DisciplinaryActionProgram
j:DisciplinaryActionRestitution
j:DisciplinaryActionSanction
j:DisciplinaryActionSubject
j:Disposition
j:DispositionAgency
j:DispositionDate
j:DispositionDescriptionText
j:DispositionInstrument
j:DispositionReasonText
j:DispositionReportedAuthorityText
j:DispositionText
j:DispositionTypeText
j:distributionText
j:DiversionProgram
j:DNACollectionStatusCode
j:DNACollectionStatusText
j:DNAImage
j:DNALocus
j:DNALocusTypeText
j:DNALocusValue
j:Document
j:DocumentAbstractText
j:DocumentAlternativeTitleText
j:DocumentApplicationName
j:DocumentApprovedIndicator
j:DocumentAuthor.Organization
j:DocumentAuthor.Person
j:DocumentBinary
j:DocumentCategoryDescriptionText
j:DocumentCategoryID
j:DocumentCategoryName
j:DocumentCommentText
j:DocumentContentTableText
j:DocumentContributor.Organization
j:DocumentContributor.Person
j:DocumentControlMetadata
j:DocumentCopyrightIndicator
j:DocumentCountryCode.fips10-4
j:DocumentCountryCode.iso3166Alpha2
j:DocumentCountryCode.iso3166Alpha3
j:DocumentCountryCode.iso3166Numeric
j:DocumentCoverageText.Address
j:DocumentCoverageText.Date
j:DocumentCoverageText.Text
j:DocumentCoverageText.Time
j:DocumentCreationDate
j:DocumentCreator.Organization
j:DocumentCreator.Person
j:DocumentCutDate
j:DocumentDescriptionText
j:DocumentDescriptiveMetadata
j:DocumentDispositionAuthorityName
j:DocumentDispositionInstructionText
j:DocumentDisputedIndicator
j:DocumentDisputedReasonCodeText
j:DocumentDisputedReasonText
j:DocumentEffectiveDate
j:DocumentEnteredBy
j:DocumentExpirationDate
j:DocumentFileControlID
j:DocumentFiledDate
j:DocumentFiledTime
j:DocumentFileExtensionText
j:DocumentFileName
j:DocumentFormatText
j:DocumentFormatTypeText
j:DocumentGroupID
j:DocumentID
j:DocumentIntelligenceTypeCode
j:DocumentKeywordText
j:DocumentLanguageCode.iso639-2b
j:DocumentLanguageCode.iso639-2t
j:DocumentLastModifiedDate
j:DocumentLocation
j:DocumentLocationURI
j:DocumentManagementCyclePeriodText
j:DocumentMangementCyclePeriodText
j:DocumentMediaTypeText
j:DocumentMediumText
j:DocumentOtherAddresseeName
j:DocumentOtherMetadataField
j:DocumentPermanentRecordIndicator
j:DocumentPostDate
j:DocumentPrivacyActIndicator
j:DocumentPublicationDate
j:DocumentReceivedDate
j:DocumentRelatedResourceText
j:DocumentRelationText
j:DocumentRightsText
j:DocumentSecurityMetadata
j:DocumentSequenceID
j:DocumentSource.Organization
j:DocumentSource.Person
j:DocumentSourceText
j:DocumentStatus
j:DocumentSubject.Organization
j:DocumentSubject.Person
j:DocumentSubjectCodeText
j:DocumentSubjectText
j:DocumentSubmitter.Organization
j:DocumentSubmitter.Person
j:DocumentSummaryText
j:DocumentSupplementalMarkingText
j:DocumentTitleText
j:DocumentTypeText
j:DocumentVitalIndicator
j:DriverAuthorization
j:DriverAuthorizationEndorsementCode
j:DriverAuthorizationEndorsementText
j:DriverAuthorizationExpirationDate
j:DriverAuthorizationID
j:DriverAuthorizationID.Detailed
j:DriverAuthorizationIssueDate
j:DriverAuthorizationPerson
j:DriverAuthorizationRestriction
j:DriverConviction
j:DriverConvictionCitation
j:DriverConvictionCMVCode
j:DriverConvictionCMVText
j:DriverConvictionHazMatCode
j:DriverConvictionHazMatText
j:DriverConvictionOffenseCode
j:DriverConvictionOffenseDescriptionText
j:DriverConvictionOffenseText
j:DriverHistoryAccidentQuantity
j:DriverHistoryConvictionQuantity
j:DriverHistorySummary
j:DriverHistoryWithdrawalQuantity
j:DriverLicense
j:DriverLicenseCommercialClassCode
j:DriverLicenseCommercialClassText
j:DriverLicenseCommercialStatusCode
j:DriverLicenseCommercialStatusText
j:DriverLicenseConviction
j:DriverLicenseIssuedPerson
j:DriverLicenseNonCommercialClassText
j:DriverLicenseNonCommercialStatusCode
j:DriverLicenseNonCommercialStatusText
j:DriverLicensePermit
j:DriverLicensePermitClassificationText
j:DriverLicensePermitQuantity
j:DriverLicensePermitStatusCode
j:DriverLicensePermitStatusText
j:DriverLicenseWithdrawal
j:DriverLicenseWithdrawalActionCode
j:DriverLicenseWithdrawalActionText
j:DriverLicenseWithdrawalBasisCode
j:DriverLicenseWithdrawalBasisText
j:DriverLicenseWithdrawalCode
j:DriverLicenseWithdrawalDueProcessStatusCode
j:DriverLicenseWithdrawalDueProcessStatusText
j:DriverLicenseWithdrawalEffectiveDate
j:DriverLicenseWithdrawalEligibilityCode
j:DriverLicenseWithdrawalEligibilityDate
j:DriverLicenseWithdrawalExtentCode
j:DriverLicenseWithdrawalExtentText
j:DriverLicenseWithdrawalIssuingAuthorityCode
j:DriverLicenseWithdrawalIssuingAuthorityText
j:DriverLicenseWithdrawalLocatorReferenceID
j:DriverLicenseWithdrawalPendingIndicator
j:DriverLicenseWithdrawalReasonReferenceCodeText
j:DriverLicenseWithdrawalReinstatementDate
j:DriverLicenseWithdrawalText
j:DrivingAccidentSeverityCode
j:DrivingAccidentSeverityText
j:DrivingIncident
j:DrivingIncidentCMVCode
j:DrivingIncidentCMVText
j:DrivingIncidentCollisionIndicator
j:DrivingIncidentDriverOwnershipIndicator
j:DrivingIncidentFemalePassengerQuantityText
j:DrivingIncidentHazMatCode
j:DrivingIncidentHazMatText
j:DrivingIncidentJurisdiction
j:DrivingIncidentLaserDetectionIndicator
j:DrivingIncidentLegalSpeedRate
j:DrivingIncidentLocatorReferenceID
j:DrivingIncidentMalePassengerQuantityText
j:DrivingIncidentMobilePhoneIndicator
j:DrivingIncidentPassenger
j:DrivingIncidentPassengerDescriptionText
j:DrivingIncidentPassengerQuantityText
j:DrivingIncidentRadarDetectionIndicator
j:DrivingIncidentRecordedSpeedRate
j:DrivingIncidentRecordedSpeedRate.Range
j:DrivingIncidentRoadDescriptionText
j:DrivingIncidentRoadTypeText
j:DrivingIncidentTrafficDescriptionText
j:DrivingIncidentWeatherDescriptionText
j:DrivingJurisdictionAuthorityCode
j:DrivingJurisdictionAuthorityCode.ncicLSTA
j:DrivingRestriction
j:DrivingRestrictionCode
j:DrivingRestrictionDescriptionText
j:DrivingRestrictionEndDate
j:DrivingRestrictionText
j:Drug
j:DrugCompositionDescriptionText
j:DrugContainerDescriptionText
j:DrugFoundDescriptionText
j:DrugQuantityMeasure
j:DrugSubstanceFormText
j:DrugTypeCode
j:drugUnitCode
j:effectiveDate
j:effectiveTime
j:elevationUnitCode
j:EmergencyContactInformation
j:Employment
j:EmploymentAssignedUnit.EnforcementUnit
j:EmploymentAssignedUnit.Organization
j:EmploymentContactInformation
j:EmploymentDepartmentName
j:EmploymentEarningsRate
j:EmploymentEmployee
j:EmploymentEmployer.Organization
j:EmploymentEmployer.Person
j:EmploymentEmployerName
j:EmploymentEndDate
j:EmploymentEndReasonText
j:EmploymentLocation
j:EmploymentOccupationCode
j:EmploymentOccupationText
j:EmploymentOccupationTypeCode
j:EmploymentOccupationTypeText
j:EmploymentPersonID
j:EmploymentPositionName
j:EmploymentRankText
j:EmploymentShiftText
j:EmploymentStartDate
j:EmploymentStatus
j:EmploymentSupervisor
j:EnforcementOfficial
j:EnforcementOfficialActivityTypeCode
j:EnforcementOfficialActivityTypeText
j:EnforcementOfficialAssignmentTypeCode
j:EnforcementOfficialAssignmentTypeText
j:EnforcementOfficialBadgeID
j:EnforcementOfficialPOSTLicenseID
j:EnforcementOfficialTypeText
j:EnforcementOfficialUnavailableSchedule
j:EnforcementOfficialUnit
j:EnforcementUnit
j:EnforcementUnitBeatID
j:EnforcementUnitID
j:EnforcementUnitName
j:EnforcementUnitNumberID
j:EnforcementUnitSectionID
j:EnginePowerDisplacement
j:enginePowerDisplacementUnitCode
j:Event
j:EventDate
j:EventDescriptionText
j:EventName
j:EventStatus
j:EventTime
j:EventTypeText
j:Evidence
j:EvidenceAmount
j:EvidenceCollector
j:EvidenceCustodyTransfer
j:EvidenceDocumentBinary
j:EvidenceItem.Binary
j:EvidenceItem.Biometric
j:EvidenceItem.Property
j:EvidenceKit
j:EvidenceNumberID
j:EvidenceOtherID
j:EvidencePreviousLocation
j:EvidenceQuantityText
j:EvidenceReceiptID
j:EvidenceReturnedIndicator
j:EvidenceReturnRecipient.Organization
j:EvidenceReturnRecipient.Person
j:EvidenceTakenFrom.Organization
j:EvidenceTakenFrom.Person
j:EvidenceTakenLocation
j:Exhibit
j:ExhibitAcceptingAgency
j:ExhibitAdmittedIndicator
j:ExhibitEvidence
j:ExhibitID
j:ExhibitRemainingProofIndicator
j:ExhibitStatusText
j:expirationDate
j:expirationTime
j:Facility
j:FacilityCapacityDescriptionText
j:FacilityCapacityQuantity
j:FacilityCaseLoadQuantity
j:FacilityID
j:FacilityJuvenileIndicator
j:FacilityMemberTypeText
j:FacilityOperatingAgency
j:FacilitySecurityLevelText
j:FacilitySupervisingAgency
j:Fee
j:Fee.Detailed
j:Felony
j:FinalPlea
j:FinancialObligation
j:FinancialObligationDueAmount
j:FinancialObligationExemptionAmount
j:FinancialObligationPaidAmount
j:FinancialObligationTotalAmount
j:Fingerprint
j:FingerprintClassificationCode
j:FingerprintClassificationText
j:FingerprintFingerCode
j:FingerprintFingerText
j:FingerprintPatternCode
j:FingerprintPatternText
j:Firearm
j:FirearmAutomaticIndicator
j:FirearmBarrelLengthMeasure
j:FirearmCaliberCode
j:FirearmCaliberText
j:FirearmFinishCode
j:FirearmFinishText
j:FirearmGaugeText
j:FirearmGripText
j:FirearmMakeCode
j:FirearmTypeCode
j:FirearmTypeDescriptionCode
j:FirearmTypeDescriptionText
j:Force
j:ForcePhysicalDescriptionText
j:ForceSubject
j:ForceTakenAsEvidence
j:ForceToolProperty
j:ForceTypeCode
j:ForceTypeText
j:ForceUser.Organization
j:ForceUser.Person
j:ForceVictim
j:ForceWeaponProperty
j:GeographicCoordinate
j:GeographicCoordinateLatitude
j:GeographicCoordinateLongitude
j:GeographicCoordinateSystemID
j:GeographicDatumID
j:Highway
j:HighwayFullText
j:HighwayID
j:HighwayName
j:HighwayPositionText
j:HomeContactInformation
j:ID
j:IDEffectiveDate
j:IDExpirationDate
j:IDIssuingAuthorityText
j:IDJurisdictionCode
j:IDJurisdictionCode.ncicLIS
j:IDJurisdictionCode.ncicLSTA
j:IDJurisdictionCode.ncicRES
j:IDJurisdictionText
j:IDObject
j:IDSourceText
j:IDStatus
j:IDTypeCodeSourceText
j:IDTypeCodeText
j:IDTypeCodeVersionText
j:IDTypeDescriptionText
j:IDTypeText
j:Image
j:ImageCreatedOrganization
j:ImageFacialText
j:ImageHeightValue
j:ImageJuvenileIndicator
j:ImageLocation
j:ImageOperator
j:ImagePoseCode
j:ImagePoseText
j:ImageTypeCode
j:ImageWidthValue
j:Incarceration
j:Incident
j:IncidentArrest
j:IncidentArrestMadeIndicator
j:IncidentAssistingOfficial
j:IncidentCategory
j:IncidentCategoryTypeCode
j:IncidentCategoryTypeText
j:IncidentCriminalIndicator
j:IncidentDamagedProperty
j:IncidentDayPeriodText
j:IncidentEntryPoint
j:IncidentEvent
j:IncidentEvidence
j:IncidentEvidenceHeldIndicator
j:IncidentExceptionalClearanceCode
j:IncidentExceptionalClearanceText
j:IncidentExceptionClearanceDate
j:IncidentExitPoint
j:IncidentFactor
j:IncidentFactorCode
j:IncidentFactorCode.nibrsAggravatedAssaultHomicide
j:IncidentFactorCode.nibrsBiasMotivation
j:IncidentFactorCode.nibrsJustifiableHomicide
j:IncidentFactorDescriptionText
j:IncidentFactorKnownIndicator
j:IncidentFactorSubtypeText
j:IncidentFactorText
j:IncidentForce
j:IncidentForceInvolvedIndicator
j:IncidentForm
j:IncidentFormComment
j:IncidentFormName
j:IncidentFormSubmittedIndicator
j:IncidentInjuryLevelText
j:IncidentInvolvedProperty
j:IncidentInvolvedStructure
j:IncidentJurisdictionalOrganization
j:IncidentLevelCode
j:IncidentLevelText
j:IncidentLocation
j:IncidentMethodDescriptionText
j:IncidentMinorInvolvedIndicator
j:IncidentNonPropertyItemText
j:IncidentObservationText
j:IncidentOfficialPresentIndicator
j:IncidentPrintsRequestedIndicator
j:IncidentPropertyDisposition
j:IncidentRecoveredProperty
j:IncidentRecoveredVehicleQuantity
j:IncidentReportedNarrative
j:IncidentReportingOfficial
j:IncidentResponse
j:IncidentResponseOfficial
j:IncidentResponseOrganization
j:IncidentSeizedProperty
j:IncidentServiceCall
j:IncidentSourceText
j:IncidentStolenProperty
j:IncidentStolenVehicleQuantity
j:IncidentStructuresEnteredQuantity
j:IncidentSubject
j:IncidentSubjectOrganization
j:IncidentSubjectWeapon
j:IncidentSupervisingOfficial
j:IncidentSurroundingLocation
j:IncidentTarget
j:IncidentTrafficAccidentInvolvedIndicator
j:IncidentTypeCode
j:IncidentVictim
j:IncidentViolatedStatute
j:IncidentWeaponInvolvedIndicator
j:IncidentWitness
j:Infraction
j:InjuryCauser.Force
j:InjuryCauser.Person
j:InjuryDate
j:InjuryDescriptionText
j:InjuryLocationText
j:InjurySeverityText
j:InjuryTime
j:InjuryTreater.Organization
j:InjuryTreater.Person
j:InjuryTreatmentEndDate
j:InjuryTreatmentStartDate
j:InjuryTreatmentText
j:InjuryTypeCode
j:InjuryTypeText
j:Insurance
j:InsuranceActiveIndicator
j:InsuranceCancelationDate
j:InsuranceCarrierID
j:InsuranceCarrierName
j:InsuranceCertifiedDate
j:InsuranceCoverageTypeCode
j:InsuranceCoverageTypeText
j:InsuranceCoveredProperty
j:InsuranceEffectiveDate
j:InsuranceEndDate
j:InsurancePersonalIndicator
j:InsurancePolicyID
j:IntellectualProperty
j:IntellectualPropertyBusinessAreaText
j:IntellectualPropertyCreationDate
j:IntellectualPropertyCreationEventText
j:IntellectualPropertyRegistrationDate
j:IntellectualPropertyRegistrationID
j:IntellectualPropertyTerminationDate
j:IntellectualPropertyTerminationEventText
j:intelligenceInformationIndicator
j:IntoxicationAlcoholInvolvedIndicator
j:IntoxicationDrugInvolvedIndicator
j:IntoxicationIntoxicantIllegalIndicator
j:IntoxicationIntoxicantTypeCode
j:IntoxicationIntoxicantTypeText
j:IntoxicationLevelText
j:IntoxicationOverLimitIndicator
j:IntoxicationTestAdministrator
j:IntoxicationTestDate
j:IntoxicationTestDescriptionText
j:IntoxicationTestTime
j:IntoxicationTestTypeText
j:IsAssociatedWith
j:Jewelry
j:JewelryCaratText
j:JewelryMetalText
j:JewelryStone
j:JewelryStoneCaratText
j:JewelryStoneColorText
j:JewelryStoneCutText
j:JewelryStoneQuantity
j:JewelryStoneTypeText
j:JewelryTypeCode
j:Judge
j:JudgePanel
j:JudgePanelID
j:JudgePanelRequiredQuantity
j:JudgePanelTotalQuantity
j:JudicialOfficial
j:JudicialOfficialBarID
j:JudicialOfficialBarMembership
j:JudicialOfficialBarStatus
j:JudicialOfficialCourt
j:JudicialOfficialFirm
j:JudicialOfficialPanelID
j:JudicialOfficialRegistrationID
j:JudicialOfficialTypeText
j:Jurisdiction
j:JurisdictionDescriptionText
j:JurisdictionDistrictText
j:JurisdictionID
j:JurisdictionRestrictionText
j:JurisdictionText
j:JurisdictionTitle
j:Juror
j:JurorDismissedDate
j:JurorDismissedIndicator
j:JurorDismissedReasonText
j:JurorForemanIndicator
j:JurorID
j:JurorPanelID
j:JurorPrimaryIndicator
j:KitID
j:KitTypeText
j:languageCode
j:languageText
j:lastUpdatedDate
j:lastUpdatedTime
j:lastVerifiedDate
j:lastVerifiedTime
j:LatitudeDegreeValue
j:LatitudeMinuteValue
j:LatitudeSecondValue
j:LengthMeasure
j:lengthUnitCode
j:Lessee
j:LesseeJurisdictionAuthorityCode
j:LesseeJurisdictionAuthorityText
j:LesseeParty.Organization
j:LesseeParty.Person
j:Lessor.Organization
j:Lessor.Person
j:LessorDetails
j:LessorID
j:Lien
j:LienAmount
j:LienDate
j:LienHolder.Organization
j:LienHolder.Person
j:LienHolderEntity
j:LienReleaseDate
j:LienReleaseReasonCode
j:LienReleaseReasonText
j:LienTime
j:Locale
j:LocaleCensusBlockID
j:LocaleCensusTractID
j:LocaleCommunityName
j:LocaleDescriptionText
j:LocaleDistrictName
j:LocaleEmergencyServicesCityName
j:LocaleFireJurisdictionID
j:LocaleJudicialDistrictCodeText
j:LocaleJudicialDistrictName
j:LocaleNeighborhoodName
j:LocalePoliceBeatText
j:LocalePoliceGridText
j:LocalePoliceJurisdictionID
j:LocaleRegionName
j:LocaleSubdivisionName
j:LocaleZoneName
j:Location
j:LocationAddress
j:LocationAddressGrid
j:LocationArea
j:LocationBuilding
j:LocationCityName
j:LocationContactInformation
j:LocationContainsOrganization
j:LocationCountryCode.fips10-4
j:LocationCountryCode.iso3166Alpha2
j:LocationCountryCode.iso3166Alpha3
j:LocationCountryCode.iso3166Numeric
j:LocationCountryName
j:LocationCountyCode
j:LocationCountyName
j:LocationCrossStreet
j:LocationDescriptionText
j:LocationElevation
j:LocationEmergencyServices
j:LocationGeographicCoordinate
j:LocationHighway
j:LocationLandmarkText
j:LocationLocale
j:LocationMapLocation
j:LocationMGRSCoordinate
j:LocationName
j:LocationNeighbor
j:LocationPoliceDepartment
j:LocationPostalCodeExtensionID
j:LocationPostalCodeID
j:LocationRangeDescriptionText
j:LocationRelativeLocation
j:LocationSecondaryUnitText
j:LocationStateCode.CanadianProvince
j:LocationStateCode.fips10-4International
j:LocationStateCode.fips5-2Alpha
j:LocationStateCode.fips5-2Numeric
j:LocationStateCode.ncicLIS
j:LocationStateCode.ncicLSTA
j:LocationStateCode.ncicRES
j:LocationStateCode.USPostalService
j:LocationStateName
j:LocationStreet
j:LocationSurroundingAreaDescriptionText
j:LocationTypeCode
j:LocationTypeText
j:LocationUTMCoordinate
j:LongitudeDegreeValue
j:LongitudeMinuteValue
j:LongitudeSecondValue
j:LowerBound
j:MapCoordinateFullText
j:MapDate
j:MapElevationCoordinateText
j:MapHorizontalCoordinateText
j:MapLocation
j:MapLocationDescriptionText
j:MapName
j:MapPageID
j:MapQuandrantText
j:MapVersionID
j:MapVerticalCoordinateText
j:Measure
j:measureDate
j:measurementEstimatedIndicator
j:measurementTypeText
j:measurerID
j:measurerName
j:measureTime
j:measureUnitText
j:MedicalConditionCauseText
j:MedicalConditionDescriptionText
j:MedicalConditionPresentIndicator
j:MedicalConditionSeverityText
j:MedicalConditionText
j:MetadataFieldName
j:MetadataFieldValueText
j:MGRSCoordinate
j:MGRSCoordinateID
j:MGRSCoordinateSquareID
j:MilitaryBranchName
j:MilitaryDischargeDate
j:MilitaryDischargeTypeCode
j:MilitaryDischargeTypeText
j:MilitaryExemptionDescriptionText
j:MilitaryExperienceIndicator
j:MilitaryReleaseDate
j:MilitaryReleaseTypeText
j:MilitaryServiceActiveIndicator
j:MilitaryServiceTimeMeasure
j:MilitaryStatus
j:Misdemeanor
j:MissingPerson
j:MissingPersonCircumstanceCode
j:MissingPersonCircumstanceText
j:MissingPersonDeclarationDate
j:MissingPersonDeclarationPerson
j:MissingPersonDeclarationTime
j:MissingPersonDisappearanceTypeCode
j:MissingPersonDisappearanceTypeText
j:MissingPersonFoundDate
j:MissingPersonFoundIndicator
j:MissingPersonFoundLocation
j:MissingPersonFoundTime
j:MissingPersonID
j:MissingPersonLastSeenDate
j:MissingPersonLastSeenLocation
j:MissingPersonLastSeenTime
j:MissingPersonLastSeenWitness
j:MissingPersonStatus
j:NonStandardCode
j:NonStandardCodeDetails
j:NonStandardCodeSourceName
j:NonStandardCodeValueDescriptionText
j:NonStandardCodeVersionText
j:Numeric
j:Obligation
j:ObligationCompleteIndicator
j:ObligationComplianceIndicator
j:ObligationDueDate
j:ObligationDueTime
j:ObligationEndDate
j:ObligationEndTime
j:ObligationExemption
j:ObligationExemptionDescriptionText
j:ObligationExemptionIndicator
j:ObligationPaidDate
j:ObligationPaidTime
j:ObligationPeriodText
j:ObligationProgressDescriptionText
j:ObligationRecipient.Organization
j:ObligationRecipient.Person
j:ObligationRequirementDescriptionText
j:ObligationStartDate
j:ObligationStartTime
j:ObligationSubject.Organization
j:ObligationSubject.Person
j:ObligationTypeText
j:Offense
j:OfferedPlea
j:Organization
j:OrganizationAbbreviationText
j:OrganizationActivityText
j:OrganizationAffiliate
j:OrganizationBranchName
j:OrganizationDayContact
j:OrganizationDescriptionText
j:OrganizationDoingBusinessAsName
j:OrganizationEmergencyContact
j:OrganizationEmploymentHistory
j:OrganizationEstablishedDate
j:OrganizationEveningContact
j:OrganizationGovernmentLevelCode
j:OrganizationID
j:OrganizationIncorporatedIndicator
j:OrganizationJurisdiction
j:OrganizationLocalID
j:OrganizationLocation
j:OrganizationMember
j:OrganizationName
j:OrganizationNightContact
j:OrganizationOccupiedStructure
j:OrganizationORIID
j:OrganizationOtherID
j:OrganizationParent.Affiliate
j:OrganizationParent.Organization
j:OrganizationPrimaryContact
j:OrganizationPrincipalOfficial
j:OrganizationStatusText
j:OrganizationSubsidiary
j:OrganizationSubUnit
j:OrganizationSubunitName
j:OrganizationTaxID
j:OrganizationTerminationDate
j:OrganizationTypeCode.ncicORIAgency
j:OrganizationTypeCode.ncicTYPO
j:OrganizationTypeText
j:OrganizationUnitName
j:OrganizationUnspecifiedContact
j:Parole
j:PartialContent
j:PassagePoint
j:PassagePointDescriptionText
j:PassagePointMethodCode
j:PassagePointMethodText
j:PassagePointSecurityTypeText
j:PassagePointText
j:PassagePointTypeText
j:Percentage
j:Person
j:PersonAccentText
j:PersonAccompliceActivity
j:PersonAccompliceWithSubject
j:PersonAcquaintance
j:PersonAdoptedChild
j:PersonAdoptiveParent
j:PersonAffiliationOrganization
j:PersonAFISID
j:PersonAgeDescriptionText
j:PersonAgeMeasure
j:PersonAgeMeasure.Range
j:PersonAlias
j:PersonAlternateName
j:PersonAssignedIDDetails
j:PersonAssignmentUnit.EnforcementUnit
j:PersonAssignmentUnit.Organization
j:PersonAuthorityFigure
j:PersonBabysittee
j:PersonBabysitter
j:PersonBiologicalChild
j:PersonBiologicalParent
j:PersonBiometricDetails
j:PersonBirthDate
j:PersonBirthLocation
j:PersonBirthPlaceCode
j:PersonBloodTypeCode
j:PersonBloodTypeText
j:PersonBodyOdor
j:PersonBodyXRaysAvailableCode
j:PersonBodyXRaysAvailableText
j:PersonBuildText
j:PersonCapability
j:PersonCharge
j:PersonChild
j:PersonCircumcisionIndicator
j:PersonCitizenshipCode.fips10-4
j:PersonCitizenshipCode.iso3166Alpha2
j:PersonCitizenshipCode.iso3166Alpha3
j:PersonCitizenshipCode.iso3166Numeric
j:PersonCitizenshipText
j:PersonClothing
j:PersonCohabitant
j:PersonCommonLawSpouse
j:PersonComplexionText
j:PersonComprehendsSpokenLanguageIndicator
j:PersonConcealedFirearmPermitHolderIndicator
j:PersonDayContact
j:PersonDeathDate
j:PersonDental
j:PersonDentalCharacteristicGeneralCode
j:PersonDentalCharacteristicGeneralText
j:PersonDentalCharacteristicOtherCode
j:PersonDentalCharacteristicOtherText
j:PersonDentalCharacteristicRemovableAppliancesCode
j:PersonDentalCharacteristicRemovableAppliancesText
j:PersonDentalCharacteristicRestorationCariesCode
j:PersonDentalCharacteristicRestorationCariesText
j:PersonDentalCharacteristicStatusCode
j:PersonDentalCharacteristicStatusText
j:PersonDentalCharacteristicText
j:PersonDependentQuantity
j:PersonDescriptionText
j:PersonDetainedLocation.Location
j:PersonDetainedLocation.Structure
j:PersonDigitalImage
j:PersonDigitizedSignatureImage
j:PersonDisguiseDescriptionText
j:PersonDNA
j:PersonDomesticPartner
j:PersonDriverLicenseID
j:PersonDriversLicense
j:PersonDrivingIncident
j:PersonDrivingInsuranceCoverageTypeText
j:PersonDrivingInsuranceStatusText
j:PersonEarShape
j:PersonEducationLevelText
j:PersonEmergencyContact
j:PersonEmploymentHistory
j:PersonEthnicityCode
j:PersonEthnicityText
j:PersonEveningContact
j:PersonEyeColorCode
j:PersonEyeColorText
j:PersonEyewearDescriptionText
j:PersonFacialFeatures
j:PersonFamilyRelation
j:PersonFBIID
j:PersonFingerGeometry
j:PersonFingerprintSet
j:PersonFirearmPermitHolderIndicator
j:PersonFirearmSalesDisqualifiedCode
j:PersonFirearmSalesDisqualifiedIndicator
j:PersonFootPrint
j:PersonFosterChild
j:PersonFosterParent
j:PersonFullName
j:PersonGait
j:PersonGangAffiliation
j:PersonGeneralAppearanceDescriptionText
j:PersonGeneralLedgerID
j:PersonGivenName
j:PersonGuardian
j:PersonGuardianRecipient
j:PersonHairAppearanceText
j:PersonHairColorCode
j:PersonHairColorText
j:PersonHairFacialText
j:PersonHairLengthText
j:PersonHairStyleText
j:PersonHairTypeText
j:PersonHandednessText
j:PersonHandGeometry
j:PersonHeightDescriptionText
j:PersonHeightMeasure
j:PersonHeightMeasure.Range
j:personHeightUnitCode
j:PersonHumanResourcesID
j:PersonIDTypeCode
j:PersonInjury
j:PersonIntoxication
j:PersonIrisFeatures
j:PersonIssuedTitle.PropertyRegistration
j:PersonIssuedTitle.PropertyTitle
j:PersonJewelryDescriptionText
j:PersonKeystrokeDynamics
j:PersonLanguageCode.iso639-2b
j:PersonLanguageCode.iso639-2t
j:PersonLanguageEnglishIndicator
j:PersonLanguageText
j:PersonLearningDisabilityText
j:PersonLicenseID
j:PersonLipMovement
j:PersonLivingIndicator
j:PersonMaidenName
j:PersonMaritalStatusText
j:PersonMarriagePartner
j:PersonMedicalCondition
j:PersonMedicalDescriptionText
j:PersonMedicalDetails
j:PersonMedicalFileIndicator
j:PersonMedicationRequiredText
j:PersonMentalStateText
j:PersonMiddleName
j:PersonMilitarySummary
j:PersonModusOperandi
j:PersonMoodDescriptionText
j:PersonName
j:personNameCommentText
j:personNameInitialIndicator
j:PersonNameInitialsText
j:PersonNameSoundexText
j:personNameTypeCode
j:PersonNationalID
j:PersonNationalityCode.fips10-4
j:PersonNationalityCode.iso3166Alpha2
j:PersonNationalityCode.iso3166Alpha3
j:PersonNationalityCode.iso3166Numeric
j:PersonNationalityText
j:PersonNeighbor
j:PersonNightContact
j:PersonOrganDonatorIndicator
j:PersonOrganDonorCode
j:PersonOrganDonorText
j:PersonOtherID
j:PersonPalmPrint
j:PersonParent
j:PersonPhysicalDetails
j:PersonPhysicalDisabilityText
j:PersonPhysicalFeature
j:PersonPrefixName
j:PersonPrimaryLanguage
j:PersonPrimaryLanguageCode.iso639-2b
j:PersonPrimaryLanguageCode.iso639-2t
j:PersonPrimaryLanguageText
j:PersonPrimaryWorker
j:PersonRaceCode
j:PersonRaceText
j:PersonReadsLanguageIndicator
j:PersonReferralWorker
j:PersonRegisteredOffenderIndicator
j:PersonReligionText
j:PersonResidentCode
j:PersonResidentText
j:PersonRetina
j:PersonSaliva
j:PersonSecondaryLanguage
j:PersonSecondaryLanguageCode.iso639-2b
j:PersonSecondaryLanguageCode.iso639-2t
j:PersonSecondaryLanguageText
j:PersonSemen
j:PersonSexCode
j:PersonSexText
j:PersonSexualOrientationText
j:PersonSkinToneCode
j:PersonSkinToneText
j:PersonSocialDetails
j:PersonSocialFriend
j:PersonSpeaksLanguageIndicator
j:PersonSpeechDescriptionText
j:PersonSpeechPattern
j:PersonSpouse
j:PersonSSNID
j:PersonStateID
j:PersonStranger
j:PersonSuffixName
j:PersonSurName
j:PersonTaxID
j:PersonTemporaryAssignmentUnit
j:PersonThermalFaceImage
j:PersonThermalHandImage
j:PersonThermalImage
j:PersonTooth
j:PersonToothIDCode
j:PersonToothIDText
j:PersonUnspecifiedContact
j:PersonUrine
j:PersonUSCitizenIndicator
j:PersonVeinPattern
j:PersonVendorID
j:PersonVisionPrescriptionText
j:PersonWasCommonLawSpouse
j:PersonWasDomesticPartner
j:PersonWasMarriedTo
j:PersonWasSpouse
j:PersonWeightDescriptionText
j:PersonWeightMeasure
j:PersonWeightMeasure.Range
j:personWeightUnitCode
j:PersonWorkContact
j:PersonWorkLocation.Location
j:PersonWorkLocation.Structure
j:PersonWritesLanguageIndicator
j:PersonXRayImage
j:PhysicalFeatureCategoryText
j:PhysicalFeatureDescriptionText
j:PhysicalFeatureImage
j:PhysicalFeatureLocationText
j:PhysicalFeatureTypeCode
j:PhysicalFeatureTypeText
j:Plea
j:PleaDescriptionText
j:PleaGuiltyIndicator
j:PleaNegotiatedIndicator
j:PleaNoContestIndicator
j:PleaRecommendationText
j:PleaTypeCode
j:PreviousSentence
j:PrimaryContactInformation
j:probabilityNumeric
j:Probation
j:Program
j:ProgramAction
j:ProgramAdministrator.Organization
j:ProgramAdministrator.Person
j:ProgramCapacityText
j:ProgramCondition
j:ProgramFacility
j:ProgramPubliclyRunIndicator
j:ProgramPurposeText
j:ProgramReferral
j:ProgramRelease
j:ProgramResidentialIndicator
j:ProgramSubject
j:ProgramSupervisedIndicator
j:ProgramSupervisor.Organization
j:ProgramSupervisor.Person
j:Progress
j:ProgressComplianceIndicator
j:ProgressComplianceText
j:ProgressPaymentAmountText
j:ProgressTimeAmountText
j:Property
j:PropertyActionText
j:PropertyAgeMeasure
j:PropertyAssignedIDDetails
j:PropertyBarCodeID
j:PropertyBinary
j:PropertyBrandName
j:PropertyCategoryCode.ncicTYP
j:PropertyCategoryCode.nibrsPropertyCategory
j:PropertyCategoryText
j:PropertyColorDescriptionText
j:PropertyConditionText
j:PropertyContainedInStructure
j:PropertyCurrentResaleValue
j:PropertyDealerID
j:PropertyDescriptionText
j:PropertyDetail
j:PropertyDetailCode
j:PropertyDetailDescription
j:PropertyDetailText
j:PropertyDisposition
j:PropertyDispositionCode
j:PropertyDispositionLocation
j:PropertyDispositionProperty
j:PropertyFederalID
j:PropertyHeightMeasure
j:PropertyHolding
j:PropertyHoldingOrganization
j:PropertyImage
j:PropertyLengthMeasure
j:PropertyLocation
j:PropertyMakeName
j:PropertyMissingValue
j:PropertyModelName
j:PropertyMovingOrganization
j:PropertyNCICID
j:PropertyOtherID
j:PropertyOtherValue
j:PropertyOwner.Organization
j:PropertyOwner.Person
j:PropertyOwnerAppliedID
j:PropertyOwnerPurchasedValue
j:PropertyPhysicalDetails
j:PropertyPossessionDescriptionText
j:PropertyPossessor.Organization
j:PropertyPossessor.Person
j:PropertyQuantity
j:PropertyReceiptID
j:PropertyRecoveredValue
j:PropertyRegistration
j:PropertySeizedLocation
j:PropertySeizer.Organization
j:PropertySeizer.Person
j:PropertySeizure
j:PropertySeizureDisposition
j:PropertySeizureMethodText
j:PropertySeizureOwningPerson
j:PropertySeizurePossessingPerson
j:PropertySeizureProperty
j:PropertySeizurePropertyHoldingOrganization
j:PropertySeizureReleaseConditionText
j:PropertySeizureSeizingEnforcementOfficial
j:PropertySeizureWarrant
j:PropertySerialID
j:PropertySizeDescriptionText
j:PropertyStateID
j:PropertyStatus
j:PropertyStyleText
j:PropertyTitle
j:PropertyTitleHolder.Organization
j:PropertyTitleHolder.Person
j:PropertyTotalDamageValue
j:PropertyTransaction
j:PropertyTransactionBuyer.Organization
j:PropertyTransactionBuyer.Person
j:PropertyTransactionPriceValue
j:PropertyTransactionSeller.Organization
j:PropertyTransactionSeller.Person
j:PropertyTypeCode
j:PropertyTypeCode.nibrsArresteeWeapon
j:PropertyTypeText
j:PropertyUsageText
j:PropertyValue
j:PropertyValueAmount
j:PropertyValueAssigningMethodText
j:PropertyValueAssigningOrganization
j:PropertyValueAssigningPerson
j:PropertyValueDate
j:PropertyValueDescriptionText
j:PropertyValueDetails
j:PropertyValueTaxIncludedIndicator
j:PropertyVisibleID
j:PropertyWeaponIndicator
j:PropertyWeaponUsageIndicator
j:PropertyWeaponUseText
j:PropertyWeightMeasure
j:PropertyWidthMeasure
j:PropertyYearDate
j:ProsecutionCharge
j:ProtectionOrder
j:ProtectionOrderConditionCode
j:ProtectionOrderRestrictedPerson
j:Quantity
j:quantityUnitText
j:RangeMaximumMeasure
j:RangeMeasure
j:RangeMinimumMeasure
j:Rate
j:rateUnitText
j:RealEstate
j:RealEstateAcreageText
j:RealEstateAttachedStructure
j:RealEstateBoundaryDescriptionText
j:RecurringObligation
j:Referral
j:ReferralActivity
j:ReferralCourtOrder
j:ReferralDesignation.Organization
j:ReferralDesignation.Person
j:ReferralIssuer.Organization
j:ReferralIssuer.Person
j:ReferralMandatoryIndicator
j:ReferralProperty
j:ReferralSubject
j:ReferralSupervisor.Organization
j:ReferralSupervisor.Person
j:RegisterAction
j:RegisterActionDate
j:RegisterActionDescriptionText
j:RegisterActionJudge
j:RegisterActionTime
j:RegisterActionTitle
j:RegisteredOffender
j:RegisteredOffenderConviction
j:RegisteredOffenderCourtOrder
j:RegisteredOffenderDescription
j:RegisteredOffenderEndDate
j:RegisteredOffenderEntryDate
j:RegisteredOffenderID
j:RegisteredOffenderReportingCriteriaText
j:RegisteredOffenderReportingProfessionName
j:RegisteredOffenderStartDate
j:RegisteredOffenderTypeText
j:RegisteredSexOffender
j:RegisterOfActions
j:RegistrationAuthorityName
j:RegistrationDuplicateQuantity
j:RegistrationEffectiveDate
j:RegistrationExpirationDate
j:RegistrationFee
j:RegistrationID
j:RegistrationJurisdictionCode.ANSID20JurisdictionAuthority
j:RegistrationJurisdictionCode.CanadianProvince
j:RegistrationJurisdictionCode.fips10-4International
j:RegistrationJurisdictionCode.fips5-2Alpha
j:RegistrationJurisdictionCode.fips5-2Numeric
j:RegistrationJurisdictionCode.ncicLIS
j:RegistrationJurisdictionCode.ncicLSTA
j:RegistrationJurisdictionCode.ncicRES
j:RegistrationJurisdictionCode.USPostalService
j:RegistrationJurisdictionName
j:RegistrationOutsideJurisdictionIndicator
j:RegistrationParty.Organization
j:RegistrationParty.Person
j:RegistrationProperty
j:RegistrationStatus
j:RehabilitationProgram
j:RelativeLocation
j:RelativeLocationDescriptionText
j:RelativeLocationDirectionCode
j:RelativeLocationDirectionText
j:RelativeLocationDistanceText
j:RelativeLocationHeadingValue
j:RelativeLocationReferencePoint
j:Release
j:ReleaseFromLocation
j:ReleaseIssuer.Organization
j:ReleaseIssuer.Person
j:ReleaseProperty
j:ReleaseRecipient.Organization
j:ReleaseRecipient.Person
j:ReleaseSubject
j:ReleaseSupervisor.Organization
j:ReleaseSupervisor.Person
j:ReleaseToLocation
j:reliabilityNumeric
j:reportedDate
j:reportedTime
j:reportingOrganizationText
j:reportingPersonRoleText
j:reportingPersonText
j:Residence
j:ResidenceDescriptionText
j:ResidenceEndDate
j:ResidenceOccupancyTypeText
j:ResidencePaymentAmount
j:ResidencePaymentPeriodText
j:ResidenceStartDate
j:ResidenceTypeText
j:ResidentialStructure
j:RiskReductionFacility
j:RiskReductionProgram
j:SameAs
j:Sanction
j:SanctionAdultSentenceIndicator
j:SanctionCreditedObligation
j:SanctionCreditedTerm
j:SanctionDisciplinaryAction
j:SanctionFrequencyText
j:SanctionGroupingText
j:SanctionIssuingAgency
j:SanctionJurisdictionalAgency
j:SanctionProgress
j:SanctionRelatedChargeDispositionText
j:SanctionRelatedSanctionID
j:SanctionSentenceDefinitionIndicator
j:SanctionSetDate
j:SanctionSetObligation
j:SanctionSetTerm
j:SanctionStayedObligation
j:SanctionStayedTerm
j:SanctionSuspendedObligation
j:SanctionSuspendedTerm
j:SanctionTypeText
j:ScheduleActivityText
j:ScheduleDate
j:ScheduleDay
j:ScheduleDayEndTime
j:ScheduleDayStartTime
j:SchedulePerson
j:SearchWarrant
j:Security
j:SecurityClassificationCurrent
j:SecurityClassificationDowngrade
j:SecurityClassificationInitial
j:SecurityClassificationUpgrade
j:SecurityCollectionEndDate
j:SecurityCollectionStartDate
j:SecurityControlText
j:SecurityDateSeriesCode
j:SecurityDateSeriesText
j:SecurityDeclassification
j:SecurityDenominationCode
j:SecurityDenominationText
j:SecurityDisseminationText
j:SecurityFGICode
j:SecurityFGIText
j:SecurityForeignReleasabilityText
j:SecurityIssuer.Organization
j:SecurityIssuer.Person
j:SecurityLevelCode
j:SecurityLevelText
j:SecurityMetadata
j:SecurityNonICMarkingsText
j:SecurityTypeCode
j:sensitivityText
j:Sentence
j:SentenceAggravatedIndicator
j:SentenceCharge
j:SentenceCondition
j:SentenceConfinementCreditDayQuantity
j:SentenceConfinementCreditIndicator
j:SentenceDeferredIndicator
j:SentenceDeferredTerm
j:SentenceDescriptionText
j:SentenceDetails
j:SentenceGroupingText
j:SentenceIssuer.Organization
j:SentenceIssuer.Person
j:SentenceModification
j:SentenceModificationAggravatedIndicator
j:SentenceModificationCharge
j:SentenceModificationConfinementCreditDayText
j:SentenceModificationConfinementCreditIndicator
j:SentenceModificationDismissalIndicator
j:SentenceModificationDismissalRemainingCase
j:SentenceModificationDismissalRemainingQuantity
j:SentenceModificationMitigatedIndicator
j:SentenceModificationOriginalTerm
j:SentenceModificationParoleIndicator
j:SentenceModificationParoleTerm
j:SentenceModificationProbation
j:SentenceModificationProbationIndicator
j:SentenceModificationRestitutionIndicator
j:SentenceModificationSuspendedIndicator
j:SentenceModificationSuspendedTerm
j:SentenceRegisterSexOffenderIndicator
j:SentenceSeverityLevel
j:SentenceSubject
j:SentenceSuspendedIndicator
j:SentenceSuspendedTerm
j:SentenceTerm
j:SentencingGuideline
j:SentencingGuidelineChargeSeverityLevelText
j:SentencingGuidelineDepartureReasonText
j:SentencingGuidelineDepartureTypeText
j:SentencingGuidelineMonthsMaximumText
j:SentencingGuidelineMonthsMinimumText
j:SentencingGuidelineRecommendationMonthsText
j:sequenceID
j:ServiceCall
j:ServiceCallArrivedDate
j:ServiceCallArrivedTime
j:ServiceCallAssignedUnit
j:ServiceCallAssistingUnit
j:ServiceCallClearanceText
j:ServiceCallClearedDate
j:ServiceCallClearedTime
j:ServiceCallDispatchedDate
j:ServiceCallDispatchedOfficial
j:ServiceCallDispatchedTime
j:ServiceCallDispatcher
j:ServiceCallMechanismText
j:ServiceCallOperator
j:ServiceCallOriginator
j:ServiceCallResponseLocation
j:ServiceCallResponsePerson
j:SeverityLevel
j:SeverityLevelAssignedDate
j:SeverityLevelAssignedJudge
j:SeverityLevelCriminalHistoryScoreText
j:SeverityLevelDescriptionText
j:SeverityLevelID
j:SeverityLevelIssuingAgency
j:sourceIDText
j:sourceText
j:speedRateUnitCode
j:Status
j:StatusDate
j:StatusDescriptionText
j:StatusIssuerID
j:StatusIssuerText
j:StatusText
j:StatusTime
j:Statute
j:StatuteCodeID
j:StatuteCodeSectionID
j:StatuteCommentText
j:StatuteDescriptionText
j:StatuteEnactmentDate
j:StatuteJurisdiction
j:StatuteKeywordText
j:StatuteLevelText
j:StatuteOffenseCode
j:StatuteOffenseCode.Minnesota
j:StatuteOffenseEnhancibleIndicator
j:StatuteOffenseID
j:StatuteRepealDate
j:StatuteStatus
j:StatuteText
j:StatuteTypeCode
j:StatuteTypeText
j:Street
j:StreetExtensionText
j:StreetFullText
j:StreetName
j:StreetNumberText
j:StreetPostdirectionalText
j:StreetPredirectionalText
j:StreetTypeText
j:Structure
j:StructureCommercialIndicator
j:StructureContainsProperty
j:StructureGarageForVehicle
j:StructureLocation
j:StructureOccupant.Organization
j:StructureOccupant.Person
j:StructureOrganization
j:StructureResident
j:StructureWorker
j:SubExhibit
j:Subject
j:SubjectArmedWeapon
j:SubjectCautionInformationCaveat
j:SubjectCautionInformationCode
j:SubjectCriminalOrganizationInvolvementCode
j:SubjectCriminalTraitDetails
j:SubjectDetainmentLocation
j:SubjectDisciplinaryAction
j:SubjectID
j:SubjectInvolvementCriminalOrganization
j:SubjectInvolvementPerson
j:SubjectMultiSourceOffenderCode
j:SubjectMultiSourceOffenderText
j:SubjectOffenderNoticeCaveat
j:SubjectOffenderNoticeText
j:SubjectStatus
j:SubjectSupervision
j:SubjectWarrantTypeDescriptionText
j:Submission
j:SubmissionDocument
j:SubmissionFee
j:SubmissionReceivedDate
j:SubmissionReceivedTime
j:SubmissionReceiver.Organization
j:SubmissionReceiver.Person
j:SubmissionSubmittedDate
j:SubmissionSubmittedTime
j:SubmissionSubmitter.Organization
j:SubmissionSubmitter.Person
j:Summons
j:SuperObject
j:Supervision
j:SupervisionAgency
j:SupervisionAreaID
j:SupervisionAssessment
j:SupervisionAssignedTerm
j:SupervisionBedID
j:SupervisionBoardActionDocument
j:SupervisionCautionText
j:SupervisionCellID
j:SupervisionClassificationDate
j:SupervisionCondition
j:SupervisionConditionalRelease
j:SupervisionCurrentIndicator
j:SupervisionCustodyStatus
j:SupervisionCustodyTransfer
j:SupervisionDisciplinaryAction
j:SupervisionFacility
j:SupervisionFee
j:SupervisionFelonyOffenseIndicator
j:SupervisionGoodDaysCreditText
j:SupervisionIntensiveIndicator
j:SupervisionIsolationIndicator
j:SupervisionJurisdiction
j:SupervisionLevelCode
j:SupervisionLevelText
j:SupervisionMandatoryIndicator
j:SupervisionModifiedTerm
j:SupervisionOfficial
j:SupervisionOtherLocation
j:SupervisionReinstatementDate
j:SupervisionRelease
j:SupervisionRestriction
j:SupervisionRestrictionBehaviorText
j:SupervisionRestrictionCode
j:SupervisionRestrictionLocation
j:SupervisionRestrictionPerson
j:SupervisionSelfImposedIndicator
j:SupervisionServedTerm
j:SupervisionSubject
j:SupervisionSubjectResponsibilityText
j:SupervisionSubjectStatus
j:SupervisionViolationText
j:SupervisionVisitation
j:Suspect
j:Target
j:TargetDescriptionText
j:TargetLocation
j:TargetName
j:TargetOrganization
j:TargetPerson
j:TargetProperty
j:TargetReasonText
j:TargetTypeText
j:TelephoneAreaCodeID
j:TelephoneCityCodeID
j:TelephoneCountryCodeID
j:TelephoneExchangeID
j:TelephoneNumber
j:TelephoneNumberCommentText
j:TelephoneNumberFullID
j:TelephoneSubscriberID
j:TelephoneSuffixID
j:Term
j:TermDuration
j:TermLifeIndicator
j:TermMaximumDuration
j:TermMinimumDuration
j:Text
j:TimeMeasure
j:TimeObligation
j:TimeObligationDueDuration
j:TimeObligationPaidDuration
j:TimeObligationTotalDuration
j:timeUnitCode
j:TitleDuplicateQuantity
j:TitleID
j:TitleIssueDate
j:TitleIssuingAuthorityName
j:TitleLienIndicator
j:TitleParty.Organization
j:TitleParty.Person
j:TitleProperty
j:TitleReplacesTitle
j:TitleStatus
j:TitleStatusCode
j:TitleStatusText
j:TitleTypeText
j:toleranceNumeric
j:TowingCompany
j:UpperBound
j:UTMCoordinate
j:UTMCoordinateID
j:UTMDatumID
j:UTMEastingValue
j:UTMGridZoneID
j:UTMGridZoneSquareID
j:UTMNorthingValue
j:Vehicle
j:VehicleAxleQuantity
j:VehicleBasics
j:VehicleBrand
j:VehicleBrandCode
j:VehicleBrandDamagePercentageTypeCode
j:VehicleBrandDamagePercentageTypeText
j:VehicleBrandDate
j:VehicleBrander
j:VehicleBrandSalvagePercentage
j:VehicleBrandText
j:VehicleBrandVehicleDispositionCode
j:VehicleBrandVehicleDispositionText
j:VehicleBrandVehicleSourceName
j:VehicleCargoText
j:VehicleCMVIndicator
j:VehicleColorInteriorText
j:VehicleColorPrimaryCode
j:VehicleColorPrimaryText
j:VehicleColorSecondaryCode
j:VehicleColorSecondaryText
j:VehicleCurrentWeightMeasure
j:VehicleDoorQuantity
j:VehicleEmissionInspection
j:VehicleEmissionInspectionQuantity
j:VehicleEngine
j:VehicleEngineCylinderQuantity
j:VehicleEngineDisplacementMeasure
j:vehicleEngineDisplacementUnitCode
j:VehicleEngineHorsepowerQuantity
j:VehicleEngineID
j:VehicleEnginePowerDisplacementText
j:VehicleEngineQuantity
j:VehicleFirstSoldYearDate
j:VehicleFuelTypeCode
j:VehicleFuelTypeText
j:VehicleGarage
j:VehicleGarageIndicator
j:VehicleGrossLadenSumWeightMeasure
j:VehicleGrossLadenUnitWeightMeasure
j:VehicleID
j:VehicleInspection
j:VehicleInspectionAddress
j:VehicleInspectionEmissionCertificationID
j:VehicleInspectionEmissionPassIndicator
j:VehicleInspectionInspectorID
j:VehicleInspectionJurisdictionAuthorityCode
j:VehicleInspectionJurisdictionAuthorityText
j:VehicleInspectionSafetyPassIndicator
j:VehicleInspectionSmogCertificateCode
j:VehicleInspectionStationID
j:VehicleInspectionTestTypeText
j:VehicleInvoiceDate
j:VehicleInvoiceID
j:VehicleLeaseIndicator
j:VehicleLicensePlateID
j:VehicleMakeCode
j:VehicleMaximumLoadWeightMeasure
j:VehicleModelCode
j:VehicleModelCodeText
j:VehicleModelYearDate
j:VehicleMSRPAmount
j:VehicleOdometerReadingMeasure
j:vehicleOdometerReadingUnitCode
j:VehicleOwnershipTypeText
j:VehiclePaperMCOIssuedIndicator
j:VehiclePart
j:VehiclePart.Detailed
j:VehiclePartBrandCode
j:VehiclePartBrandName
j:VehiclePartCategoryCode
j:VehiclePartCategoryText
j:VehiclePartDescriptionText
j:VehiclePartID
j:VehiclePassengerSafeQuantity
j:VehicleRegistration
j:VehicleRegistrationDecal
j:VehicleRegistrationGrossWeightMeasure
j:VehicleRegistrationLocation
j:VehicleRegistrationPermenantIndicator
j:VehicleRegistrationPlateBackgroundText
j:VehicleRegistrationPlateColorCode
j:VehicleRegistrationPlateColorText
j:VehicleRegistrationPlateID
j:VehicleRegistrationPlateTypeCode
j:VehicleRegistrationPlateTypeText
j:VehicleRegistrationRoadIndicator
j:VehicleRegistrationStatus
j:VehicleRegistrationStatus.Detailed
j:VehicleRegistrationStatusCode
j:VehicleRegistrationStatusDetailCode
j:VehicleRegistrationStatusDetailText
j:VehicleRentalIndicator
j:VehicleSafetyInspection
j:VehicleSalesTaxPercentage
j:VehicleSeatingQuantity
j:VehicleShipDate
j:VehicleStyleCode
j:VehicleTaxableAmount
j:VehicleTitle
j:VehicleTitleDocumentTypeCode
j:VehicleTitlePurchaseDate
j:VehicleTitlePurchasePriceAmount
j:VehicleTitleSalesTaxAmount
j:VehicleTitleSalesTaxPercentage
j:VehicleTitleTaxableValue
j:VehicleTowedIndicator
j:VehicleTower
j:VehicleTransmissionTypeCode
j:VehicleTransmissionTypeText
j:VehicleUnladenWeightMeasure
j:VehicleUseCode
j:VehicleUseText
j:VehicleVINAText
j:VehicleWantedIndicator
j:Verdict
j:VerdictDate
j:VerdictDescriptionText
j:VerdictDispositionDate
j:VerdictDispositionName
j:VerdictIssuingCourt
j:VerdictIssuingJudge
j:VerdictIssuingJudgeIndicator
j:VerdictSubject
j:Victim.Organization
j:Victim.Person
j:Victim.Property
j:VictimAffectedProperty
j:VictimDispositionText
j:VictimEntity
j:VictimID
j:VictimInjury
j:VictimMedicalTreatmentRequiredIndicator
j:VictimOffenseChargeCode
j:VictimOffenseChargeText
j:VictimSeeksProsecutionIndicator
j:VictimTypeCode
j:VictimTypeText
j:Violation
j:Visitation
j:VisitationPurposeText
j:VisitationRestrictedAccessPerson
j:VisitationRestrictedAccessReasonText
j:VisitationSupervisingOfficial.Enforcement
j:VisitationSupervisingOfficial.Judicial
j:VisitationVisitor
j:VisitationVisitorRelationshipText
j:Warrant
j:WarrantAppearanceBail
j:WarrantAppearanceBailForfeitText
j:WarrantExtraditionLimitationCode
j:WarrantExtraditionLimitationText
j:WarrantExtraditionStateName
j:WarrantFurtherProcessingText
j:WarrantLevelText
j:WarrantProbableCauseText
j:WeightMeasure
j:weightUnitCode
j:Witness
j:WitnessAccountDescriptionText
j:WitnessDate
j:WitnessID
j:WitnessLocationDescriptionText
j:WitnessReportVerifiedIndicator
j:WitnessSpecialConditionText
j:WitnessTime
j:WitnessWillTestifyIndicator

Types:

ansi_d20:AccidentSeverityCodeType
ansi_d20:BrandCodeType
ansi_d20:BrandDamagePercentageTypeCodeType
ansi_d20:BranderTypeCodeType
ansi_d20:BrandVehicleDispositionCodeType
ansi_d20:CMVCodeType
ansi_d20:CourtTypeCodeType
ansi_d20:DecalPeriodCodeType
ansi_d20:DriverLicenseClassCodeType
ansi_d20:DriverLicenseWithdrawalActionCodeType
ansi_d20:DriverLicenseWithdrawalBasisCodeType
ansi_d20:DriverLicenseWithdrawalDueProcessStatusCodeType
ansi_d20:DriverLicenseWithdrawalEligibilityCodeType
ansi_d20:DriverLicenseWithdrawalExtentCodeType
ansi_d20:DrivingEndorsementCodeType
ansi_d20:DrivingInsuranceStatusCodeType
ansi_d20:DrivingOffenseCodeType
ansi_d20:DrivingRestrictionCodeType
ansi_d20:DrivingStatusCodeType
ansi_d20:HazMatCodeType
ansi_d20:InsuranceCoverageTypeCodeType
ansi_d20:JurisdictionAuthorityCodeType
ansi_d20:LienReleaseReasonCodeType
ansi_d20:PassFailCodeType
ansi_d20:PersonOrganDonorCodeType
ansi_d20:RegistrationPlateColorCodeType
ansi_d20:RegistrationStatusCodeType
ansi_d20:RegistrationStatusDetailCodeType
ansi_d20:SmogCertificateCodeType
ansi_d20:TitleStatusCodeType
ansi_d20:VehicleEngineDisplacementUnitCodeType
ansi_d20:VehicleFuelTypeCodeType
ansi_d20:VehicleOdometerReadingUnitCodeType
ansi_d20:VehicleTitleDocumentTypeCodeType
ansi_d20:VehicleTransmissionTypeCodeType
ansi_d20:VehicleUseCodeType
can:CanadianProvinceCodeType
cap:AlertCertaintyCodeType
cap:AlertEventCategoryCodeType
cap:AlertSeverityCodeType
cap:AlertUrgencyCodeType
census:OccupationCodeType
census:OccupationTypeCodeType
dod:SecurityLevelCodeType
dod_exec-12958:SecurityClassificationCodeType
dod_jcs-pub2.0:DocumentIntelligenceTypeCodeType
fips_10-4:CountryCodeType
fips_10-4:InternationalStateCodeType
fips_5-2:USStateCodeType
fips_5-2:USStateNumericCodeType
fips_6-4:USCountyCodeType
iso_3166:CountryAlpha2CodeType
iso_3166:CountryAlpha3CodeType
iso_3166:CountryNumericCodeType
iso_4217:CurrencyCodeType
iso_639-2b:LanguageCodeType
iso_639-2t:LanguageCodeType
j-ansi_d20:AccidentSeverityCodeType
j-ansi_d20:BrandCodeType
j-ansi_d20:BrandDamagePercentageTypeCodeType
j-ansi_d20:BranderTypeCodeType
j-ansi_d20:BrandVehicleDispositionCodeType
j-ansi_d20:CMVCodeType
j-ansi_d20:CourtTypeCodeType
j-ansi_d20:DecalPeriodCodeType
j-ansi_d20:DriverLicenseClassCodeType
j-ansi_d20:DriverLicenseWithdrawalActionCodeType
j-ansi_d20:DriverLicenseWithdrawalBasisCodeType
j-ansi_d20:DriverLicenseWithdrawalDueProcessStatusCodeType
j-ansi_d20:DriverLicenseWithdrawalEligibilityCodeType
j-ansi_d20:DriverLicenseWithdrawalExtentCodeType
j-ansi_d20:DrivingEndorsementCodeType
j-ansi_d20:DrivingInsuranceStatusCodeType
j-ansi_d20:DrivingOffenseCodeType
j-ansi_d20:DrivingRestrictionCodeType
j-ansi_d20:DrivingStatusCodeType
j-ansi_d20:HazMatCodeType
j-ansi_d20:InsuranceCoverageTypeCodeType
j-ansi_d20:JurisdictionAuthorityCodeType
j-ansi_d20:LienReleaseReasonCodeType
j-ansi_d20:PassFailCodeType
j-ansi_d20:PersonOrganDonorCodeType
j-ansi_d20:RegistrationPlateColorCodeType
j-ansi_d20:RegistrationStatusCodeType
j-ansi_d20:RegistrationStatusDetailCodeType
j-ansi_d20:SmogCertificateCodeType
j-ansi_d20:TitleStatusCodeType
j-ansi_d20:VehicleEngineDisplacementUnitCodeType
j-ansi_d20:VehicleFuelTypeCodeType
j-ansi_d20:VehicleOdometerReadingUnitCodeType
j-ansi_d20:VehicleTitleDocumentTypeCodeType
j-ansi_d20:VehicleTransmissionTypeCodeType
j-ansi_d20:VehicleUseCodeType
j-can:CanadianProvinceCodeType
j-cap:AlertCertaintyCodeType
j-cap:AlertEventCategoryCodeType
j-cap:AlertSeverityCodeType
j-cap:AlertUrgencyCodeType
j-census:OccupationCodeType
j-census:OccupationTypeCodeType
j-dod:SecurityLevelCodeType
j-dod_exec-12958:SecurityClassificationCodeType
j-dod_jcs-pub2.0:DocumentIntelligenceTypeCodeType
j-fips_10-4:CountryCodeType
j-fips_10-4:InternationalStateCodeType
j-fips_5-2:USStateCodeType
j-fips_5-2:USStateNumericCodeType
j-fips_6-4:USCountyCodeType
j-iso_3166:CountryAlpha2CodeType
j-iso_3166:CountryAlpha3CodeType
j-iso_3166:CountryNumericCodeType
j-iso_639-2b:LanguageCodeType
j-iso_639-2t:LanguageCodeType
j-lasd:DNACollectionStatusCodeType
j-lasd:IncidentTypeCodeType
j-mn_off:OffenseCodeType
j-mn_off:OffenseLevelCodeType
j-mn_off:StatuteTypeCodeType
j-ncic:BCOType
j-ncic:BLTType
j-ncic:BMAType
j-ncic:BRAType
j-ncic:BTMAType
j-ncic:BTYType
j-ncic:BXRType
j-ncic:CALType
j-ncic:CATType
j-ncic:CMCType
j-ncic:DCHGeneralType
j-ncic:DCHOtherType
j-ncic:DCHRemovableAppliancesType
j-ncic:DCHRestorationCariesType
j-ncic:DCHStatusType
j-ncic:DENType
j-ncic:ECRType
j-ncic:EPDType
j-ncic:EXLType
j-ncic:EYEType
j-ncic:FPCFingerType
j-ncic:FPCPatternType
j-ncic:FPCType
j-ncic:GUNColorFinishType
j-ncic:HAIType
j-ncic:HSPType
j-ncic:HULType
j-ncic:IFSType
j-ncic:IMTType
j-ncic:JWTType
j-ncic:LISType
j-ncic:LITType
j-ncic:LSTAType
j-ncic:MAKType
j-ncic:MNPType
j-ncic:MNUType
j-ncic:MPCType
j-ncic:OFFType
j-ncic:ORIAgencyType
j-ncic:ORIGovernmentLevelType
j-ncic:PCOType
j-ncic:POBType
j-ncic:PROType
j-ncic:RACType
j-ncic:RESType
j-ncic:SDTType
j-ncic:SEXType
j-ncic:SFIType
j-ncic:SKNType
j-ncic:SMTType
j-ncic:ToothIDCodeType
j-ncic:TYPArticleCategoryType
j-ncic:TYPAType
j-ncic:TYPDescriptionType
j-ncic:TYPOType
j-ncic:TYPSType
j-ncic:TYPType
j-ncic:VCOType
j-ncic:VMAType
j-ncic:VMOType
j-ncic:VSTType
j-nibrs:AggravatedAssaultHomicideFactorsCodeType
j-nibrs:ArresteeWeaponCodeType
j-nibrs:ArrestTypeCodeType
j-nibrs:CriminalActivityTypeCodeType
j-nibrs:DrugMeasurementCodeType
j-nibrs:DrugTypeCodeType
j-nibrs:EthnicityCodeType
j-nibrs:ForceTypeCodeType
j-nibrs:IncidentBiasMotivationCodeType
j-nibrs:IncidentExceptionalClearanceCodeType
j-nibrs:IncidentFactorCodeType
j-nibrs:InjuryTypeCodeType
j-nibrs:JustifiableHomicideFactorsCodeType
j-nibrs:LEOKAActivityTypeCodeType
j-nibrs:LEOKAOfficerAssignmentTypeCodeType
j-nibrs:LocationTypeCodeType
j-nibrs:MethodOfEntryType
j-nibrs:MultipleArresteeSegmentsCodeType
j-nibrs:PropertyCategoryCodeType
j-nibrs:PropertyLossCodeType
j-nibrs:ResidentCodeType
j-nibrs:VictimTypeCodeType
j-nonauth:ImagePoseCodeType
j-nonauth:PersonNameTypeCodeType
j-ucr:OffenseCodeType
j-usps:USStateCodeType
j-ut_offender:CaseDispositionDecisionTypeCodeType
j-ut_offender:MilitaryDischargeTypeCodeType
j-ut_offender:PleaTypeCodeType
j-ut_offender:SupervisionLevelCodeType
j-ut_offender:SupervisionRestrictionCodeType
j-xsd:base64Binary
j-xsd:boolean
j-xsd:date
j-xsd:decimal
j-xsd:duration
j-xsd:gMonth
j-xsd:gYear
j-xsd:hexBinary
j-xsd:integer
j-xsd:nonNegativeInteger
j-xsd:string
j-xsd:time
j-xsd:token
j:ActivityType
j:AddressComponentType
j:AddressGridType
j:AddressType
j:AffiliateType
j:AgeMeasureType
j:AgeUnitCodeType
j:AirCraftType
j:AlertType
j:AmountType
j:AngularMinuteType
j:AngularSecondType
j:AppellateCaseDecisionType
j:AppellateCaseNoticeType
j:AppellateCaseType
j:ApplicationNameType
j:AreaType
j:ArrestType
j:AssessmentType
j:BailType
j:BinaryType
j:BiometricType
j:BoatType
j:BondType
j:BookingTelephoneCallType
j:BookingType
j:BuildingType
j:CapabilityType
j:CaseClassificationType
j:CaseConvictionReportingRequirementsType
j:CaseDetailsType
j:CaseDispositionDecisionType
j:CaseDispositionType
j:CaseOfficialType
j:CaseParticipantsType
j:CaseType
j:ChargeClassificationType
j:ChargeDispositionType
j:ChargeEnhancingFactorType
j:ChargeReportingType
j:ChargeType
j:CircularRegionType
j:CitationType
j:ClassificationType
j:ClothingType
j:CommercialVehicleType
j:ConditionalReleaseType
j:ConditionGroupType
j:ConditionType
j:ContactInformationType
j:ContactRadioType
j:ConvictionType
j:CourtActivityType
j:CourtAppearanceType
j:CourtEventType
j:CourtOrderType
j:CourtType
j:CriminalOrganizationType
j:CriminalTraitDetailsType
j:CrossStreetType
j:CustodyTransferType
j:DecalType
j:DirectionCodeType
j:DisciplinaryActionType
j:DispositionType
j:DNALocusType
j:DNAType
j:DocumentControlMetadataType
j:DocumentDescriptiveMetadataType
j:DocumentType
j:DriverAuthorizationType
j:DriverConvictionType
j:DriverHistorySummaryType
j:DriverLicensePermitType
j:DriverLicenseType
j:DriverLicenseWithdrawalType
j:DrivingIncidentType
j:DrivingJurisdictionAuthorityIDType
j:DrivingRestrictionType
j:DrugMeasurementType
j:DrugType
j:ElevationType
j:ElevationUnitCodeType
j:EmploymentType
j:EnforcementOfficialType
j:EnforcementUnitType
j:EnginePowerDisplacementType
j:EventType
j:EvidenceType
j:ExhibitType
j:FacilityType
j:FinancialObligationType
j:FingerprintSetType
j:FingerprintType
j:FirearmType
j:ForceType
j:GeographicCoordinateType
j:HighwayType
j:IDType
j:ImageType
j:IncidentCategoryType
j:IncidentFactorType
j:IncidentFormType
j:IncidentResponseType
j:IncidentType
j:InjuryType
j:InsuranceType
j:IntellecualPropertyType
j:IntoxicationType
j:JewelryStoneType
j:JewelryType
j:JudgePanelType
j:JudicialOfficialBarMembershipType
j:JudicialOfficialType
j:JurisdictionType
j:JurorType
j:KitType
j:LatitudeCoordinateType
j:LatitudeDegreeType
j:LengthMeasureType
j:LesseeType
j:LessorType
j:LienHolderType
j:LienType
j:LocaleType
j:LocationType
j:LongitudeCoordinateType
j:LongitudeDegreeType
j:MapLocationType
j:MeasureType
j:MedicalConditionType
j:MetadataFieldType
j:MGRSCoordinateType
j:MilitarySummaryType
j:MissingPersonType
j:NonStandardCodeType
j:NumericType
j:ObligationExemptionType
j:ObligationType
j:OdometerReadingMeasureType
j:OrganizationType
j:PartialContentType
j:PassagePointType
j:PercentageType
j:PersonAssignedIDDetailsType
j:PersonBiometricDetailsType
j:PersonDentalType
j:PersonHeightMeasureType
j:PersonHeightUnitCodeType
j:PersonLanguageType
j:PersonMedicalDetailsType
j:PersonNameTextType
j:PersonNameType
j:PersonOtherIDType
j:PersonPhysicalDetailsType
j:PersonSocialDetailsType
j:PersonToothType
j:PersonType
j:PersonWeightMeasureType
j:PersonWeightUnitCodeType
j:PhysicalFeatureType
j:PleaType
j:ProgramType
j:ProgressType
j:PropertyAssignedIDDetailsType
j:PropertyDetailType
j:PropertyDispositionType
j:PropertyHoldingType
j:PropertyPhysicalDetailsType
j:PropertyRegistrationType
j:PropertySeizureType
j:PropertyTitleType
j:PropertyTransactionType
j:PropertyType
j:PropertyValueDetailsType
j:PropertyValueType
j:ProtectionOrderType
j:QuantityType
j:RangeAgeMeasureType
j:RangeMeasureType
j:RangePersonHeightMeasureType
j:RangePersonWeightMeasureType
j:RangeVehicleSpeedMeasureType
j:RateType
j:RealEstateType
j:RecurringObligationType
j:ReferenceType
j:ReferralType
j:RegisterActionType
j:RegisteredOffenderType
j:RegisterOfActionsType
j:RelationshipType
j:RelativeLocationHeadingType
j:RelativeLocationType
j:ReleaseType
j:ResidenceType
j:SanctionType
j:ScheduleDayType
j:SecurityMetadataType
j:SecurityType
j:SentenceDetailsType
j:SentenceModificationType
j:SentenceType
j:SentencingGuidelineType
j:ServiceCallType
j:SeverityLevelType
j:SpeedRateType
j:StatusType
j:StatuteType
j:StreetType
j:StructureType
j:SubjectType
j:SubmissionType
j:SuperType
j:SupervisionRestrictionType
j:SupervisionType
j:TargetType
j:TelephoneNumberType
j:TermType
j:TextType
j:TimeMeasureType
j:TimeObligationType
j:TitleStatusType
j:UTMCoordinateType
j:VehicleBasicsType
j:VehicleBranderType
j:VehicleBrandType
j:VehicleEmissionInspectionType
j:VehicleEngineDisplacementMeasureType
j:VehicleEngineType
j:VehicleInspectionType
j:VehiclePartType
j:VehicleRegistrationStatusType
j:VehicleRegistrationType
j:VehicleSafetyInspectionType
j:VehicleTitleType
j:VehicleType
j:VerdictType
j:VictimType
j:ViolatedStatuteType
j:VisitationType
j:WarrantType
j:WeightMeasureType
j:WitnessType
lasd:DNACollectionStatusCodeType
lasd:IncidentTypeCodeType
mn_off:OffenseCodeType
mn_off:OffenseLevelCodeType
mn_off:StatuteTypeCodeType
ncic:BCOType
ncic:BLTType
ncic:BMAType
ncic:BRAType
ncic:BTMAType
ncic:BTYType
ncic:BXRType
ncic:CALType
ncic:CATType
ncic:CMCType
ncic:DCHGeneralType
ncic:DCHOtherType
ncic:DCHRemovableAppliancesType
ncic:DCHRestorationCariesType
ncic:DCHStatusType
ncic:DENType
ncic:ECRType
ncic:EPDType
ncic:EXLType
ncic:EYEType
ncic:FPCFingerType
ncic:FPCPatternType
ncic:FPCType
ncic:GUNColorFinishType
ncic:HAIType
ncic:HSPType
ncic:HULType
ncic:IFSType
ncic:IMTType
ncic:JWTType
ncic:LISType
ncic:LITType
ncic:LSTAType
ncic:MAKType
ncic:MNPType
ncic:MNUType
ncic:MPCType
ncic:OFFType
ncic:ORIAgencyType
ncic:ORIGovernmentLevelType
ncic:PCOType
ncic:POBType
ncic:PROType
ncic:RACType
ncic:RESType
ncic:SDTType
ncic:SEXType
ncic:SFIType
ncic:SKNType
ncic:SMTType
ncic:ToothIDCodeType
ncic:TYPArticleCategoryType
ncic:TYPAType
ncic:TYPDescriptionType
ncic:TYPOType
ncic:TYPSType
ncic:TYPType
ncic:VCOType
ncic:VMAType
ncic:VMOType
ncic:VSTType
nibrs:AggravatedAssaultHomicideFactorsCodeType
nibrs:ArresteeWeaponCodeType
nibrs:ArrestTypeCodeType
nibrs:CriminalActivityTypeCodeType
nibrs:DrugMeasurementCodeType
nibrs:DrugTypeCodeType
nibrs:EthnicityCodeType
nibrs:ForceTypeCodeType
nibrs:IncidentBiasMotivationCodeType
nibrs:IncidentExceptionalClearanceCodeType
nibrs:IncidentFactorCodeType
nibrs:InjuryTypeCodeType
nibrs:JustifiableHomicideFactorsCodeType
nibrs:LEOKAActivityTypeCodeType
nibrs:LEOKAOfficerAssignmentTypeCodeType
nibrs:LocationTypeCodeType
nibrs:MethodOfEntryType
nibrs:MultipleArresteeSegmentsCodeType
nibrs:PropertyCategoryCodeType
nibrs:PropertyLossCodeType
nibrs:ResidentCodeType
nibrs:VictimTypeCodeType
nonauth:ImagePoseCodeType
nonauth:PersonNameTypeCodeType
ucr:OffenseCodeType
unece:LengthType
unece:MassType
unece:TimeType
unece:VelocityType
usps:USStateCodeType
ut_offender:CaseDispositionDecisionTypeCodeType
ut_offender:MilitaryDischargeTypeCodeType
ut_offender:PleaTypeCodeType
ut_offender:SupervisionLevelCodeType
ut_offender:SupervisionRestrictionCodeType
xsd:base64Binary
xsd:boolean
xsd:date
xsd:decimal
xsd:duration
xsd:gMonth
xsd:gYear
xsd:hexBinary
xsd:integer
xsd:nonNegativeInteger
xsd:string
xsd:time
xsd:token

Note: The descriptions can be found by searching for the particular component using the Wayfarer tool which is located at the following page:

http://niemwayfarer.org/

"...As the GJXDM became ready for release in production, many developers and administrators realized that very little information was available regarding the real-world performance of properly defined subset schemas. The Office of Justice Programs (OJP) in the U.S. Department of Justice concluded that performance testing of the GJXDM was a high priority. The testing would define the relative impact of using the GJXDM as a basis for creating XML schemas representing documents exchanged.

To carry out the testing program, OJP awarded a grant to the IJIS Institute to conduct performance testing of the initial production release to provide industry and government developers and administrators with insights into the impact of using this important new tool. The IJIS Institute created a partnership with The George Washington University (GWU) to conduct the performance testing under the leadership of a project committee. The committee consisted of developers from IJIS Institute member companies and other organizations having specific interest in the test results (Georgia Tech Research Institute, the engineering arm that designed the GJXDM; the Global XML Structure Task Force, the practitioner group guiding the development process; and OJP)."

Click Here to access the full report.

Access to all of the GJXDM releases, patches, documentation, and links to other resources can be obtained via the following URL:

https://bja.ojp.gov/program/it/national-initiatives/gjxdm

What GJXDM is Not

The is many things. But, for all the ground it covers, there are many things that the GJXDM is not. Here are a few misconceptions about the role of the GJXDM:

The GJXDM is not a database technology.
The GJXDM is not a guideline for designing your internal databases. The GJXDM is only for exchanges between systems. You should not try to make your internal databases mirror the GJXDM.

The GJXDM is not just XML.
The GJXDM is not just XML. It's a set of reusable objects and their definitions. The definitions are not an afterthought. They are a major feature and benefit of the model.

The GJXDM is not Big "J" Justice Specific.
The GJXDM is not limited to the U.S. Department of Justice. (That's Big-J Justice.) The GJXDM includes courts, corrections, juvenile, and other aspects of justice at Federal, state, local, and tribal levels.

The GJXDM is not a programming language.
The GJXDM is a data model. It's not a programming language. It's represented as XML, which isn't a programming language either.

The GJXDM is not a silver bullet.
The GJXDM is a tool for creating exchanges. The model defines pieces and how they fit together. You can use those pieces to build exchanges. But you still need to do the building.

The GJXDM is not a replacement for exchanges and interagency agreements.
Again, the model is a set of objects. Which objects are used and precisely how they will fit together are questions that will still need to be negotiated and decided between and among exchange partners.

The GJXDM is not a definition of interoperability.
The GJXDM helps define the payload of an exchange. Topics like security and messaging layers are beyond the scope of the model.

There is a wide variety of tools available for using the GJXDM.

American Association of Motor Vehicle Administrators (AAMVA)

http://www.aamva.org
The American Association of Motor Vehicle Administrators (AAMVA) is a nonprofit organization striving to develop model programs in motor vehicle administration, police traffic services, and highway safety. AAMVA serves as an information clearinghouse for these same disciplines and acts as an international spokesperson for these interests.

Automated Regional Justice Information System (ARJIS)

http://www.arjis.org/
The Automated Regional Justice Information System (ARJIS) is a complex criminal justice enterprise network utilized by local, state, and federal agencies in the San Diego, California, region. ARJIS is chartered with supporting a regional Web-based enterprise network that utilizes technical and operational standards to build interfaces to all criminal justice systems in the region. The ARJIS secure intranet, ARJISNet, contains data on the region’s crime cases, arrests, citations, field interviews, traffic accidents, fraudulent documents, photographs, gang information, and stolen property.

ARJIS is also utilized for tactical analysis, investigations, statistical information, and crime analysis. Officers and investigators can additionally request electronic notification when information is obtained by another agency or officer concerning an individual, location, or vehicle. The critical success factor for ARJIS is the “single point of entry” to query all regional justice data.

ARJIS is currently collaborating with the National Institute of Justice (NIJ) to build new Web-based technologies to continue the support of the criminal justice community.

Criminal Justice Information Services (CJIS) Division, Federal Bureau of Investigation (FBI)

https://www.fbi.gov/services/cjis
The Criminal Justice Information Services (CJIS) Division was established in February 1992 to serve as the focal point and central repository for criminal justice information services in the Federal Bureau of Investigation (FBI). It is the largest division within the FBI. Programs that were initially consolidated under the CJIS Division include the National Crime Information Center (NCIC), Uniform Crime Reporting (UCR), and Fingerprint Identification. In addition, responsibility for several ongoing technological initiatives was also transferred to the CJIS Division, including the Integrated Automated Fingerprint Identification System (IAFIS), NCIC 2000, and the National Incident-Based Reporting System (NIBRS).

CriMNet

http://www.crimnet.state.mn.us
CriMNet is an enterprise architecture that puts in place a statewide framework of people, processes, data, standards, and technology focused on providing accurate and comprehensive data to the criminal justice community in the state of Minnesota. It provides the means to put “the right data in the hands of the right people at the right time and in the right place.”

The CriMNet integration effort is not one single project but incorporates many projects that are being developed by criminal justice organizations throughout Minnesota. The integration architecture is driven by local operational needs and uses standards that will support the exchange of data across existing and developing systems.

Georgia Tech Research Institute (GTRI)

http://www.gtri.gatech.edu
The Georgia Tech Research Institute (GTRI) is the nonprofit applied research arm of the Georgia Institute of Technology in Atlanta, Georgia. With more than 1,000 employees, GTRI supports approximately $100 million in research yearly, for more than 200 clients in industry and government. GTRI researchers have played a pivotal role in the engineering support and technical guidance of the Global Justice Extensible Markup Language (XML) Data Model (Global JXDM).

GJXDM Training and Technical Assistance Committee (GTTAC)

https://bja.ojp.gov/program/it/policy-implementation/training
The GJXDM Training and Technical Assistance Committee (GTTAC) is a consortium of organizations engaged in technical assistance and training related to technology in the justice field, specifically the Global JXDM. The GTTAC supports the development of training and technical assistance for the Global JXDM. The Committee was established in January 2004 as an outreach effort for the Global JXDM. It is related to, but external from, the Global Justice Information Sharing Initiative (Global) and is an operating entity on behalf of the Global JXDM to assist the justice community’s need to better understand and implement the Global JXDM.

GTTAC’s mission is to coordinate the work of national service providers in providing training and technical assistance on issues related to the implementation of the Global JXDM. Major projects include building Global JXDM Information Exchange Package Descriptions, creating a national virtual help desk centered on the Global JXDM, and coordinating regional large-scale Global JXDM training events.

Global Justice Information Sharing Initiative (Global)

https://bja.ojp.gov/program/it/global 
The Global Justice Information Sharing Initiative (Global) is a “group of groups,” representing more than 30 independent organizations spanning the spectrum of law enforcement, judicial, correctional, and related bodies. Member organizations participate in Global out of shared responsibility and shared belief that together they can bring about positive changes in inter-organizational communication and data sharing.

The Global Advisory Committee (GAC) serves as an advisory committee for the U.S. Department of Justice. Global aids its member organizations and the people they serve through a series of important initiatives. These include the facilitation of the Global Working Groups, development of technology standards, creation of white papers on data sharing issues, and the dissemination of information via the Global Web site.

The work of the GAC has implications of the highest importance and helps to make the GAC the foremost voice for justice information sharing.

Global Infrastructure/Standards Working Group (GISWG)

https://bja.ojp.gov/program/it/giswg
Successful data exchange is greatly facilitated by the development and adoption of standards that enable transparent integration of disparate systems. The Global Justice Information Sharing Initiative (Global) Infrastructure/Standards Working Group (GISWG) is implementing a coordination process to identify information sharing standards within the justice community. This effort includes publishing, cataloging, and sharing these standards to promote collaborative efforts and offer blueprints to those beginning the information exchange planning process.

Global XML Structure Task Force (GXSTF)

https://bja.ojp.gov/program/it/national-initiatives/gjxdm 
The Global Extensible Markup Language (XML) Structure Task Force (GXSTF) is a component of the Global Justice Information Sharing Initiative (Global) Infrastructure/Standards Working Group (GISWG).

The GXSTF addresses the requirements, design, structure, and implementation for the Global Justice XML Data Model (Global JXDM). Their vision is to significantly advance justice information sharing by providing a common language and vocabulary that reduces cost and technical barriers. More specifically, the GXSTF has developed a consistent, extendable, maintainable XML schema reference specification for data elements and types that represent the data requirements of the general justice and public safety communities. The GXSTF is heavily involved in the Global JXDM release process and approves all fixes, additions, deletions, and modifications to each implementation. The GXSTF is also responsible for Global JXDM guidance, review, and issue resolution.

Institute for Telecommunication Sciences (ITS)

http://its.bldrdoc.gov/
The National Telecommunications and Information Administration (NTIA), an agency of the U.S. Department of Commerce, is the Executive Branch’s principal voice on domestic and international telecommunications and information technology issues. NTIA works to spur innovation, encourage competition, help create jobs, and provide consumers with more choices and better quality telecommunications products and services at lower prices.

The Institute for Telecommunication Sciences (ITS) is the chief research and engineering arm of NTIA. ITS supports NTIA telecommunications objectives such as promotion of advanced telecommunications and information infrastructure development in the United States, enhancement of domestic competitiveness, improvement of foreign trade opportunities for U.S. telecommunications firms, and facilitation of more efficient and effective use of the radio spectrum.

ITS also serves as a principal federal resource for solving the telecommunications concerns of other federal agencies, local and state governments, private corporations and associations, and international organizations.

Integrated Criminal Justice Information System (ICJIS)

http://www.Maricopa.gov/ICJIS
ICJIS is a Maricopa County, Arizona sponsored project that provides integration services for sharing information between its internal stakeholders (Sheriff’s Office, County Attorney Office, Clerk of the Superior Court, Superior Court and Indigent Representation Agencies) and to provide these internal stakeholders information sharing capabilities with external agencies that include municipal, state and federal agencies.  ICJIS stakeholders share information between 25 criminal justice systems in addition to all state and federal information sources. 

Integrated Justice Information Systems (IJIS)

http://www.ijis.org/
The mission of the IJIS Institute is to contribute to the implementation of Integrated Justice Information Systems (IJIS) throughout the country by applying the knowledge and experience of the information technology (IT) industry. As IT professionals responsible for the achievement of solution systems, IJIS believes that experience and perspective will improve the quality and reduce the time to market for solutions. IJIS supports the initiative of the Office of Justice Programs to involve industry in its information sharing programs and believes that the program will benefit from its unique and collective experience.

International Organization for Standardization (ISO)

http://www.iso.org
The International Organization for Standardization (ISO) is a network of national standards institutes from 145 countries working in partnership with international organizations, governments, industry, business, and consumer representatives.

Joint Task Force on Rap Sheet Standardization

https://www.nlets.org/sites/default/files/2021-05/chief_fact-sheet.pdf
The Joint Task Force (JTF) on Rap Sheet Standardization is an endeavor by the Federal Bureau of Investigation (FBI) and NLETS – The International Justice and Public Safety Information Sharing Network to bring about a national standard for the exchange of criminal history rap sheets. Sponsored by the FBI, members include staff of the FBI, NLETS, and states that operate criminal history repositories.

In 1995, the National Task Force on Increasing the Utility of the Criminal History Record recommended expanded data content, a presentation format (page layout) for the expanded content, and the creation of a transmission format for the interstate sharing of criminal history information. The National Task Force included representatives from the FBI Criminal Justice Information Services (CJIS) Advisory Policy Board (APB); NLETS; the National Center for State Courts; and SEARCH, The National Consortium for Justice Information and Statistics. Its members were a diverse array of justice practitioners drawn from the judiciary; prosecution; court administration; local, state, and federal law enforcement; juvenile justice pretrial services; and state criminal records repositories.

Justice Information Exchange Model (JIEM)

https://www.search.org/solutions/information-sharing-standards-and-models/jiem/
The Justice Information Exchange Model (JIEM) consists of a framework that defines universal dimensions of information exchange, a research and planning methodology for modeling the operational dynamics of this information exchange, and a Web-based software application - the JIEM Modeling Tool - that enables data collection, analysis, and reporting by users and researchers.

Justice Information Sharing Professionals (JISP)

http://www.jisp.us
The Justice Information Sharing Professionals (JISP) is a national network of local and state justice and public safety integrators responsible for the facilitation, collaboration, and advocacy of information sharing. JISP was created to focus on the need to enhance communication among practitioners. JISP coordinates a member-only Internet mail list at http://groups.yahoo.com/group/JISP/

Law Enforcement Information Technology Standards Council (LEITSC) Technology Center

http://www.leitsc.org/
The Law Enforcement Information Technology Standards Council (LEITSC) is funded through the Office of Justice Programs (OJP), U.S. Department of Justice, to address the issue of information technology standards specific to the law enforcement community. The mission of LEITSC is to foster the growth of strategic planning and implementation of integrated justice systems by promoting the merits of information technology (IT) standards, providing advice to the nation’s law enforcement community on technical aspects of IT standards, sharing practical solutions, and representing the voice of law enforcement in the expansion of justice and public safety IT standards.

LEITSC partners include the International Association of Chiefs of Police (IACP), the Police Executive Research Forum (PERF), the National Sheriffs’ Association (NSA), and the National Organization of Black Law Enforcement Executives (NOBLE).

LegalXML Court Filing Standard Initiative

https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=legalxml-courtfiling
Pursuant to discussions at an August 1999 planning meeting, the Conference of State Court Administrators/National Association of Court Managers Joint Technology Committee (JTC) formed an e-filing standards subcommittee to pursue an Internet electronic filing specification for the courts.

To that end, in December 1999, the JTC voted to partner with LegalXML, a nonprofit organization that facilitates development of XML standards for application within the legal community. This coalition produced the LegalXML Court Filing Standard.

LegalXML Integrated Justice Initiative

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=legalxml-intjustice
The purpose of the Integrated Justice Technical Committee is to support XML specifications for exchanging data among justice system branches and agencies. While its principal focus will be on data pertaining to criminal cases, its scope will include certain data exchanges in civil cases, such as civil protection order, child support enforcement and dependency and neglect cases.  The Committee will also serve as a vehicle for vetting the Global Justice XML Data Dictionary being developed under the auspices of the Infrastructure/Standards Working Group of the Global Justice Information Network Advisory Committee, US Department of Justice.

Los Angeles County Information Systems Advisory Body (ISAB)

http://ccjcc.lacounty.gov/Subcommittees-Task-Forces/Information-Systems-Advisory-Board-ISAB
ISAB is a member of the Countywide Criminal Justice Coordination Committee (CCJCC) and is responsible for overseeing the development and coordination of countywide criminal justice information systems.  ISAB has overall responsibility for the planning, development, implementation and management of countywide criminal justice data and telecommunication system projects and providing related technical assistance to ISAB members which include the Sheriff, District Attorney, Public Defender, Probation Department, Coroner, Superior and Municipal Courts, Chief Administrative Office, Internal Services Department, Los Angeles County Police Chiefs Association, Los Angeles Police Department and the Alternate Public Defender.

Los Angeles County Sheriff’s Department (LASD)

http://www.lasd.org
The Los Angeles Sheriff's Department is the largest Sheriff's Department in the world. The Department serves the entire County of Los Angeles encompassing 4,061 square miles with a population of about 10 million. The Department manages the largest County jail system in the world which averages about 19,000 inmates daily. Additionally, the Department is responsible for police services in the unincorporated areas and 41 incorporated cities for which police and traffic services have been contracted

Mapping Alaska’s Justice InterChanges (MAJIC)

https://bja.ojp.gov/sites/bja/files/media/document/mapping_alaskas_justice_interchanges_majic.pdf
The Mapping Alaska’s Justice InterChanges (MAJIC) program, managed by the state’s Criminal Justice Information Advisory Board, brings together the systems in many organizations statewide, including the Department of Public Safety, the Alaska Court System, the Public Defender Agency, and the National Law Enforcement and Corrections Technology Center-Northwest.

National Center for State Courts (NCSC)

https://www.ncsc.org/
The National Center for State Courts (NCSC) provides up-to-date information and hands-on assistance that help court administrators to better serve the public. Through original research, consulting services, publications, and national educational programs, NCSC offers solutions that enhance court operations with the latest technology, collects and interprets the latest data on court operations nationwide, and provides information on proven “best practices” for improving court operations in areas such as civil case management.

National Crime Information Center (NCIC)

http://www.fas.org/irp/agency/doj/fbi/is/ncic.htm
The National Crime Information Center (NCIC) is a computerized index of criminal justice information (i.e., criminal record history information, fugitives, stolen properties, and missing persons). It is available to local, state, and federal law enforcement and other criminal justice agencies and is operational 24 hours per day, 365 days per year. The purpose for maintaining the NCIC system is to provide a computerized database for ready access by a criminal justice agency making an inquiry and to provide prompt disclosure of information in the system from other criminal justice agencies. This information assists authorized agencies in criminal justice and related law enforcement objectives, such as apprehending fugitives, locating missing persons, and locating and returning stolen property, as well as protecting law enforcement officers.

National Governors Association (NGA)

http://www.nga.org
The National Governors Association (NGA) is the collective voice of the nation's governors and one of Washington, D.C.'s, most respected public policy organizations. NGA provides governors and their senior staff members with services that range from representing states on Capitol Hill and before the Administration on key federal issues to developing policy reports on innovative state programs and hosting networking seminars for state government executive branch officials. The NGA Center for Best Practices focuses on state innovations and best practices on issues that range from education and health to technology, including support for the GJXDM.

National Incident-Based Reporting System (NIBRS)

http://www.ojp.usdoj.gov/bjs/nibrs.htm
The Federal Bureau of Investigation’s (FBI) Uniform Crime Reporting (UCR) Program, which began in 1929, collects information about crimes reported to the police. In 1982, the Bureau of Justice Statistics and the FBI sponsored a study of the UCR Program, with the objective of revising it to meet law enforcement needs into the twenty-first century. A five-year redesign effort to provide more comprehensive and detailed crime statistics resulted in the National Incident-Based Reporting System (NIBRS), which collects data on each reported crime incident. The UCR Program is currently being expanded to NIBRS.

National Institute of Justice (NIJ)

http://www.ojp.usdoj.gov/nij
The National Institute of Justice (NIJ) is the research, development, and evaluation agency of the U.S. Department of Justice. NIJ provides objective, independent, nonpartisan, evidence-based knowledge and tools to meet the challenges of crime and justice, particularly at the state and local levels. NIJ’s principal authorities are derived from the Omnibus Crime Control and Safe Streets Act of 1968, as amended (see 42 USC * 3721-3723).

The NIJ director is appointed by the President and confirmed by the Senate. The NIJ director establishes the Institute’s objectives, guided by the priorities of the Office of Justice Programs, the U.S. Department of Justice, and the needs of the field. NIJ actively solicits the views of criminal justice and other professionals and researchers to inform its search for the knowledge and tools to guide policy and practice.

National Telecommunications and Information Administration (NTIA)

http://www.ntia.doc.gov
The National Telecommunications and Information Administration (NTIA), an agency of the U.S. Department of Commerce, is the Executive Branch’s principal voice on domestic and international telecommunications and information technology issues. NTIA works to spur innovation, encourage competition, help create jobs, and provide consumers with more choices and better quality telecommunications products and services at lower prices.

NLETS – The International Justice and Public Safety Information Sharing Network 

http://www.nlets.org
The mission of NLETS – The International Justice and Public Safety Information Sharing Network is to provide, within a secure environment, an international criminal justice telecommunication capability that will benefit, to the highest degree, the safety, security, and preservation of human life and the protection of property. NLETS will assist those national and international governmental agencies and other organizations with similar missions who enforce or aid in enforcing local, state, federal, or international laws or ordinances.

Pennsylvania Justice Network (JNET)

https://www.pajnet.pa.gov/Pages/default.aspx
JNET is a collaboration of municipal, county, state, bordering states, and federal justice agencies that develop and provide a secure, online integrated justice system that allows participating agencies to access driver and offender records and other justice information. Local and state police officers, JNET’s largest users, have immediate access to critical criminal justice information that helps them to perform their jobs more effectively.

Regional Information Sharing Systems® (RISS)

https://www.iir.com/Initiatives/#information
The Regional Information Sharing Systems (RISS) Program is composed of six regional centers that share intelligence and coordinate efforts against criminal networks that operate in many locations across jurisdictional lines. Typical targets of RISS activities are drug trafficking, terrorism, violent crime, cybercrime, gang activity, and organized criminal activities. Each of the centers, however, selects its own target crimes and the range of services provided to member agencies.

SEARCH, The National Consortium for Justice Information and Statistics

http://www.search.org
SEARCH, The National Consortium for Justice Information and Statistics is a nonprofit membership organization created by and for the states, dedicated to improving the criminal justice system and the quality of justice through better information management, the effective application of information and identification technology, and responsible justice information law and policy.

Washington Justice Information Network (JIN)

https://www.courts.wa.gov/committee/?fa=committee.home&committee_id=98
The mission of JIN is to is to improve public safety by providing criminal justice practitioners with complete, timely and accurate information, and to improve operating efficiency by facilitating the integration of disparate systems throughout the state. Its governance Board includes key state and local members of the justice community. Using the principles of services-oriented architecture, JIN is designing and deploying a model for information sharing in the Washington justice community.