Procurement labels and translations
Introduction
We use the term "procurement labels" to refer to all natural language texts (names, descriptions, tooltips etc.) associated with any business term or other entity that is defined in the eForms Regulation or contained within the eForms SDK. The Publications Office is compiling and will continue to maintain a list of all procurement labels and their translations in all official EU languages.
In order to help implementers in the localization/internationalization of their applications, the eForms SDK contains the latest update of all procurement labels maintained by the Publications Office, in all official EU languages.
The labels are distributed in several files under the "translations" folder. Each file contains a specific type of label, in one language, as identified by its filename (see File naming conventions below).
The texts provided are not final and are subject to change. In particular, languages other than English have often been obtained via automated translation, and have not been reviewed yet. We will continue to add and update procurement labels in every future release of the SDK. |
File naming conventions
The file name is composed of two parts: <asset-type>_<language-identifier>.xml
. The filename is always in lower case.
field_en.xml
The <asset-type>
indicates the type of element the labels in the file are associated with. The possible asset types can be found in the relevant section below. The language identifier used is the standard 2 letter code in lowercase.
File format
The file format used is XML, with the structure used for Java Properties, with UTF-8 encoding.
Each translation is represented by an entry
XML element. Each entry
element
has a key
attribute which identifies the specific label. The translated text
for the specific language is encoded in the element’s text content.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd"> (1)
<properties>
<comment>Source: EMD-0.0.3</comment>
<entry key="field|name|BT-01-notice"> (2)
Legal basis of the procedure (3)
</entry>
<entry key="field|name|BT-13(d)-Part">Deadline for requesting additional information</entry>
<entry key="field|name|BT-531-Part">Additional nature of the contract</entry>
<entry key="field|name|BT-632-Lot">Name</entry>
</properties>
1 | Document type definition |
2 | Label key |
3 | Translated text |
Each label key is composed of three parts separated by a pipe character "|":
<asset-type>|<label-type>|<asset-id>
<asset‑type>
|
The same as the one indicated in the filename (see the list of available asset types below). |
<label‑type>
|
Allows the same asset to have different labels associated with it for different use cases (i.e. name, description etc.). A list of the allowed label types can be found in the relevant section below. |
<asset‑id>
|
Indicates the identifier of the asset (i.e. business term, field etc.). The asset identifiers are indicated in the field metadata ( |
To resolve a label you will need the label identifier which you can construct
from the current context of your application using the appropriate
<asset-type>
, <label-type>
and <asset-id>
.
Valid asset types
Standard asset types
business-term
|
The business terms are defined by the eForms regulation. Although there is no explicit list of business terms in the eForms SDK, all business terms are referenced by their corresponding fields in |
||
field
|
As the behaviour of a business term can vary among the different contexts it may appear in, the concept of a field is used to represent and encapsulate the behaviour of a business term under each specific context. We provide translated names, descriptions and fill-in instructions (hints) for all fields. |
||
group
|
Display groups are used to organise the fields of a notice when displayed in a form for filling-in. We provide translated names, descriptions and hints for all display groups.
|
||
node
|
Nodes are used to reconstruct the hierarchical structure of a notice XML file. They correspond to non-leaf XML elements in the notice. We try to provide translated names and descriptions for all nodes, however these are typically unnecessary for UI scenarios. |
||
codelist
|
These labels are used to provide translations of codelist names and descriptions. |
||
code
|
These labels are used to provide translations of codelist codes. When displaying the list of codes in a codelist or the selected code in a field use the corresponding |
||
notice
|
These labels provide translations of names and descriptions of all available notice types. Notice types are listed in |
||
view
|
These labels provide translations of names and descriptions of all available notice view templates. Notice view templates listed in |
||
pattern
|
Patterns are regular expressions (RegEx) that restrict the shape (format) of values that some text fields are allowed to accept. They are used in some business rules and implementers commonly find them associated with field constraints in |
||
interval
|
Intervals are numeric ranges that a field’s value is restricted in, and are used in some business rules. Implementers commonly find them associated with field constraints in |
||
expression
|
EFX expressions are used to formally express business rules and notice view templates. We try to provide translations for expression names, descriptions and hints for all expressions. |
||
rule
|
These labels correspond do business rules. Apart from the standard |
Special asset types
indicator
|
These labels provide text values that can be used when visualising a notice, in place of the standard |
auxiliary
|
Auxiliary labels (formerly known as |
Valid Label types
Standard label types
There are three label types that are available for all standard asset types.
name
|
Used with all standard asset types, these labels provide the name of the asset (e.g. the name of a field or a business term etc.). |
description
|
Used with all standard asset types, these labels provide a description of the asset (e.g. a description of a field or a business term etc.) |
hint
|
Formerly known as |
Special label types
text
|
When used with the The |
template
|
Used only with the |
when‑true
|
Used only with the |
when‑false
|
Used only with the |