(This is not called a "Table Of Contents" because it does not reflect the actual structure of this page, and sometimes links to content elsewhere, bypassing information contained here or in other necessary resources. It's more of a quick link reference -- use judiciously.)


WIJIS Commons serves as the official primary publication site for various data definition and format specifications. This includes, but is not necessarily limited to, all specifications issued by WIJIS.

WIJIS Commons welcomes, and is willing to publish, specifications issued by entities other than WIJIS, provided they are of value or relevance to the Justice Community.

WIJIS publishes specifications for various purposes. WIJIS Commons is the authoritative reference for those specifications, and also provides persistent publication URLs. These publication URLs are, when practicable, direct references to a machine-readable file (XML schema etc) rather than a containing Web page, so that they can be referenced for processing purposes (e.g., in a schemaLocation attribute in another XML Schema or a WSDL.)

If any other representation or publication of a WIJIS specification conflicts with the specification's definition published here, the information at this site should be regarded as definitive. Furthermore, any purported WIJIS specification that is not published at this site has no official standing, is not endorsed by WIJIS, and should be considered to be in error.

wijis specification URIs

All WIJIS specifications are identified by URIs of the form As a general rule, the WIJIS Commons persistent publication URLs are derived by substituting for as the URI authority, and appending the specification filename to the end of the path.


WIJIS Specification URIs usually include versioning and (optionally) effective-date information, normally at the end of the URI. The general form of this version-control construct is conformant with URI path syntax:

in which the "v", dot, forward-slash, and hyphen characters are literals; the x characters represent integer numbers (major and minor version numbers respectively); and the effective date is written in the familiar ANSI standard format. In all cases, the version is considered primary, and the effective date is used to identify updates to that version. (This construct does not address the case in which more than one update of a given version needs to be defined on a given date.)

The difference between "version" and "effective date"

WIJIS Commons makes a simple distinction between a modification with a version change, and a modification with only a new effective date but the same version:

From the point of view of a provider of data representations or messages, effective-dates releases will therefore always implement elective features and enhancements. However, for any entity that is consuming those representations and messages, upgrading to the new specification will be necessary, unless there's a safe assumption that nobody will be sending the new kinds of data or messages..

This is why the Service Definition Schemas have version numbers but not effective dates. Providers of those services are required to handle messages according to the newest specifications. Consumers are not required to do so. When a version changes, the ordinary strategy would be for providers to offer both the new and old versions of the service, with a clear deprecation schedule for the older.

service message tracking info

Any WIJIS Service Message is sent with an associated metadata element called Message Tracking Info that precisely identifies the message, for purposes of auditing and high-level correlation. It's a rich and rather complex datatype (although easier to build than you'd think).

Every message is identified by

These characteristics, and the structure of the metadata element, are defined and discussed at the Message Tracking Info location.

There is also an important resource available for implementers: the Message Tracking Info Builder's Kit, which provides examples and explanations targeted at those who are providing or invoking WIJIS Services. It's also a useful overview of Message Tracking Info for anyone who wants to know. Note that it's a standalone HTML page that can be downloaded and saved independently.

wijis schemas

WIJIS XML Schemas are defined with namespace URIs that begin with These Schemas are published on this site. The URLs of the schemas at this site are declared by WIJIS to be official and persistent.

WIJIS Schemas are generally grouped into three types:

Note that neither of these Schema types is in any sense GJXDM-compliant. Some of the Invocations or Responses import GJXDM types or components to transmit content, but that's not the same thing as an extension or constraint schema created to validate GJXDM messages. In that sense, these Schemas are supplemental; they are auxiliary to the use of GJXDM datamodel.

Should it become necessary for WIJIS to create GJXDM constraint or extension schemas, they would be posted here in a separate category.

IEP documentation

WIJIS Supervision Conditions IEPD Information

Supervision Subject IEPD

Warrant and Protection Order Service Messages

Warrant Schemas
Protection Order Schemas

Drug Case Information IEPD

Drug Case IEPD

datamodel schemas

The list of Datamodel Schemas published by WIJIS can be found here. Specific entries in that list can be located via the links below (the schemas themselves are located at the "persistent URL" link in the main list):


WIJIS Services

WIJIS Services are provided and consumed within the definitions of WIJIS Record Space. In other words, they exchange information formatted as designated GJXDM IEPDs, using metadata and action vocabularies drawn from the WIJIS Datamodel Schemas, and a unified addressing scheme of Record URIs.

Service Definition URIs

WIJIS Services are identified by Service Definition URIs. These URIs are defined within the WIJIS URI domain, but have no other format constraints.

Service Definition URIs tend to be assigned in pairs: one for the Request and one for the Response. The authoritative source for these is the Service Interface Definition Schema, which lists request and response Service Definition URIs as appinfo annotation elements.

Service Instance Identification

Within the WIJIS Record Space, every runtime Service instance can be uniquely identified by three properties:

WIJIS Gateway Services