What constitutes GJXDM Compliance?

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: