What the GJXDM is not.

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.