| Ticket Medium | A physical medium that may contain one or more tickets. For example, a mobile phone or a DesFire card. |
| Capabilities | A text that identifies resting properties a given NOD Client possesses. NOD Customizes the NOD Client Commands to the Client's Capabilites |
| DIS | Detailed Interface Specification. Detailed description of, among other things, the transaction format used for electronic ticketing |
| Travelers | A person traveling with a public ticket. |
| HB206 | Abbreviation for Handbook 206. |
| Image | A representation of the contents of a ticket medium, eg the contents of a Travel Card or a QR Code |
| Interoperable | Property of a ticket if PTOs can verify the validity of the ticket independently. |
| Client command | A simple, low-level command from NOD to NOD Client that the client must support. For example, "View Message" or "View Mobile Ticket". Client commands can be combined to perform complex scenarios without the NOD Client needing to be upgraded. |
| Logical Order | A representation of an Order that focuses on information and purpose rather than being tied to the physical representation of the Order on a Ticket Medium. |
| NOD | National Order Database. National platform for distribution of tickets. |
| NOD Backsystem | Services used by PTOs for the administration of orders distributed by the NOD |
| NOD Client | Functionality of a device that a Traveler uses to carry out a Pickup. A NOD Client can be part of a larger system, for example combined with a sales solution. Examples are a Mobile APP or a PDO. |
| Nortic Specification DESFire (NSD) | Specification for the data structures of the DESFire cards used for electronic ticketing in Norway. |
| Online Service | A type of functionality that depends on being connected to the internet to work. |
| Order | A document that tells what a given Plugin should change on an Image. |
| OrderGroup | A collection Order to be performed in a single operation. May contain Orders executed by different Plugins. |
| Pickup | The process by which a NOD Client initiates and executes an OrderGroup in the form of a series of simple client commands. |
| PL4 | Existing back system for PTOs owned by IO. The NOD back system services (eg for ordering orders) are exposed through this system. |
| Plugin | An independent module that extends NOD's functionality. |
| PTO | Public Transport Operator. A public transport operator. |
| PUD | Pick Up Device. Specialized entity that allows Travelers to execute Orders posted via other channels (eg, a WEB based sales solution). |
| Travel Card | The electronic travel card used in Norway, based on the DESFire standard. |
| Sales Solution | Service for the traveler who sells a product and puts it out for distribution in NOD as an OrderGroup. The sales solution is not part of NOD. |
| Static OrderGroup | An Order Group with a unique name that a NOD Client can retrieve on their own initiative to perform special actions such as displaying card content. |
| Transaction | A document produced by a Plugin under Pickup. This document can be distributed back to PTO or Clearing Systems. |
| TVM | Counter Vending Machine. Specialized unit that contains both a Sales solution and a NOD Client. An Order is executed immediately after the sale and is perceived by the Traveler as one system. |
