eForms SDK glossary

A

authority tables

Authority tables standardise the codes used as values in certain fields. Published by the Publications Office in EU Vocabularies. For eForms, also included in the codelists folder of the SDK.

C

codelists	Alternative name for *authority tables*. Also, the name of a folder in the SDK that contains… codelists.
conceptual model	An abstraction used to decouple the business concept of an eForms notice from its XML representation. Comprised of a hierarchy of *nodes* and *fields*.

D

display group	A structural element of the *visual model*.
domain specific language	A computer language designed specifically to cover the needs of a particular business domain.
DSL	Acronym for *Domain Specific Language*.

E

eForms Expression Language	A *domain specific language* designed for eForms. Used in the SDK to encode business rules and *view templates*.
EFX	Acronym for *eForms Expression Language*.
end-user	The person using an eForms application.

F

fields.json	A JSON file in the `fields` folder of the eForms SDK, containing the *conceptual model*.
fields repository	See *fields.json*.
field	A data element of the *conceptual model. Contained within a parent node*. Points to an element value or an attribute value inside a notice XML file.
form	Short for *notice form*.

I

input field

A data element of the visual model. Contained in a parent display group. Represents an interactive element on a form where the end-user can enter or select the value of a field.

J

jargon

See slang.

L

labels	Short for *public procurement labels*.
logical model	The eForms Schema. Defines the data types, elements and attributes that can constitute an eForms notice XML file.

N

node	A structural element of the *conceptual model. Contains other nodes* and *fields*. Points to an XML element inside a notice XML file.
notice form	A computer user interface for an *end-user* to fill in and submit a notice.
notice type definition	A file containing information on how a notice form is to be shown on a user’s screen. See also *visual model*.
NTD	Acronym for *notice type definition*.

P

parser	A computer program used for *parsing* a computer language.
parsing	The process of breaking down a text written in a computer language, and recognising the instructions contained in it.
physical model	The *UBL*/XML inside a notice XML file.
public procurement labels	Static texts (names, descriptions, messages etc.) related to public procurement terms and elements contained within the eForms SDK. Translated in all official EU languages. Intended to be used by the user interface of eForms Applications. Provided in the `translations` folder of the SDK.

S

schematrons	The name of a folder inside the eForms SDK. It contains the Schematron validation rules used by *TED CVS*.
slang	See *jargon*.
SVRL	Acronym for "Schematron Validation Report Language". A flavour of XML produced by a Schematron processor. Used by *TED CVS* to create validation reports.

T

TED Central Validation Service	A RESTFull web service, that validates notice XML files before they can be accepted for publication.
TED CVS	Acronym of the *TED Central Validation Service*.
translations	The name of a folder in the eForms SDK, containing *public procurement labels*
transpiler	A computer program that reads source code written in an input language and translates it to source code written in a target output language.

U

UBL	Acronym for *Universal Business Language*.
Universal Business Language	An open standard for XML business documents. The eForms Schema is based on *UBL*.

V

view templates	Templates for visualising notices in a readable document form (PDF, HTML etc.). Written in *EFX*.
visual model	An abstraction defining the visual structure of a *notice form. Comprised of display groups* and *input fields*.