oSIST prEN 17014-2:2026

SLOVENSKI STANDARD
01-marec-2026
Elektronska javna naročila - Faza pred oddajo naročila - 2. del: Transakcije
Electronic public procurement - Pre-award - Part 2: Transactions
Elektronisches öffentliches Beschaffungswesen - Ausschreibungsverfahren - Teil 2:
Transaktionen
Marchés publics électroniques - Avant attribution - Partie 2: Transactions
Ta slovenski standard je istoveten z: prEN 17014-2
ICS:
03.100.10 Nabava. Dobava. Logistika Purchasing. Procurement.
Logistics
35.240.20 Uporabniške rešitve IT pri IT applications in office work
pisarniškem delu
35.240.63 Uporabniške rešitve IT v IT applications in trade
trgovini
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

DRAFT
EUROPEAN STANDARD
NORME EUROPÉENNE
EUROPÄISCHE NORM
January 2026
ICS 35.240.63
English Version
Electronic public procurement - Pre-award - Part 2:
Transactions
Marchés publics électroniques - Avant attribution - Elektronisches öffentliches Beschaffungswesen -
Partie 2: Transactions Ausschreibungsverfahren - Teil 2: Transaktionen
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/TC 440.
If this draft becomes a European Standard, CEN members are bound to comply with the CEN/CENELEC Internal Regulations
which stipulate the conditions for giving this European Standard the status of a national standard without any alteration.

This draft European Standard was established by CEN in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CEN member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.

CEN members are the national standards bodies of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia,
Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway,
Poland, Portugal, Republic of North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Türkiye and
United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.

Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.

EUROPEAN COMMITTEE FOR STANDARDIZATION
COMITÉ EUROPÉEN DE NORMALISATION

EUROPÄISCHES KOMITEE FÜR NORMUNG

CEN-CENELEC Management Centre: Rue de la Science 23, B-1040 Brussels
© 2026 CEN All rights of exploitation in any form and by any means reserved Ref. No. prEN 17014-2:2026 E
worldwide for CEN national Members.

