<?xml version="1.0" encoding="UTF-8"?>

 <!--

 Free Telco Dictionary

 Copyright © 2013 František Kučera (frantovo.cz)

 Permission is granted to copy, distribute and/or modify this document

 under the terms of the GNU Free Documentation License, Version 1.3

 or any later version published by the Free Software Foundation;

 with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.

 A copy of the license is included in the section entitled "GNU

 Free Documentation License".

 You should have received a copy of the GNU Free Documentation License

 along with this program.  If not, see <http://www.gnu.org/licenses/>.

 -->

 <dictionary xmlns="https://telco.frantovo.cz/xmlns/dictionary">

 	<tags>

 		<tag id="acision" name="Acision" description="comes from Acision or is specific for this company"/>

 		<tag id="ericsson" name="Ericsson" description="comes from Ericsson or is specific for this company"/>

 		<tag id="nsn" name="Nokia Siemens Networks" description="comes from Nokia Siemens Networks or is specific for this company"/>

 		<tag id="charging" name="Charging" description="charging, billing"/>

 		<tag id="messaging" name="Messaging" description="sending messages, receiving messages (SMS, MMS etc.)"/>

 		<tag id="computer" name="Computer" description="general IS/ICT term"/>

 		<tag id="general" name="General" description="general term"/>

 		<tag id="finance" name="Finance" description="financial term"/>

 		<tag id="java" name="Java" description="Java and other JVM languages"/>

 		<tag id="xml" name="XML" description="eXtensible Markup Language"/>

 		<tag id="security" name="Security" description="security and cryptography"/>

 		<tag id="protocol" name="Protocol" description="communication protocol"/>

 	</tags>

 	<concept>

 		<term abbreviation="MVNO" completeForm="mobile virtual network operator" language="en"/>

 		<term abbreviation="MOLO" completeForm="mobile other licensed operator" language="en"/><!-- in the United Kingdom -->

 		<explanation language="en"><text>a provider which does not have own wireless network infrastructure; but does marketing and sets the prices for subscribers</text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="MVNE" completeForm="mobile virtual network enabler" language="en"/>

 		<explanation language="en"><text>a company that provides technical services to MVNO thus MVNO can focus on marketing, pricing, brand and customer care</text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="hot billing" language="en"/>

 		<term abbreviation="" completeForm="late billing" language="en"/>

 		<term abbreviation="" completeForm="latebiller" language="en"/>

 		<explanation language="en">

 			<text>

 				a technique used in charging;

 				for pre-paid subscribers the standard way to charge services is online

 				– subscriber's balance is checked in the billing system and if sufficient, the service (e.g. sending a SMS) is provided, otherwise the service is denied;

 				if the billing system is not currently available (so we can't say if the subscriber's balance is high enough), we can provide the service anyway and try to charge it later;

 				this feature requires saving state (transactions which weren't charged yet) in some persitent storage (CDR files, SQL database etc.)

 				and can be done at the billing gateway or directly at system like SMSC

 			</text>

 		</explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SMS" completeForm="short message service" language="en"/>

 		<explanation language="en">

 			<text>

 				a service or particular short text message sent from or to a mobile phone;

 				length of the content in one message is 140 bytes (octets), the number of characters depends on encoding, if 7-bit one is used, it is well known 160 characters;

 				the number „160“ is iconic for SMS

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="octet" language="en"/>

 		<term abbreviation="" completeForm="byte" language="en"/>

 		<explanation language="en">

 			<text>

 				a unit of digital information;

 				byte (almost always) consists of 8 bits, which means 256 possible values (2^8);

 				octet is a synonym for 8-bit byte which accents that we really mean the 8-bit byte (and not e.g. the 7-bit one)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MMS" completeForm="multimedia messaging service" language="en"/>

 		<explanation language="en">

 			<text>

 				a service or particular multimedia message sent from or to a mobile phone;

 				in contrast to SMS, supports not only text but also pictures, videos, sounds…

 				thus subscriber can take a photo by his mobile phone and easily send it to a friend;

 				other use case is AOMT messaging e.g. news with pictures or some premium content;

 				MMS requires special infrastructure including MMSC deployed by the operator

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="DMS" completeForm="donors message service" language="en"/>

 		<term abbreviation="DMS" completeForm="dárcovská SMS" language="cs"/>

 		<explanation language="en">

 			<text>

 				specific kind of MOAT short message which is used to donate money to charity or some organization;

 				the donation is charged from sender's pre-paid balance or in his monthly bill alongside the fees for placed calls and sent SMS

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="EMS" completeForm="enhanced messaging service" language="en"/>

 		<explanation language="en">

 			<text>

 				an application-level extension to SMS;

 				adds some new features like formatted text, pictures or sounds

 				but works with existing networks (unlike MMS which requires new infrastructure)

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SMIL" completeForm="synchronized multimedia integration language" language="en"/>

 		<explanation language="en">

 			<text>

 				a markup language for describing multimedia presentations;

 				describes timing, layout, animations etc.

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SVG" completeForm="scalable vector graphics" language="en"/>

 		<explanation language="en"><text>an XML-based file format for vector graphics</text></explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="IM" completeForm="instant messaging" language="en"/>

 		<term abbreviation="OTT" completeForm="over the top" language="en"/>

 		<explanation language="en">

 			<text>

 				a kind of electronic communication between two persons or a group chat;

 				compared to e-mail, IM messages are short (few words, sentence) and the other side is expected (depending on his/her online status) to read and respond it immediately;

 				compared to SMS, IM messages are cheap – typically free of charge;

 				important IM feature is presence – the sender knows current status of the recipient: online, offline, away, busy etc.;

 				IM is rooted in the computer world but nowadays it is often used also on mobile phones as an alternative to (expensive) SMS – in such case it is called OTT and requires mobile Internet connectivity;

 				IM messages are usually transferred over an TCP/IP protocol – good example is Jabber/XMPP which is free and open protocol for IM and presence based on XML

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="IMS" completeForm="IP Multimedia Subsystem" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="RCS" completeForm="Rich Communication Suite" language="en"/>

 		<term abbreviation="RCSE" completeForm="" language="en"/>

 		<term abbreviation="RCSx" completeForm="" language="en"/>

 		<term abbreviation="" completeForm="Joyn" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="XMPP" completeForm="extensible messaging and presence protocol" language="en"/>

 		<term abbreviation="" completeForm="jabber" language="en"/><!-- original name -->

 		<explanation language="en">

 			<text>

 				a communication protocol for messaging based on XML;

 				used for transferring

 					IM messages,

 					presence information (statuses like: online, busy, away etc.),

 					contact list (called roster here) management,

 					singaling of VoIP and video, file transfers etc.;

 				can be also used as generic messaging protocol for connecting computer systems (not only human-human interaction)

 				or for human-computer interaction (for accessing services like dictionaries, weather forecast or TV guide)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="roster" language="en"/>

 		<explanation language="en"><text>a contact list; term used by Jabber/XMPP</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="IMAP4" completeForm="Internet message access protocol version 4" language="en"/>

 		<term abbreviation="IMAP" completeForm="Internet message access protocol" language="en"/>

 		<explanation language="en">

 			<text>

 				a text-based client-server protocol for accessing e-mail mailbox;

 				supports

 					multiple hierarchical folders (inbox, sent, drafts… or user defined),

 					marging messages with tags/flags,

 					notifications of new messages from server to client (the client does not have to periodically check the inbox and just waits for new messages),

 					full-text search and other features;

 				messages usually stays at server storage after reading which allows using multiple client programs/devices;

 				is more complex than POP3 protocol;

 				uses TCP and standard port is 143 (STARTTLS or unencrypted) or 993 (SSL/TLS)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="POP3" completeForm="post office protocol version 3" language="en"/>

 		<term abbreviation="POP" completeForm="post office protocol" language="en"/>

 		<explanation language="en">

 			<text>

 				a text-based client-server protocol for accessing e-mail mailbox;

 				messages are usually deleted from server after reading and are stored only on the client side;

 				nowadays the more advanced IMAP4 protocol is often used instead of POP3;

 				uses TCP and standard port is 110 (STARTTLS or unencrypted) or 995 (SSL/TLS)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SMTP" completeForm="simple mail transfer protocol" language="en"/>

 		<term abbreviation="ESMTP" completeForm="Extended SMTP" language="en"/>

 		<explanation language="en">

 			<text>

 				a text-based client-server protocol for sending e-mail messages

 				uses TCP and standard port is 25 (STARTTLS or unencrypted) or 465 (SSL/TLS) or 587 (STARTTLS or unencrypted for Message Submission – RFC 6409);

 				is defined in RFC 5321

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="LMTP" completeForm="local mail transfer protocol" language="en"/>

 		<explanation language="en">

 			<text>

 				a derivative of ESMTP designed for transferring messages locally from MTA component to MDA (mail storage, no queue);

 				uses TCP/IP but must not use port 25 (SMTP);

 				is defined in RFC 2033

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MUA" completeForm="mail user agent" language="en"/>

 		<explanation language="en">

 			<text>

 				an e-mail client – a software used for managing user's e-mail;

 				because the MUA (like most client software) runs only when user needs it,

 					the messages from the Internet are received by a remote MTA over the SMTP protocol,

 					then delivered using an MDA into user's remote mailbox,

 					from which they are obtained by the MUA using POP3 or IMAP4 protocols;

 				when sending an e-mail, the MUA composes the message in RFC 5322 format and then submits it using the SMTP protocol to a MTA or MSA server;

 				examples of MUA: Mozilla Thunderbird, KMail, Evolution, Mutt, Lotus Notes

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MTA" completeForm="message transfer agent" language="en"/>

 		<term abbreviation="MTA" completeForm="mail transfer agent" language="en"/>

 		<term abbreviation="MX" completeForm=" mail exchanger" language="en"/>

 		<explanation language="en">

 			<text>

 				a software component which transferres e-mails from one computer to another using SMTP protocol (implements both sending and receiving);

 				messages can be passed over network (relayed) or for local recipients stored locally (passing them to the MDA using LMTP);

 				examples of MTA: Postfix, Sendmail, Exim, Courier Mail Server, Apache James

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MSA" completeForm="message submission agent" language="en"/>

 		<explanation language="en">

 			<text>

 				a software component dedicated to receive e-mails from MUA;

 				cooperates with MTA or is often integrated in MTA as one of its features;

 				uses a variant of SMTP (RFC 6409) and TCP port 587 (different than SMTP/MTA port 25)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MDA" completeForm="message delivery agent" language="en"/>

 		<term abbreviation="LDA" completeForm="local delivery agent" language="en"/>

 		<explanation language="en">

 			<text>

 				a software component that receives e-mail from the MTA and stores them in the recipient's mailbox;

 				the MDA can also apply Sieve filters on processed messages;

 				examples of MDA: Dovecot, Cyrus IMAP, procmail, maildrop

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MRA" completeForm="message retrieval agent" language="en"/>

 		<explanation language="en">

 			<text>

 				a software component that fetches e-mails from remote server (over POP3 or IMAP4 protocol)

 				and then passes them to the MDA for local storage, or over SMTP to an MTA, or directly delivers it to the mailbox, or prints to standard output etc.;

 				implements pull (not push) approach: fetches messages periodically (or on user's demand)

 				instead of waiting for incoming messages and receiving them immediatelly when they emerge (like MTA does);

 				examples of MRA: fetchmail, getmail

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="sieve" language="en"/>

 		<explanation language="en">

 			<text>

 				a standardized language for describing e-mail filters;

 				the MDA can apply system-wide or user-defined filters on incoming messages;

 				a filter has conditions (connected by logical operators: AND, OR…) like „message header contains value X“

 				and actions that will be done with the message like „file into folder X“ or „add flag/label X“ or „redirect message to some.address@example.com“ or „discard message“;

 				filters are executed on the server where MDA resides,

 				so they are independent of the MUA currently used by the user

 				and works even if the user is offline (useful for OOTO messages when the user is on vacation)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="OOTO" completeForm="out of the office" language="en"/>

 		<explanation language="en">

 			<text>

 				an automatic response on a message (e-mail, SMS etc.) which is sent when the recipient is for example on vacation and can't respond immediately;

 				in case of e-mail it can be easily configured as a Sieve filter

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MIME" completeForm="multipurpose Internet mail extensions" language="en"/>

 		<explanation language="en">

 			<text>

 				an Internet standard for extended e-mail format which supports

 					international character sets for body parts,

 					international characters in message headers,

 					attachements of various types,

 					multipart messages;

 				MIME message itself is a human-readable text starting with header section and having one or more body parts;

 				binary or non-ASCII values are encoded in several ways described by the MIME's RFCs;

 				the content types defined by MIME is used also outside of e-mail – for indicating format of the content in HTTP, databases or operating systems

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SAP" completeForm="sms application protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SPID" completeForm="service provider ID" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="UTF-8" completeForm="unicode transformation format 8-bit" language="en"/>

 		<explanation language="en">

 			<text>

 				an character encoding that can represent every character in the Unicode character set;

 				is multibyte and variable-width encoding which means that one character can be represented by one or more bytes

 				(i.e. character length of the text does not have to be equal to byte lenght of the data),

 				in case of UTF-8 it is from 1 byte up to 6 bytes per character;

 				is backward compatible with ASCII – one-byte characters in UTF-8 are encoded in same way as in ACSII;

 				nowadays is widely used: on web, in e-mail, in operating systems (file names), in XML files etc.

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="UCS-2" completeForm="universal character set 2-byte" language="en"/>

 		<explanation language="en">

 			<text>

 				an multibyte but fixed-length (2 byte) character encoding;

 				sometimes is used for SMS when international characters are needed – such single message has only 70 characters instead of 160 (7-bit encoding);

 				for general use it was superseded by UTF-16 (in Unicode 2.0 in 1996)

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="UTF-16" completeForm="unicode transformation format 16-bit" language="en"/>

 		<explanation language="en">

 			<text>

 				an multibyte and variable-width encoding for Unicode codepoints from 0 to 0x10FFFF;

 				successor of UCS-2 encoding (for range 0-0xFFFF they have same values)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SMPP" completeForm="short message peer-to-peer" language="en"/>

 		<explanation language="en">

 			<text>

 				open and industry standard protocol for transferring SMS messages among service centers (SC), applications (ESME) and routing entities (RE);

 				was designed by the Aldiscon company (later Logica CMG and later Acision);

 				binary PDUs are transported over TCP/IP or X.25 connection

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 		<tag>acision</tag>

 	</concept>

 	<concept>

 		<term abbreviation="NMS" completeForm="network management system" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SNMP" completeForm="simple network management protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MIB" completeForm="management information base" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="OID" completeForm="object identifier" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SPBP" completeForm="SMS prepaid billing protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 		<tag>acision</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="RTPP" completeForm="Real Time Payment Protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="BIP" completeForm="billing interface protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="LTE" completeForm="Long Term Evolution" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="VoLTE" completeForm="Voice over LTE" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="FTTH" completeForm=" fiber to the home" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="CIC" completeForm="Carrier Identification Code" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="E.164" language="en"/>

 		<explanation language="en">

 			<text>

 				an ITU-T recommendation;

 				full title: The international public telecommunication numbering plan;

 				defines the numbering plan of the PSTN and general format of international phone numbers

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="MSISDN" completeForm="mobile subscriber integrated services digital network number" language="en"/>

 		<term abbreviation="MSISDN" completeForm="mobile subscriber ISDN number" language="en"/>

 		<term abbreviation="MSISDN" completeForm="mobile station international ISDN number" language="en"/>

 		<explanation language="en">

 			<text>

 				a globally unique indentifier of a subscription in a GSM or a UMTS network;

 				follows numbering plan defined by E.164 – international phone number

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="IMEI" completeForm="international mobile station equipment identity" language="en"/>

 		<explanation language="en">

 			<text>

 				a number used to identify GSM, UMTS, LTE, iDEN or satelite mobile phones;

 				it identifies the device not the subscribtion (like IMSI or MSISDN);

 				on most phones can be displayed by typing *#06#

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="IMSI" completeForm="international mobile subscriber identity" language="en"/>

 		<explanation language="en">

 			<text>

 				a globally unique identifier stored on the SIM card used in GSM, UMTS and LTE networks;

 				a 64 bit value usually presented as 15 digit number;

 				consists of MCC (country code), MNC (network code) and MSIN (subscription ID)

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="MCC" completeForm="mobile country code" language="en"/>

 		<explanation language="en">

 			<text>

 				a unique numeric identifier of a country;

 				a part of IMSI;

 				often used in tuple with MNC;

 			</text>

 		</explanation>

 	</concept>

 	<!--

 		Lists of MCC/MNC:

 		https://en.wikipedia.org/wiki/Mobile_country_code

 		http://wammu.eu/tools/countries/

 		http://wammu.eu/tools/networks/

 	-->

 	<concept>

 		<term abbreviation="MNC" completeForm="mobile network code" language="en"/>

 		<explanation language="en">

 			<text>

 				a unique numeric identifier of a mobile network (carrier);

 				a part of IMSI;

 				often used in tuple with MCC

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="MSIN" completeForm="mobile subscription identification number" language="en"/>

 		<term abbreviation="MIN" completeForm="mobile identification number" language="en"/>

 		<explanation language="en">

 			<text>

 				a part of IMSI

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="Ki" completeForm="" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="SIM" completeForm="subscriber identification module" language="en"/>

 		<term abbreviation="SIM" completeForm="subscriber identity module" language="en"/>

 		<explanation language="en">

 			<text>

 				a smartcard which contains IMSI, ke and cryptographic functions;

 				is used to identify and authenticate subscribers in mobile phone networks

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="ICCID" completeForm="integrated circuit card identifier" language="en"/>

 		<!-- https://en.wikipedia.org/wiki/Subscriber_identity_module#ICCID -->

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="GT" completeForm="global title" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="SCCP" completeForm="signalling connection control part" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="MWC" completeForm="Mobile World Congress" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="ITU" completeForm="International Telecommunication Union" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="3GPP" completeForm="3rd Generation Partnership Project" language="en"/>

 		<term abbreviation="TGPP" completeForm="Third Generation Partnership Project" language="en"/><!-- used as an identifier if can not start with number -->

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="ASN.1" completeForm="abstract syntax notation one" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="X.400" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="X.500" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="X.509" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="BER" completeForm="basic encoding rules" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="DER" completeForm="distinguished encoding rules" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="CER" completeForm="canonical encoding rules" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="PER" completeForm="packed encoding rules" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="XER" completeForm="XML Encoding Rules" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="EMV" completeForm="Europay, MasterCard and Visa" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>finance</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AVP" completeForm="attribute-value pair" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="TLV" completeForm="type-length-value" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="PDU" completeForm="protocol data unit" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MM1" completeForm="" language="en"/>

 		<explanation language="en">

 			<text>

 				an MMS protocol used between a Mobile Station and an MMSC;

 				is based on WAP and SMS

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MM7" completeForm="" language="en"/>

 		<explanation language="en">

 			<text>

 				an MMS protocol used between an MMSC and VASP;

 				is based on SOAP, HTTP and MIME

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AAA" completeForm="authentication, authorization and accounting" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="Diameter" language="en"/>

 		<explanation language="en">

 			<text>

 				an AAA protocol and a successor of the RADIUS protocol;

 				consists of the base protocol and many „Diameter Applications“ (protocols based on Diameter)

 				e.g.

 					Diameter Credit-Control Application,

 					Diameter Session Initiation Protocol Application or

 					Diameter Extensible Authentication Protocol Application

 			</text>

 		</explanation>

 		<tag>security</tag>

 		<tag>charging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="RADIUS" completeForm="remote access dial in user service" language="en"/>

 		<explanation language="en">

 			<text>

 				an AAA protocol and the predecessor of the Diameter protocol;

 			</text>

 		</explanation>

 		<tag>security</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SCAP" completeForm="service charging application protocol" language="en"/>

 		<term abbreviation="SCAPv2" completeForm="service charging application protocol version 2" language="en"/>

 		<term abbreviation="" completeForm="Draft 8" language="en"/>

 		<term abbreviation="" completeForm="Draft-8" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>ericsson</tag>

 		<tag>charging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="DCC" completeForm="Diameter credit control" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="DAAC" completeForm="Diameter accounting and authorization control" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SPI" completeForm="service parameter info" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="result code" language="en"/>

 		<explanation language="en">

 			<text>

 				a number which represents the result of an operation in the Diameter protocol;

 				codes are divided into several groups:

 					1xxx – Informational,

 					2xxx – Success,

 					3xxx – Protocol errors,

 					4xxx – Transient failures,

 					5xxx – Permanent failure;

 				for example 2001 means success, 2002 limited success, 3001 unsupported command or 5001 unsupported AVP

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="CCR" completeForm="Credit-Control-Request" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="CCA" completeForm="Credit-Control-Answer" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="CCN" completeForm="Charging Control Node" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="IN" completeForm="Intelligent Network" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>nsn</tag>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="BS" completeForm="billing system" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="CTF" completeForm="Charging Trigger Function" language="en"/>

 		<explanation language="en">

 			<text>

 				one of two peers involved in charging process;

 				CTF decides how to charge particular subscriber for specific service;

 				issues requests to the OCF

 			</text>

 		</explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="OCF" completeForm="Online Charging Function" language="en"/>

 		<explanation language="en">

 			<text>

 				one of two peers involved in charging process;

 				accepts requests from CTF and performs actual charging

 				based on the message type, service logic, user's profile or other circumstances

 			</text>

 		</explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="charged party" language="en"/>

 		<!-- A, B, AB, - RTPP/MMSC -->

 		<explanation language="en">

 			<text>

 				the party (sender or recipient) who is charged for the service (e.g. SMS);

 				MOMT messages (or other traffic) are typically charged to the sender (A);

 				AOMT messages (like weather forecast or news) are typically charged to the recipient (B);

 				some messages can be free of charge and some can be charged to both party (AB)

 			</text>

 		</explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="subscriber" language="en"/>

 		<explanation language="en">

 			<text>

 				a subscriber of a mobile network, a customer of a telco operator

 				(but term „customer“ is ambiguous because „customer“ from SW development team point of view is the telco operator)

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="SMS gateway" language="en"/>

 		<term abbreviation="RE" completeForm="routing entity" language="en"/>

 		<explanation language="en">

 			<text>

 				a software component located between the SMSC (or other service centre) and ESME (applications);

 				passes messages in both directions,

 				uses SMPP and other messaging protocols,

 				does routing of messages, their transformations, conversions or other operations

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="pre-paid" language="en"/>

 		<explanation language="en">

 			<text>

 				a kind of subscription where the subscriber pays in advance

 				and his services are charged (usually immediately, online) from his pre-paid balance

 			</text>

 		</explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="post-paid" language="en"/>

 		<explanation language="en">

 			<text>

 				a kind of subscription where the subscriber pays later than he uses the services (usually monthly);

 				compared to pre-paid, batch processing of CDR files and offline processing is common here

 			</text>

 		</explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="CDR" completeForm="call detail record" language="en"/>

 		<term abbreviation="SDR" completeForm="service detail record" language="en"/>

 		<explanation language="en">

 			<text>

 				kind of log file in machine-readable format (ASN.1, XML, CSV etc.)

 				which describes particular usages of a service – e.g. placed phone call, sent SMS, Internet connection;

 				CDR/SDR files are used for post-paid billing (not processed online but in batch) and as documentation of usage;

 				they must be handled carefully because they contain private information (who calls or texts who);

 				always respect subscriber's privacy!

 			</text>

 		</explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MO" completeForm="mobile originated" language="en"/>

 		<explanation language="en">

 			<text>

 				traffic which comes from a cell phone resp. mobile network,

 				e.g. an SMS sent from your Handy

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MT" completeForm="mobile terminated" language="en"/>

 		<explanation language="en">

 			<text>

 				traffic which comes to a cell phone resp. mobile network,

 				e.g. a received SMS

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AO" completeForm="application originated" language="en"/>

 		<explanation language="en">

 			<text>

 				traffic which comes from an application i.e. not from the mobile network/phone,

 				e.g. some weather forecast messages generated by an SPA

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AT" completeForm="application terminated" language="en"/>

 		<explanation language="en">

 			<text>

 				traffic which comes to an application i.e. not to the mobile network/phone,

 				e.g. message sent to an application in order to subscribe the service or to send your vote

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MOMT" completeForm="mobile originated → mobile terminated" language="en"/>

 		<explanation language="en"><text>e.g. when Bob texts Alice from his phone to her phone</text></explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MOAT" completeForm="mobile originated → application terminated" language="en"/>

 		<explanation language="en"><text>e.g. if Bob subscribes a weather forecast service by sending a message from his phone</text></explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AOMT" completeForm="application originated → mobile terminated" language="en"/>

 		<explanation language="en"><text>e.g. if Alice receives to her phone a news message which she has previously subscribed</text></explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AOAT" completeForm="application originated → application terminated" language="en"/>

 		<explanation language="en">

 			<text>

 				if two applications communicates over an SMS gateway and there are no cell phones involved;

 				this is pretty rare, but somewhere you can meet such configuration

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="Handy" language="de"/>

 		<explanation language="en"><text>a cell phone</text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="billing" language="en"/>

 		<term abbreviation="" completeForm="charging" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="IEC" completeForm="immediate event charging" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="ECUR" completeForm="event charging with unit reservation" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SCUR" completeForm="session charging with unit reservation" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>charging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="COI" completeForm="community of interest" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="aliasing" language="en"/>

 		<term abbreviation="" completeForm="de-aliasing" language="en"/>

 		<term abbreviation="" completeForm="dealiasing" language="en"/>

 		<term abbreviation="" completeForm="hashing" language="en"/>

 		<explanation language="en">

 			<text>

 				when a subscriber communicates with an application (MOAT/AOMT messaging)

 				he might not want expose his identity (MSISDN or IMSI);

 				the aliasing feature (sometimes called hashing) deployed on an SMS gateway enables this communication and rewrites the subscriber's ID to some generated ID;

 				the application can then send a response on a message without knowing subscriber's identity (on the gateway the ID is translated back to real ID – de-aliasing);

 				use case:

 					subscribers can vote in some survey,

 					everyone will have one vote,

 					but the owner of the survey will not know the opinion of particular subscibers

 					because of missing their real IDs

 			</text>

 		</explanation>

 		<tag>security</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="provisioning" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="CP" completeForm="content provider" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="short code" language="en"/>

 		<term abbreviation="" completeForm="short number" language="en"/>

 		<explanation language="en">

 			<text>

 				a special kind of phone number which has few digits (e.g. four);

 				ESME usually has assigned a short number

 				thus subscriber can do MOAT messaging without remembering/typing long phone numbers;

 				texting or calling to/from this numbers might be charged with an extra rate

 				(the subscriber pays not only for the telco service but also for the VAS provided)

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="VASP" completeForm="value-added service provider" language="en"/>

 		<explanation language="en">

 			<text>

 				a provider who operates an ESME (application)

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="ESME" completeForm="external short message entity" language="en"/>

 		<term abbreviation="" completeForm="application" language="en"/>

 		<term abbreviation="LA" completeForm="large account" language="en"/>

 		<term abbreviation="VAS" completeForm="value-added service" language="en"/>

 		<term abbreviation="SPA" completeForm="service provider application" language="en"/>

 		<term abbreviation="AIM" completeForm="application interface module" language="en"/>

 		<!--

 			LA vs. AIM „Use AIM instead of LA (AIM is an MCO term, LA is a V5 term).“

 			ESME = any application which can either

 			recieve or send or both is an ESME (also known as VAS or SPA or LA)

 			LA	Large Account (also known as ESME or SPA or VAS)

 			SPA	Service Provider Application (also known as ESME or VAS or LA)

 			VAS	Value Added Service (also known as ESME or SPA or LA)

 		-->

 		<explanation language="en">

 			<text>

 				an application a software component which sends and receives messages (SMS, MMS, e-mail…) and is connected over IP (not directly attached to mobile network) and protocol like SMPP;

 				often is operated by different company than telco operator – a VASP;

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="NEP" completeForm="network end point" language="en"/>

 		<explanation language="en">

 			<text>

 				an end-point in RE where SC is connected

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AEP" completeForm="application end point" language="en"/>

 		<explanation language="en">

 			<text>

 				an end-point in RE where SPA is connected

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SPDB" completeForm="service provider database" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="MCO" completeForm="Message Controller" language="en"/>

 		<!-- bridge mezi TCP/IP a SS7 ? -->

 		<explanation language="en"><text></text></explanation>

 		<tag>acision</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SME" completeForm="short message entity" language="en"/>

 		<explanation language="en">

 			<text>

 				e.g. a mobile handset

 				(see also EMSE)

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="GSM" completeForm="Global System for Mobile communications" language="en"/>

 		<term abbreviation="GSM" completeForm="Groupe Spécial Mobile" language="fr"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="GSMA" completeForm="GSM Association" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="CDMA" completeForm="code division multiple access" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="TDMA" completeForm="time division multiple access" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="UMTS" completeForm="universal mobile telecommunications system" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="SS7" completeForm="signalling system no. 7" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="SIGTRAN" completeForm="SIGnaling TRAnsport" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="3G" completeForm="third generation" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="4G" completeForm="fourth generation" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="Baby Bell" language="en"/>

 		<!-- https://en.wikipedia.org/wiki/Regional_Bell_Operating_Company -->

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="EAIF" completeForm="external application interface" language="en"/>

 		<explanation language="en"><text>Nokia's protocol for sending and receiving MMS, is based on HTTP and transferres  binary content.</text></explanation>

 		<tag>nsn</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="UCP" completeForm="universal computer protocol" language="en"/>

 		<explanation language="en">

 			<text>

 				an SMS messaging protocol developed by CMG (later Acision)

 				as interface for ESME to SMSC;

 				an extended variant of it is called EMI

 			</text>

 		</explanation>

 		<tag>acision</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="EMI" completeForm="external machine interface" language="en"/>

 		<explanation language="en"><text>an extension of UCP</text></explanation>

 		<tag>acision</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="CIMD" completeForm="computer interface to message distribution" language="en"/>

 		<explanation language="en">

 			<text>

 				a proprietary SMS messaging protocol developed by Nokia

 				for connecting to their SMSC

 			</text>

 		</explanation>

 		<tag>nsn</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="URLP" completeForm="URL encoded message protocol" language="en"/>

 		<explanation language="en">

 			<text>

 				a simple protocol that can be used between AAG and SPA for transmitting messages;

 				uses HTTP GET method and encodes data in the URL or in HTTP response body

 			</text>

 		</explanation>

 		<tag>acision</tag>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SMAP" completeForm="short message application protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>messaging</tag>

 		<tag>protocol</tag>

 	</concept>

 	<!--

 	<concept>

 		<term abbreviation="PSA" completeForm="" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	-->

 	<concept>

 		<term abbreviation="PAP" completeForm="push access protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SC" completeForm="service center" language="en"/>

 		<term abbreviation="MC" completeForm="message centre" language="en"/>

 		<explanation language="en">

 			<text>

 				a component in telecommunication network;

 				SMSC for SMS or MMSC for MMS messages

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SMSC" completeForm="SMS service center" language="en"/>

 		<term abbreviation="SMS-SC" completeForm="Short Message Service - Service Centre" language="en"/>

 		<explanation language="en">

 			<text>

 				a component in telecommunication network dedicated to store, forward, convert and deliver SMS messages;

 				is connected to the SS7 network on one side and to routing entities (RE) using SMPP on the other side;

 				is able to process MOMT messaging and also MOAT or AOMT messaging (using RE)

 				Example of SMSC: SMSCv5

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SMSCv5" completeForm="SMS service center version 5" language="en"/>

 		<term abbreviation="v5" completeForm="" language="en"/><!-- jargon -->

 		<explanation language="en">

 			<text>

 				an implementation of SMSC from Acision;

 				runs on an OpenVMS system

 			</text>

 		</explanation>

 		<tag>acision</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MMSC" completeForm="Multimedia Messaging Service Centre" language="en"/>

 		<term abbreviation="MMSC" completeForm="MMS Service Centre" language="en"/>

 		<term abbreviation="" completeForm="MMS store and forward server" language="en"/>

 		<explanation language="en">

 			<text>

 				a kind of SC dedicated to processing multimedia messages;

 				the messaging is more comlex process than in case of SMS:

 					MO MMS message is received (in similar format to MIME e-mail) by the MMSC and stored,

 					then SC determines if the recipient is capable to receive MMS,

 					if yes, the message is put at a server with HTTP interface and the recipient gets special SMS containing the URL and downloads it over WAP,

 					if recipient is not capable he gets plain text SMS with URL and have to use computer and www browser

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="BMSC" completeForm="Broadband Messaging Service Centre" language="en"/>

 		<term abbreviation="" completeForm="Fusion" language="en"/>

 		<explanation language="en">

 			<text>

 				a consolidated messaging platform announced by the Acision company in 2013;

 				integrates RSC, SMS, MMS and voice mail

 			</text>

 		</explanation>

 		<tag>acision</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="IWG" completeForm="inter-working gateway" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="WAP" completeForm="wireless application protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="OTA" completeForm="over-the-air" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="FOTA" completeForm="firmware over the air" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="DRM" completeForm="digital restrictions management" language="en"/>

 		<term abbreviation="DRM" completeForm="digital rights management" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SyncML" completeForm="synchronization markup language" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="VoIP" completeForm="voice over IP" language="en"/>

 		<explanation language="en">

 			<text>

 				delivering voice communication (or other multimedia sessions like video) over the Internet Protocol (IP) instead of traditional telco networks;

 				there are open and standard protocols for signaling: SIP and XMPP and open protocols for the payload (audio/video) like RTP;

 				VoIP is nowadays widely used inside companies where often shares same ethernet network with computers (can be separeted by VLANs)

 				and also in households espetially for cheap overseas calls;

 				as VoIP phone can be used a computer with appropriate software or a cell phone or dedicated hardware phone;

 				there are also gateways that enable connecting old analog phones to the VoIP network

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="SIP" completeForm="session initiation protocol" language="en"/>

 		<explanation language="en">

 			<text>

 				an open signalling protocol for initiation of VoIP calls (audio, video or possibly other media sessions);

 				has similar format of headers and request/response model as HTTP;

 				transported over UDP or TCP (for TLS encryption) or SCTP;

 				for the media payload is typically used RTP protocol

 			</text>

 		</explanation>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="RTP" completeForm="real-time transport protocol" language="en"/>

 		<explanation language="en">

 			<text>

 				a standardized packet format for delivering audio and video over IP;

 				can transfer audio or video streams for telephony or television streams;

 				is used heavily in VoIP in combination with SIP;

 				can be secured with SRTP/ZRTP to avoid wiretrapping

 			</text>

 		</explanation>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SRTP" completeForm="secure RTP" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>security</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="ZRTP" completeForm="Zimmermann RTP" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>security</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="throttling" language="en"/>

 		<explanation language="en">

 			<text>

 				limiting the flow rate;

 				e.g. short messages per second

 			</text>

 		</explanation>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="keep alive" language="en"/>

 		<term abbreviation="" completeForm="keep-alive" language="en"/>

 		<explanation language="en">

 			<text>

 				a packet or message or command without useful content

 				which is sent in order to avoid closing the connection (time out) and to check, it is still working;

 				in HTTP this term means persistent connection

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="inroaming" language="en"/>

 		<explanation language="en"><text>roaming of subscribers from other operator in your network</text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="outroaming" language="en"/>

 		<explanation language="en"><text>roaming of your subscribers in other operator's network</text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="TON" completeForm="type of number" language="en"/>

 		<explanation language="en">

 			<text>

 				(0x00)	Unknown type of number;

 				(0x01)	International number;

 				(0x02)	National number;

 				(0x03)	Network specific number;

 				(0x04)	Subscriber number, dedicated access, short code;

 				(0x05)	Alphanumeric, in 7-bit GSM alphabet;

 				(0x06)	Abbreviated number

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="NPI" completeForm="numbering plan indicator" language="en"/>

 		<explanation language="en">

 			<text>

 				a number which indicates the numbering plan of a telephone number;

 				values:

 					(0x00)	Unknown numbering plan;

 					(0x01)	ISDN/telephone numbering plan – E.164/E.163;

 					(0x02)	Generic;

 					(0x03)	Data numbering plan – X.121;

 					(0x04)	Telex numbering plan – F.96;

 					(0x05)	Service Centre Specific plan;

 					(0x06)	Land mobile numbering plan – E.212;

 					(0x07)	ISDN/mobile numbering plan – E.214;

 					<!-- only 0-7 defined in the ITU standard Q.713 ? -->

 					(0x08)	National numbering plan;

 					(0x09)	Private numbering plan;

 					(0x0A)	ERMES numbering plan – ETSI DE/PS 3 01-3;

 					(0x0D)	Binary Internet addres – IP;

 					(0x0E)	Alphanumeric Internet address

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="PID" completeForm="protocol identifier" language="en"/>

 		<explanation language="en">

 			<text>

 				one octet of information which describes the protocol resp. type of telematic device;

 				0 means implicit (plain MOMT messages);

 				other values are described in 3GPP TS 03.40

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="PID" completeForm="process identifier" language="en"/>

 		<explanation language="en">

 			<text>

 				identifier of an process (running program) in an operating system;

 				PID 1 is usually assigned to the init process (the first process which starts other ones)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="Blue box" language="en"/>

 		<term abbreviation="" completeForm="BlueBox" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<!--

 		Orange box	https://en.wikipedia.org/wiki/Orange_box

 		Vermilion box	https://en.wikipedia.org/wiki/Vermilion_box

 		Magenta box	https://en.wikipedia.org/wiki/Magenta_box

 	-->

 	<concept>

 		<term abbreviation="" completeForm="Orange box" language="en"/>

 		<term abbreviation="" completeForm="OrangeBox" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="Vermilion box" language="en"/>

 		<term abbreviation="" completeForm="VermilionBox" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="Magenta box" language="en"/>

 		<term abbreviation="" completeForm="MagentaBox" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="hack" language="en"/>

 		<term abbreviation="" completeForm="hacking" language="en"/>

 		<term abbreviation="" completeForm="hacker" language="en"/>

 		<explanation language="en">

 			<text>

 				hacker is an interrogative person interested in internal principles of things;

 				often it is a software developer or a system administrator but hacking is also possible outside the digital world;

 				hacking is the activity of these people – usually

 					improving a software by adding new features

 					or discovering secrets in existing software or hardware systems

 					or running extraordinary configurations or combinations of components;

 				hack is the product of their work – e.g. improved computer program or piece of hardware;

 				<!-- hack can mean also the insctructions how to do it; -->

 				don't confuse with „cracker“

 			</text>

 			<!--

 				RMS - https://www.gnu.org/philosophy/rms-hack.html

 				„someone who enjoys playful cleverness, especially in programming but other media are also possible“

 				ESR - http://www.catb.org/~esr/jargon/html/H/hacker.html

 				[originally, someone who makes furniture with an axe] 

 				1. A person who enjoys exploring the details of programmable systems and how to stretch their capabilities, as opposed to most users, who prefer to learn only the minimum necessary. RFC1392, the Internet Users' Glossary, usefully amplifies this as: A person who delights in having an intimate understanding of the internal workings of a system, computers and computer networks in particular.

 				2. One who programs enthusiastically (even obsessively) or who enjoys programming rather than just theorizing about programming. 

 				3. A person capable of appreciating hack value. 

 				4. A person who is good at programming quickly. 

 				5. An expert at a particular program, or one who frequently does work using it or on it; as in ‘a Unix hacker’. (Definitions 1 through 5 are correlated, and people who fit them congregate.) 

 				6. An expert or enthusiast of any kind. One might be an astronomy hacker, for example. 

 				7. One who enjoys the intellectual challenge of creatively overcoming or circumventing limitations. 

 				8. [deprecated] A malicious meddler who tries to discover sensitive information by poking around. Hence password hacker, network hacker. The correct term for this sense is cracker.

 				The term ‘hacker’ also tends to connote membership in the global community defined by the net (see the network. For discussion of some of the basics of this culture, see the How To Become A Hacker FAQ. It also implies that the person described is seen to subscribe to some version of the hacker ethic (see hacker ethic).

 				It is better to be described as a hacker by others than to describe oneself that way. Hackers consider themselves something of an elite (a meritocracy based on ability), though one to which new members are gladly welcome. There is thus a certain ego satisfaction to be had in identifying yourself as a hacker (but if you claim to be one and are not, you'll quickly be labeled bogus). See also geek, wannabee.

 				This term seems to have been first adopted as a badge in the 1960s by the hacker culture surrounding TMRC and the MIT AI Lab. We have a report that it was used in a sense close to this entry's by teenage radio hams and electronics tinkerers in the mid-1950s.

 				RFC 1392 - https://tools.ietf.org/html/rfc1392

 				A person who delights in having an intimate understanding of the

 				internal workings of a system, computers and computer networks in

 				particular.  The term is often misused in a pejorative context,

 				where "cracker" would be the correct term.  See also: cracker.

 			-->

 		</explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="crack" language="en"/>

 		<term abbreviation="" completeForm="cracking" language="en"/>

 		<term abbreviation="" completeForm="cracker" language="en"/>

 		<explanation language="en">

 			<text>

 				someone who breaks the security protections in order to get unauthorized access to a computer system;

 				they often misuse their skills to steal private data, destroy systems or steal money;

 				don't confuse with „hacker“

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="phreak" language="en"/>

 		<term abbreviation="" completeForm="phreaking" language="en"/>

 		<term abbreviation="" completeForm="phreaker" language="en"/>

 		<explanation language="en">

 			<text>

 				a hacker interested in phone systems or telecommunications in general;

 				sometimes they can become cracker if they don't only experiment but misuse telephone networks excessively (fraud);

 				the term is a portmanteau of the words „phone“ and „freak“

 			</text>

 		</explanation>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AAGP" completeForm="Acision Application Gateway Provisioning" language="en"/>

 		<term abbreviation="GAS" completeForm="Generic application server" language="en"/>

 		<term abbreviation="CPS" completeForm="Central provisioning system" language="en"/>

 		<explanation language="en">

 			<text>

 				a software component developed by the Acision company;

 				a provisioning tool for AAG and other products of this company;

 				can be used as generic provisioning tool for any product provided that particular connector exists;

 				has web GUI and several APIs

 			</text>

 		</explanation>

 		<tag>acision</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AAG" completeForm="Acision Application Gateway" language="en"/>

 		<term abbreviation="OMG" completeForm="Open Messaging Gateway" language="en"/>

 		<explanation language="en">

 			<text>

 				a software component developed by the Acision company;

 				typical use case is: a messaging gateway between SMSC and applications (ESME)

 			</text>

 		</explanation>

 		<tag>acision</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="GBG" completeForm="General Billing Gateway" language="en"/>

 		<term abbreviation="AFG" completeForm="Acision Flexible Gateway" language="en"/>

 		<term abbreviation="TGC" completeForm="Test Gateway Component" language="en"/>

 		<term abbreviation="UGC" completeForm="Universal Gateway Component" language="en"/>

 		<explanation language="en">

 			<text>

 				a software component developed by the Acision company;

 				works as a messaging gateway and can interconnect systems talking many various messaging protocols;

 				is highly configurable and can translate and transform messages in many formats;

 				original purpose was doing a gateway for billing messages comming from e.g. SMSC to some billing system

 			</text>

 		</explanation>

 		<tag>acision</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="UGC" completeForm="user generated content" language="en"/>

 		<explanation language="en">

 			<text>

 				content in various media formats (text, pictures, video, sound…)

 				which is created by users (or subscribers);

 				e.g. photos taken by mobile and sent over MMS, e-mail or web to some server which displays them to other users

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="VCS" completeForm="version control system" language="en"/>

 		<term abbreviation="RCS" completeForm="revision control system" language="en"/>

 		<explanation language="en">

 			<text>

 				a software tool used for management of changes in documents;

 				often is used for managing source code and other artifacts (like documentation or analytic models) created during software development;

 				VCS tracks versions of particular files or changesets, branches, tags (named revisions);

 				examples of traditional centralized VCS: SCCS, RCS, CVS or SVN (quite modern but centralized);

 				nowadays are very popular decentralized systems (DVCS)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="DVCS" completeForm="distributed version control system" language="en"/>

 		<term abbreviation="DRCS" completeForm="distributed revision control system" language="en"/>

 		<explanation language="en">

 			<text>

 				kind of version control system which allows not only workflow with one central server

 				but also decentralized workflows where changesets are pushed or pulled between particular nodes;

 				each node has typically full repository clone with all the history (commits, branches, tags);

 				this facilitates offline work –

 					developer can do commits or work with branches and tags even if he is offline –

 					and after going online,

 						he pushed his work to other developers

 						or to the central repository

 						or his work is pulled by others;

 				other advantage is easy backup – just clone the repository and then do push/pull from the working one;

 				Examples of DVCS: Mercurial (Hg), Git, Bazaar (bzr), Monotone (mtn), Fossil, GNU arch, Darcs, DCVS or SVK

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SCM" completeForm="software configuration management" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="hg" completeForm="mercurial" language="en"/>

 		<explanation language="en"><text>a distributed version control system</text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="cvs" completeForm="Concurrent Versions System" language="en"/>

 		<explanation language="en"><text>a centralized version control system</text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="svn" completeForm="Subversion" language="en"/>

 		<explanation language="en"><text>a centralized version control system</text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="bzr" completeForm="Bazaar" language="en"/>

 		<explanation language="en"><text>a distributed version control system</text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="git" language="en"/>

 		<explanation language="en"><text>a distributed version control system</text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="XML" completeForm="eXtensible markup language" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="xmlns" completeForm="XML name space" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="DTD" completeForm="document type definition" language="en"/>

 		<explanation language="en">

 			<text>

 				a schema language for XML;

 				used to describe the format based on XML

 				and perform validations of XML documents

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="XSD" completeForm="XML schema definition" language="en"/>

 		<explanation language="en">

 			<text>

 				a schema language for XML;

 				used to describe the format based on XML

 				and perform validations of XML documents

 				XSD itself is written in XML;

 				is more powerful than DTD

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="Schematron" language="en"/>

 		<explanation language="en">

 			<text>

 				a validation language;

 				can describe formats based on XML like XSD or DTD does, but has entirely different approach;

 				Schematron is rule-based – defines assertions which must be met to have valid document;

 				this rules are transformed into XSL template which is executed during validation;

 				Schematron can be also combined with XSD

 					– XSD schemas (which are more declarative and more clearly represents the desired structure of the document for humans)

 					are enriched with Schematron assertions that adds more complex rules (that cannot be easily expressed in pure XSD)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="XSLT" completeForm="Extensible Stylesheet Language Transformations" language="en"/>

 		<term abbreviation="XSL" completeForm="Extensible Stylesheet Language" language="en"/>

 		<explanation language="en">

 			<text>

 				a transformation language for XML;

 				can be used e.g. for

 					conversion from one XML format to another one,

 					for generating (plain) text or HTML,

 					for user friendly visualisation of XML data (XHTML or SVG output),

 					or for validations (raise error message on invalid input, see also Schematron);

 				XSL templates are also written in XML

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="XQuery" language="en"/>

 		<explanation language="en">

 			<text>

 				functional programming language for processing XML and other data

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="XPath" completeForm="XML Path Language" language="en"/>

 		<explanation language="en">

 			<text>

 				a query language for selecting XML nodes;

 				an XPath expression can also compute values and call XPath functions

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="Ant" language="en"/>

 		<explanation language="en">

 			<text>

 				a tool for automating software build processes;

 				does similar job like GNU Make, but is written in and for Java;

 				equivalent for the Makefile is here build.xml which describes particular tasks and their dependencies;

 				there is lot of tasks distributed with Apache Ant e.g.

 					compilation of Java code,

 					unit testing,

 					running XSLT transformations,

 					packing JARs and other archives,

 					copying and moving files

 					or calling system commands;

 				and user can also write own tasks in Java

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="mvn" completeForm="Maven" language="en"/>

 		<explanation language="en">

 			<text>

 				a tool for automating software build processes;

 				compared to Ant, Maven is much more declarative instead of procedural and is strongly focused on resolving dependencies on modules, components, libraries;

 				dependencies (libraries) of a project are automatically downloaded from a repository;

 				projects in Maven are described by a POM file

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="POM" completeForm="Project Object Model" language="en"/>

 		<explanation language="en">

 			<text>

 				an XML configuration file which describes one Maven project;

 				contains project metadata like name, owner, version, dependencies

 				and phases of its build process

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="Java" language="en"/>

 		<explanation language="en">

 			<text>

 				an object-oriented programming language designed by James Gosling at Sun Microsystems;

 				Java source code is compiled into byte code (.class files) which can be executed in JVM on many architectures and operating systems;

 				Java is completely free software, there is OpenJDK and standard library distributed under GNU GPL license;

 				there is also GNU Classpath – an independent and free software implementation of the standard library;

 				Java is popular and well established enterprise-grade software platform

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="JVM" completeForm="Java virtual machine" language="en"/>

 		<explanation language="en">

 			<text>

 				a runtime environment for running Java byte code;

 				there is lot of programming languages that can be compiled into the bytecode and executed in JVM e.g.

 					Clojure (a Lisp dialect),

 					Scala (OOP and functional language),

 					Groovy (a scripting language),

 					Jython (an implementation of Python),

 					JRuby

 					or Rhino (JavaScript)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="JavaDoc" completeForm="Java documentation" language="en"/>

 		<explanation language="en">

 			<text>

 				documentation of Java source code (classes, enumerations, interfaces, packages);

 				describes API and software's internals;

 				is useful for developers, not too much for end-users

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="Erlang" language="en"/>

 		<explanation language="en">

 			<text>

 				a functional programming language developed in Ericsson;

 				influenced by Prolog and SmallTalk languages;

 				Erlang implementation is a free software

 			</text>

 		</explanation>

 		<tag>ericsson</tag>

 	</concept>

 	<concept>

 		<term abbreviation="RegEx" completeForm="Regular Expression" language="en"/>

 		<term abbreviation="RegExp" completeForm="Regular Expression" language="en"/>

 		<term abbreviation="RE" completeForm="Regular Expression" language="en"/>

 		<explanation language="en">

 			<text>

 				an expression (sequence of characters) which forms a pattern that can be used for string matching –

 				finding occurrences of the pattern in the text or evaluating whether the whole text matches the pattern;

 				Example: regular expression (a|b)cde\d+ matches strings acde123 or bcde0 but not cde1 or acdex

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="PCRE" completeForm=" Perl Compatible Regular Expressions" language="en"/>

 		<explanation language="en">

 			<text>

 				a C library for regular expressions compatible with Perl's RegEx dialect

 				or this dialect itself

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="Perl" completeForm="Practical Extraction and Reporting Language" language="en"/>

 		<explanation language="en">

 			<text>

 				an interpreted dynamic programming language;

 				popular in UNIX environment for scripting and text processing;

 				Perl syntax allows very effective and elegant notation especially while working with regular expressions, but sometimes it is hard to read;

 				its implementation is free software

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="POSIX" completeForm="Portable Operating System Interface" language="en"/>

 		<explanation language="en">

 			<text>

 				a family of standards for maintaining compatibility between operating systems;

 				defines API, command line shells and utility interfaces

 				and thus brings compatibility amog many variants of unix and unix-like operating systems;

 				the name POSIX was suggested by Richard Stallman (the standards was formerly known as IEEE-IX);

 				there are standards for e.g. process creation and control, signals, pipes, message passing, shared memory or semaphores;

 				Examples of fully or mostly POSIX-compliant systems: AIX, IRIS, Solaris, OS X, GNU/Linux, BeOS (Haiku) or several BSD variants

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="UNIX" language="en"/>

 		<term abbreviation="Unics" completeForm="UNiplexed Information and Computing Service" language="en"/>

 		<explanation language="en">

 			<text>

 				a multitasking and multi-user operating system developed in 1969 by a group of AT&T hackers at Bell Labs;

 				has influenced many other operating systems (now called UNIX-like OS) and established distinctive UNIX culture and philosophy;

 				nowadays we have completely free software implementation called GNU (resp. GNU/Linux where Linux is operating system kernel or GNU/Hurd);

 				UNIX and UNIX-like operating systems runs on many mission-critical servers and are also used on personal computers or even mobile phones and small devices like routers or firewalls;

 				GNU/Linux runs on 95,2 % (and other 3,4 % are Unices too) of world's supercomputers with 97,4 % performance share (top500.org, June 2013 statistics)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="GNU/Linux" language="en"/>

 		<term abbreviation="" completeForm="Linux" language="en"/>

 		<explanation language="en">

 			<text>

 				the GNU operating system with Linux kernel

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="GNU" completeForm="GNU's Not Unix!" language="en"/>

 		<explanation language="en">

 			<text>

 				a Unix-like operating system that is free software and is upward-compatible with Unix;

 				the GNU Project was initially announced in September 1983 by Richard Stallman;

 				nowadays is mostly used in combination with Linux kernel and called GNU/Linux

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="GNU GPL" completeForm="GNU General Public License" language="en"/>

 		<term abbreviation="GPL" completeForm="General Public License" language="en"/>

 		<explanation language="en">

 			<text>

 				a free software and copyleft license which is used by many free software packages

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="GNU FDL" completeForm="GNU Free Documentation License" language="en"/>

 		<term abbreviation="FDL" completeForm="Free Documentation License" language="en"/>

 		<explanation language="en">

 			<text>

 				whereas GNU GPL is free and copyleft license for software,

 				the GNU FDL is similar license designed for documentaion – books, articles, drawings etc.

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="FS" completeForm="free software" language="en"/>

 		<explanation language="en">

 			<text>

 				a category of software which respects user's freedoms – user of such software has the four essential freedoms:

 					0) The freedom to run the program, for any purpose.

 					1) The freedom to study how the program works, and change it so it does your computing as you wish. Access to the source code is a precondition for this.

 					2) The freedom to redistribute copies so you can help your neighbor.

 					3) The freedom to distribute copies of your modified versions to others. By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.;

 				the term „Free software“ was defined by Richard Stallman

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="OSS" completeForm="open source software" language="en"/>

 		<explanation language="en">

 			<text>

 				a category of software similar to Free software;

 				the term „open source software“ was defined by Open Source Initiative;

 				its definition contains ten requirements like free redistribution, available source code or allowing derived works;

 				almost every open source license is also a free software license and vice versa;

 				but there is different philosophical background – the free software movement has user's freedom as the main priority

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="FSF" completeForm="Free Software Foundation" language="en"/>

 		<explanation language="en">

 			<text>

 				a non-profit organization founded by Richard Stallman on 4 October 1985 to support the free software movement;

 					has developed the GNU operating system,

 					issued licenses like GPL or FDL,

 					maintains the Free Software Definition,

 					does political campaigns and other activities related to user's freedoms;

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="OSI" completeForm="Open Source Initiative" language="en"/>

 		<explanation language="en">

 			<text>

 				an organization dedicated to promoting open-source software;

 				was founded in February 1998, by Bruce Perens and Eric S. Raymond;

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="EFF" completeForm="Electronic Frontier Foundation" language="en"/>

 		<explanation language="en">

 			<text>

 				a non-profit organization focused on protecting user's freedoms and privacy in mostly digital world;

 				fights against censorship and spying, criticises software patents

 				and promotes – among others – free speech, privacy, e-voting and network neutrality

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="OpenVMS" completeForm="Open Virtual Memory System" language="en"/>

 		<term abbreviation="VMS" completeForm="Virtual Memory System" language="en"/><!-- informally -->

 		<explanation language="en">

 			<text>

 				an operating system for VAX, Alpha and Itanium-based computers

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="VMS" completeForm="voice mail system" language="en"/><!-- informally -->

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="LDAP" completeForm="Lightweight Directory Access Protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SQL" completeForm="structured query language" language="en"/>

 		<term abbreviation="SEQUEL" completeForm="structured english query language" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="noSQL" completeForm="Not SQL" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="RDBMS" completeForm="relational database management system" language="en"/>

 		<term abbreviation="SŘDB" completeForm="systém řízení báze dat" language="cs"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="ODBC" completeForm="open database connectivity" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="JDBC" completeForm="java database connectivity" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AS" completeForm="application server" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="JBoss" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="GlassFish" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="WSDL" completeForm="web services description language" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="WADL" completeForm="web application description language" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SOAP" completeForm="simple object access protocol" language="en"/>

 		<term abbreviation="SOAP" completeForm="SOA Protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>xml</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="REST" completeForm="representational state transfer" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="EJB" completeForm="Enterprise JavaBeans" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="CORBA" completeForm="common object request broker architecture" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="IDL" completeForm="interface definition language" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="IIOP" completeForm="Internet InterORB Protocol" language="en"/>

 		<term abbreviation="GIOP" completeForm="General Inter-ORB Protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="RMI" completeForm="Remote Method Invocation" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="JAR" completeForm="Java ARchive" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="EAR" completeForm="Enterprise ARchive" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="WAR" completeForm="Web ARchive" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="RAR" completeForm="Resource Adapter aRchive" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AJP" completeForm="Apache JServ Protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="HTTP" completeForm="hypertext transfer protocol" language="en"/>

 		<term abbreviation="HTTPS" completeForm="hypertext transfer protocol secure" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SSL" completeForm="secure socket layer" language="en"/>

 		<term abbreviation="TLS" completeForm="transport layer security" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="DTLS" completeForm="datagram transport layer security" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>security</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="BASH" completeForm="Bourne Again Shell" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SH" completeForm="shell" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SSH" completeForm="secure shell" language="en"/>

 		<term abbreviation="" completeForm="OpenSSH" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SCP" completeForm="secure copy" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SFTP" completeForm="SSH file transfer protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="FTP" completeForm="file transfer protocol" language="en"/>

 		<term abbreviation="FTPS" completeForm="file transfer protocol secure" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="PGP" completeForm="Pretty Good Privacy" language="en"/>

 		<term abbreviation="GPG" completeForm="GNU Privacy Guard" language="en"/>

 		<term abbreviation="GnuPG" completeForm="GNU Privacy Guard" language="en"/>

 		<term abbreviation="OpenPGP" completeForm="Open Pretty Good Privacy" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="DSA" completeForm="digital signature algorithm" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="RSA" completeForm="Ron Rivest, Adi Shamir and Leonard Adleman" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="EC" completeForm="elliptic curve" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AES" completeForm="Advanced Encryption Standard" language="en"/>

 		<term abbreviation="AES-128" completeForm="Advanced Encryption Standard 128-bit" language="en"/>

 		<term abbreviation="AES-192" completeForm="Advanced Encryption Standard 192-bit" language="en"/>

 		<term abbreviation="AES-256" completeForm="Advanced Encryption Standard 256-bit" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="Camellia" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SHA" completeForm="secure hash algorithm" language="en"/>

 		<term abbreviation="SHA-1" completeForm="secure hash algorithm 160-bit" language="en"/>

 		<term abbreviation="SHA-2" completeForm="" language="en"/>

 		<term abbreviation="SHA-3" completeForm="" language="en"/>

 		<term abbreviation="SHA-256" completeForm="secure hash algorithm 256-bit" language="en"/>

 		<term abbreviation="SHA-512" completeForm="secure hash algorithm 512-bit" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MD4" completeForm="message-digest algorithm 4" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MD5" completeForm="message-digest algorithm 5" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="ethernet" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="LAN" completeForm="local area network" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="WAN" completeForm="wide area network" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="WLAN" completeForm="wireless local area network" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="VLAN" completeForm="virtual local area network" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="IP" completeForm="Internet Protocol" language="en"/>

 		<term abbreviation="IPv4" completeForm="Internet Protocol version 4" language="en"/>

 		<term abbreviation="IPv6" completeForm="Internet Protocol version 6" language="en"/>

 		<term abbreviation="" completeForm="IP address" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="FQDN" completeForm="fully qualified domain name" language="en"/>

 		<term abbreviation="" completeForm="absolute domain name" language="en"/>

 		<explanation language="en">

 			<text>

 				a domain name like „some-machine.example.com“ which completely specifies the location in the DNS hierarchy including the TLD;

 				compared to „some-machine“ which is not FQDN – is not globally unambiguous and will be resolved differently in different contexts

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MAC" completeForm="media access control" language="en"/>

 		<explanation language="en">

 			<text>

 				a data communication protocol, a sublayer of the layer 2 in OSI model (data link layer); 

 				a MAC address is a unique identifier of an network interface – used for IEEE 802 networks including Ethernet;

 				they are assigned by the manufacturer of the card and stored in the hardware (can be often changed by the software);

 				there are three numbering namespaces: MAC-48, EUI-48 and EUI-64;

 				the address has 6 or 8 bytes and they are usually written in HEX, octets separated by : (a colon)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="TCP" completeForm="transmission control protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="UDP" completeForm="user datagram protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SCTP" completeForm="stream control transmission protocol" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="QoS" completeForm="quality of service" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="FUP" completeForm="fair usage policy" language="en"/>

 		<explanation language="en">

 			<text>

 				a set of rules that should avoid excessive usage of a service by one user to the detriment of other user's comfort;

 				example: „You can download 10 GB at full speed every month. If you exceed this limit the speed of your connection will descend to 64 kb/s“

 			</text>

 		</explanation>

 	</concept>

 	<concept>

 		<term abbreviation="API" completeForm="application programming interface" language="en"/>

 		<explanation language="en">

 			<text>

 				specifies interaction between software components;

 				adds an abstraction layer which divides calling code and called code

 				and enables multiple implementations of such API (or SPI) like multiple databases (database drivers), file systems, remote services etc.

 				examples of API: POSIX, OpenGL, JDBC, JMS or JMX

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SPI" completeForm="service provider interface" language="en"/>

 		<explanation language="en">

 			<text>

 				a kind of API to be implemented by third party;

 				can be installed as plugin/addon/extension and used by the application over standard interface;

 				examples of SPI: JDBC, JNDI or JAXP

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="JMX" completeForm="Java management extensions" language="en"/>

 		<term abbreviation="MBean" completeForm="managed bean" language="en"/>

 		<explanation language="en">

 			<text>

 				a Java technology for monitoring and managing applications or devices;

 				similar to SNMP;

 				managed objects (MBeans) can emit events, can be asked for values (e.g. counters) or an action (method) can be called on them;

 				this native Java technology can be also adapted/translated to other protocols like SNMP or WS/SOAP and integrated with the non-Java world;

 				thanks to this abstraction, the managed object can implement only simple Java interface and don't have to deal with other protocols (which is job of generic adaptors)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="JMS" completeForm="Java message service" language="en"/>

 		<explanation language="en">

 			<text>

 				a Java API for message-oriented middleware (MOM);

 				allows JEE components to create, send, receive and read messages;

 				supports both point-to-point and publish-subscribe messaging models;

 				can be adapted/translated to many other protocols like SMTP, AMQP, XMPP or SOAP;

 				is defined in  JSR 914;

 				examples of JMS implementations: Apache ActiveMQ, OpenJMS, HornetQ

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="MOM" completeForm="message-oriented middleware" language="en"/>

 		<explanation language="en">

 			<text>

 				a software (or even hardware) infrastructure for sending and receiving messages;

 				can also offer routing and transformation features;

 				for Java the MOM API is standardized as JMS

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AMQP" completeForm="advanced message queuing protocol" language="en"/>

 		<explanation language="en">

 			<text>

 				an open and standard binary protocol for message-oriented middleware (MOM);

 				is vendor and platform independent;

 				whereas JMS defines programming API and is Java specific, the AMQP defines the wire-level protocol;

 				so JMS (or other language/platform specific API) can be used inside the system and AMQP can be used for interconnection of systems in heterogenous environment;

 				example of implementation: Apache ActiveMQ

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>messaging</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="wire-level protocol" language="en"/>

 		<explanation language="en">

 			<text>

 				the format of data sent over the network as stream of bytes;

 				an application layer protocol

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="JCA" completeForm="Java connector architecture" language="en"/>

 		<explanation language="en">

 			<text>

 				a Java EE technology for connecting application servers (AS) and enterprise information systems (EIS);

 				is similar to JDBC (which is used for connecting to databases) but is much more generic

 				and allows connecting any (often legacy) system using a specific connector

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="EIS" completeForm="enterprise information system" language="en"/>

 		<explanation language="en">

 			<text>

 				an enterprise-class software system;

 				typically high quality and critical service, large volumes of data, robust, supporting business processes

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="OSGi" completeForm="Open Services Gateway initiative" language="en"/>

 		<explanation language="en">

 			<text>

 				a framework and module system for Java;

 				allows applications with modular architecture composed from components

 				that can be loaded, started, stopped, updated or uninstalled without restarting the JVM and the application;

 				examples of OSGi implementations: Apache Felix, Equinox and Knopflerfish

 			</text>

 		</explanation>

 		<tag>computer</tag>

 		<tag>java</tag>

 	</concept>

 	<concept>

 		<term abbreviation="VPN" completeForm="virtual private network" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>security</tag>

 	</concept>

 	<concept>

 		<term abbreviation="P2P" completeForm="peer to peer" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="DNS" completeForm="domain name system" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 		<tag>protocol</tag>

 	</concept>

 	<concept>

 		<term abbreviation="ENUM" completeForm="E.164 number mapping" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="NAPTR" completeForm="naming authority pointer resource records" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="SPID" completeForm="service profile identifier" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="DN" completeForm="distinguished name" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="CN" completeForm="common name" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SN" completeForm="surname" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="DC" completeForm="domain component" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="CR" completeForm="change request" language="en"/>

 		<explanation language="en">

 			<text>

 				a request for changing a software – new features or modification of existing ones;

 				when one or more CRs are developed, they are delivered as new version of software product;

 				CR is requested by the customer (mobile network operator) and is delivered by the development team;

 				CR consists of one or more DT which are assigned to particular developers

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="DT" completeForm="development ticket" language="en"/>

 		<explanation language="en">

 			<text>

 				a task assigned to a software developer;

 				one or more DTs together usually forms a CR;

 				it is also possible to have an internal DT which is not linked to any CR (e.g. some refactoring or fixes or maintenence which was not requested by the customer);

 				each commit in the versioning system should be linked to a DT

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="TT" completeForm="trouble ticket" language="en"/>

 		<explanation language="en">

 			<text>

 				a request for fixing something in the production;

 				requires some investigation and then can be solved by changing the configuration on site or by fixing the software (development)

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="SRS" completeForm="System Requirement Specification" language="en"/>

 		<explanation language="en">

 			<text>

 				requirements on a software product or its particular change;

 				is written from the system's point of view

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="URS" completeForm="User Requirement Specification" language="en"/>

 		<explanation language="en">

 			<text>

 				requirements on a software product or its particular change;

 				is written from the user's point of view

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="engineering build" language="en"/>

 		<explanation language="en">

 			<text>

 				a build of a software product which was not done according to regular procedure and processes;

 				might be used only for testing on site or during development – not in production;

 				such software is often delivered as a tar.gz or JAR, WAR etc. file to be patched into existing installation, not as regular package (RPM, DEB etc.) as production version

 			</text>

 		</explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="monkey patching" language="en"/>

 		<explanation language="en"><text></text></explanation>

 	</concept>

 	<concept>

 		<term abbreviation="GMT" completeForm="Greenwich mean time" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="UTC" completeForm="coordinated universal time" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="TZ" completeForm="timezone" language="en"/>

 		<term abbreviation="TZ" completeForm="time-zone" language="en"/>

 		<term abbreviation="TZ" completeForm="time zone" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="IETF" completeForm="Internet Engineering Task Force" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="RFC" completeForm="request for comments" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="vendor lock-in" language="en"/>

 		<term abbreviation="" completeForm="vendor-lock-in" language="en"/>

 		<term abbreviation="" completeForm="vendor lock in" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="UT" completeForm="unit test" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="AT" completeForm="acceptance testing" language="en"/>

 		<term abbreviation="UAT" completeForm="user acceptance testing" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>

 	<concept>

 		<term abbreviation="" completeForm="code coverage" language="en"/>

 		<explanation language="en"><text></text></explanation>

 		<tag>computer</tag>

 	</concept>