General Information - Generic Messages (LQ/LR)
Generic Messages (LQ/LR)
This section describes generic transactions which provide Nlets users with the capability to inquire on other state's unique databases. Some state files may not be of nationwide value or availability; however nearby states may benefit from access to these files.
Generic Message Requirements
There are no specific formats to allow automated access and response for generic transactions. All coordination is the responsibility of the states.
Rules have been kept to a minimum due to the general nature of the LQ/LR message:
The standard Nlets header must be used for both XML and Legacy messages.
Only a single 2 or 9 character address may be used.
XML inquiries and responses will use the following element to identify the message type for both queries and responses:
Legacy inquiries must use LQ as the message key, while the responses must use LR as the message key.
Generic Message Example
New York may have implemented a widget registration file. There may be definite benefits in New Jersey accessing this file. To implement such a capability nationwide is not feasible at this time. Therefore, representatives from New Jersey and New York coordinate an effort to allow access through Nlets utilizing the generic message transaction (LQ/LR).
Nlets will not edit the text of the message (LQ) so New Jersey may include whatever information is required by the receiving state.
They may put an embedded message key and data elements that match New York's internal message formats.
New York will dissect the message, query their widget registration file and return the response over Nlets under the generic message key (LR).