1 <?xml version="1.0" encoding="UTF-8"?>
4 Copyright © 2013 František Kučera (frantovo.cz)
6 Permission is granted to copy, distribute and/or modify this document
7 under the terms of the GNU Free Documentation License, Version 1.3
8 published by the Free Software Foundation;
9 with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
10 A copy of the license is included in the section entitled "GNU
11 Free Documentation License".
13 You should have received a copy of the GNU Free Documentation License
14 along with this program. If not, see <http://www.gnu.org/licenses/>.
16 <dictionary xmlns="https://telco.frantovo.cz/xmlns/dictionary">
18 <id>fca6b6ec-34dd-4cb2-83a3-d1b8ceccb296</id>
21 <tag id="analog" name="Analog" description="classic analog telephone lines"/>
23 <tag id="acision" name="Acision" description="comes from Acision or is specific for this company"/>
24 <tag id="ericsson" name="Ericsson" description="comes from Ericsson or is specific for this company"/>
25 <tag id="nsn" name="Nokia Siemens Networks" description="comes from Nokia Siemens Networks or is specific for this company"/>
27 <tag id="charging" name="Charging" description="charging, billing"/>
28 <tag id="messaging" name="Messaging" description="sending messages, receiving messages (SMS, MMS etc.)"/>
30 <tag id="computer" name="Computer" description="general IS/ICT term"/>
31 <tag id="general" name="General" description="general term"/>
32 <tag id="finance" name="Finance" description="financial term"/>
34 <tag id="java" name="Java" description="Java and other JVM languages"/>
35 <tag id="xml" name="XML" description="eXtensible Markup Language"/>
36 <tag id="database" name="Database" description="SQL/Relational and other DBMS"/>
37 <tag id="security" name="Security" description="security and cryptography"/>
38 <tag id="protocol" name="Protocol" description="communication protocol"/>
42 <term abbreviation="MVNO" completeForm="mobile virtual network operator" language="en"/>
43 <term abbreviation="MOLO" completeForm="mobile other licensed operator" language="en"/><!-- in the United Kingdom -->
44 <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>
47 <term abbreviation="MVNE" completeForm="mobile virtual network enabler" language="en"/>
48 <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>
51 <term abbreviation="" completeForm="hot billing" language="en"/>
52 <term abbreviation="" completeForm="late billing" language="en"/>
53 <term abbreviation="" completeForm="latebiller" language="en"/>
54 <explanation language="en">
56 a technique used in charging;
57 for pre-paid subscribers the standard way to charge services is online
58 – 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;
59 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;
60 this feature requires saving state (transactions which weren't charged yet) in some persitent storage (CDR files, SQL database etc.)
61 and can be done at the billing gateway or directly at system like SMSC
67 <term abbreviation="SMS" completeForm="short message service" language="en"/>
68 <explanation language="en">
70 a service or particular short text message sent from or to a mobile phone;
71 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;
72 the number „160“ is iconic for SMS
78 <term abbreviation="" completeForm="octet" language="en"/>
79 <term abbreviation="" completeForm="byte" language="en"/>
80 <explanation language="en">
82 a unit of digital information;
83 byte (almost always) consists of 8 bits, which means 256 possible values (2^8);
84 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)
90 <term abbreviation="" completeForm="octet string" language="en"/>
91 <term abbreviation="" completeForm="OctetString" language="en"/>
92 <explanation language="en">
94 a basic data type in ASN.1, LDAP and other protocols;
95 just a byte array – an ordered sequence of zero or more octets;
96 can contain human readable text (in any character encoding) or any binary data;
97 the most generic data type
102 <term abbreviation="MMS" completeForm="multimedia messaging service" language="en"/>
103 <explanation language="en">
105 a service or particular multimedia message sent from or to a mobile phone;
106 in contrast to SMS, supports not only text but also pictures, videos, sounds…
107 thus subscriber can take a photo by his mobile phone and easily send it to a friend;
108 other use case is AOMT messaging e.g. news with pictures or some premium content;
109 MMS requires special infrastructure including MMSC deployed by the operator
115 <term abbreviation="DMS" completeForm="donors message service" language="en"/>
116 <term abbreviation="DMS" completeForm="dárcovská SMS" language="cs"/>
117 <explanation language="en">
119 specific kind of MOAT short message which is used to donate money to charity or some organization;
120 the donation is charged from sender's pre-paid balance or in his monthly bill alongside the fees for placed calls and sent SMS
126 <term abbreviation="EMS" completeForm="enhanced messaging service" language="en"/>
127 <explanation language="en">
129 an application-level extension to SMS;
130 adds some new features like formatted text, pictures or sounds
131 but works with existing networks (unlike MMS which requires new infrastructure)
137 <term abbreviation="SMIL" completeForm="synchronized multimedia integration language" language="en"/>
138 <explanation language="en">
140 a markup language for describing multimedia presentations;
141 describes timing, layout, animations etc.
148 <term abbreviation="SVG" completeForm="scalable vector graphics" language="en"/>
149 <explanation language="en"><text>an XML-based file format for vector graphics</text></explanation>
154 <term abbreviation="IM" completeForm="instant messaging" language="en"/>
155 <term abbreviation="OTT" completeForm="over the top" language="en"/>
156 <explanation language="en">
158 a kind of electronic communication between two persons or a group chat;
159 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;
160 compared to SMS, IM messages are cheap – typically free of charge;
161 important IM feature is presence – the sender knows current status of the recipient: online, offline, away, busy etc.;
162 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;
163 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
170 <term abbreviation="IMS" completeForm="IP Multimedia Subsystem" language="en"/>
171 <explanation language="en"><text></text></explanation>
175 <term abbreviation="RCS" completeForm="Rich Communication Suite" language="en"/>
176 <term abbreviation="RCSE" completeForm="" language="en"/>
177 <term abbreviation="RCSx" completeForm="" language="en"/>
178 <term abbreviation="" completeForm="Joyn" language="en"/>
179 <explanation language="en"><text></text></explanation>
183 <term abbreviation="XMPP" completeForm="extensible messaging and presence protocol" language="en"/>
184 <term abbreviation="" completeForm="jabber" language="en"/><!-- original name -->
185 <explanation language="en">
187 a communication protocol for messaging based on XML;
188 used for transferring
190 presence information (statuses like: online, busy, away etc.),
191 contact list (called roster here) management,
192 signaling of VoIP and video, file transfers etc.;
193 can be also used as generic messaging protocol for connecting computer systems (not only human-human interaction)
194 or for human-computer interaction (for accessing services like dictionaries, weather forecast or TV guide)
203 <term abbreviation="" completeForm="roster" language="en"/>
204 <explanation language="en"><text>a contact list; term used by Jabber/XMPP</text>
210 <term abbreviation="IMAP4" completeForm="Internet message access protocol version 4" language="en"/>
211 <term abbreviation="IMAP" completeForm="Internet message access protocol" language="en"/>
212 <explanation language="en">
214 a text-based client-server protocol for accessing e-mail mailbox;
216 multiple hierarchical folders (inbox, sent, drafts… or user defined),
217 marging messages with tags/flags,
218 notifications of new messages from server to client (the client does not have to periodically check the inbox and just waits for new messages),
219 full-text search and other features;
220 messages usually stays at server storage after reading which allows using multiple client programs/devices;
221 is more complex than POP3 protocol;
222 uses TCP and standard port is 143 (STARTTLS or unencrypted) or 993 (SSL/TLS)
230 <term abbreviation="POP3" completeForm="post office protocol version 3" language="en"/>
231 <term abbreviation="POP" completeForm="post office protocol" language="en"/>
232 <explanation language="en">
234 a text-based client-server protocol for accessing e-mail mailbox;
235 messages are usually deleted from server after reading and are stored only on the client side;
236 nowadays the more advanced IMAP4 protocol is often used instead of POP3;
237 uses TCP and standard port is 110 (STARTTLS or unencrypted) or 995 (SSL/TLS)
245 <term abbreviation="SMTP" completeForm="simple mail transfer protocol" language="en"/>
246 <term abbreviation="ESMTP" completeForm="Extended SMTP" language="en"/>
247 <explanation language="en">
249 a text-based client-server protocol for sending e-mail messages
250 uses TCP and standard port is 25 (STARTTLS or unencrypted) or 465 (SSL/TLS) or 587 (STARTTLS or unencrypted for Message Submission – RFC 6409);
251 is defined in RFC 5321
259 <term abbreviation="LMTP" completeForm="local mail transfer protocol" language="en"/>
260 <explanation language="en">
262 a derivative of ESMTP designed for transferring messages locally from MTA component to MDA (mail storage, no queue);
263 uses TCP/IP but must not use port 25 (SMTP);
264 is defined in RFC 2033
272 <term abbreviation="MUA" completeForm="mail user agent" language="en"/>
273 <explanation language="en">
275 an e-mail client – a software used for managing user's e-mail;
276 because the MUA (like most client software) runs only when user needs it,
277 the messages from the Internet are received by a remote MTA over the SMTP protocol,
278 then delivered using an MDA into user's remote mailbox,
279 from which they are obtained by the MUA using POP3 or IMAP4 protocols;
280 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;
281 examples of MUA: Mozilla Thunderbird, KMail, Evolution, Mutt, Lotus Notes
288 <term abbreviation="MTA" completeForm="message transfer agent" language="en"/>
289 <term abbreviation="MTA" completeForm="mail transfer agent" language="en"/>
290 <term abbreviation="MX" completeForm=" mail exchanger" language="en"/>
291 <explanation language="en">
293 a software component which transferres e-mails from one computer to another using SMTP protocol (implements both sending and receiving);
294 messages can be passed over network (relayed) or for local recipients stored locally (passing them to the MDA using LMTP);
295 examples of MTA: Postfix, Sendmail, Exim, Courier Mail Server, Apache James
302 <term abbreviation="MSA" completeForm="message submission agent" language="en"/>
303 <explanation language="en">
305 a software component dedicated to receive e-mails from MUA;
306 cooperates with MTA or is often integrated in MTA as one of its features;
307 uses a variant of SMTP (RFC 6409) and TCP port 587 (different than SMTP/MTA port 25)
314 <term abbreviation="MDA" completeForm="message delivery agent" language="en"/>
315 <term abbreviation="LDA" completeForm="local delivery agent" language="en"/>
316 <explanation language="en">
318 a software component that receives e-mail from the MTA and stores them in the recipient's mailbox;
319 the MDA can also apply Sieve filters on processed messages;
320 examples of MDA: Dovecot, Cyrus IMAP, procmail, maildrop
327 <term abbreviation="MRA" completeForm="message retrieval agent" language="en"/>
328 <explanation language="en">
330 a software component that fetches e-mails from remote server (over POP3 or IMAP4 protocol)
331 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.;
332 implements pull (not push) approach: fetches messages periodically (or on user's demand)
333 instead of waiting for incoming messages and receiving them immediatelly when they emerge (like MTA does);
334 examples of MRA: fetchmail, getmail
341 <term abbreviation="" completeForm="sieve" language="en"/>
342 <explanation language="en">
344 a standardized language for describing e-mail filters;
345 the MDA can apply system-wide or user-defined filters on incoming messages;
346 a filter has conditions (connected by logical operators: AND, OR…) like „message header contains value X“
347 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“;
348 filters are executed on the server where MDA resides,
349 so they are independent of the MUA currently used by the user
350 and works even if the user is offline (useful for OOTO messages when the user is on vacation)
357 <term abbreviation="OOTO" completeForm="out of the office" language="en"/>
358 <explanation language="en">
360 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;
361 in case of e-mail it can be easily configured as a Sieve filter
368 <term abbreviation="MIME" completeForm="multipurpose Internet mail extensions" language="en"/>
369 <explanation language="en">
371 an Internet standard for extended e-mail format which supports
372 international character sets for body parts,
373 international characters in message headers,
374 attachements of various types,
376 MIME message itself is a human-readable text starting with header section and having one or more body parts;
377 binary or non-ASCII values are encoded in several ways described by the MIME's RFCs;
378 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
385 <term abbreviation="SAP" completeForm="sms application protocol" language="en"/>
386 <explanation language="en"><text></text></explanation>
391 <term abbreviation="SPID" completeForm="service provider ID" language="en"/>
392 <explanation language="en"><text></text></explanation>
395 <term abbreviation="UTF-8" completeForm="unicode transformation format 8-bit" language="en"/>
396 <explanation language="en">
398 an character encoding that can represent every character in the Unicode character set;
399 is multibyte and variable-width encoding which means that one character can be represented by one or more bytes
400 (i.e. character length of the text does not have to be equal to byte lenght of the data),
401 in case of UTF-8 it is from 1 byte up to 6 bytes per character;
402 is backward compatible with ASCII – one-byte characters in UTF-8 are encoded in same way as in ACSII;
403 nowadays is widely used: on web, in e-mail, in operating systems (file names), in XML files etc.
408 <term abbreviation="UCS-2" completeForm="universal character set 2-byte" language="en"/>
409 <explanation language="en">
411 an multibyte but fixed-length (2 byte) character encoding;
412 sometimes is used for SMS when international characters are needed – such single message has only 70 characters instead of 160 (7-bit encoding);
413 for general use it was superseded by UTF-16 (in Unicode 2.0 in 1996)
419 <term abbreviation="UTF-16" completeForm="unicode transformation format 16-bit" language="en"/>
420 <explanation language="en">
422 an multibyte and variable-width encoding for Unicode codepoints from 0 to 0x10FFFF;
423 successor of UCS-2 encoding (for range 0-0xFFFF they have same values)
429 <term abbreviation="SMPP" completeForm="short message peer-to-peer" language="en"/>
430 <explanation language="en">
432 open and industry standard protocol for transferring SMS messages among service centers (SC), applications (ESME) and routing entities (RE);
433 was designed by the Aldiscon company (later Logica CMG and later Acision);
434 binary PDUs are transported over TCP/IP or X.25 connection
442 <term abbreviation="NMS" completeForm="network management system" language="en"/>
443 <explanation language="en"><text></text></explanation>
447 <term abbreviation="SNMP" completeForm="simple network management protocol" language="en"/>
448 <explanation language="en"><text></text></explanation>
452 <term abbreviation="MIB" completeForm="management information base" language="en"/>
453 <explanation language="en"><text></text></explanation>
457 <term abbreviation="OID" completeForm="object identifier" language="en"/>
458 <explanation language="en"><text></text></explanation>
462 <term abbreviation="SPBP" completeForm="SMS prepaid billing protocol" language="en"/>
463 <explanation language="en"><text></text></explanation>
470 <term abbreviation="RTPP" completeForm="Real Time Payment Protocol" language="en"/>
471 <explanation language="en"><text></text></explanation>
477 <term abbreviation="BIP" completeForm="billing interface protocol" language="en"/>
478 <explanation language="en"><text></text></explanation>
483 <term abbreviation="LTE" completeForm="Long Term Evolution" language="en"/>
484 <explanation language="en"><text></text></explanation>
487 <term abbreviation="VoLTE" completeForm="Voice over LTE" language="en"/>
488 <explanation language="en"><text></text></explanation>
491 <term abbreviation="FTTH" completeForm=" fiber to the home" language="en"/>
492 <explanation language="en"><text></text></explanation>
495 <term abbreviation="CIC" completeForm="Carrier Identification Code" language="en"/>
496 <explanation language="en"><text></text></explanation>
499 <term abbreviation="" completeForm="E.164" language="en"/>
500 <explanation language="en">
502 an ITU-T recommendation;
503 full title: The international public telecommunication numbering plan;
504 defines the numbering plan of the PSTN and general format of international phone numbers
509 <term abbreviation="MSISDN" completeForm="mobile subscriber integrated services digital network number" language="en"/>
510 <term abbreviation="MSISDN" completeForm="mobile subscriber ISDN number" language="en"/>
511 <term abbreviation="MSISDN" completeForm="mobile station international ISDN number" language="en"/>
512 <explanation language="en">
514 a globally unique indentifier of a subscription in a GSM or a UMTS network;
515 follows numbering plan defined by E.164 – international phone number
520 <term abbreviation="IMEI" completeForm="international mobile station equipment identity" language="en"/>
521 <explanation language="en">
523 a number used to identify GSM, UMTS, LTE, iDEN or satelite mobile phones;
524 it identifies the device not the subscribtion (like IMSI or MSISDN);
525 on most phones can be displayed by typing *#06#
530 <term abbreviation="IMSI" completeForm="international mobile subscriber identity" language="en"/>
531 <explanation language="en">
533 a globally unique identifier stored on the SIM card used in GSM, UMTS and LTE networks;
534 a 64 bit value usually presented as 15 digit number;
535 consists of MCC (country code), MNC (network code) and MSIN (subscription ID)
540 <term abbreviation="MCC" completeForm="mobile country code" language="en"/>
541 <explanation language="en">
543 a unique numeric identifier of a country;
545 often used in tuple with MNC;
551 https://en.wikipedia.org/wiki/Mobile_country_code
552 http://wammu.eu/tools/countries/
553 http://wammu.eu/tools/networks/
556 <term abbreviation="MNC" completeForm="mobile network code" language="en"/>
557 <explanation language="en">
559 a unique numeric identifier of a mobile network (carrier);
561 often used in tuple with MCC
566 <term abbreviation="MSIN" completeForm="mobile subscription identification number" language="en"/>
567 <term abbreviation="MIN" completeForm="mobile identification number" language="en"/>
568 <explanation language="en">
575 <term abbreviation="Ki" completeForm="" language="en"/>
576 <explanation language="en"><text></text></explanation>
579 <term abbreviation="SIM" completeForm="subscriber identification module" language="en"/>
580 <term abbreviation="SIM" completeForm="subscriber identity module" language="en"/>
581 <explanation language="en">
583 a smartcard which contains IMSI, ke and cryptographic functions;
584 is used to identify and authenticate subscribers in mobile phone networks
589 <term abbreviation="ICCID" completeForm="integrated circuit card identifier" language="en"/>
590 <!-- https://en.wikipedia.org/wiki/Subscriber_identity_module#ICCID -->
591 <explanation language="en"><text></text></explanation>
594 <term abbreviation="GT" completeForm="global title" language="en"/>
595 <explanation language="en"><text></text></explanation>
598 <term abbreviation="SCCP" completeForm="signalling connection control part" language="en"/>
599 <explanation language="en"><text></text></explanation>
602 <term abbreviation="MWC" completeForm="Mobile World Congress" language="en"/>
603 <explanation language="en"><text></text></explanation>
606 <term abbreviation="ITU" completeForm="International Telecommunication Union" language="en"/>
607 <explanation language="en"><text></text></explanation>
610 <term abbreviation="3GPP" completeForm="3rd Generation Partnership Project" language="en"/>
611 <term abbreviation="TGPP" completeForm="Third Generation Partnership Project" language="en"/><!-- used as an identifier if can not start with number -->
612 <explanation language="en"><text></text></explanation>
615 <term abbreviation="ASN.1" completeForm="abstract syntax notation one" language="en"/>
616 <explanation language="en"><text></text></explanation>
619 <term abbreviation="" completeForm="X.400" language="en"/>
620 <explanation language="en"><text></text></explanation>
623 <term abbreviation="" completeForm="X.500" language="en"/>
624 <explanation language="en"><text></text></explanation>
627 <term abbreviation="" completeForm="X.509" language="en"/>
628 <explanation language="en"><text></text></explanation>
633 <term abbreviation="BER" completeForm="basic encoding rules" language="en"/>
634 <explanation language="en"><text></text></explanation>
638 <term abbreviation="DER" completeForm="distinguished encoding rules" language="en"/>
639 <explanation language="en"><text></text></explanation>
643 <term abbreviation="CER" completeForm="canonical encoding rules" language="en"/>
644 <explanation language="en"><text></text></explanation>
648 <term abbreviation="PER" completeForm="packed encoding rules" language="en"/>
649 <explanation language="en"><text></text></explanation>
653 <term abbreviation="XER" completeForm="XML Encoding Rules" language="en"/>
654 <explanation language="en"><text></text></explanation>
659 <term abbreviation="EMV" completeForm="Europay, MasterCard and Visa" language="en"/>
660 <explanation language="en"><text></text></explanation>
665 <term abbreviation="AVP" completeForm="attribute-value pair" language="en"/>
666 <explanation language="en"><text></text></explanation>
670 <term abbreviation="TLV" completeForm="type-length-value" language="en"/>
671 <explanation language="en"><text></text></explanation>
675 <term abbreviation="PDU" completeForm="protocol data unit" language="en"/>
676 <explanation language="en"><text></text></explanation>
680 <term abbreviation="MM1" completeForm="" language="en"/>
681 <explanation language="en">
683 an MMS protocol used between a Mobile Station and an MMSC;
684 is based on WAP and SMS
691 <term abbreviation="MM7" completeForm="" language="en"/>
692 <explanation language="en">
694 an MMS protocol used between an MMSC and VASP;
695 is based on SOAP, HTTP and MIME
702 <term abbreviation="AAA" completeForm="authentication, authorization and accounting" language="en"/>
703 <explanation language="en"><text></text></explanation>
708 <term abbreviation="" completeForm="Diameter" language="en"/>
709 <explanation language="en">
711 an AAA protocol and a successor of the RADIUS protocol;
712 consists of the base protocol and many „Diameter Applications“ (protocols based on Diameter)
714 Diameter Credit-Control Application,
715 Diameter Session Initiation Protocol Application or
716 Diameter Extensible Authentication Protocol Application
724 <term abbreviation="RADIUS" completeForm="remote access dial in user service" language="en"/>
725 <explanation language="en">
727 an AAA protocol and the predecessor of the Diameter protocol;
734 <term abbreviation="SCAP" completeForm="service charging application protocol" language="en"/>
735 <term abbreviation="SCAPv2" completeForm="service charging application protocol version 2" language="en"/>
736 <term abbreviation="" completeForm="Draft 8" language="en"/>
737 <term abbreviation="" completeForm="Draft-8" language="en"/>
738 <explanation language="en"><text></text></explanation>
744 <term abbreviation="DCC" completeForm="Diameter credit control" language="en"/>
745 <explanation language="en"><text></text></explanation>
749 <term abbreviation="DAAC" completeForm="Diameter accounting and authorization control" language="en"/>
750 <explanation language="en"><text></text></explanation>
754 <term abbreviation="SPI" completeForm="service parameter info" language="en"/>
755 <explanation language="en"><text></text></explanation>
759 <term abbreviation="" completeForm="result code" language="en"/>
760 <explanation language="en">
762 a number which represents the result of an operation in the Diameter protocol;
763 codes are divided into several groups:
764 1xxx – Informational,
766 3xxx – Protocol errors,
767 4xxx – Transient failures,
768 5xxx – Permanent failure;
769 for example 2001 means success, 2002 limited success, 3001 unsupported command or 5001 unsupported AVP
774 <term abbreviation="CCR" completeForm="Credit-Control-Request" language="en"/>
775 <explanation language="en"><text></text></explanation>
779 <term abbreviation="CCA" completeForm="Credit-Control-Answer" language="en"/>
780 <explanation language="en"><text></text></explanation>
784 <term abbreviation="CCN" completeForm="Charging Control Node" language="en"/>
785 <explanation language="en"><text></text></explanation>
789 <term abbreviation="IN" completeForm="Intelligent Network" language="en"/>
790 <explanation language="en"><text></text></explanation>
795 <term abbreviation="BS" completeForm="billing system" language="en"/>
796 <explanation language="en"><text></text></explanation>
800 <term abbreviation="CTF" completeForm="Charging Trigger Function" language="en"/>
801 <explanation language="en">
803 one of two peers involved in charging process;
804 CTF decides how to charge particular subscriber for specific service;
805 issues requests to the OCF
811 <term abbreviation="OCF" completeForm="Online Charging Function" language="en"/>
812 <explanation language="en">
814 one of two peers involved in charging process;
815 accepts requests from CTF and performs actual charging
816 based on the message type, service logic, user's profile or other circumstances
822 <term abbreviation="" completeForm="charged party" language="en"/>
823 <!-- A, B, AB, - RTPP/MMSC -->
824 <explanation language="en">
826 the party (sender or recipient) who is charged for the service (e.g. SMS);
827 MOMT messages (or other traffic) are typically charged to the sender (A);
828 AOMT messages (like weather forecast or news) are typically charged to the recipient (B);
829 some messages can be free of charge and some can be charged to both party (AB)
835 <term abbreviation="" completeForm="subscriber" language="en"/>
836 <explanation language="en">
838 a subscriber of a mobile network, a customer of a telco operator
839 (but term „customer“ is ambiguous because „customer“ from SW development team point of view is the telco operator)
844 <term abbreviation="" completeForm="SMS gateway" language="en"/>
845 <term abbreviation="RE" completeForm="routing entity" language="en"/>
846 <explanation language="en">
848 a software component located between the SMSC (or other service centre) and ESME (applications);
849 passes messages in both directions,
850 uses SMPP and other messaging protocols,
851 does routing of messages, their transformations, conversions or other operations
856 <term abbreviation="" completeForm="pre-paid" language="en"/>
857 <explanation language="en">
859 a kind of subscription where the subscriber pays in advance
860 and his services are charged (usually immediately, online) from his pre-paid balance
866 <term abbreviation="" completeForm="post-paid" language="en"/>
867 <explanation language="en">
869 a kind of subscription where the subscriber pays later than he uses the services (usually monthly);
870 compared to pre-paid, batch processing of CDR files and offline processing is common here
876 <term abbreviation="CDR" completeForm="call detail record" language="en"/>
877 <term abbreviation="SDR" completeForm="service detail record" language="en"/>
878 <explanation language="en">
880 kind of log file in machine-readable format (ASN.1, XML, CSV etc.)
881 which describes particular usages of a service – e.g. placed phone call, sent SMS, Internet connection;
882 CDR/SDR files are used for post-paid billing (not processed online but in batch) and as documentation of usage;
883 they must be handled carefully because they contain private information (who calls or texts who);
884 always respect subscriber's privacy!
890 <term abbreviation="SDR" completeForm="software-defined radio" language="en"/>
891 <explanation language="en">
893 a radio communication system that has important parts (filters, modulators, demodulators…) implemented as computer software instead of hardware components;
894 examples: Universal Software Radio Peripheral (USRP), GNU Radio (software)
899 <term abbreviation="MO" completeForm="mobile originated" language="en"/>
900 <explanation language="en">
902 traffic which comes from a cell phone resp. mobile network,
903 e.g. an SMS sent from your Handy
909 <term abbreviation="MT" completeForm="mobile terminated" language="en"/>
910 <explanation language="en">
912 traffic which comes to a cell phone resp. mobile network,
919 <term abbreviation="AO" completeForm="application originated" language="en"/>
920 <explanation language="en">
922 traffic which comes from an application i.e. not from the mobile network/phone,
923 e.g. some weather forecast messages generated by an SPA
929 <term abbreviation="AT" completeForm="application terminated" language="en"/>
930 <explanation language="en">
932 traffic which comes to an application i.e. not to the mobile network/phone,
933 e.g. message sent to an application in order to subscribe the service or to send your vote
939 <term abbreviation="MOMT" completeForm="mobile originated → mobile terminated" language="en"/>
940 <explanation language="en"><text>e.g. when Bob texts Alice from his phone to her phone</text></explanation>
944 <term abbreviation="MOAT" completeForm="mobile originated → application terminated" language="en"/>
945 <explanation language="en"><text>e.g. if Bob subscribes a weather forecast service by sending a message from his phone</text></explanation>
949 <term abbreviation="AOMT" completeForm="application originated → mobile terminated" language="en"/>
950 <explanation language="en"><text>e.g. if Alice receives to her phone a news message which she has previously subscribed</text></explanation>
954 <term abbreviation="AOAT" completeForm="application originated → application terminated" language="en"/>
955 <explanation language="en">
957 if two applications communicates over an SMS gateway and there are no cell phones involved;
958 this is pretty rare, but somewhere you can meet such configuration
964 <term abbreviation="" completeForm="Handy" language="de"/>
965 <explanation language="en"><text>a cell phone</text></explanation>
968 <term abbreviation="" completeForm="billing" language="en"/>
969 <term abbreviation="" completeForm="charging" language="en"/>
970 <explanation language="en"><text></text></explanation>
974 <term abbreviation="IEC" completeForm="immediate event charging" language="en"/>
975 <explanation language="en"><text></text></explanation>
979 <term abbreviation="ECUR" completeForm="event charging with unit reservation" language="en"/>
980 <explanation language="en"><text></text></explanation>
984 <term abbreviation="SCUR" completeForm="session charging with unit reservation" language="en"/>
985 <explanation language="en"><text></text></explanation>
989 <term abbreviation="COI" completeForm="community of interest" language="en"/>
990 <explanation language="en"><text></text></explanation>
993 <term abbreviation="" completeForm="aliasing" language="en"/>
994 <term abbreviation="" completeForm="de-aliasing" language="en"/>
995 <term abbreviation="" completeForm="dealiasing" language="en"/>
996 <term abbreviation="" completeForm="hashing" language="en"/>
997 <explanation language="en">
999 when a subscriber communicates with an application (MOAT/AOMT messaging)
1000 he might not want expose his identity (MSISDN or IMSI);
1001 the aliasing feature (sometimes called hashing) deployed on an SMS gateway enables this communication and rewrites the subscriber's ID to some generated ID;
1002 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);
1004 subscribers can vote in some survey,
1005 everyone will have one vote,
1006 but the owner of the survey will not know the opinion of particular subscibers
1007 because of missing their real IDs
1011 <tag>messaging</tag>
1014 <term abbreviation="" completeForm="provisioning" language="en"/>
1015 <explanation language="en"><text></text></explanation>
1019 <term abbreviation="CP" completeForm="content provider" language="en"/>
1020 <explanation language="en"><text></text></explanation>
1023 <term abbreviation="" completeForm="short code" language="en"/>
1024 <term abbreviation="" completeForm="short number" language="en"/>
1025 <explanation language="en">
1027 a special kind of phone number which has few digits (e.g. four);
1028 ESME usually has assigned a short number
1029 thus subscriber can do MOAT messaging without remembering/typing long phone numbers;
1030 texting or calling to/from this numbers might be charged with an extra rate
1031 (the subscriber pays not only for the telco service but also for the VAS provided)
1034 <tag>messaging</tag>
1037 <term abbreviation="VASP" completeForm="value-added service provider" language="en"/>
1038 <explanation language="en">
1040 a provider who operates an ESME (application)
1043 <tag>messaging</tag>
1046 <term abbreviation="ESME" completeForm="external short message entity" language="en"/>
1047 <term abbreviation="" completeForm="application" language="en"/>
1048 <term abbreviation="LA" completeForm="large account" language="en"/>
1049 <term abbreviation="VAS" completeForm="value-added service" language="en"/>
1050 <term abbreviation="SPA" completeForm="service provider application" language="en"/>
1051 <term abbreviation="AIM" completeForm="application interface module" language="en"/>
1053 LA vs. AIM „Use AIM instead of LA (AIM is an MCO term, LA is a V5 term).“
1055 ESME = any application which can either
1056 recieve or send or both is an ESME (also known as VAS or SPA or LA)
1057 LA Large Account (also known as ESME or SPA or VAS)
1058 SPA Service Provider Application (also known as ESME or VAS or LA)
1059 VAS Value Added Service (also known as ESME or SPA or LA)
1061 <explanation language="en">
1063 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;
1064 often is operated by different company than telco operator – a VASP;
1067 <tag>messaging</tag>
1070 <term abbreviation="NEP" completeForm="network end point" language="en"/>
1071 <explanation language="en">
1073 an end-point in RE where SC is connected
1076 <tag>messaging</tag>
1079 <term abbreviation="AEP" completeForm="application end point" language="en"/>
1080 <explanation language="en">
1082 an end-point in RE where SPA is connected
1085 <tag>messaging</tag>
1088 <term abbreviation="SPDB" completeForm="service provider database" language="en"/>
1089 <explanation language="en"><text></text></explanation>
1092 <term abbreviation="MCO" completeForm="Message Controller" language="en"/>
1093 <!-- bridge mezi TCP/IP a SS7 ? -->
1094 <explanation language="en"><text></text></explanation>
1096 <tag>messaging</tag>
1099 <term abbreviation="SME" completeForm="short message entity" language="en"/>
1100 <explanation language="en">
1102 e.g. a mobile handset
1106 <tag>messaging</tag>
1109 <term abbreviation="GSM" completeForm="Global System for Mobile communications" language="en"/>
1110 <term abbreviation="GSM" completeForm="Groupe Spécial Mobile" language="fr"/>
1111 <explanation language="en"><text></text></explanation>
1114 <term abbreviation="GSMA" completeForm="GSM Association" language="en"/>
1115 <explanation language="en"><text></text></explanation>
1118 <term abbreviation="CDMA" completeForm="code division multiple access" language="en"/>
1119 <explanation language="en"><text></text></explanation>
1122 <term abbreviation="TDMA" completeForm="time division multiple access" language="en"/>
1123 <explanation language="en"><text></text></explanation>
1126 <term abbreviation="UMTS" completeForm="universal mobile telecommunications system" language="en"/>
1127 <explanation language="en"><text></text></explanation>
1130 <term abbreviation="SS7" completeForm="signalling system no. 7" language="en"/>
1131 <explanation language="en"><text></text></explanation>
1134 <term abbreviation="SIGTRAN" completeForm="SIGnaling TRAnsport" language="en"/>
1135 <explanation language="en"><text></text></explanation>
1138 <term abbreviation="3G" completeForm="third generation" language="en"/>
1139 <explanation language="en"><text></text></explanation>
1142 <term abbreviation="4G" completeForm="fourth generation" language="en"/>
1143 <explanation language="en"><text></text></explanation>
1146 <term abbreviation="" completeForm="Baby Bell" language="en"/>
1147 <!-- https://en.wikipedia.org/wiki/Regional_Bell_Operating_Company -->
1148 <explanation language="en"><text></text></explanation>
1151 <term abbreviation="EAIF" completeForm="external application interface" language="en"/>
1152 <explanation language="en"><text>Nokia's protocol for sending and receiving MMS, is based on HTTP and transferres binary content.</text></explanation>
1154 <tag>messaging</tag>
1158 <term abbreviation="UCP" completeForm="universal computer protocol" language="en"/>
1159 <explanation language="en">
1161 an SMS messaging protocol developed by CMG (later Acision)
1162 as interface for ESME to SMSC;
1163 an extended variant of it is called EMI
1167 <tag>messaging</tag>
1171 <term abbreviation="EMI" completeForm="external machine interface" language="en"/>
1172 <explanation language="en"><text>an extension of UCP</text></explanation>
1174 <tag>messaging</tag>
1178 <term abbreviation="CIMD" completeForm="computer interface to message distribution" language="en"/>
1179 <explanation language="en">
1181 a proprietary SMS messaging protocol developed by Nokia
1182 for connecting to their SMSC
1186 <tag>messaging</tag>
1190 <term abbreviation="URLP" completeForm="URL encoded message protocol" language="en"/>
1191 <explanation language="en">
1193 a simple protocol that can be used between AAG and SPA for transmitting messages;
1194 uses HTTP GET method and encodes data in the URL or in HTTP response body
1198 <tag>messaging</tag>
1202 <term abbreviation="SMAP" completeForm="short message application protocol" language="en"/>
1203 <explanation language="en"><text></text></explanation>
1204 <tag>messaging</tag>
1209 <term abbreviation="PSA" completeForm="" language="en"/>
1210 <explanation language="en"><text></text></explanation>
1214 <term abbreviation="PAP" completeForm="push access protocol" language="en"/>
1215 <explanation language="en"><text></text></explanation>
1219 <term abbreviation="SC" completeForm="service center" language="en"/>
1220 <term abbreviation="MC" completeForm="message centre" language="en"/>
1221 <explanation language="en">
1223 a component in telecommunication network;
1224 SMSC for SMS or MMSC for MMS messages
1227 <tag>messaging</tag>
1230 <term abbreviation="SMSC" completeForm="SMS service center" language="en"/>
1231 <term abbreviation="SMS-SC" completeForm="Short Message Service - Service Centre" language="en"/>
1232 <explanation language="en">
1234 a component in telecommunication network dedicated to store, forward, convert and deliver SMS messages;
1235 is connected to the SS7 network on one side and to routing entities (RE) using SMPP on the other side;
1236 is able to process MOMT messaging and also MOAT or AOMT messaging (using RE)
1237 Example of SMSC: SMSCv5
1240 <tag>messaging</tag>
1243 <term abbreviation="SMSCv5" completeForm="SMS service center version 5" language="en"/>
1244 <term abbreviation="v5" completeForm="" language="en"/><!-- jargon -->
1245 <explanation language="en">
1247 an implementation of SMSC from Acision;
1248 runs on an OpenVMS system
1252 <tag>messaging</tag>
1255 <term abbreviation="MMSC" completeForm="Multimedia Messaging Service Centre" language="en"/>
1256 <term abbreviation="MMSC" completeForm="MMS Service Centre" language="en"/>
1257 <term abbreviation="" completeForm="MMS store and forward server" language="en"/>
1258 <explanation language="en">
1260 a kind of SC dedicated to processing multimedia messages;
1261 the messaging is more comlex process than in case of SMS:
1262 MO MMS message is received (in similar format to MIME e-mail) by the MMSC and stored,
1263 then SC determines if the recipient is capable to receive MMS,
1264 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,
1265 if recipient is not capable he gets plain text SMS with URL and have to use computer and www browser
1268 <tag>messaging</tag>
1271 <term abbreviation="BMSC" completeForm="Broadband Messaging Service Centre" language="en"/>
1272 <term abbreviation="" completeForm="Fusion" language="en"/>
1273 <explanation language="en">
1275 a consolidated messaging platform announced by the Acision company in 2013;
1276 integrates RSC, SMS, MMS and voice mail
1280 <tag>messaging</tag>
1283 <term abbreviation="IWG" completeForm="inter-working gateway" language="en"/>
1284 <explanation language="en"><text></text></explanation>
1285 <tag>messaging</tag>
1288 <term abbreviation="WAP" completeForm="wireless application protocol" language="en"/>
1289 <explanation language="en"><text></text></explanation>
1293 <term abbreviation="OTA" completeForm="over-the-air" language="en"/>
1294 <explanation language="en"><text></text></explanation>
1297 <term abbreviation="FOTA" completeForm="firmware over the air" language="en"/>
1298 <explanation language="en"><text></text></explanation>
1301 <term abbreviation="DRM" completeForm="digital restrictions management" language="en"/>
1302 <term abbreviation="DRM" completeForm="digital rights management" language="en"/>
1303 <explanation language="en"><text></text></explanation>
1307 <term abbreviation="SyncML" completeForm="synchronization markup language" language="en"/>
1308 <explanation language="en"><text></text></explanation>
1312 <term abbreviation="VoIP" completeForm="voice over IP" language="en"/>
1313 <explanation language="en">
1315 delivering voice communication (or other multimedia sessions like video) over the Internet Protocol (IP) instead of traditional telco networks;
1316 there are open and standard protocols for signaling: SIP and XMPP and open protocols for the payload (audio/video) like RTP;
1317 VoIP is nowadays widely used inside companies where often shares same ethernet network with computers (can be separeted by VLANs)
1318 and also in households espetially for cheap overseas calls;
1319 as VoIP phone can be used a computer with appropriate software or a cell phone or dedicated hardware phone;
1320 there are also gateways that enable connecting old analog phones to the VoIP network
1325 <term abbreviation="SIP" completeForm="session initiation protocol" language="en"/>
1326 <explanation language="en">
1328 an open signalling protocol for initiation of VoIP calls (audio, video or possibly other media sessions);
1329 has similar format of headers and request/response model as HTTP;
1330 transported over UDP or TCP (for TLS encryption) or SCTP;
1331 for the media payload is typically used RTP protocol
1337 <term abbreviation="RTP" completeForm="real-time transport protocol" language="en"/>
1338 <explanation language="en">
1340 a standardized packet format for delivering audio and video over IP;
1341 can transfer audio or video streams for telephony or television streams;
1342 is used heavily in VoIP in combination with SIP;
1343 can be secured with SRTP/ZRTP to avoid wiretrapping
1349 <term abbreviation="SRTP" completeForm="secure RTP" language="en"/>
1350 <explanation language="en"><text></text></explanation>
1355 <term abbreviation="ZRTP" completeForm="Zimmermann RTP" language="en"/>
1356 <explanation language="en"><text></text></explanation>
1361 <term abbreviation="" completeForm="throttling" language="en"/>
1362 <explanation language="en">
1364 limiting the flow rate;
1365 e.g. short messages per second
1368 <tag>messaging</tag>
1371 <term abbreviation="" completeForm="keep alive" language="en"/>
1372 <term abbreviation="" completeForm="keep-alive" language="en"/>
1373 <explanation language="en">
1375 a packet or message or command without useful content
1376 which is sent in order to avoid closing the connection (time out) and to check, it is still working;
1377 in HTTP this term means persistent connection
1383 <term abbreviation="" completeForm="inroaming" language="en"/>
1384 <explanation language="en"><text>roaming of subscribers from other operator in your network</text></explanation>
1387 <term abbreviation="" completeForm="outroaming" language="en"/>
1388 <explanation language="en"><text>roaming of your subscribers in other operator's network</text></explanation>
1391 <term abbreviation="TON" completeForm="type of number" language="en"/>
1392 <explanation language="en">
1394 (0x00) Unknown type of number;
1395 (0x01) International number;
1396 (0x02) National number;
1397 (0x03) Network specific number;
1398 (0x04) Subscriber number, dedicated access, short code;
1399 (0x05) Alphanumeric, in 7-bit GSM alphabet;
1400 (0x06) Abbreviated number
1405 <term abbreviation="NPI" completeForm="numbering plan indicator" language="en"/>
1406 <explanation language="en">
1408 a number which indicates the numbering plan of a telephone number;
1410 (0x00) Unknown numbering plan;
1411 (0x01) ISDN/telephone numbering plan – E.164/E.163;
1413 (0x03) Data numbering plan – X.121;
1414 (0x04) Telex numbering plan – F.96;
1415 (0x05) Service Centre Specific plan;
1416 (0x06) Land mobile numbering plan – E.212;
1417 (0x07) ISDN/mobile numbering plan – E.214;
1418 <!-- only 0-7 defined in the ITU standard Q.713 ? -->
1419 (0x08) National numbering plan;
1420 (0x09) Private numbering plan;
1421 (0x0A) ERMES numbering plan – ETSI DE/PS 3 01-3;
1422 (0x0D) Binary Internet addres – IP;
1423 (0x0E) Alphanumeric Internet address
1428 <term abbreviation="PID" completeForm="protocol identifier" language="en"/>
1429 <explanation language="en">
1431 one octet of information which describes the protocol resp. type of telematic device;
1432 0 means implicit (plain MOMT messages);
1433 other values are described in 3GPP TS 03.40
1438 <term abbreviation="PID" completeForm="process identifier" language="en"/>
1439 <explanation language="en">
1441 identifier of an process (running program) in an operating system;
1442 PID 1 is usually assigned to the init process (the first process which starts other ones)
1448 <term abbreviation="" completeForm="Blue box" language="en"/>
1449 <term abbreviation="" completeForm="BlueBox" language="en"/>
1450 <explanation language="en"><text></text></explanation>
1453 Orange box https://en.wikipedia.org/wiki/Orange_box
1454 Vermilion box https://en.wikipedia.org/wiki/Vermilion_box
1455 Magenta box https://en.wikipedia.org/wiki/Magenta_box
1458 <term abbreviation="" completeForm="Orange box" language="en"/>
1459 <term abbreviation="" completeForm="OrangeBox" language="en"/>
1460 <explanation language="en"><text></text></explanation>
1463 <term abbreviation="" completeForm="Vermilion box" language="en"/>
1464 <term abbreviation="" completeForm="VermilionBox" language="en"/>
1465 <explanation language="en"><text></text></explanation>
1468 <term abbreviation="" completeForm="Magenta box" language="en"/>
1469 <term abbreviation="" completeForm="MagentaBox" language="en"/>
1470 <explanation language="en"><text></text></explanation>
1473 <term abbreviation="" completeForm="hack" language="en"/>
1474 <term abbreviation="" completeForm="hacking" language="en"/>
1475 <term abbreviation="" completeForm="hacker" language="en"/>
1476 <explanation language="en">
1478 hacker is an interrogative person interested in internal principles of things;
1479 often it is a software developer or a system administrator but hacking is also possible outside the digital world;
1480 hacking is the activity of these people – usually
1481 improving a software by adding new features
1482 or discovering secrets in existing software or hardware systems
1483 or running extraordinary configurations or combinations of components;
1484 hack is the product of their work – e.g. improved computer program or piece of hardware;
1485 <!-- hack can mean also the insctructions how to do it; -->
1486 don't confuse with „cracker“
1489 RMS - https://www.gnu.org/philosophy/rms-hack.html
1490 „someone who enjoys playful cleverness, especially in programming but other media are also possible“
1492 ESR - http://www.catb.org/~esr/jargon/html/H/hacker.html
1493 [originally, someone who makes furniture with an axe]
1494 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.
1495 2. One who programs enthusiastically (even obsessively) or who enjoys programming rather than just theorizing about programming.
1496 3. A person capable of appreciating hack value.
1497 4. A person who is good at programming quickly.
1498 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.)
1499 6. An expert or enthusiast of any kind. One might be an astronomy hacker, for example.
1500 7. One who enjoys the intellectual challenge of creatively overcoming or circumventing limitations.
1501 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.
1502 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).
1503 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.
1504 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.
1506 RFC 1392 - https://tools.ietf.org/html/rfc1392
1507 A person who delights in having an intimate understanding of the
1508 internal workings of a system, computers and computer networks in
1509 particular. The term is often misused in a pejorative context,
1510 where "cracker" would be the correct term. See also: cracker.
1517 <term abbreviation="" completeForm="crack" language="en"/>
1518 <term abbreviation="" completeForm="cracking" language="en"/>
1519 <term abbreviation="" completeForm="cracker" language="en"/>
1520 <explanation language="en">
1522 someone who breaks the security protections in order to get unauthorized access to a computer system;
1523 they often misuse their skills to steal private data, destroy systems or steal money;
1524 don't confuse with „hacker“
1531 <term abbreviation="" completeForm="phreak" language="en"/>
1532 <term abbreviation="" completeForm="phreaking" language="en"/>
1533 <term abbreviation="" completeForm="phreaker" language="en"/>
1534 <explanation language="en">
1536 a hacker interested in phone systems or telecommunications in general;
1537 sometimes they can become cracker if they don't only experiment but misuse telephone networks excessively (fraud);
1538 the term is a portmanteau of the words „phone“ and „freak“
1544 <term abbreviation="AAGP" completeForm="Acision Application Gateway Provisioning" language="en"/>
1545 <term abbreviation="GAS" completeForm="Generic application server" language="en"/>
1546 <term abbreviation="CPS" completeForm="Central provisioning system" language="en"/>
1547 <explanation language="en">
1549 a software component developed by the Acision company;
1550 a provisioning tool for AAG and other products of this company;
1551 can be used as generic provisioning tool for any product provided that particular connector exists;
1552 has web GUI and several APIs
1556 <tag>messaging</tag>
1559 <term abbreviation="AAG" completeForm="Acision Application Gateway" language="en"/>
1560 <term abbreviation="OMG" completeForm="Open Messaging Gateway" language="en"/>
1561 <explanation language="en">
1563 a software component developed by the Acision company;
1564 typical use case is: a messaging gateway between SMSC and applications (ESME)
1568 <tag>messaging</tag>
1571 <term abbreviation="GBG" completeForm="General Billing Gateway" language="en"/>
1572 <term abbreviation="AFG" completeForm="Acision Flexible Gateway" language="en"/>
1573 <term abbreviation="TGC" completeForm="Test Gateway Component" language="en"/>
1574 <term abbreviation="UGC" completeForm="Universal Gateway Component" language="en"/>
1575 <explanation language="en">
1577 a software component developed by the Acision company;
1578 works as a messaging gateway and can interconnect systems talking many various messaging protocols;
1579 is highly configurable and can translate and transform messages in many formats;
1580 original purpose was doing a gateway for billing messages comming from e.g. SMSC to some billing system
1584 <tag>messaging</tag>
1587 <term abbreviation="UGC" completeForm="user generated content" language="en"/>
1588 <explanation language="en">
1590 content in various media formats (text, pictures, video, sound…)
1591 which is created by users (or subscribers);
1592 e.g. photos taken by mobile and sent over MMS, e-mail or web to some server which displays them to other users
1598 <term abbreviation="VCS" completeForm="version control system" language="en"/>
1599 <term abbreviation="RCS" completeForm="revision control system" language="en"/>
1600 <explanation language="en">
1602 a software tool used for management of changes in documents;
1603 often is used for managing source code and other artifacts (like documentation or analytic models) created during software development;
1604 VCS tracks versions of particular files or changesets, branches, tags (named revisions);
1605 examples of traditional centralized VCS: SCCS, RCS, CVS or SVN (quite modern but centralized);
1606 nowadays are very popular decentralized systems (DVCS)
1612 <term abbreviation="DVCS" completeForm="distributed version control system" language="en"/>
1613 <term abbreviation="DRCS" completeForm="distributed revision control system" language="en"/>
1614 <explanation language="en">
1616 kind of version control system which allows not only workflow with one central server
1617 but also decentralized workflows where changesets are pushed or pulled between particular nodes;
1618 each node has typically full repository clone with all the history (commits, branches, tags);
1619 this facilitates offline work –
1620 developer can do commits or work with branches and tags even if he is offline –
1621 and after going online,
1622 he pushed his work to other developers
1623 or to the central repository
1624 or his work is pulled by others;
1625 other advantage is easy backup – just clone the repository and then do push/pull from the working one;
1626 Examples of DVCS: Mercurial (Hg), Git, Bazaar (bzr), Monotone (mtn), Fossil, GNU arch, Darcs, DCVS or SVK
1632 <term abbreviation="SCM" completeForm="software configuration management" language="en"/>
1633 <explanation language="en"><text></text></explanation>
1637 <term abbreviation="hg" completeForm="mercurial" language="en"/>
1638 <explanation language="en"><text>a distributed version control system</text></explanation>
1642 <term abbreviation="cvs" completeForm="Concurrent Versions System" language="en"/>
1643 <explanation language="en"><text>a centralized version control system</text></explanation>
1647 <term abbreviation="svn" completeForm="Subversion" language="en"/>
1648 <explanation language="en"><text>a centralized version control system</text></explanation>
1652 <term abbreviation="bzr" completeForm="Bazaar" language="en"/>
1653 <explanation language="en"><text>a distributed version control system</text></explanation>
1657 <term abbreviation="" completeForm="git" language="en"/>
1658 <explanation language="en"><text>a distributed version control system</text></explanation>
1662 <term abbreviation="XML" completeForm="eXtensible markup language" language="en"/>
1663 <explanation language="en"><text></text></explanation>
1668 <term abbreviation="xmlns" completeForm="XML name space" language="en"/>
1669 <explanation language="en"><text></text></explanation>
1674 <term abbreviation="DTD" completeForm="document type definition" language="en"/>
1675 <explanation language="en">
1677 a schema language for XML;
1678 used to describe the format based on XML
1679 and perform validations of XML documents
1686 <term abbreviation="XSD" completeForm="XML schema definition" language="en"/>
1687 <explanation language="en">
1689 a schema language for XML;
1690 used to describe the format based on XML
1691 and perform validations of XML documents
1692 XSD itself is written in XML;
1693 is more powerful than DTD
1700 <term abbreviation="" completeForm="Schematron" language="en"/>
1701 <explanation language="en">
1703 a validation language;
1704 can describe formats based on XML like XSD or DTD does, but has entirely different approach;
1705 Schematron is rule-based – defines assertions which must be met to have valid document;
1706 this rules are transformed into XSL template which is executed during validation;
1707 Schematron can be also combined with XSD
1708 – XSD schemas (which are more declarative and more clearly represents the desired structure of the document for humans)
1709 are enriched with Schematron assertions that adds more complex rules (that cannot be easily expressed in pure XSD)
1716 <term abbreviation="XSLT" completeForm="Extensible Stylesheet Language Transformations" language="en"/>
1717 <term abbreviation="XSL" completeForm="Extensible Stylesheet Language" language="en"/>
1718 <explanation language="en">
1720 a transformation language for XML;
1721 can be used e.g. for
1722 conversion from one XML format to another one,
1723 for generating (plain) text or HTML,
1724 for user friendly visualisation of XML data (XHTML or SVG output),
1725 or for validations (raise error message on invalid input, see also Schematron);
1726 XSL templates are also written in XML
1733 <term abbreviation="" completeForm="XQuery" language="en"/>
1734 <explanation language="en">
1736 functional programming language for processing XML and other data
1743 <term abbreviation="XPath" completeForm="XML Path Language" language="en"/>
1744 <explanation language="en">
1746 a query language for selecting XML nodes;
1747 an XPath expression can also compute values and call XPath functions
1754 <term abbreviation="" completeForm="Ant" language="en"/>
1755 <explanation language="en">
1757 a tool for automating software build processes;
1758 does similar job like GNU Make, but is written in and for Java;
1759 equivalent for the Makefile is here build.xml which describes particular tasks and their dependencies;
1760 there is lot of tasks distributed with Apache Ant e.g.
1761 compilation of Java code,
1763 running XSLT transformations,
1764 packing JARs and other archives,
1765 copying and moving files
1766 or calling system commands;
1767 and user can also write own tasks in Java
1774 <term abbreviation="mvn" completeForm="Maven" language="en"/>
1775 <explanation language="en">
1777 a tool for automating software build processes;
1778 compared to Ant, Maven is much more declarative instead of procedural and is strongly focused on resolving dependencies on modules, components, libraries;
1779 dependencies (libraries) of a project are automatically downloaded from a repository;
1780 projects in Maven are described by a POM file
1787 <term abbreviation="POM" completeForm="Project Object Model" language="en"/>
1788 <explanation language="en">
1790 an XML configuration file which describes one Maven project;
1791 contains project metadata like name, owner, version, dependencies
1792 and phases of its build process
1799 <term abbreviation="" completeForm="Java" language="en"/>
1800 <explanation language="en">
1802 an object-oriented programming language designed by James Gosling at Sun Microsystems;
1803 Java source code is compiled into byte code (.class files) which can be executed in JVM on many architectures and operating systems;
1804 Java is completely free software, there is OpenJDK and standard library distributed under GNU GPL license;
1805 there is also GNU Classpath – an independent and free software implementation of the standard library;
1806 Java is popular and well established enterprise-grade software platform
1813 <term abbreviation="JVM" completeForm="Java virtual machine" language="en"/>
1814 <explanation language="en">
1816 a runtime environment for running Java byte code;
1817 there is lot of programming languages that can be compiled into the bytecode and executed in JVM e.g.
1818 Clojure (a Lisp dialect),
1819 Scala (OOP and functional language),
1820 Groovy (a scripting language),
1821 Jython (an implementation of Python),
1823 or Rhino (JavaScript)
1830 <term abbreviation="JavaDoc" completeForm="Java documentation" language="en"/>
1831 <explanation language="en">
1833 documentation of Java source code (classes, enumerations, interfaces, packages);
1834 describes API and software's internals;
1835 is useful for developers, not too much for end-users
1842 <term abbreviation="" completeForm="Erlang" language="en"/>
1843 <explanation language="en">
1845 a functional programming language developed in Ericsson;
1846 influenced by Prolog and SmallTalk languages;
1847 Erlang implementation is a free software
1853 <term abbreviation="RegEx" completeForm="Regular Expression" language="en"/>
1854 <term abbreviation="RegExp" completeForm="Regular Expression" language="en"/>
1855 <term abbreviation="RE" completeForm="Regular Expression" language="en"/>
1856 <explanation language="en">
1858 an expression (sequence of characters) which forms a pattern that can be used for string matching –
1859 finding occurrences of the pattern in the text or evaluating whether the whole text matches the pattern;
1860 Example: regular expression (a|b)cde\d+ matches strings acde123 or bcde0 but not cde1 or acdex
1866 <term abbreviation="PCRE" completeForm=" Perl Compatible Regular Expressions" language="en"/>
1867 <explanation language="en">
1869 a C library for regular expressions compatible with Perl's RegEx dialect
1870 or this dialect itself
1876 <term abbreviation="Perl" completeForm="Practical Extraction and Reporting Language" language="en"/>
1877 <explanation language="en">
1879 an interpreted dynamic programming language;
1880 popular in UNIX environment for scripting and text processing;
1881 Perl syntax allows very effective and elegant notation especially while working with regular expressions, but sometimes it is hard to read;
1882 its implementation is free software
1888 <term abbreviation="POSIX" completeForm="Portable Operating System Interface" language="en"/>
1889 <explanation language="en">
1891 a family of standards for maintaining compatibility between operating systems;
1892 defines API, command line shells and utility interfaces
1893 and thus brings compatibility amog many variants of unix and unix-like operating systems;
1894 the name POSIX was suggested by Richard Stallman (the standards was formerly known as IEEE-IX);
1895 there are standards for e.g. process creation and control, signals, pipes, message passing, shared memory or semaphores;
1896 Examples of fully or mostly POSIX-compliant systems: AIX, IRIS, Solaris, OS X, GNU/Linux, BeOS (Haiku) or several BSD variants
1902 <term abbreviation="" completeForm="UNIX" language="en"/>
1903 <term abbreviation="Unics" completeForm="UNiplexed Information and Computing Service" language="en"/>
1904 <explanation language="en">
1906 a multitasking and multi-user operating system developed in 1969 by a group of AT&T hackers at Bell Labs;
1907 has influenced many other operating systems (now called UNIX-like OS) and established distinctive UNIX culture and philosophy;
1908 nowadays we have completely free software implementation called GNU (resp. GNU/Linux where Linux is operating system kernel or GNU/Hurd);
1909 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;
1910 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)
1916 <term abbreviation="" completeForm="GNU/Linux" language="en"/>
1917 <term abbreviation="" completeForm="Linux" language="en"/>
1918 <explanation language="en">
1920 the GNU operating system with Linux kernel;
1926 <term abbreviation="GNU" completeForm="GNU's Not Unix!" language="en"/>
1927 <explanation language="en">
1929 a Unix-like operating system that is free software and is upward-compatible with Unix;
1930 the GNU Project was initially announced in September 1983 by Richard Stallman;
1931 nowadays is mostly used in combination with Linux kernel and called GNU/Linux
1937 <term abbreviation="GNU GPL" completeForm="GNU General Public License" language="en"/>
1938 <term abbreviation="GPL" completeForm="General Public License" language="en"/>
1939 <explanation language="en">
1941 a free software and copyleft license which is used by many free software packages
1947 <term abbreviation="GNU FDL" completeForm="GNU Free Documentation License" language="en"/>
1948 <term abbreviation="FDL" completeForm="Free Documentation License" language="en"/>
1949 <explanation language="en">
1951 whereas GNU GPL is free and copyleft license for software,
1952 the GNU FDL is similar license designed for documentaion – books, articles, drawings etc.
1958 <term abbreviation="FS" completeForm="free software" language="en"/>
1959 <explanation language="en">
1961 a category of software which respects user's freedoms – user of such software has the four essential freedoms:
1962 0) The freedom to run the program, for any purpose.
1963 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.
1964 2) The freedom to redistribute copies so you can help your neighbor.
1965 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.;
1966 the term „Free software“ was defined by Richard Stallman
1972 <term abbreviation="OSS" completeForm="open source software" language="en"/>
1973 <explanation language="en">
1975 a category of software similar to Free software;
1976 the term „open source software“ was defined by Open Source Initiative;
1977 its definition contains ten requirements like free redistribution, available source code or allowing derived works;
1978 almost every open source license is also a free software license and vice versa;
1979 but there is different philosophical background – the free software movement has user's freedom as the main priority
1985 <term abbreviation="FSF" completeForm="Free Software Foundation" language="en"/>
1986 <explanation language="en">
1988 a non-profit organization founded by Richard Stallman on 4 October 1985 to support the free software movement;
1989 has developed the GNU operating system,
1990 issued licenses like GPL or FDL,
1991 maintains the Free Software Definition,
1992 does political campaigns and other activities related to user's freedoms;
1998 <term abbreviation="OSI" completeForm="Open Source Initiative" language="en"/>
1999 <explanation language="en">
2001 an organization dedicated to promoting open-source software;
2002 was founded in February 1998, by Bruce Perens and Eric S. Raymond;
2008 <term abbreviation="EFF" completeForm="Electronic Frontier Foundation" language="en"/>
2009 <explanation language="en">
2011 a non-profit organization focused on protecting user's freedoms and privacy in mostly digital world;
2012 fights against censorship and spying, criticises software patents
2013 and promotes – among others – free speech, privacy, e-voting and network neutrality
2019 <term abbreviation="OpenVMS" completeForm="Open Virtual Memory System" language="en"/>
2020 <term abbreviation="VMS" completeForm="Virtual Memory System" language="en"/><!-- informally -->
2021 <explanation language="en">
2023 an operating system for VAX, Alpha and Itanium-based computers
2029 <term abbreviation="VMS" completeForm="voice mail system" language="en"/><!-- informally -->
2030 <explanation language="en"><text></text></explanation>
2033 <term abbreviation="LDAP" completeForm="Lightweight Directory Access Protocol" language="en"/>
2034 <explanation language="en">
2036 a binary protocol for accessing directories (specialized databases);
2037 LDAP databases are usually optimalized for reading operations with rare write operations;
2038 provides a tree-oriented view on data which is different from relational one in RDBMS;
2039 despite that some LDAP servers use relational database as its backend
2047 <term abbreviation="GAL" completeForm="global address list" language="en"/>
2048 <explanation language="en">
2050 The Global Address List is a term used in groupware software
2051 and means the shared address book which contains usually all people of given organization (company, school etc.).
2052 This address book is accessed over the computer network using LDAP protocol, CardDAV or other electronic way (it is not a printed book).
2053 The GAL is usually read-only for users – only administrators adds or updates the items.
2054 Users can search it, lookup other people (employees, students, members etc.)
2055 and obtain information about them like e-mail address, phone number, work position, office location and others.
2056 The common usage of GAL is
2057 if the user is writing an e-mail,
2058 knows recipient's name,
2059 but don't know his e-mail address
2060 – the groupware or e-mail client (e.g. SOGo, Zimbra or Thunderbird) can lookup the e-mail address in the GAL while user is writing only a part of the recipient's name.
2066 <term abbreviation="" completeForm="white pages" language="en"/>
2067 <explanation language="en">
2069 a method of looking up in a directory;
2070 we know a person's name or MSISDN and we are fetching particular record from LDAP or other database;
2071 so it is similar to using the white pages (not yellow) of a telephone directory (a thick paperback book)
2077 <term abbreviation="" completeForm="yellow pages" language="en"/>
2078 <explanation language="en">
2080 a method of looking up in a directory;
2081 we know just some criteria of desired object and we are fetching a list of records from LDAP or other database;
2082 for example we can search for a PostScript printer in second floor or subscribers with particular tariff;
2083 so it is similar to using the yellow pages (not white) of a telephone directory (a thick paperback book)
2089 <term abbreviation="" completeForm="black list" language="en"/>
2090 <term abbreviation="" completeForm="black-list" language="en"/>
2091 <term abbreviation="" completeForm="blacklist" language="en"/>
2092 <term abbreviation="" completeForm="blacklisting" language="en"/>
2093 <term abbreviation="" completeForm="blacklisted" language="en"/>
2094 <explanation language="en">
2096 a list of elements that are not allowed or should be excluded;
2097 the element might be e.g. IP address, e-mail address, regular expression, name pattern or name;
2098 example 1: we do not accept e-mail messages from blacklisted IP addresses, because such IP addresses are known to send spam
2099 example 2: blacklisted kernel modules are not loaded during the system start
2106 <term abbreviation="" completeForm="white list" language="en"/>
2107 <term abbreviation="" completeForm="white-list" language="en"/>
2108 <term abbreviation="" completeForm="whitelist" language="en"/>
2109 <term abbreviation="" completeForm="whitelisting" language="en"/>
2110 <term abbreviation="" completeForm="whitelisted" language="en"/>
2111 <explanation language="en">
2113 a list of elements that are allowed or should be included;
2114 the element might be e.g. IP address, e-mail address, regular expression, name pattern or name;
2115 example 1: connections from whitelisted IP addresses to the service are allowed, while connections from all other IP addresses are rejected;
2116 example 2: connections from whitelisted IP addresses to the service are allowed, connections from blacklisted IP addresses are dropped (the will not get a any response) and connections from all other IP addresses are rejected (will get a negative response);
2123 <term abbreviation="" completeForm="grey list" language="en"/>
2124 <term abbreviation="" completeForm="grey-list" language="en"/>
2125 <term abbreviation="" completeForm="greylist" language="en"/>
2126 <term abbreviation="" completeForm="greylisting" language="en"/>
2127 <term abbreviation="" completeForm="gray list" language="en"/>
2128 <term abbreviation="" completeForm="gray-list" language="en"/>
2129 <term abbreviation="" completeForm="graylist" language="en"/>
2130 <term abbreviation="" completeForm="graylisting" language="en"/>
2131 <explanation language="en">
2133 a method of preventing e-mail spam;
2134 1) utilizes standard behavior of legitimate e-mail servers that tries to redeliver the message multiple times when a temporary error occurs
2135 2) expects that spammers are not going to redeliver in that case, because they are focused more on quantitiy than quality (few lost messages are not an issue for them);
2136 MTA equiped with a greylisting filter will respond with a simulated temporary error to incomming messages from an unknown sender;
2137 when the sender attempts to deliver the massage for the second time, the message will be accepted (if it is long enough after the first attempt);
2138 this method is stateful which means that the MTA server needs to maintain a list of senders and their send attempts – this list is called greylist;
2139 disadvantage of this method is that it causes delays in the e-mail delivery;
2140 this disadvantage can be partially mitigated using a whitelist: trusted senders (domains or IP addresses) are put on the whitelist and do not have to wait even if they are sending the first message
2144 <tag>messaging</tag>
2147 <term abbreviation="" completeForm="master" language="en"/>
2148 <explanation language="en">
2150 a role of a component (both hardware and software) that controls other ones (slaves) and issues commands for them;
2157 <term abbreviation="" completeForm="slave" language="en"/>
2158 <explanation language="en">
2160 a role of a component (both hardware and software) that is controlled by a master and follows the commands issued by the master;
2172 TODO: ASR - https://en.wikipedia.org/wiki/Answer-seizure_ratio
2176 <term abbreviation="SQL" completeForm="structured query language" language="en"/>
2177 <term abbreviation="SEQUEL" completeForm="structured english query language" language="en"/>
2178 <explanation language="en">
2187 <term abbreviation="noSQL" completeForm="Not SQL" language="en"/>
2188 <explanation language="en"><text></text></explanation>
2193 <term abbreviation="RDBMS" completeForm="relational database management system" language="en"/>
2194 <term abbreviation="DBMS" completeForm="database management system" language="en"/>
2195 <term abbreviation="SŘDB" completeForm="systém řízení báze dat" language="cs"/>
2196 <explanation language="en"><text></text></explanation>
2201 <term abbreviation="ODBC" completeForm="open database connectivity" language="en"/>
2202 <explanation language="en">
2204 an industry standard that provides API for accessing a DBMS;
2205 in late 80s several vendors (mostly from the Unix and database communities) established the SQL Access Group (SAG)
2206 and then specified the Call Level Interface (CLI). ODBC, which is based on CLI, was published in early 90s;
2207 ODBC is available on many operating systems and there are at least two free software implementations: unixODBC and iODBC;
2208 in particular, it is an API consisting of C functions (see the files sql.h and sqlext.h e.g. in unixODBC or iODBC)
2215 <term abbreviation="JDBC" completeForm="java database connectivity" language="en"/>
2216 <explanation language="en">
2218 a standard Java API for accessing relational (SQL) databases
2226 <term abbreviation="" completeForm="data source" language="en"/>
2227 <explanation language="en">
2229 a set of parameters (like server name, user name, password etc.) needed for connecting to a database;
2230 a configuration (e.g. in a file) or then its instantiation (an object) in a running program from which particular database connections can be obtained;
2231 see also DSN, connection string
2238 <term abbreviation="DSN" completeForm="data source name" language="en"/>
2239 <explanation language="en">
2241 the name of a preconfigured data source
2242 – when connecting, we need to know only the DSN –
2243 all parameters (like server name, user name, password etc.) can be then looked-up in the configuration;
2244 see also data source, connection string
2251 <term abbreviation="" completeForm="connection string" language="en"/>
2252 <explanation language="en">
2254 a text string consisting of serialized parameters needed for connecting
2255 – we can specify all parameters ad-hoc in the connection string without creating any permanent configuration;
2256 a connection string can also refer to an already defined DSN and add or override its parameters
2257 see also DSN, data source
2264 <term abbreviation="AS" completeForm="application server" language="en"/>
2265 <explanation language="en"><text></text></explanation>
2270 <term abbreviation="" completeForm="JBoss" language="en"/>
2271 <explanation language="en"><text>an application server</text></explanation>
2276 <term abbreviation="" completeForm="GlassFish" language="en"/>
2277 <explanation language="en"><text>an application server</text></explanation>
2282 <term abbreviation="WSDL" completeForm="web services description language" language="en"/>
2283 <explanation language="en"><text></text></explanation>
2288 <term abbreviation="WADL" completeForm="web application description language" language="en"/>
2289 <explanation language="en"><text></text></explanation>
2294 <term abbreviation="SOAP" completeForm="simple object access protocol" language="en"/>
2295 <term abbreviation="SOAP" completeForm="SOA Protocol" language="en"/>
2296 <explanation language="en"><text></text></explanation>
2302 <term abbreviation="REST" completeForm="representational state transfer" language="en"/>
2303 <explanation language="en"><text></text></explanation>
2307 <term abbreviation="EJB" completeForm="Enterprise JavaBeans" language="en"/>
2308 <explanation language="en"><text></text></explanation>
2313 <term abbreviation="CORBA" completeForm="common object request broker architecture" language="en"/>
2314 <explanation language="en"><text></text></explanation>
2318 <term abbreviation="IDL" completeForm="interface definition language" language="en"/>
2319 <explanation language="en"><text></text></explanation>
2323 <term abbreviation="IIOP" completeForm="Internet InterORB Protocol" language="en"/>
2324 <term abbreviation="GIOP" completeForm="General Inter-ORB Protocol" language="en"/>
2325 <explanation language="en"><text></text></explanation>
2330 <term abbreviation="RMI" completeForm="Remote Method Invocation" language="en"/>
2331 <explanation language="en"><text></text></explanation>
2337 <term abbreviation="JAR" completeForm="Java ARchive" language="en"/>
2338 <explanation language="en">
2340 an archive format in which compiled Java classes, metadata and other resources are distributed;
2341 is based on the ZIP format and files have .jar extension;
2342 basic JAR files are used for desktop applications and Java libraries;
2343 there are also EAR and WAR for enterprise and web applications
2350 <term abbreviation="EAR" completeForm="Enterprise ARchive" language="en"/>
2351 <explanation language="en">
2353 a kind of JAR file in which an enterprise application is distributed/deployed
2360 <term abbreviation="WAR" completeForm="Web ARchive" language="en"/>
2361 <explanation language="en">
2363 a kind of JAR file in which a web application is distributed/deployed
2370 <term abbreviation="RAR" completeForm="Resource Adapter aRchive" language="en"/>
2371 <explanation language="en"><text></text></explanation>
2376 <term abbreviation="AJP" completeForm="Apache JServ Protocol" language="en"/>
2377 <explanation language="en"><text></text></explanation>
2383 <term abbreviation="HTTP" completeForm="hypertext transfer protocol" language="en"/>
2384 <term abbreviation="HTTPS" completeForm="hypertext transfer protocol secure" language="en"/>
2385 <explanation language="en"><text></text></explanation>
2390 <term abbreviation="SSL" completeForm="secure socket layer" language="en"/>
2391 <term abbreviation="TLS" completeForm="transport layer security" language="en"/>
2392 <explanation language="en"><text></text></explanation>
2398 <term abbreviation="DTLS" completeForm="datagram transport layer security" language="en"/>
2399 <explanation language="en"><text></text></explanation>
2404 <term abbreviation="BASH" completeForm="Bourne Again Shell" language="en"/>
2405 <explanation language="en"><text></text></explanation>
2409 <term abbreviation="SH" completeForm="shell" language="en"/>
2410 <explanation language="en"><text></text></explanation>
2414 <term abbreviation="SSH" completeForm="secure shell" language="en"/>
2415 <term abbreviation="" completeForm="OpenSSH" language="en"/>
2416 <explanation language="en"><text></text></explanation>
2422 <term abbreviation="SCP" completeForm="secure copy" language="en"/>
2423 <explanation language="en"><text></text></explanation>
2428 <term abbreviation="SFTP" completeForm="SSH file transfer protocol" language="en"/>
2429 <explanation language="en"><text></text></explanation>
2435 <term abbreviation="FTP" completeForm="file transfer protocol" language="en"/>
2436 <term abbreviation="FTPS" completeForm="file transfer protocol secure" language="en"/>
2437 <explanation language="en"><text></text></explanation>
2442 <term abbreviation="PGP" completeForm="Pretty Good Privacy" language="en"/>
2443 <term abbreviation="GPG" completeForm="GNU Privacy Guard" language="en"/>
2444 <term abbreviation="GnuPG" completeForm="GNU Privacy Guard" language="en"/>
2445 <term abbreviation="OpenPGP" completeForm="Open Pretty Good Privacy" language="en"/>
2446 <explanation language="en"><text></text></explanation>
2451 <term abbreviation="DSA" completeForm="digital signature algorithm" language="en"/>
2452 <explanation language="en"><text></text></explanation>
2457 <term abbreviation="RSA" completeForm="Ron Rivest, Adi Shamir and Leonard Adleman" language="en"/>
2458 <explanation language="en"><text></text></explanation>
2463 <term abbreviation="EC" completeForm="elliptic curve" language="en"/>
2464 <term abbreviation="ECC" completeForm="elliptic curve cryptography" language="en"/>
2465 <explanation language="en"><text></text></explanation>
2470 <term abbreviation="AES" completeForm="Advanced Encryption Standard" language="en"/>
2471 <term abbreviation="AES-128" completeForm="Advanced Encryption Standard 128-bit" language="en"/>
2472 <term abbreviation="AES-192" completeForm="Advanced Encryption Standard 192-bit" language="en"/>
2473 <term abbreviation="AES-256" completeForm="Advanced Encryption Standard 256-bit" language="en"/>
2474 <explanation language="en"><text></text></explanation>
2479 <term abbreviation="" completeForm="Camellia" language="en"/>
2480 <explanation language="en"><text></text></explanation>
2485 <term abbreviation="SHA" completeForm="secure hash algorithm" language="en"/>
2486 <term abbreviation="SHA-1" completeForm="secure hash algorithm 160-bit" language="en"/>
2487 <term abbreviation="SHA-2" completeForm="" language="en"/>
2488 <term abbreviation="SHA-3" completeForm="" language="en"/>
2489 <term abbreviation="SHA-256" completeForm="secure hash algorithm 256-bit" language="en"/>
2490 <term abbreviation="SHA-512" completeForm="secure hash algorithm 512-bit" language="en"/>
2491 <explanation language="en"><text></text></explanation>
2496 <term abbreviation="MD4" completeForm="message-digest algorithm 4" language="en"/>
2497 <explanation language="en"><text></text></explanation>
2502 <term abbreviation="MD5" completeForm="message-digest algorithm 5" language="en"/>
2503 <explanation language="en"><text></text></explanation>
2508 <term abbreviation="" completeForm="ethernet" language="en"/>
2509 <explanation language="en"><text></text></explanation>
2514 <term abbreviation="LAN" completeForm="local area network" language="en"/>
2515 <explanation language="en"><text></text></explanation>
2519 <term abbreviation="WAN" completeForm="wide area network" language="en"/>
2520 <explanation language="en"><text></text></explanation>
2524 <term abbreviation="WLAN" completeForm="wireless local area network" language="en"/>
2525 <explanation language="en"><text></text></explanation>
2529 <term abbreviation="VLAN" completeForm="virtual local area network" language="en"/>
2530 <explanation language="en"><text></text></explanation>
2535 <term abbreviation="IP" completeForm="Internet Protocol" language="en"/>
2536 <term abbreviation="IPv4" completeForm="Internet Protocol version 4" language="en"/>
2537 <term abbreviation="IPv6" completeForm="Internet Protocol version 6" language="en"/>
2538 <term abbreviation="" completeForm="IP address" language="en"/>
2539 <explanation language="en"><text></text></explanation>
2544 <term abbreviation="FQDN" completeForm="fully qualified domain name" language="en"/>
2545 <term abbreviation="" completeForm="absolute domain name" language="en"/>
2546 <explanation language="en">
2548 a domain name like „some-machine.example.com“ which completely specifies the location in the DNS hierarchy including the TLD;
2549 compared to „some-machine“ which is not FQDN – is not globally unambiguous and will be resolved differently in different contexts
2555 <term abbreviation="MAC" completeForm="media access control" language="en"/>
2556 <explanation language="en">
2558 a data communication protocol, a sublayer of the layer 2 in OSI model (data link layer);
2559 a MAC address is a unique identifier of an network interface – used for IEEE 802 networks including Ethernet;
2560 they are assigned by the manufacturer of the card and stored in the hardware (can be often changed by the software);
2561 there are three numbering namespaces: MAC-48, EUI-48 and EUI-64;
2562 the address has 6 or 8 bytes and they are usually written in HEX, octets separated by : (a colon)
2568 <term abbreviation="TCP" completeForm="transmission control protocol" language="en"/>
2569 <explanation language="en"><text></text></explanation>
2574 <term abbreviation="UDP" completeForm="user datagram protocol" language="en"/>
2575 <explanation language="en"><text></text></explanation>
2580 <term abbreviation="SCTP" completeForm="stream control transmission protocol" language="en"/>
2581 <explanation language="en"><text></text></explanation>
2585 <term abbreviation="QoS" completeForm="quality of service" language="en"/>
2586 <explanation language="en"><text></text></explanation>
2590 <term abbreviation="FUP" completeForm="fair usage policy" language="en"/>
2591 <explanation language="en">
2593 a set of rules that should avoid excessive usage of a service by one user to the detriment of other user's comfort;
2594 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“
2599 <term abbreviation="API" completeForm="application programming interface" language="en"/>
2600 <explanation language="en">
2602 specifies interaction between software components;
2603 adds an abstraction layer which divides calling code and called code
2604 and enables multiple implementations of such API (or SPI) like multiple databases (database drivers), file systems, remote services etc.
2605 examples of API: POSIX, OpenGL, JDBC, JMS or JMX
2611 <term abbreviation="SPI" completeForm="service provider interface" language="en"/>
2612 <explanation language="en">
2614 a kind of API to be implemented by third party;
2615 can be installed as plugin/addon/extension and used by the application over standard interface;
2616 examples of SPI: JDBC, JNDI or JAXP
2623 <term abbreviation="JMX" completeForm="Java management extensions" language="en"/>
2624 <term abbreviation="MBean" completeForm="managed bean" language="en"/>
2625 <explanation language="en">
2627 a Java technology for monitoring and managing applications or devices;
2629 managed objects (MBeans) can emit events, can be asked for values (e.g. counters) or an action (method) can be called on them;
2630 this native Java technology can be also adapted/translated to other protocols like SNMP or WS/SOAP and integrated with the non-Java world;
2631 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)
2638 <term abbreviation="JMS" completeForm="Java message service" language="en"/>
2639 <explanation language="en">
2641 a Java API for message-oriented middleware (MOM);
2642 allows JEE components to create, send, receive and read messages;
2643 supports both point-to-point and publish-subscribe messaging models;
2644 can be adapted/translated to many other protocols like SMTP, AMQP, XMPP or SOAP;
2645 is defined in JSR 914;
2646 examples of JMS implementations: Apache ActiveMQ, OpenJMS, HornetQ
2651 <tag>messaging</tag>
2654 <term abbreviation="MOM" completeForm="message-oriented middleware" language="en"/>
2655 <explanation language="en">
2657 a software (or even hardware) infrastructure for sending and receiving messages;
2658 can also offer routing and transformation features;
2659 for Java the MOM API is standardized as JMS
2663 <tag>messaging</tag>
2666 <term abbreviation="AMQP" completeForm="advanced message queuing protocol" language="en"/>
2667 <explanation language="en">
2669 an open and standard binary protocol for message-oriented middleware (MOM);
2670 is vendor and platform independent;
2671 whereas JMS defines programming API and is Java specific, the AMQP defines the wire-level protocol;
2672 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;
2673 example of implementation: Apache ActiveMQ
2677 <tag>messaging</tag>
2680 <term abbreviation="" completeForm="wire-level protocol" language="en"/>
2681 <explanation language="en">
2683 the format of data sent over the network as stream of bytes;
2684 an application layer protocol
2690 <term abbreviation="JCA" completeForm="Java connector architecture" language="en"/>
2691 <explanation language="en">
2693 a Java EE technology for connecting application servers (AS) and enterprise information systems (EIS);
2694 is similar to JDBC (which is used for connecting to databases) but is much more generic
2695 and allows connecting any (often legacy) system using a specific connector
2702 <term abbreviation="EIS" completeForm="enterprise information system" language="en"/>
2703 <explanation language="en">
2705 an enterprise-class software system;
2706 typically high quality and critical service, large volumes of data, robust, supporting business processes
2712 <term abbreviation="OSGi" completeForm="Open Services Gateway initiative" language="en"/>
2713 <explanation language="en">
2715 a framework and module system for Java;
2716 allows applications with modular architecture composed from components
2717 that can be loaded, started, stopped, updated or uninstalled without restarting the JVM and the application;
2718 examples of OSGi implementations: Apache Felix, Equinox and Knopflerfish
2725 <term abbreviation="VPN" completeForm="virtual private network" language="en"/>
2726 <explanation language="en"><text></text></explanation>
2731 <term abbreviation="P2P" completeForm="peer to peer" language="en"/>
2732 <explanation language="en"><text></text></explanation>
2736 <term abbreviation="DNS" completeForm="domain name system" language="en"/>
2737 <explanation language="en"><text></text></explanation>
2742 <term abbreviation="ENUM" completeForm="E.164 number mapping" language="en"/>
2743 <explanation language="en"><text></text></explanation>
2746 <term abbreviation="NAPTR" completeForm="naming authority pointer resource records" language="en"/>
2747 <explanation language="en"><text></text></explanation>
2750 <term abbreviation="SPID" completeForm="service profile identifier" language="en"/>
2751 <explanation language="en"><text></text></explanation>
2754 <term abbreviation="DN" completeForm="distinguished name" language="en"/>
2755 <explanation language="en"><text></text></explanation>
2759 <term abbreviation="CN" completeForm="common name" language="en"/>
2760 <explanation language="en"><text></text></explanation>
2764 <term abbreviation="SN" completeForm="surname" language="en"/>
2765 <explanation language="en"><text></text></explanation>
2769 <term abbreviation="DC" completeForm="domain component" language="en"/>
2770 <explanation language="en"><text></text></explanation>
2774 <term abbreviation="CR" completeForm="change request" language="en"/>
2775 <explanation language="en">
2777 a request for changing a software – new features or modification of existing ones;
2778 when one or more CRs are developed, they are delivered as new version of software product;
2779 CR is requested by the customer (mobile network operator) and is delivered by the development team;
2780 CR consists of one or more DT which are assigned to particular developers
2786 <term abbreviation="DT" completeForm="development ticket" language="en"/>
2787 <explanation language="en">
2789 a task assigned to a software developer;
2790 one or more DTs together usually forms a CR;
2791 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);
2792 each commit in the versioning system should be linked to a DT
2798 <term abbreviation="TT" completeForm="trouble ticket" language="en"/>
2799 <explanation language="en">
2801 a request for fixing something in the production;
2802 requires some investigation and then can be solved by changing the configuration on site or by fixing the software (development)
2808 <term abbreviation="SRS" completeForm="System Requirement Specification" language="en"/>
2809 <explanation language="en">
2811 requirements on a software product or its particular change;
2812 is written from the system's point of view
2818 <term abbreviation="URS" completeForm="User Requirement Specification" language="en"/>
2819 <explanation language="en">
2821 requirements on a software product or its particular change;
2822 is written from the user's point of view
2828 <term abbreviation="" completeForm="engineering build" language="en"/>
2829 <explanation language="en">
2831 a build of a software product which was not done according to regular procedure and processes;
2832 might be used only for testing on site or during development – not in production;
2833 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
2839 <term abbreviation="" completeForm="monkey patching" language="en"/>
2840 <explanation language="en"><text></text></explanation>
2843 <term abbreviation="GMT" completeForm="Greenwich mean time" language="en"/>
2844 <explanation language="en"><text></text></explanation>
2848 <term abbreviation="UTC" completeForm="coordinated universal time" language="en"/>
2849 <explanation language="en"><text></text></explanation>
2853 <term abbreviation="TZ" completeForm="timezone" language="en"/>
2854 <term abbreviation="TZ" completeForm="time-zone" language="en"/>
2855 <term abbreviation="TZ" completeForm="time zone" language="en"/>
2856 <explanation language="en"><text></text></explanation>
2860 <term abbreviation="IETF" completeForm="Internet Engineering Task Force" language="en"/>
2861 <explanation language="en"><text></text></explanation>
2865 <term abbreviation="RFC" completeForm="request for comments" language="en"/>
2866 <explanation language="en"><text></text></explanation>
2870 <term abbreviation="" completeForm="vendor lock-in" language="en"/>
2871 <term abbreviation="" completeForm="vendor-lock-in" language="en"/>
2872 <term abbreviation="" completeForm="vendor lock in" language="en"/>
2873 <explanation language="en"><text></text></explanation>
2877 <term abbreviation="UT" completeForm="unit test" language="en"/>
2878 <explanation language="en"><text></text></explanation>
2882 <term abbreviation="AT" completeForm="acceptance testing" language="en"/>
2883 <term abbreviation="UAT" completeForm="user acceptance testing" language="en"/>
2884 <explanation language="en"><text></text></explanation>
2888 <term abbreviation="" completeForm="code coverage" language="en"/>
2889 <explanation language="en"><text></text></explanation>
2893 <term abbreviation="" completeForm="jUnit" language="en"/>
2894 <explanation language="en"><text></text></explanation>
2899 <term abbreviation="" completeForm="TestNG" language="en"/>
2900 <explanation language="en"><text></text></explanation>
2905 <term abbreviation="" completeForm="tcpdump" language="en"/>
2906 <term abbreviation="" completeForm="tshark" language="en"/>
2907 <term abbreviation="" completeForm="wireshark" language="en"/>
2908 <explanation language="en"><text></text></explanation>
2913 <term abbreviation="" completeForm="Asterisk" language="en"/>
2914 <explanation language="en"><text></text></explanation>
2917 <term abbreviation="OTR" completeForm="off-the-record messaging" language="en"/>
2918 <explanation language="en"><text></text></explanation>
2921 <tag>messaging</tag>
2925 <term abbreviation="CLI" completeForm="command-line interface" language="en"/>
2926 <explanation language="en"><text></text></explanation>
2930 <term abbreviation="TUI" completeForm="text user interface" language="en"/>
2931 <explanation language="en"><text></text></explanation>
2935 <term abbreviation="GUI" completeForm="graphical user interface" language="en"/>
2936 <explanation language="en"><text></text></explanation>
2940 <term abbreviation="UI" completeForm="user interface" language="en"/>
2941 <explanation language="en"><text></text></explanation>
2945 <term abbreviation="EOL" completeForm="end of line" language="en"/>
2946 <explanation language="en"><text></text></explanation>
2950 <term abbreviation="COB" completeForm="close of business" language="en"/>
2951 <!-- e.g. you have until COB today to show us why you should not be disconnected -->
2952 <explanation language="en"><text></text></explanation>
2956 <term abbreviation="SCCB" completeForm="software configuration control board" language="en"/>
2957 <explanation language="en"><text></text></explanation>
2961 <term abbreviation="SCCB" completeForm="site configuration control board" language="en"/>
2962 <explanation language="en"><text></text></explanation>
2966 <term abbreviation="RBDL" completeForm="rule based decision logic" language="en"/>
2967 <explanation language="en"><text></text></explanation>
2972 <term abbreviation="" completeForm="OpenMoko" language="en"/>
2973 <term abbreviation="" completeForm="FreeRunner" language="en"/>
2974 <explanation language="en">
2976 an open hardware GSM phone
2981 <term abbreviation="" completeForm="OpenBSC" language="en"/>
2983 <explanation language="en"><text></text></explanation>
2986 <term abbreviation="BSC" completeForm="base station controller" language="en"/>
2987 <explanation language="en"><text></text></explanation>
2990 <term abbreviation="BTS" completeForm="base transceiver station" language="en"/>
2991 <explanation language="en"><text></text></explanation>
2994 <term abbreviation="MSC" completeForm="mobile switching center" language="en"/>
2995 <explanation language="en"><text></text></explanation>
2998 <term abbreviation="HLR" completeForm="home location register" language="en"/>
2999 <explanation language="en"><text></text></explanation>
3002 <term abbreviation="AuC" completeForm="authentication center" language="en"/>
3003 <explanation language="en"><text></text></explanation>
3006 <term abbreviation="VLR" completeForm="visitor location register" language="en"/>
3007 <explanation language="en"><text></text></explanation>
3010 <term abbreviation="EIR" completeForm="equipment identity register" language="en"/>
3011 <explanation language="en"><text></text></explanation>
3014 <term abbreviation="FXO" completeForm="foreign exchange office" language="en"/>
3015 <explanation language="en">
3017 the FXO interface is typically the plug on the phone (or modem)
3018 which receives the POTS service;
3019 should be connected to an FXS interface (not to another FXO interface)
3024 <term abbreviation="FXS" completeForm="foreign exchange station" language="en"/>
3025 <explanation language="en">
3027 the FXS interface is typically the plug on the wall
3028 which delivers the POTS service from telephone company to the subscriber;
3030 supplies battery power,
3033 should be connected to an FXO interface (not to another FXS interface)
3038 <term abbreviation="PBX" completeForm="private branch exchange" language="en"/>
3039 <explanation language="en">
3041 a kind of telephone exchange used in some office or company for its own purposes;
3042 provides FSX interface for connected phones;
3043 can have FXO interface for connecting to PSTN (for calling outside the company);
3044 nowadays are often deployed digital VoIP PBXes based on free software like Asterisk;
3045 such telephony can be pure IP based with no POTS or can have some FSX or FXO interfaces
3050 <term abbreviation="PLMN" completeForm="public land mobile network" language="en"/>
3051 <explanation language="en">
3053 a network established for providing mobile telecommunications services to the public;
3054 e.g. GSM or UMTS networks operated by various carriers;
3055 particular PLMNs are identified by MCC and MNC codes
3060 <term abbreviation="PSTN" completeForm="public switched telephone network" language="en"/>
3061 <explanation language="en">
3063 the worldwide public telephony network consisting of networks of particular carriers;
3064 the network is developed according to ITU-T standards and recommendations
3065 and uses uniform system of telephone numbers based on ITU-T recommendation E.164
3066 which provides a single global address space for telephone numbers
3071 <term abbreviation="POTS" completeForm="plain old telephone service" language="en"/>
3072 <explanation language="en">
3074 traditional wired telephony based on analog signals
3075 (contrary to ISDN which is digital)
3080 <term abbreviation="CID" completeForm="caller ID" language="en"/>
3081 <term abbreviation="CLIP" completeForm="calling line identification presentation" language="en"/>
3082 <term abbreviation="CLID" completeForm="calling line identification" language="en"/>
3083 <term abbreviation="CNID" completeForm="calling number identification" language="en"/>
3084 <term abbreviation="CND" completeForm="calling number delivery" language="en"/>
3085 <explanation language="en">
3087 a service that delivers caller's phone number to the called party's device during ringing;
3088 so the called party knows who is calling before answering the phone;
3089 this service is common in digital networks like VoIP, GSM or ISDN but can be provided also on analog POTS networks
3094 <term abbreviation="DTMF" completeForm="dual-tone multi-frequency signaling" language="en"/>
3095 <explanation language="en"><text></text></explanation>
3098 <term completeForm="tip" language="en"/>
3099 <term completeForm="wire B" language="en"/>
3100 <term completeForm="b-Ader" language="de"/>
3101 <explanation language="en">
3103 tip of the telephone plug used for connecting telephone calls
3104 and metaphorically the one of the wires in the analog telephone line;
3105 ring conductor has negative direct current (DC) potential relative to the tip conductor;
3106 neither tip not ring are grounded in order to minimize hum from nearby AC power lines;
3107 in the RJ11 connector it is the fourth contact from the left (when holding the cable and looking at the contacts);
3108 usually only middle two (3 and 4) of six contacts are used;
3109 the wire is white-blue in common twisted pair or brown in German TAE system
3116 <term completeForm="ring" language="en"/>
3117 <term completeForm="wire A" language="en"/>
3118 <term completeForm="a-Ader" language="de"/>
3119 <explanation language="en">
3121 ring (middle section between tip and sleeve)
3122 of the telephone plug used for connecting telephone calls
3123 and metaphorically the one of the wires in the analog telephone line;
3124 has negative direct current (DC) potential relative to the tip conductor;
3125 the voltage is circa -48 to -60 Volts;
3126 neither tip not ring are grounded in order to minimize hum from nearby AC power lines;
3127 in the RJ11 connector it is the third contact from the left (when holding the cable and looking at the contacts)
3128 usually only middle two (3 and 4) of six contacts are used;
3129 the wire is blue in common twisted pair or white in German TAE system
3136 <term abbreviation="AGC" completeForm="auto gain control" language="en"/>
3137 <explanation language="en"><text></text></explanation>
3140 <term abbreviation="AEC" completeForm="auto echo cancellation" language="en"/>
3141 <explanation language="en"><text></text></explanation>
3144 <term abbreviation="VAD" completeForm="voice activity detection" language="en"/>
3145 <explanation language="en"><text></text></explanation>
3148 <term abbreviation="CNG" completeForm="comfort noise generation" language="en"/>
3149 <explanation language="en"><text></text></explanation>
3152 <term abbreviation="" completeForm="streamlining" language="en"/>
3153 <explanation language="en"><text>delivering better product faster with smaller teams of less-experienced engineers</text></explanation>
3154 <!-- Internal: if you dont understand, just ignore it :-) -->
3157 <term abbreviation="" completeForm="relevant company" language="en"/>
3158 <explanation language="en"><text>a company which is not going to bankrupt</text></explanation>
3159 <!-- Internal: if you dont understand, just ignore it :-) -->
3162 <term abbreviation="DAO" completeForm="data access object" language="en"/>
3163 <explanation language="en"><text></text></explanation>
3167 <term abbreviation="DTO" completeForm="data transfer object" language="en"/>
3168 <explanation language="en"><text></text></explanation>
3172 <term abbreviation="GSoC" completeForm="Google Summer of Code" language="en"/>
3173 <explanation language="en"><text>an annual program (since 2005) for students working on tasks for free software (open-source) projects</text></explanation>
3177 <term abbreviation="TBD" completeForm="to be done" language="en"/>
3178 <term abbreviation="TODO" completeForm="to do" language="en"/>
3179 <explanation language="en"><text>Something that should or will be done later. Used as comments in draft version of documents or in software source code.</text></explanation>
3183 <term abbreviation="FIXME" completeForm="fix me" language="en"/>
3184 <explanation language="en"><text>Something that should be fixed. Similar to TODO but describes rather some problem (bug) than feature request.</text></explanation>
3188 <term abbreviation="WIP" completeForm="work in progress" language="en"/>
3189 <explanation language="en"><text>It is not finished yet but it is in more advanced state than TODO. Someone is working on this task.</text></explanation>
3193 <term abbreviation="etc" completeForm="et cetera" language="la"/>
3194 <explanation language="en"><text>and so forth, and the rest</text></explanation>
3198 <term abbreviation="e.g" completeForm="exempli gratia" language="la"/>
3199 <explanation language="en"><text>for instance, for example</text></explanation>
3203 <term abbreviation="i.e." completeForm="id est" language="la"/>
3204 <explanation language="en"><text>in other words, that is</text></explanation>
3208 <term abbreviation="i.a." completeForm="inter alia" language="la"/>
3209 <explanation language="en"><text>among other things</text></explanation>
3213 <term abbreviation="N.B." completeForm="nota bene" language="la"/>
3214 <explanation language="en"><text>note well, note</text></explanation>
3218 <term abbreviation="per cent." completeForm="per centum" language="la"/>
3219 <explanation language="en"><text>percent, for each one hundred</text></explanation>
3223 <term abbreviation="p.a." completeForm="per annum" language="la"/>
3224 <explanation language="en"><text>annually</text></explanation>
3228 <term abbreviation="cca" completeForm="circa" language="la"/>
3229 <explanation language="en"><text>approximately</text></explanation>
3233 <term abbreviation="c.v." completeForm="curriculum vitae" language="la"/>
3234 <term abbreviation="CV" completeForm="curriculum vitae" language="la"/>
3235 <explanation language="en"><text>a document summarizing your relevant job experience and education</text></explanation>
3239 <term abbreviation="et al." completeForm="et alii" language="la"/>
3240 <explanation language="en"><text>and others, and co-workers</text></explanation>
3244 <term abbreviation="P.S." completeForm="post scriptum" language="la"/>
3245 <explanation language="en"><text>after what has been written; used at the end of the letters/messages for additions</text></explanation>
3249 <term abbreviation="Q.E.D." completeForm="quod erat demonstrandum" language="la"/>
3250 <explanation language="en"><text>which was to be demonstrated</text></explanation>
3254 <term abbreviation="R.I.P." completeForm="requiescat in pace" language="la"/>
3255 <explanation language="en"><text>rest in peace</text></explanation>
3259 <term abbreviation="vs." completeForm="versus" language="la"/>
3260 <explanation language="en"><text>against</text></explanation>