Section 46: TASER Transactions

From Nlets Wiki
Jump to: navigation, search

TASER International (TSQ/TSR)

TASER is an industry leading Conducted Electrical Weapons (CEWs) company used worldwide by law enforcement, military and correctional markets to incapacitate dangerous, combative, or high-risk subjects who pose a risk to law enforcement/correctional officers, innocent citizens, or themselves in a manner that is generally recognized as a safer alternative to other uses of force. They were approved for strategic partnership at the 2015 Spring Board meeting in Charleston, South Carolina. By partnering with Nlets, TASER gains the ability to provide enhanced services to the law enforcement community.

Through this partnership with TASER, Nlets users now have access to TASER's CEW Cartridge and Handle Purchase/Registration data via a real-time query capability of the TASER database. The technical specifications for this service can be found below. Questions regarding the service should be directed to the Nlets help desk at 800-528-4020 or via email at helpdesk@nlets.org. Questions related to response data returned from the TASER service should be directed to TASER Support at NLETSDataRequest@taser.com.

Note on Law Enforcement records

Law enforcement records will be redacted from the service. When the search returns records that are redacted, the Redacted field will be set to 1. These records may still be required during an investigation and can be provided on a case by case basis by contacting TASER International at NLETSDataRequest@taser.com.

XML and Legacy Field Requirements

The following is required to inquire upon the TASER database. The message type will be "TSQ" The resultant response will be "TSR"

GJXDM XML Tag: NIEM XML Tag: Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
    <nc:ItemSerialIdentification>
    <nc:IdentificationID>
    <nc:ItemSerialIdentification>
    <nc:IdentificationID>
SER/ 15 Alphanumeric Taser Serial Number


GJXDM (DEPRECATED)

GJXDM has been deprecated. Please contact Nlets for additional assistance with GJXDM.

Top

NIEM

TASER NIEM Specifications

This section describes the format and provides examples for TASER queries and responses. TASER queries should be sent to destination TI.

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: TASER Query by Serial Number (TSQ), TASER Positive Response (TSR) and TASER Negative (no hit) Response (TSR)

Query Formats

TASER Query by Serial Number (TSQ)

Inquiry Data (n2:NLETSInquiryData)
This element will contain all elements specific to this transaction.

  ItemSerialIdentification (nc:ItemSerialIdentification)
  GJXDM: Taser serial number
  This element encapsulates the information about the serial number.

    Organization's TASER ID (nc:IdentificationID)
    GJXDM: A generic identifier assigned to an serial number.
    This element contains the TASER Serial number [Discription on how to aquire the serial number here]

Response Formats

TASER Positive (hit) Response (TSR)

n2:NLETSResponseData
This element will contain all elements specific to this transaction.

  Taser Record Of Sale (n2-tsr:TaserRecordOfSale)
  NIEM: Details about a Taser Record Of Sale.
  This element encapsulates the information about record Of Sale. A response can one or more of this element

    Billing Address (n2-tsr:BillingAddress)
    NIEM: Address of the entity that purchased the TASER ECD device.
    This element contains the Address of the organization.

    Billing Company Text (n2-tsr:BillingCompanyText)
    NIEM: Name of the entity that purchased the TASER ECD device.
    This element contains the Name of the organization.

    Billing Name Text (n2-tsr:BillingNameText)
    NIEM: Name of person on the bill of the organization that purchased the TASER ECD device if provided.
    This element contains the Name of the person.

    Record Redacted Indicator (n2-tsr:RecordRedactedIndicator)
    NIEM: The redacted flag will be set to 1 when an occurrence of a record node is redacted
    It is possible a unit could have multiple owners and sales. This could result in only part of a record being redacted

    ItemSerialIdentification (nc:ItemSerialIdentification)
    NIEM: Taser serial number
    This element encapsulates the information about the serial number.

     IdentificationID (nc:IdentificationID)
     NIEM: A generic identifier assigned to an serial number.
     This element contains the TASER Serial number.

    Shipping Address (n2-tsr:ShippingAddress)
    NIEM: Address where the TASER ECD device was shipped.
    This element contains the Address of the organization.

    Shipping Company Text (n2-tsr:ShippingCompanyText)
    NIEM: Name of the entity where the TASER ECD device was shipped.
    This element contains the Name of the organization.

    Shipping Name Text (n2-tsr:ShippingNameText)
    NIEM: Name of person on the bill of the organization where the TASER ECD device was shipped if provided.
    This element contains the Name of the person.

    PurchaseDate (n2-tsr:PurchaseDate)
    NIEM: TASER ECD device Purchase Date
    This element encapsulates the information about the Purchase Date.

     Date (nc:Date)
     NIEM: TASER ECD device Purchase Date
     This element contains the TASER ECD device Purchase Date.

TASER Negative (no hit) Response (TSR)

Response Data (n2:ResponseText)
This element will contain all elements specific to this transaction.

  Response Text (n2:NLETSResponseData)


  This element will indicate that you inqurey did not produce any results. Nlets recommends the use of

<!&#91;CDATA&#91;&#93;&#93;>

tags to


  ensure that the response does not contain any characters illegal in XML.

TASER NIEM Examples

Example 1: TASER query by Serial.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>TSQ</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>AZNLETS20</nh2:OriginatingORIID>
    <nh2:DestinationORIID>TI</nh2:DestinationORIID>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="TSQ">
    <nc:ItemSerialIdentification>
      <nc:IdentificationID>T8-0123456</nc:IdentificationID>
    </nc:ItemSerialIdentification>
  </n2:NLETSInquiryData>
