NIEM Examples - Generic Messages (LQ/LR)
NIEM
Generic Message NIEM Specifications
This section includes format specifications and an example of a NIEM generic transaction (LQ/LR).
There are no edits or requirements on generic message queries and responses, other than standard Nlets NIEM formatting. A generic message can be sent to any 2 or 9 character destination and should adhere to the rules set up between agencies for any specific generic transactions.
All Nlets NIEM messages must be based on the Nlets NIEM Message Structure and include the standard Nlets XML Header as detailed in Message Structure. The NIEM header and hierarchy of the elements in this section have been omitted to avoid redundancy. The associated schemas and instances should be consulted to determine the correct XPaths of the elements.
Element Dictionary
Transaction types detailed below include: Generic Message Query (LQ) and Generic Message Response (LR).
Query Formats
Generic Message Query (LQ)
n2:NLETSInquiryData
This element will contain all elements specific to this transaction.
n2:InquiryDescriptionText
This element contains free text. Include personal descriptors (name, sex) with other relevant data (case
number, booking number, state ID, miscellaneous number) followed by any additional free text.
Response Formats
Generic Message Response (LR)
n2:NLETSResponseData
n2:ResponseText
This element will contain the free text response. Nlets recommends the use of
<![CDATA[]]>
tags to
ensure that the response does not contain any characters illegal in XML.
Generic Message NIEM Examples
Example 1: A Generic Message sent to Arizona.
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>LQ</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZNLETS47</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZ</nh2:DestinationORIID>
</n2:NLETSMessageHeader>
<n2:NLETSInquiryData n2:key="LQ">
<n2:InquiryDescriptionText>INQUIRY DATA</n2:InquiryDescriptionText>
</n2:NLETSInquiryData>
</n2:NLETS>
Example 2: A Generic Response from Arizona.
<n2:NLETS xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" n2:version="4.00" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:n2="http://www.nlets.org/niem/1.0">
<n2:NLETSMessageHeader>
<nh2:MessageKeyCodeText>LR</nh2:MessageKeyCodeText>
<nh2:OriginatingORIID>AZ1110000</nh2:OriginatingORIID>
<nh2:DestinationORIID>AZNLETS47</nh2:DestinationORIID>
<nh2:MessageReceiveDate>10/22/2019</nh2:MessageReceiveDate>
<nh2:MessageReceiveTime>10:11</nh2:MessageReceiveTime>
<nh2:MessageSendDate>10/22/2019</nh2:MessageSendDate>
<nh2:MessageSendTime>10:11</nh2:MessageSendTime>
<nh2:ReceiveMessageNumeric>00000</nh2:ReceiveMessageNumeric>
<nh2:SendMessageNumeric>00834</nh2:SendMessageNumeric>
</n2:NLETSMessageHeader>
<n2:NLETSResponseData n2:key="LR">
<n2:ResponseText>RESPONSE DATA</n2:ResponseText>
</n2:NLETSResponseData>
</n2:NLETS>