Contents Page
European foreword . 5
Introduction . 6
0.1 Derivative use pilot . 6
0.2 Intended use of this publication . 6
0.3 Parts of the document to which derivative use apply . 6
0.4 Use of ePO ontology . 6
1 Scope . 7
2 Normative references . 7
3 Terms and definitions . 7
4 Procurement procedure subscription . 9
4.1 Subscribe to procedure . 9
4.1.1 Business requirements . 9
4.1.2 Data model . 9
4.1.3 Business rules . 14
4.1.4 Mapping to eProcurement Ontology . 15
4.2 Subscribe to procedure confirmation . 19
4.2.1 Business requirements . 19
4.2.2 Data model . 19
4.2.3 Business rules . 24
4.2.4 Mapping to eProcurement Ontology . 25
4.3 Unsubscribe from procedure . 29
4.3.1 Business requirements . 29
4.3.2 Data model . 29
4.3.3 Business rules . 34
4.3.4 Mapping to eProcurement Ontology . 35
4.4 Unsubscribe from procedure confirmation . 39
4.4.1 Business requirements . 39
4.4.2 Data model . 39
4.4.3 Business rules . 44
4.4.4 Mapping to eProcurement Ontology . 45
5 Procurement documents access . 49
5.1 Procurement documents request . 49
5.1.1 Business requirements . 49
5.1.2 Data model . 49
5.1.3 Business rules . 54
5.1.4 Mapping to eProcurement Ontology . 55
5.2 Procurement documents . 59
5.2.1 Business requirements . 59
5.2.2 Data model . 60
5.2.3 Business rules . 75
5.2.4 Mapping to eProcurement Ontology . 77
6 Tender submission . 86
6.1 Tender . 86
6.1.1 Business requirements . 86
6.1.2 Data model . 87
6.1.3 Business rules . 94
6.1.4 Mapping to eProcurement Ontology . 95
6.2 Tender reception notification . 99
6.2.1 Business requirements . 99
6.2.2 Data model . 99
6.2.3 Business rules . 105
6.2.4 Mapping to eProcurement Ontology . 106
7 Procurement documents questions and answers . 110
7.1 Procurement documents questions . 110
7.1.1 Business emquirements . 110
7.1.2 Data model . 110
7.1.3 Business rules . 116
7.1.4 Mapping to eProcurement Ontology . 117
7.2 Procurement documents answers . 121
7.2.1 Business requirements . 121
7.2.2 Data model . 121
7.2.3 Business rules . 127
7.2.4 Mapping to eProcurement Ontology . 128
8 Tender clarification . 132
8.1 Tender clarification request . 132
8.1.1 Business requirements . 132
8.1.2 Data model . 133
8.1.3 Business rules . 139
8.1.4 Mapping to eProcurement Ontology . 140
8.2 Tender clarification . 145
8.2.1 Business requirements . 145
8.2.2 Data model . 145
8.2.3 Business rules . 151
8.2.4 Mapping to eProcurement Ontology . 152
9 Tender withdrawal . 157
9.1 Tender withdrawal . 157
9.1.1 Business requirements . 157
9.1.2 Data model . 157
9.1.3 Business rules . 163
9.1.4 Mapping to eProcurement Ontology . 164
9.2 Tender withdrawal reception notification . 168
9.2.1 Business requirements . 168
9.2.2 Data model . 168
9.2.3 Business rules . 174
9.2.4 Mapping to eProcurement Ontology . 175
10 Awarding . 179
10.1 Awarding notification . 179
10.1.1 Business requirements . 179
10.1.2 Data model . 180
10.1.3 Business rules . 187
10.1.4 Mapping to eProcurement Ontology . 189
11 Tendering message response . 194
11.1 Tendering message response . 194
11.1.1 Business requirements . 194
11.1.2 Data model . 194
11.1.3 Business rules . 198
12 Tenderer qualification . 199
12.1 Tenderer qualification . 199
12.1.1 Business requirements . 199
12.1.2 Data model . 200
12.1.3 Business rules . 208
12.1.4 Mapping to eProcurement Ontology . 210
12.2 Tenderer qualification reception confirmation . 216
12.2.1 Business requirements . 216
12.2.2 Data model . 216
12.2.3 Business rules . 222
12.2.4 Mapping to eProcurement Ontology . 223
12.3 Qualification response . 228
12.3.1 Business requirements . 228
12.3.2 Data model . 228
12.3.3 Business rules . 234
12.3.4 Mapping to eProcurement Ontology . 235
13 Invitation to tender . 239
13.1 Invitation to tender . 239
13.1.1 Business requirements . 239
13.1.2 Data model . 240
13.1.3 Business rules . 255
13.1.4 Mapping to eProcurement Ontology . 257
Annex A (normative) Overview of the clauses and sub-clauses which fall under derivative use 266
Bibliography . 270
European foreword
This document (prEN 17014-2:2026) has been prepared by Technical Committee CEN/TC 440
"Electronic Public Procurement", the secretariat of which is held by DIN.
This document is currently submitted to the CEN Enquiry.
This document is part of a series of multi-part documents prepared, or under preparation, by CEN/
TC 440:
— EN 17011 series [1]: e-Procurement Architecture, providing a set of spécifications outlining
different aspects of the e-Procurement architecture for Business Interoperability Spécifications.
— EN 17014 series [2]: Pre-award Business Interoperability Spécifications, providing a set of
spécifications outlining business choreography, transaction, syntax binding spécifications and
guidelines required to support the pre-award processes.
— EN 17015 series [3]: e-Catalogue Business Interoperability Spécifications, providing a set of
spécifications outlining business choreography, transaction, syntax binding spécifications and
guidelines required to support the e-Catalogue processes.
— EN 17016 series [4]: e-Ordering Business Interoperability Spécifications, providing a set of
spécifications outlining business choreography, transaction, syntax binding spécifications and
guidelines required to support the e-Ordering processes.
— EN 17017 series [5]: é-Fulfilmént Business Interoperability Spécifications, providing a set of
spécifications outlining business choreography, transaction, syntax binding spécifications and
guidelines required to support the e-Delivery processes.
Introduction
0.1 Derivative use pilot
This document falls under a CEN-CENELEC pilot on derivative use (as approved by the CEN/CA
(Administrative Board) through Decision 38/2019).
CEN has the copyright to all CEN publications, including their entire content and associated metadata,
as spécifiéd in CEN-CENELEC Guide 10 "Policy on dissemination, sales and copyright of CEN-CENELEC
Publications". However, through the derivative use pilot, CEN gives permission to the copying,
replication and translation of content from CEN/TC 440 deliverables in spécific circumstances.
Under the derivative use pilot, spécific sections of CEN/TC 440 publications may be copied, replicated
and translated in cases where this is a necessary condition for the meaningful implementation of the
publication. The sections which fall under derivative use will typically be elements, such as semantic
définitions and rules related to the use of information elements, and the name, définition and description
of processes and transactions, which are needed in software solutions, whether intended for sale in the
private market or for use in the public sector, and documents guiding the implementation and use in
spécific countries and/or business sectors.
Under derivative use, any use of content which has been copied, replicated, or translated from a
CEN/TC 440 publication must comply with the intended use of the publication. Derivative use cannot
be applied in use cases other than those the publication is intended to support. The intended use of this
publication is set out below.
0.2 Intended use of this publication
This document has been developed for any organization looking for guidance on the implementation
and use of electronic procurement deliverables as well as for organizations developing or implementing
software applications related to electronic procurement, such as software providers, business entities
and national authorities. These software applications shall be in conformance with this publication.
0.3 Parts of the document to which derivative use apply
Each subclause, which falls under derivative use, will be clearly marked with a note. The degree to which
the spécific content can be modifiéd is définéd in CEN/TS 17011-3 [6].
Annex A provides an overview of the line number references to all subclauses of the publication which
fall under derivative use.
0.4 Use of ePO ontology
This document uses the ePO ontology, owned by the European Union, available here (https://github
.com/OP-TED/ePO) and licensed under a CC BY 4.0 licence.
1 Scope
The document describes the transactions for pre-award processes between Contracting Entities (Buyer)
and Economic Operators (Seller), where the Buyer seeks to establish a contract for the procurement of
products, services, or works. The various possible behaviours of Buyers and Sellers are represented
through choreography variants as described in prEN 17014-2:2025 [7].
This document spécifiés the transactions described by the choreography variants and captures their
spécific functional and informational aspects. The transactions are grouped along the following
collaborations which are applied in pre-award choreographies:
— Procurement procedure subscription
— Procurement documents access
— Tender submission
— Procurement documents questions and answers
— Tender clarification
— Tender withdrawal
— Notify awarding
— Tendering message response
— Tenderer qualification
— Qualification response
— Invitation to tender
For each transaction, the document spécifiés the underlying business and information requirements,
including the functional and procedural objectives the transaction must fulfil, the structure and
semantics of the related data, and the governing business rules ensuring valid execution. In addition,
all définéd data elements are aligned with the eProcurement Ontology (ePO) to achieve semantic
interoperability and consistent representation across procurement systems.
This document is linked to Directive 2014/24/EC on public procurement [8], Directive 2014/25/EC on
procurement by entities operating in the water, energy, transport and postal services sectors [9],
Directive 2014/23/EC on the award of concession contracts [10] and Directive 2009 /81/EC on the
coordination of procedures for the award of contracts in the fiélds of defence and security [11].
Implementing Regulation (EU) 2019/1780 establishing standard forms for the publication of notices
[eForms] [12] and Implementing Regulation (EU) 2016/7 establishing the standard form for the
European Single Procurement Document [ESPD] [13] are supplementary regulations that are relevant
to this document.
The idéntifiér of this choreographies document is EN 17014-1:2026.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and définitions apply.
ISO and IEC maintain terminology databases for use in standardization at the following addresses:
— IEC Electropedia: available at http://www.electropedia.org/
— ISO Online browsing platform: available at http://www.iso.org/obp
3.1
agent
person, organization, or system that acts in procurement or has the power to act in procurement
3.2
business process
sequence or network of activities and collaborations between two or more agents
3.3
business process variant
sequence or network of activities and collaborations between two or more agents
Note 1 to entry: Different variants may support different electronic information exchange or collaborations. Agents
may publicly advertise their capability to support one or more variants in an automated fashion.
3.4
choreography
set of business processes having the same goals
3.5
collaboration
interaction between two or more agents that result in the exchange of data between the agents involved
as part of a business process
3.6
role
part played by an agent in a particular business process, including its responsibilities (options and
obligations) to perform certain activities and collaborations in that business process
Note 1 to entry: The role is used to show the division of labour and responsibility amongst the agents involved in
the process or within the organization of an agent.
3.7
state
set of options and obligations of the participating agents at a définéd step in a business process to
perform spécific activities and collaborations
Note 1 to entry: An activity of an agent or a collaboration can cause the transition of one state to another in a
prédéfinéd set of next steps.
3.8
transaction
content of data exchanged or shared between the agents in a collaboration
Note 1 to entry: A transaction is the atomic unit that leads to a synchronized state in the information systems of
collaborating agents. It is the basic building block to définé the choreography between agents. When an agent
recognizes an event that changes the state of a business object within a business process, it uses a transaction to
synchronize with the collaborating agent. A transaction therefore changes the state of a business process. It carries
the intention of the initiating agent and is represented by a data structure that is définéd by a data model. The
exchange of a transaction may alter legal obligations between business partners.
4 Procurement procedure subscription
4.1 Subscribe to procedure
4.1.1 Business requirements
The business requirements of the subscribe to procedure are spécifiéd in Table 1.
Table 1
ID Group Requirement
T-17014-2:2025-01- Subscribe to procedure (BG- The transaction shall include an idéntifiér, issue date,
R01 SUB) and issue time with seconds and time zone.
T-17014-2:2025-01- Economic operator preferred The transaction may specify the economic operator’s
R02 language preferred language.
T-17014-2:2025-01- The transaction shall include spécification
Process control (BG-PC)
R03 idéntification and business process type idéntifiér.
T-17014-2:2025-01- The transaction shall include the unique idéntifiér of
Procedure (BG-PROC)
R04 the procurement procedure.
The transaction shall include registration name,
T-17014-2:2025-01-
Economic operator (BG-ECOP) registration idéntifiér with scheme, electronic address
R05
idéntifiér with scheme, and country of registration.
The transaction may provide postal address (lines, city,
T-17014-2:2025-01- Economic operator postal
post code, subdivision) and shall include a country
R06 address (BG-EOAD)
code.
T-17014-2:2025-01- Economic operator contact The transaction shall include a contact point, and may
R07 information (BG-EOCI) include telephone number, email, and fax number.
The transaction shall include contracting body
T-17014-2:2025-01- registration idéntifiér with scheme and electronic
Contracting body (BG-COBO)
R08 address idéntifiér with scheme; it may include the
registration name.
The transaction may provide the contracting body’s
T-17014-2:2025-01- Contracting body postal address
postal address (lines, city, post code, subdivision) and
R09 (BG-CBAD)
shall include a country code.
T-17014-2:2025-01- Contracting body contact The transaction shall include a contact point, and may
R10 information (BG-CBCI) include telephone number, email, and fax number.
The transaction may include references to one or more
T-17014-2:2025-01- Procurement project lot
lots, each with a procurement project lot reference
R11 reference (BG-LOTR)
idéntifiér.
4.1.2 Data model
This data model describes the subscribe to procedure transaction:
Table 2
ID Level Card Business Term Description Semantic Type Usage Note
BG-SUB 0 1.1 Subscribe to procedure Transaction
BT-SUB-1 1 1.1 Issue Date The date on which the transaction is issued. Date
Time of issue of transaction. The issue time shall have
BT-SUB-2 1 1.1 Issue Time granularity of seconds, and include time zone Time
information
Subscribe to procedure
BT-SUB-3 1 1.1 The idéntifiér of the subscribe to procedure. Idéntifiér
idéntifiér
The language the economic operator prefers to use The lists of valid languages are
Economic operator
BT-SUB-4 1 0.1 when receiving documents from the contracting Code registered with the list Language
preferred language
body. Use the ISO 639 1 code list (ISO 639).
Information about the spécification that apply to the
BG-PC 1 1.1 Process control Group
transaction.
Spécification Idéntifiés the spécification of content and rules that
BT-PC-1 2 1.1 Idéntifiér
idéntification apply to the transaction.
Idéntifiés the name of the collaboration or business
Business process type process context in which the transaction appears. It
BT-PC-2 2 1.1 Idéntifiér
idéntifiér enables the buyer to process the invoice in an
appropriate way.
BG-PROC 1 1.1 Procedure Information about the procurement procedure. Group
A unique idéntifiér of a procurement procedure
spécifiéd by the contracting body. The idéntifiér is
BT-PROC-1 2 1.1 Procedure idéntifiér used as a reference number for all documents in the Idéntifiér
procurement process and idéntifiés procurement
documents.
Any natural or legal person or public entity or group
of such persons and/or entities, including any
BG-ECOP 1 1.1 Economic operator temporary association of undertakings, which offers Group
the execution of works and/or a work, the supply of
products or the provision of services on the market.
Economic operator
BT-ECOP-1 2 1.1 The name of the economic operator as it is registered. Text
registration name
Economic operator An idéntifiér that idéntifiés the economic operator,
1.1
registration idéntifiér such as a legal registration idéntifiér.
The Idéntification Scheme shall be
BT-ECOP-2 2 Idéntifiér
A type définition to determine the structure of the chosen from the entries of the list
1.1 Scheme idéntifiér
economic operator idéntifiér. published by the ISO/IEC 6523
maintenance agency.
Economic operator
1.1 electronic address Electronic address of the economic operator.
idéntifiér
BT-ECOP-3 2 Idéntifiér
The scheme idéntifiér shall be
A type définition to determine the structure of the
1.1 Scheme idéntifiér chosen from the EAS (Electronic
Economic operator electronic address idéntifiér.
Address Scheme) list.
The lists of valid countries are
The country where the economic operator is
BT-ECOP-10 2 1.1 Country of registration Code registered with the list Country
registered.
Codes (ISO 3166-1)
Economic operator A group of business terms providing information
BG-EOAD 2 0.1 Group
postal address about the address.
BT-EOAD-1 3 0.1 Address line 1 The main address line in an address. Text
An additional address line in an address that can be
BT-EOAD-2 3 0.1 Address line 2 used to give further details supplementing the main Text
line.
The common name of a city where the address is
BT-EOAD-4 3 0.1 City Text
located.
The idéntifiér for an addressable group of properties
BT-EOAD-5 3 0.1 Post code according to the relevant postal service, such as a ZIP Text
code or Post Code.
The subdivision of a country such as region, county,
BT-EOAD-6 3 0.1 Country subdivision Text
state, province etc.
The lists of valid countries are
BT-EOAD-7 3 1.1 Country code A code that idéntifiés the country. Code registered with the list Country
Codes (ISO 3166-1)
Economic operator A group of business terms providing contact
BG-EOCI 2 0.1 Group
contact information information
BT-EOCI-1 3 1.1 Contact point The name of the contact point. Text
Contact telephone
BT-EOCI-2 3 0.1 A phone number for the contact point. Text
number
BT-EOCI-3 3 0.1 Contact email address An e-mail address for the contact point. Text
BT-EOCI-4 3 0.1 Contact fax number A fax number for the contact point. Text
The contracting authority or contracting entity who
is buying supplies, services or tendering public
BG-COBO 1 1.1 Contracting body Group
works. The contracting body is responsible for
executing the procurement process.
Contracting body
BT-COBO-1 2 0.1 The name of the contracting body as it is registered. Text
registration name
Contracting body
1.1 The national idéntifiér of a contracting body.
registration idéntifiér
The Idéntification Scheme shall be
BT-COBO-2 2 Idéntifiér
A type définition to determine the structure of the chosen from the entries of the list
1.1 Scheme idéntifiér
contracting body idéntifiér. published by the ISO/IEC 6523
maintenance agency.
Contracting body
1.1 electronic address Electronic address of the contracting body.
idéntifiér
BT-COBO-3 2 Idéntifiér
The scheme idéntifiér shall be
A type définition to determine the structure of the
1.1 Scheme idéntifiér chosen from the EAS (Electronic
contracting body electronic address idéntifiér.
Address Scheme) list.
Contracting body postal A group of business terms providing information
BG-CBAD 2 0.1 Group
address about the address.
BT-CBAD-1 3 0.1 Address line 1 The main address line in an address. Text
An additional address line in an address that can be
BT-CBAD-2 3 0.1 Address line 2 used to give further details supplementing the main Text
line.
The common name of a city where the address is
BT-CBAD-4 3 0.1 City Text
located.
The idéntifiér for an addressable group of properties
BT-CBAD-5 3 0.1 Post code Text
according to the relevant postal service.
The subdivision of a country such as region, county,
BT-CBAD-6 3 0.1 Country subdivision Text
state, province etc.
The lists of valid countries are
BT-CBAD-7 3 1.1 Country code A code that idéntifiés the country. Code registered with the list Country
Codes (ISO 3166-1)
Contracting body contact A group of business terms providing contact
BG-CBCI 2 0.1 Group
information information.
BT-CBCI-1 3 1.1 Contact point The name of the contact point. Text
Contact telephone
BT-CBCI-2 3 0.1 A phone number for the contact point. Text
number
BT-CBCI-3 3 0.1 Contact email address An e-mail address for the contact point. Text
BT-CBCI-4 3 0.1 Contact fax number A fax number for the contact point. Text
A reference to a procurement project lot. A lot is a
subdivision of a larger procurement project,
Procurement project lot
BG-LOTR 1 0.n grouping similar goods, services, or works, allowing Group
reference
multiple suppliers to bid on spécific parts rather than
the whole project.
Procurement project lot
BT-LOTR-1 2 1.1 An idéntifiér for the lot. Idéntifiér
reference idéntifiér
4.1.3 Business rules
These business rules are describing the subscribe to procedure transaction:
Table 3
Rule ID Description Context Term
Subscribe to procedure shall have a
Subscribe to procedure document
BR-SUB-1 subscribe to procedure document BT-SUB-3
idéntifiér
idéntifiér
Subscribe to procedure shall have a
BR-SUB-2 Issue Date BT-SUB-1
document issue date
Subscribe to procedure shall have a
BR-SUB-3 document issue time with granularity Issue Time BT-SUB-2
of seconds and time zone.
The transaction shall have a
BR-PC-1 Spécification idéntification BT-PC-1
spécification idéntifiér
The transaction shall have a business
BR-PC-2 Business process type idéntifiér BT-PC-2
process type idéntifiér
The transaction shall have a procedure
BR-PROC-1 Procedure idéntifiér BT-PROC-1
idéntifiér
The transaction shall have an
BR-ECOP-1 Economic operator registration name BT-ECOP-1
economic operator registration name.
The transaction shall have an
Economic operator registration
BR-ECOP-2 economic operator registration BT-ECOP-2
idéntifiér
idéntifiér.
The economic operator registration
BR-ECOP-3 idéntifiér shall have a scheme Scheme idéntifiér BT-ECOP-2
idéntifiér.
The transaction shall have an
Economic operator electronic address
BR-ECOP-4 economic operator electronic address BT-ECOP-3
idéntifiér
idéntifiér.
The economic operator electronic
BR-ECOP-5 address idéntifiér shall have a scheme Scheme idéntifiér BT-ECOP-3
idéntifiér.
The transaction shall have a country of
BR-ECOP-6 Economic operator BT-ECOP-10
registration of the economic operator
If an economic operator postal address
BR-EOAD-1 is provided, it shall include a country Country code BT-EOAD-7
code.
If economic operator contact
BR-EOCI-1 information is provided, it shall Contact point BT-EOCI-1
contain a contact point.
If economic operator contact
information is provided, at least one of Economic operator contact
BR-EOCI-2 BG-EOCI
telephone, fax, or email shall be information
present.
The transaction shall have a
Contracting body registration
BR-COBO-2 contracting body registration BT-COBO-2
idéntifiér
idéntifiér.
The contracting body registration
BR-COBO-3 idéntifiér shall have a scheme Scheme idéntifiér BT-COBO-2
idéntifiér.
The transaction shall have a
Contracting body electronic address
BR-COBO-4 contracting body electronic address BT-COBO-3
idéntifiér
idéntifiér.
The contracting body electronic
BR-COBO-5 address idéntifiér shall have a scheme Scheme idéntifiér BT-COBO-3
idéntifiér.
If contracting authority postal address
BR-CBAD-1 is provided, it shall include a country Country code BT-CBAD-7
code.
If contracting body contact
BR-CBCI-1 information is provided, it shall Contact point BT-CBCI-1
contain a contact point.
If contracting body contact
information is provided, at least one of
BR-CBCI-2 Contracting body contact information BG-CBCI
telephone, fax, or email shall be
present.
Procurement project lot reference
BR-LOTR-1 shall have a procurement project lot Procurement project lot reference BT-LOTR-1
reference idéntifiér.
4.1.4 Mapping to eProcurement Ontology
Table 4 shows how the business terms of the subscribe to procedure map to the eProcurement Ontology:
Table 4
ID Business Term ePO class path ePO property path
BG-SUB Subscribe to procedure epo:ExpressionOfInterest
BT-SUB-1 Issue Date epo:ExpressionOfInterest / xsd:dateTime ?this dct:issued ?value .
BT-SUB-2 Issue Time epo:ExpressionOfInterest / xsd:dateTime ?this dct:issued ?value .
epo:ExpressionOfInterest / adms:Idéntifiér /
BT-SUB-3 Subscribe to procedure idéntifiér ?this adms:idéntifiér / skos:notation ?value .
rdf:PlainLiteral
?this
BT-SUB-4 Economic operator preferred language epo:ExpressionOfInterest / at-voc:language epo:hasPreferredLanguageForProcurementDocume
nt ?value .
epo:ExpressionOfInterest /
BG-PC Process control ?this épo:hasSpécificationInformation ?value .
épo:SpécificationInformation
épo:SpécificationInformation / adms:Idéntifiér / ?this épo:hasSourcéSpécificationCustomization /
BT-PC-1 Spécification idéntification
rdf:PlainLiteral skos:notation ?value .
épo:SpécificationInformation / adms:Idéntifiér /
BT-PC-2 Business process type idéntifiér ?this épo:isUsédInProfilé / skos:notation ?value .
rdf:Plain
...