</n2:NLETS>

Example 2: TASER positive response.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>TSR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>NL0000000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>05/26/2016</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:36</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>05/26/2016</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:36</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00133</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00025</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="TSQ">
    <nc:ItemSerialIdentification>
      <nc:IdentificationID>T8-1234567</nc:IdentificationID>
    </nc:ItemSerialIdentification>
  </n2:NLETSInquiryData>
  <n2:NLETSResponseData n2:key="TSR">
    <n2-tsr:TaserRecordOfSale xmlns:n2-tsr="http://www.nlets.org/niem/nlets-taser/1.0">
      <n2-tsr:BillingAddress>
        <nc:AddressFullText>1918 W Wispering Wind DR</nc:AddressFullText>
      </n2-tsr:BillingAddress>
      <n2-tsr:BillingCompanyText>Test Company Name</n2-tsr:BillingCompanyText>
      <n2-tsr:BillingNameText>Test Name</n2-tsr:BillingNameText>
      <n2-tsr:RecordRedactedIndicator>false</n2-tsr:RecordRedactedIndicator>
      <nc:ItemSerialIdentification>
        <nc:IdentificationID>T8-1234567</nc:IdentificationID>
      </nc:ItemSerialIdentification>
      <n2-tsr:ShippingAddress>
        <nc:AddressFullText>1918 W Wispering Wind DR
PHOENIX, AZ 85085
USA</nc:AddressFullText>
      </n2-tsr:ShippingAddress>
      <n2-tsr:ShippingCompanyText>Test Company Name</n2-tsr:ShippingCompanyText>
      <n2-tsr:ShippingNameText>Test Name</n2-tsr:ShippingNameText>
      <n2-tsr:PurchaseDate>
        <nc:Date>2015-12-03</nc:Date>
      </n2-tsr:PurchaseDate>
    </n2-tsr:TaserRecordOfSale>
  </n2:NLETSResponseData>
</n2:NLETS>

Example 3: TASER Negative (no hit) response.

<n2:NLETS xmlns:i="http://niem.gov/niem/appinfo/2.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:nh2="http://www.nlets.org/niem/nlets-hdr/1.0" xmlns:niem-xsd="http://niem.gov/niem/proxy/xsd/2.0" xmlns:s="http://niem.gov/niem/structures/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" n2:version="4.00" xmlns:j5="http://release.niem.gov/niem/domains/jxdm/5.0/" xmlns:ct="http://release.niem.gov/niem/conformanceTargets/3.0/" xmlns:structures="http://release.niem.gov/niem/structures/3.0/" xmlns:n2="http://www.nlets.org/niem/1.0">
  <n2:NLETSMessageHeader>
    <nh2:MessageKeyCodeText>TSR</nh2:MessageKeyCodeText>
    <nh2:OriginatingORIID>NL0000000</nh2:OriginatingORIID>
    <nh2:DestinationORIID>AZNLETS20</nh2:DestinationORIID>
    <nh2:MessageReceiveDate>05/26/2016</nh2:MessageReceiveDate>
    <nh2:MessageReceiveTime>13:43</nh2:MessageReceiveTime>
    <nh2:MessageSendDate>05/26/2016</nh2:MessageSendDate>
    <nh2:MessageSendTime>13:43</nh2:MessageSendTime>
    <nh2:ReceiveMessageNumeric>00137</nh2:ReceiveMessageNumeric>
    <nh2:SendMessageNumeric>00027</nh2:SendMessageNumeric>
  </n2:NLETSMessageHeader>
  <n2:NLETSInquiryData n2:key="TSQ">
    <nc:ItemSerialIdentification>
      <nc:IdentificationID>T8-1111111</nc:IdentificationID>
    </nc:ItemSerialIdentification>
  </n2:NLETSInquiryData>
  <n2:NLETSResponseData n2:key="TSR">
    <n2:ResponseText>YOUR QUERY ON T8-1111111 RETURNED 0 RESULTS</n2:ResponseText>
  </n2:NLETSResponseData>
</n2:NLETS>

Legacy (DEPRECATED)

TASER Legacy Specifications

This section describes formats and provides examples for TASER queries and responses.

Query Formats

The message type will be "TSQ". The resultant response will be "TSR". The following entry will be required to query the TASER file.

Legacy
Prefix:
Field
Size:
Data
Requirements:
Translation:
SER/ 15 Alphanumeric Serial Number
TASER Legacy Examples

Example 1: TASER query by Serial Number.

TSQ.AZNLETS39.TI.TXT SER/T8-1111111

Example 2: TASER positive response.

TSR.NL0000000
13:47 05/26/2016 00140
13:47 05/26/2016 00028 AZNLETS37
TXT
Taser Record of Sale
Date of Purchase:
Billing Company: Test Company
Billing Name: Test Name
Billing Address: 1918 W Wispering Wind DR
Shipping Company: Test Shipping Company
Shipping Name: Test Shipping Name
Shipping Address: 1918 W Wispering Wind DR

Example 3: TASER Negative (no hit) response.

TSR.NL0000000
13:47 05/26/2016 00140
13:47 05/26/2016 00028 AZNLETS37
TXT
YOUR QUERY ON T8-1111111 RETURNED 0 RESULTS

Top

Downloads

Download TSQ Schema

Download TSR Schema

Download TSR Stylesheet

Top