Glossary

Class names and definitions

Class name	Definition
cccev:Constraint	Limitation applied to an Information Concept. Additional Information: Constraints are requirements in themselves, since they impose prerequisites which influence the definition, use and/or fulfilment of the requirement. They represent hard conditions such as minimum or maximum expressions which can be used to evaluate pieces of information, the required age, income, involvement in activities, etc. An example from the eProcurement domain is a threshold as the minimum turnover required by the buying organisation to select the candidates. Note that CCCEV does not provide any specific guidance on when which kind of Requirement should be used. Users of this vocabulary should make decisions on this topic in their specific context.
cccev:Criterion	Condition for evaluation or assessment. Additional Information: In general, Criteria are used for comparison, filtering or selection purposes. Criteria usually set minimum conditions (e.g. limits, intervals, thresholds, etc.) that need to be met in order to pass the requirements or to fulfil them to a certain degree or quality. The concept of Criteria is broader than the concept of Constraint since it covers more usages. The evaluation of the fulfilment is usually supported by the provision of Evidence. For example in the eProcurement domain, the eProcurement Ontology defines different subclasses of Criterion such as exclusion grounds, selection criteria or award criteria. A concrete example of a Criterion is 'participation in a criminal organisation' which could also be considered as an exclusion ground criterion in the procurement domain or for requiring a public service.
cccev:Evidence	Proof that a Requirement is met.
cccev:InformationConcept	Piece of information that the Evidence provides or the Requirement needs.
cccev:Requirement	Condition or prerequisite that is to be proven by Evidence. Additional Information: Requirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent. To illustrate the notion: the European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy.
cpov:ContactPoint	Information (e.g. e-mail address, telephone number) of a person or department through which the user can get in touch with. Additional information: This class represents the contact information for a Public Service, Channel, Public Organization, etc. The contact point could be a role, email address, telephone number, etc. WG approval 5/11/2019
cpov:PublicOrganisation	An Organization that is defined as being part of the public sector by a legal framework at any level. Additional information: A body governed by public law: - (a) established for the specific purpose of meeting needs in the general interest - (b) having legal personality; - (c) financed, for the most part by the State, or regional or local authorities. Examples of Public Organisations are municipality, international public body, ministry, others. WG Approval 28/04/2020
cpv:Person	A individual human being who may be dead or alive, but not imaginary.
cv:Channel	A medium through which an Agent provides, uses or interacts in another way with a Public Service. Typical examples include online services, phone, walk-in centres etc. Additional Information Software solutions and electronic devices for communication and exchange of information between buyers and economic operators. Lots may use ad-hoc electronic means of communication that are not generally available such as specific solutions for secure and dedicated communication or non-standard eCatalogues. See also Directive recitals 53 to 56. WG Suggestion to eForms 30/09/2019
dct:Location	An identifiable geographic place or named place.
epo:AccessTerm	Conditions and stipulations about where and how to access the procurement documents. WG Approval 09/03/2021
epo:AcquiringCentralPurchasingBody	Role of an agent procuring activities conducted on a permanent basis in the form of the acquisition of supplies and/or services intended for other buyers. Additional Information: In public procurement the role of Acquiring Central purchasing body is carried out by a Central Purchasing Body for other Contracting Authorities. WG approval 05/08/2021
epo:AcquiringParty	The role of an agent that acts on the buying side of a procurement process.
epo:AgentInRole	Relative concept that ties an agent to a part they play in a given situational context. Additional information: The classification of roles is based is based on the degree of involvement into the procurement process: - Primary (Procurement) role is directly involved in the procurement process; - Secondary (Procurement sub-)role is secondary to the procurement process - Tertiary (Related) role is not involved in the procurement process.
epo:AuxiliaryParty	Role of an agent who may be mentioned in the information exchanged during the procurement process but who does not play an active part in it.
epo:AwardCriterion	Describes a requirement that the tender needs to resolve and on which the tender is evaluated and ranked. (WG approval 05/11/2018)
epo:AwardDecision	Resolution of the buyer as to the result of the procurement procedure. (WG approval 14/11/2018)
epo:Awarder	Organisation that signs the award decision.
epo:AwardEvaluationTerm	Conditions and stipulations defining particularities of the evaluation of award criteria.
epo:AwardingCentralPurchasingBody	Role of an agent procuring activities conducted on a permanent basis in the form of the award of public contracts or the conclusion of framework agreements for works, supplies or services intended for other buyers. Additional Information: In public procurement the role of Awarding Central purchasing body is carried out by a Central Purchasing Body for other Contracting Authorities. WG approval 05/08/2021
epo:BudgetProvider	A role of an agent whose budget is used to pay for the contract.
epo:Business	A private law company registered in a national registry. WG Approval 28/04/2020
epo:Buyer	A role of an agent that awards a contract and/or purchases items. Additional information: In public procurement the role of buyer is carried out by the following types of organisation: contracting authority, contracting entity, a defence contractor, an international organisation, or an organisation awarding a contract subsidized by a contracting authority. In pre-award, the buyer generally awards the contract, however future purchasers may be foreseen. In post-award the buyer generally refers to the purchaser of items.
epo:CatalogueProvider	A role of an agent compiling and supplying a catalogue. Additional Information: The catalogue provider role is usually played by the agent that acts as a seller, or by another agent that acts on behalf of the seller. WG Approval 28/01/2021
epo:CatalogueReceiver	A role of an agent processing a catalogue. Additional Information: The catalogue receiver may not only receive it but also validate it, process it, etc. The catalogue receiver role is usually played by the agent that acts as a buyer, or by another agent that acts on behalf of the buyer. WG Approval 28/01/2021
epo:CentralPurchasingBody	Role of an agent that provides centralised purchasing activities and, possibly, ancillary purchasing activities for other buyers. Additional Information: In public procurement the role of Central purchasing body is carried out by a Contracting Authority for other Contracting Authorities. Contracting authority procuring activities conducted on a permanent basis, in one of the following forms:[...](b) the award of public contracts or the conclusion of framework agreements for works, supplies or services intended for contracting authorities; WG approval 05/08/2021
epo:ConcessionContract	A contract between one or more buyers and one or more economic operators giving the right to the economic operators to exploit the rights foreseen in the contract which may include the receipt of payments. WG Approval 24/05/2022
epo:ConcessionEstimate
epo:ContextSpecificDescription	A description concerning a procurement object or a notice in a specific situation context. Additional Information: The description has its own identity (+I) but is dependent (+D) on the concerned entity. We say that ContextSpecificDescription *concerns* an entity.
epo:ContextualProjection	Projection of an entity and all of its properties that hold in a given situation context. Additional Information: The contextual projection does not have its own identity (-I), is dependent (+D) on the described entity, and is anti-rigid (~R) We say that ContextualProjection *describes* an entity. Adaptation of ContextSlices pattern encoding a 4D view. http://ontologydesignpatterns.org/wiki/Submissions:Context_Slices
epo:Contract	A voluntary, deliberate, and legally binding agreement between two or more competent parties. Additional information: This includes concession contracts. (WG approval 01/06/2018)
epo:ContractLotCompletionInformation	Information related to a given Lot at the end of the procurement.
epo:ContractModification	An announcement of the modification of a contract/concession during its term by a buyer.
epo:Contractor	The role of an agent that has signed a contract with a Buyer. WG approval 08/11/2022
epo:ContractSpecificTerm	Gathering class for conditions and stipulations related to a contract in the post-award phase.
epo:ContractTerm	Conditions and stipulations defining particularities of the post award phase. (WG approval 23/11/2018)
epo:DesignContestRegimeTerm	Conditions and stipulations defining particularities of a Design Contest. WG approval: 04-02-2021
epo:DirectAwardTerm	Conditions and stipulations defining particularities of the award of a contract without prior publication. Addtional Information: Direct award may refer to a previous procedure and/or specific Lot(s). It may also refer to other justified situations whereby there is no previous procedure. See Directive 2014/24/EU Article 32. WG Approval 22/11/2019
epo:Document	A set of interrelated Business Information representing the business facts and associated metadata. The information may be conveyed in any language, medium or form, including textual, numerical, graphic, cartographic, audio-visual forms, etc. WG Approval 23/05/2019
epo:Duration	The length of time in which a concept occurs.
epo:DynamicPurchaseSystemTechniqueUsage	An electronic system that is set up by a procuring entity which lists the economic operators that satisfy the selection and exclusion criteria. This technique then allows the purchase via consultation of the listed tenderers using award criteria. (WG approval 13/07/2018)
epo:EAuctionTechniqueUsage	A repetitive technique in which new prices, revised downwards, and/or new values concerning certain elements of tenders are bid on-line. Additional Information: This corresponds in eForms to BT-767 Electronic Auction . WG approval 20/07/2018
epo:ElementChangeDescription	Information about a specific field to be changed with regard to a previous notice.
epo:ElementConfidentialityDescription	Information about a specific field not intended for publication. Additional Information: In the model, a field is identified by a combination of a class and a property on that class. Therefore, these two references should be both provided.
epo:ElementDescription	Description about a specific resource.
epo:ElementModificationDescription	Information about a specific field to be changed with regard to the modification of a contract.
epo:EmploymentInformationProvider	A role of an agent responsible for providing information concerning the general regulatory framework for employment protection and working conditions.
epo:EnvironmentalProtectionInformationProvider	A role of an agent responsible for providing information concerning the general regulatory framework for environmental protection.
epo:Estimate	An approximate calculation or a judgement of the value, number, quantity or extent of something.
epo:EvaluationTerm	Conditions and stipulations defining particularities of the tender evaluation. (WG approval 23/11/2018)
epo:ExclusionGround	Describes a legal requirement to be met by the economic operator to be a candidate in the procurement procedure. Additional Information: This corresponds in eForms to BG-701 Exclusion Grounds. WG approval 31/10/2018
epo:ExpressionOfInterest	Document presenting an economic operator's request to be considered for procedures covering a specific domain. WG approval 13/04/2021
epo:FrameworkAgreement	An agreement between one or more contracting authorities and one or more economic operators. WG approval 18/05/2021
epo:FrameworkAgreementTechniqueUsage	Technique that establishes the terms governing contracts to be awarded during a given period, in particular with regard to price and, where appropriate, the quantity envisaged. WG approval 18/05/2021
epo:FrameworkAgreementTerm	Conditions and stipulations defining particularities in a framework agreement.
epo:Fund	A financial resource used to support the procurement. Additional Information: In the context of EU, funds can be divided into programmes, actions and projects. Examples of EU funds are: the European Structural and Investment Funds, European Social Fund (ESF), the Connecting Europe Facility (CEF) programme, or the ISA2 programme and its actions (e.g. Action 2016.05 European Public Procurement Initiative, which supports the eProcurement Ontology under sub-action 3). Funds may change between the lot and the contract, for example in the case of an emergency crisis, a contract may be financed by a budget that was not foreseen in the call. WG Approved 14/05/2019
epo:GreenProcurement	Approach whereby buyers seek to procure with a reduced environmental impact. Additional Information: The approach may apply to the complete life cycle. The reduced environmental impact is in comparison to goods, services and works with the same primary function that would otherwise be procured. Tightly related are article 68 - Life-cycle costing and article 67 - most economically advantageous tender (see GPP handbook) https://ec.europa.eu/environment/gpp/pdf/Buying-Green-Handbook-3rd-Edition.pdf An instance of the class GreenProcurement is represented in eForms with the code "env-imp" defined in the codelist strategic-procurement.paragraphs) https://ec.europa.eu/environment/gpp/pdf/Buying-Green-Handbook-3rd-Edition.pdf
epo:Identifier	A character string to identify and distinguish uniquely, one instance of an object in an identification scheme from all other objects in the same scheme together with relevant supplementary information.
epo:IndefiniteDuration
epo:InnovativeProcurement	An instance of the class InnovativeProcurement is represented in eForms with the code "inn-pur" defined in the codelist strategic-procurement. Research (21/01/2020): Purchasing and early adoption of solutions which are not yet available on large scale commercial basis. Source: Adapted from the Digital Single Market's Policy on Public Procurement of Innovative Solutions. https://ec.europa.eu/digital-single-market/en/public-procurement-innovative-solutions Additional Information: ‘innovation’ means the implementation of a new or significantly improved product, service or process, including but not limited to production, building or construction processes, a new marketing method, or a new organisational method in business practices, workplace organisation or external relations inter alia with the purpose of helping to solve societal challenges or to support the Europe 2020 strategy for smart, sustainable and inclusive growth; See: Directive 2014/24 Articles: 2, 26 (3), 31, 67 (2.a) Question: Is Pre-Commercial Procurement (PCP) another type of Strategic Procurement?
epo:LeadBuyer	A role of an agent who is a Buyer and takes the administrative lead of the procedure. WG agreement: 2022-11-22
epo:Lot	A qualitative, quantitative or strategic subdivision of the goods, services or works to be procured, allowing the award of one or more contracts. WG approval 12/09/2018
epo:LotAwardOutcome	Result concerning the Lot attributed by the awarder.
epo:LotGroup	Combination of several lots to conduct comparative assessment of the tenders. Additional Information: The comparative assessment may refer to the selection criteria, award and value that apply to several lots. Pending of discussion with eForms Member States may provide that, where more than one lot may be awarded to the same tenderer, contracting authorities may award contracts combining several or all lots where they have specified in the contract notice or in the invitation to confirm interest that they reserve the possibility of doing so and indicate the lots or groups of lots that may be combined.
epo:LotGroupAwardInformation	Award information related to a given group of Lots.
epo:LotSpecificTerm	Gathering class for conditions and stipulations related to a lot.
epo:Mediator	A role of an agent that attempts to resolve a dispute between different agents and come to an agreement. WG approval 20/04/2021
epo:MonetaryValue	A number of monetary units specified using a given unit of currency. WG approval 13/04/2021
epo:MultipleStageProcedureTerm	Conditions and stipulations defining particularities of procedures carried out in several steps Additional Information: Generally this refers to procedures where selection is carried out to qualify tenderers who are then requested to submit the rest of their tender for evaluation is Restricted procedure. WG Approval 15/04/2021
epo:Notice	Document published by the buyer about market opportunities and results. WG Approval 23/05/2019
epo:NoticeAwardInformation	Information about an award notice.
epo:NoticeChange	Information about a corrigendum in a notice.
epo:NoticeDescription	Descriptions about the notice publishing, or providing evolutions of resources.
epo:OfferingParty	The role of an agent that acts on the economic operator side during a procurement process. Additional information: As per the European Procurement Directives the notion of ‘economic operators’ should be interpreted in a broad manner so as to include any persons and/or entities which offer the execution of works, the supply of products or the provision of services on the market, irrespective of the legal form under which they have chosen to operate. Thus, firms, branches, subsidiaries, partnerships, cooperative societies, limited companies, universities, public or private, and other forms of entities than natural persons should all fall within the notion of economic operator, whether or not they are ‘legal persons’ in all circumstances.
epo:OfflineAccessProvider	A role of an agent responsible for providing offline access to the procurement documents.
epo:OpeningTerm	Conditions and stipulations defining particularities of the opening of tenders. Additional Information: The opening of tenders is the event when tenders are made accessible for evaluation, it is generally the same date and time for all tenders. WG Approval 15/04/2021
epo:OrganisationGroup	Agreed collaboration of several organisations. Additional Information: This concept has been created to fulfill the need to represent a grouping of organisations that is not necessarily registered ie consortia. WG approval 15/04/2021
epo:OtherEntity	Economic operator (who is not a subcontractor) on which the tenderer relies upon, to meet selection criteria.
epo:ParticipationRequestProcessor	A role of an agent responsible for processing requests to participate.
epo:ParticipationRequestReceiver	A role of an agent responsible for receiving requests to participate.
epo:ParticipationRequestTerm	Conditions and stipulations defining particularities of requesting participation in a procedure.
epo:PaymentExecutor	A role of an agent responsible for executing the payment.
epo:Period	A time interval or a duration. (WG approval 28/04/2020)
epo:PlannedProcurementPart	A subdivision of a planned procurement that may later become one or more lots or a self-standing procedure. A lot or a procedure can also cover one or more parts of the planned procurement. WG Approval 20/06/2019
epo:Prize	A reward given in a contest. WG approval: 15/04/2021
epo:Procedure	A legally defined set of administrative activities conducted to conclude one or more contracts. Additional Information The procedure is categorised in the law according to different rules determining whether the procedure is open, restricted, negotiated with or without publicity, etc. (see Procedure Type). WG Approval 20/08/2019
epo:ProcedureSpecificTerm	Gathering class for conditions and stipulations related to a procedure.
epo:ProcedureTerm	Conditions and stipulations defining particularities of the procedure. (WG approval 23/11/2018)
epo:ProcessPlanningTerm	Conditions and stipulations defining particularities of the unfolding of the procurement process.
epo:ProcurementCriterion	A criterion specific to Procurement. Additional Information: This Procurement Criterion can be only Exclusion Ground, Selection Criterion or Award Criterion. Each of these criteria can contain subcriteria (Criterion class). WG Approval 23/04/2020
epo:ProcurementDocument	Document produced or referred to by the buyer to describe or determine elements of the procurement. Additional information: Procurement documents are to be accessible since the date of publication of the contract notice or the prior information notice when used as a call for competition. Examples of procurement documents are technical specifications, the descriptive document, proposed conditions of contract, formats for the presentation of documents by candidates and tenderers, information on generally applicable obligations. Other documents related to the procedure such as notices are not considered to be procurement documents. WG Approval 23/05/2019 17:08:30
epo:ProcurementElement	Gathering class for critical/central elements in the procurement process. TODO: add definition Additional information: Alias: ProcurementComponent
epo:ProcurementObject	The whole or a division of goods, services or works to be procured. Additional Information: Anything that can specify the procurement content (i.e. goods, services, work) is a Procurement Object. In a sense, such an "object" can constitute the "object of a contract". To test whether something is a Procedure Object check if it can have a Purpose and/or CPV classification (<i>The CPV establishes a single classification system for public procurement aimed at standardising the references used by contracting authorities and entities to describe the subject of procurement contracts.</i>). Note: Procedure, seems to be an exception from this rule. Because it is a conflated term: it carries process properties and "purpose" properties.
epo:ProcurementProcedureInformationProvider	A role of an agent responsible for providing additional information about the procurement procedure.
epo:ProcurementProcessInformation	Information about the temporal unfolding or succession of procurement objects.
epo:ProcurementServiceProvider	Role of a public or private body which offers ancillary purchasing activities on the market. Additional information "Ancillary purchasing activities" means activities consisting in the provision of support to purchasing activities, in particular in the following forms: (a) technical infrastructure enabling contracting authorities to award public contracts or to conclude framework agreements for works, supplies or services; (b) advice on the conduct or design of public procurement procedures; (c) preparation and management of procurement procedures on behalf and for the account of the contracting authority concerned; Source: Directive 2014/24/EU, Article 2, paragraphs 17 and 15. This would be equivalent to the concept of 'procuringEntity' in OCDS: 'The entity managing the procurement, which may be different from the buyer who is paying / using the items being procured'. WG Approval 24/03/2020
epo:PublicationProvision	Information about fields not intended for publication. Additional Information: The non-published information may become available at a later date and may differ from one element to another within a given document. Examples of fields that may not be immediately published are Winner, Tender and Procedure Lot Result, etc., e.g. for security reasons. WG Approval 16/05/2019
epo:PurchaseContract	A contract resulting from a Dynamic Purchasing System or Framework Agreement Contract. Additional Information: If BT-768 (Contract Framework Agreement) indicator is true, then epo:PurchaseContract class is instantiated. If its false, then epo:Contract class is instantiated.
epo:Purpose	The description of the objectives related to a procurement. Additional information: The description of the objectives includes the subject matter and quantities. The quantification of the objectives related to a procurement. To be re-reviewed by the WG the soonest. (WG to be discussed, this was pointed out on the 09/04/2019 14:38:25 WG Meeting) The old definition read as follows: The description of the objectives related to a procurement. (WG approval 05/12/2018)
epo:Quantity	A counted number of non-monetary units possibly including fractions.
epo:RequestForClarification	A demand for elucidation of received information. Additional Information: Requests for clarification are usually used by buyers during the process of award or evaluation to understand specific aspects of the tender without altering the tender. WG approval 20/04/2021
epo:RequestForParticipation	Application of an economic operator to be included in a procurement procedure. WG approval: 20/04/2021
epo:ReviewDecision	Information about review decisions.
epo:Reviewer	Role of an agent who investigates the overall correctness of a procurement procedure, producing a related report. Additional Information: Any organisation or person may request a review of a procurement procedure. WG approval: 20/04/2021
epo:ReviewIrregularitySummary	Information about the number and type of requests the buyer received to review any of its decisions (e.g. the technical specifications, award decision). Additional information: This class corresponds in eForms to BG-613 Buyer Review Requests.
epo:ReviewObject	Information about a review request or a review decision. Additional information: This class corresponds to the BG-714 Review in eForms.
epo:ReviewProcedureInformationProvider	A role of an agent who is providing more information on the time limits for review procedures.
epo:ReviewRequest	Information about requests to review procedures.
epo:ReviewRequester	Role of an agent who requests the review of a (procurement) procedure. WG Approval 23/10/2021
epo:ReviewRequestSummary	Summary information about the requests the buyer received to review any of its decisions (e.g. the technical specifications, award decision), as set out in Art. 1(5) of Directive 89/665/EEC and Directive 92/13/EEC, and about the complainants that submitted the requests. Additional information: This class corresponds in eForms to BG-612 Buyer Review Summary.
epo:ReviewTerm	Conditions and stipulations defining particularities of the review. (WG approval 23/11/2018)
epo:SecurityClearanceTerm	Status requested to individuals allowing them access to classified information (state or organisational secrets) or to restricted areas, after completion of a thorough background check. Additional information: This corresponds in eForms to BT-578, BT-78, BT-732 . WG Approval 2015-02-26
epo:SelectionCriterion	Describes a capacity requirement that the economic operator needs to fulfill to participate in the procedure. Additional Information: This corresponds in eForms to BG-702 Selection Criteria WG approval 31/10/2018
epo:SelectionEvaluationTerm	Conditions and stipulations defining particularities of the evaluation of selection criteria.
epo:SocialProcurement	An instance of the class SocialProcurement is represented in eForms with the code "soc-obj" defined in the codelist strategic-procurement. Research (21/01/2020): Socially responsible public procurement (SRPP): ‘SRPP’ means procurement operations that take into account one or more of the following social considerations: employment opportunities, decent work, compliance with social and labour rights, social inclusion (including persons with disabilities), equal opportunities, accessibility design for all, taking account of sustainability criteria, including ethical trade issues and wider voluntary compliance with corporate social responsibility (CSR), while observing the principles enshrined in the Treaty for the European Union (TFEU) and the Procurement Directives. Source: Buying Social - A Guide to Taking Account of Social Considerations in Public Procurement (Publications Office of the European Union, 2011) https://op.europa.eu/en/publication-detail/-/publication/cb70c481-0e29-4040-9be2-c408cddf081f/language-en See Article 18 and Annex X Directive 2014/24.
epo:SpecificDuration
epo:StatisticalInformation	Statistical data on the procedure and the lot. Additional Information At the present time Procurement Procedures are not fully electronic. At a later date, information on the tenders received could be inferred by the data in the eProcurement system. Therefore this class is temporal and should cease to exist in fully electronic procurement. The need for its presence responds also to the alignment with the Regulation (EU) 2019/1780 (eForms). Attention will have to be paid in the future to possible inconsistencies derived from data placed in other classes and data held in the Statistical Information class; e.g. the TenderEvaluation class (see eEvaluation diagram) has the attribute admissibileTender indicator, which in case of being false, may enter in contradiction with the highest or lowest tender value for that very same inadmissible tender. WG Approval 12/12/2019
epo:StrategicProcurement	Public procurement that contributes to achieving pressing policy goals. Additional Information: Specific strategic goals could be, for example, environmental protection, innovation, job creation and the development of small and medium enterprises. This corresponds in eForms to BG-713 Strategic Procurement. The subclasses are given by the choices in BT-06 Strategic Procurement. Based on https://legalinstruments.oecd.org/en/instruments/OECD-LEGAL-0411 (see paragraph on "background information". WG Approval 10/03/2020
epo:SubcontractingEstimate	Information on the approximation of the foreseen subcontracting.
epo:Subcontractor	A role of an agent that has an agreement to perform part or all of the obligations of another agents's contract. Additional information For some procedures, the subcontractor signs as well the contract between the buyer and the contractor. At tendering time, entities relied upon by the economic operators can be subcontractors or not. When modelling ESPD we well analyse whether we need or not a role named "relied upon". WG approval 05/08/2021
epo:SubcontractTerm	A concept to describe the main information regarding the share of parts of the contract to third parties.
epo:SubmissionStatisticalInformation	Statistical information about submissions on a given Lot.
epo:SubmissionTerm	Conditions and stipulations defining particularities of submitting documents to the buyer. Additional Information: These documents can be tenders, request to participate and expressions of interest. WG Approval 14/07/2020
epo:System	Software application used for performing procurement activities. WG Approval 28/04/2020
epo:TaxInformationProvider	A role of an agent responsible for providing information concerning the general regulatory framework for taxes.
epo:TechniqueUsage	Methods used for conducting procurement procedure. Addtional information: This corresponds in eForms to BG-706 Techniques. Several techniques can be combined in one single procurement procedure (e.g. eAuction can be carried out in a Framework Agreement or DPS). WG Approval 19/09/2019
epo:Tender	Information submitted by the economic operator to specify its offer regarding a specific lot, in response to the call for tender. (WG approval 03/05/2022)
epo:TenderAwardOutcome	Result concerning the Tender attributed by the awarder.
epo:Tenderer	A role of an agent that has submitted a tender. Additional Information: A tenderer is an economic operator or group of economic operators that has submitted a tender. WG approval 05/08/2021
epo:TenderGroup	Specific offer in response to a lot group. Additional Information: This class is generally used to provide the monetary value in response to a lot group.
epo:TenderProcessor	A role of an agent responsible for processing tenders.
epo:TenderReceiver	A role of an agent responsible for receiving tenders.
epo:Term	A governing condition or stipulation.
epo:Winner	A role of an agent to whom a lot is awarded. WG approval 05/08/2021 (revised 26/10/2021)
foaf:Agent	A person, an organization, or a system that acts in procurement or have the power to act in procurement. WG Approval 28/04/2020
foaf:Person	The Person class represents people. Something is a Person if it is a person. We don't nitpic about whether they're alive, dead, real, or imaginary. The Person class is a sub-class of the Agent class, since all people are considered 'agents' in FOAF.
locn:Address	The particulars of the place where a person or an organisation is located. WG Approval 28/04/2020 Additional Information: An "address representation" as conceptually defined by the INSPIRE Address Representation data type: "Representation of an address spatial object for use in external application schemas that need to include the basic, address information in a readable way.". The representation of Addresses varies widely from one country's postal system to another. Even within countries, there are almost always examples of Addresses that do not conform to the stated national standard. At the time of publication, work is progressing on ISO 19160-1 that defines a method through which different Addresses can be converted from one conceptual model to another. This specification was heavily based on the INSPIRE Address Representation data type. It is noteworthy that if an Address is provided using the detailed breakdown suggested by the properties for this class, then it will be INSPIRE-conformant. To this very granular set of properties, we add two further properties: - full address (the complete address as a formatted string) - addressID (a unique identifier for the address) The first of these allows publishers to simply provide the complete Address as one string, with or without formatting. This is analogous to vCard's label property. The addressID is part of the INSPIRE guidelines and provides a hook that can be used to link the Address to an alternative representation, such as vCard or OASIS xAL.
locn:Geometry	The Geometry class provides the means to identify a Location as a point, line, polygon, etc. expressed using coordinates in some coordinate reference system. Additional Information: This class defines the notion of "geometry" at the conceptual level, and it shall be encoded by using different formats (see usage note of the locn:geometry property). We also refer to the Examples section of this specification for a number of different geometry examples expressed in different formats.
org:Organization	A collection of people organized together into a community or other social, commercial or political structure. The group has some common purpose or reason for existence which goes beyond the set of people belonging to it and can act as an Agent. Organisations are often decomposable into hierarchical structures. (WG approval 23/11/2018).
owl:Thing	Any individual in the domain of discourse is a Thing. Additional Information: The most basic concepts in a domain should correspond to classes that are the roots of various taxonomic trees. Every individual in the OWL world is a member of the class owl:Thing.

Attributes (datatype properties) names and definitions

Class name	Attribute name	Definition	Data type / cardinality
cccev:Criterion	cccev:bias	Parameter used to adjust the evaluation of the Criterion. Additional Information: The bias parameter tries to correct a systematic error. For example in procurement, a home bias corresponds to the "presence of local preferences distorting international specialisation and resource allocation". When quantified, this systematic error can be removed.	xsd:decimal [0..1]
cccev:Requirement	cccev:description	A short explanation supporting the understanding of the Requirement. Additional Information: The explanation can include information about the nature, attributes, uses or any other additional information about the Requirement.	rdfs:Literal [0..1]
cccev:Requirement	cccev:identifier	Unambiguous reference to a Requirement.	rdfs:Literal [0..1]
cccev:Requirement	cccev:name	Name of the Requirement.	rdfs:Literal [0..1]
cccev:Criterion	cccev:weight	Relative importance of the Criterion. Additional Information: The weight must be between 0 and 1. Usually, all Criteria can be integrated within a weighted sum equal to 1.	xsd:decimal [0..1]
cccev:Criterion	cccev:weightingConsiderationDescription	Explanation of how the weighting of a Criterion is to be used. Additional Information: This description gives the view of the creator of the Criterion weights on how to interpret and use them during the evaluation process.	rdfs:Literal [0..1]
cpov:ContactPoint	cpov:email	An electronic address through which the Contact Point can be contacted.	rdfs:Literal [0..1]
cpov:ContactPoint	cpov:telephone	A telephone number through which the Contact Point can be contacted.	rdfs:Literal [0..*]
cpv:Person	cv:birthDate	The point in time on which the Person was born.	xsd:date [0..1]
locn:Geometry	cv:coordinates	The coordinate list.	rdfs:Literal [0..*]
cpv:Person	cv:deathDate	The point in time on which the Person died.	xsd:date [0..1]
locn:Geometry	cv:latitude	The latitude.	rdfs:Literal [0..*]
locn:Geometry	cv:longitude	The longitude.	rdfs:Literal [0..*]
cpv:Person	dct:alternative	Any name by which an individual is known other than their full name. WG 09/11/2021	rdfs:Literal [0..*]
epo:SubmissionStatisticalInformation	epo:hasAbnormallyLowTenders	Tenders received that were found irregular and non-acceptable due to an abnormally low price or cost. Additional Information The definition implies that abnormally Low Tender Lots are Inadmissible Tender Lots. WG Approval 28/07/2020	xsd:integer [0..1]
epo:Procedure	epo:hasAcceleratedProcedureJustification	The reasons why the procedure is accelerated. Additional Information: A procedure is accelerated to cover needs of extraordinary circumstances ie earthquake relief. WG Approval 09/06/2020	rdfs:Literal [0..*]
epo:ElementConfidentialityDescription	epo:hasAccessibilityDate	The date at which unpublished data shall be published. WG Approval 11/06/2020	xsd:date [0..1]
epo:Contract epo:Document	epo:hasAccessURL	Location where the resource can be accessed. WG approval 07/04/2022 Location where the resource can be accessed. WG approval 07/04/2022	xsd:anyURI [0..1] xsd:anyURI [0..*]
epo:Buyer	epo:hasActivityDescription	In the ePO ontology a taxonomy with all activities, based on different classifications (COFOG, UTILITIES, NACE), will be provided. In ePO this field is to be used exclusively to complement the definition attached to the MainActivityCode. However, in eForms there is the code "other" to cover undefined activities. For mapping to this eForms feature one could also use this property.	rdfs:Literal [0..*]
cv:Channel epo:ProcurementObject	epo:hasAdditionalInformation	Supplementary data about the instance of the concept. Additional Information For example, information about the Lot not specified elsewhere in the Notice. WG Approval 15/10/2019 Supplementary data about the instance of the concept. Additional Information For example, information about the Lot not specified elsewhere in the Notice. WG Approval 15/10/2019	rdfs:Literal [0..*] rdfs:Literal [0..*]
epo:AccessTerm	epo:hasAdditionalInformationDeadline	The time limit for requesting further information. Additional information: This is generally used to indicate the deadline for Economic Operators to request further information of the procedure before the submission deadline. This corresponds in eForms to BT-13 Additional Information Deadline. WG Approval 09/06/2020	xsd:dateTime [0..1]
epo:LotAwardOutcome	epo:hasAdditionalNonAwardJustification	Further justification for the non award . Additional information: This is generally used when the non award reason code is set to "Other". WG: 18/01/2022	rdfs:Literal [0..1]
foaf:Agent	epo:hasAlias	Acronym or alternative name of the Agent. WG Approval 25/03/2021	rdfs:Literal [0..*]
epo:MonetaryValue	epo:hasAmountValue	The numeric value of the amount, including decimals.	xsd:decimal [1..1]
epo:AwardEvaluationTerm	epo:hasAwardCriteriaEvaluationFormula	The mathematical equation or any other description used for complicated weighing of criteria (e.g. non-linear weighing, the analytic hierarchy process) when a weighing cannot be expressed per criterion. Additional Information: This corresponds in eForms to BT-543 Award Criteria Complicated.	rdfs:Literal [0..*]
epo:AwardEvaluationTerm	epo:hasAwardCriteriaOrderJustification	The justification for only indicating the award criteria's order of importance, not their weighing. Additional Information: This corresponds in eForms to BT-733 Award Criteria Order Justification.	rdfs:Literal [0..1]
epo:ProcessPlanningTerm	epo:hasAwardDateScheduled	Planned date for the award decision. WG Approval 09/11/2021	xsd:date [0..1]
epo:LotAwardOutcome	epo:hasAwardDecisionDate	The official date of the award decision. Additional Information: This corresponds in eForms to BT-1451 Winner Decision Date. WG Approval 09/01/2020	xsd:date [0..1]
epo:TenderAwardOutcome	epo:hasAwardRank	The position of the tender (i.e. whether the tender ended up first, second, third, etc.) in a design contest, some framework agreements with multiple winners (e.g. cascades) or an innovation partnership. Additional Information: This corresponds in eForms to BT-171 Tender Rank.	xsd:integer [0..1]
epo:Period	epo:hasBeginning	The date and time on which this period begins.	xsd:dateTime [0..1]
epo:FrameworkAgreementTerm	epo:hasBuyerCategoryDescription	A classification of buyers participating in a framework agreement. Additional Information: Buyers that can use the Framework Agreement not mentioned by name. For example, the classification "all hospitals in the Tuscany region" is used instead of naming each individual buyer. This corresponds in eForms to BT-111 Framework Buyer Categories. WG Approval 2019-05-06	rdfs:Literal [0..*]
org:Organization	epo:hasBuyerLegalTypeDescription	Self-explanatory text about the Buyer Legal Type. Additional information: This field is used when the Buyer Legal Type is not available in the controlled list at-voc:buyer-legal-type . This is necessary in to cover data provided in the TED Standard Forms. It shall be deprecated in the future. WG Approval 06/09/2022	rdfs:Literal [0..1]
epo:Buyer	epo:hasBuyerProfile	Website address where the buyer publishes information on its procurement procedures and general information. Additional information: This corresponds in the eForms to BT-508 Buyer Profile URL. WG approval 04/05/2018	xsd:anyURI [0..1]
epo:ConcessionEstimate	epo:hasCalculationMethod	Formula for obtaining values. Additional Information: The possible values are monetary values, ranking scores, criterion weighting. WG Approval 25/05/2018	rdfs:Literal [0..1]
epo:ElementChangeDescription	epo:hasChangeDescription	Explanatory text about the instance of the concept. WG Approval 30/09/2019	rdfs:Literal [0..*]
epo:ElementChangeDescription	epo:hasChangeReasonDescription	Explanatory text about why the element is altered. Additional information: This corresponds in eForms to BT-762 Change Reason Description.	rdfs:Literal [0..*]
epo:GreenProcurement	epo:hasCleanVehicles	The number of all clean vehicles that have either been purchased, leased, rented, hired-purchased or their use has been contractually committed to for the provision of a purchased service. Additional Information In the European Union, the legal requirements and scope for the provision of these vehicles or services are covered by Directive 2009/33/EC. WG Approval 28/07/2020	xsd:integer [0..1]
epo:ElementConfidentialityDescription	epo:hasConfidentialityJustification	A narrative explanation of why data is not published. Additional Information: This element is generally used when the non-publication-justification code chosen is "other". WG Approval 09/11/2021	rdfs:Literal [0..1]
cpov:ContactPoint	epo:hasContactName	A short text by which a contact is known or referred to. WG Approval: 27/01/2022	rdfs:Literal [0..1]
epo:Contract	epo:hasContractConclusionDate	The date the contract was signed by the last signatory party. <u>Additional Information:</u> In exceptional cases contracts may be concluded without signature and therefore another date may be used. The date of contract conclusion is always later than the end of any standstill period. This concept is not to be confused with the date of completion/end of the contract. This corresponds in eForms to BT-145 Contract Conclusion Date. WG Approval 09/01/2020	xsd:date [0..1]
epo:ContractTerm	epo:hasContractorLegalFormRequirement	A specific legal entity must be taken up by a tenderer composed of a group of economic operators once it has been awarded a contract. Additional information: this may be applied in the case of groups (e.g. a consortium) where the requirement is that they have to formalise the relationship of the group members as a legal entity itself once the contract is awarded. WG Approval 2019-01-29	xsd:boolean [0..1]
epo:ContractTerm	epo:hasContractorLegalFormRequirementDescription	A constraint concerning the legal form that must be adopted by a tenderer composed of a group of economic operators once it has been awarded a contract.	rdfs:Literal [0..*]
epo:ProcedureTerm	epo:hasCrossBorderLaw	The applicable law when buyers from different countries procure together within one procurement procedure. Additional Information: This corresponds in eForms to BT-09 Cross Border Law.	rdfs:Literal [0..*]
epo:MonetaryValue	epo:hasCurrencyCodeListAgencyID	Identifier of the agency that maintains the currency code list used. WG approval 13/04/2021	rdfs:Literal [0..*]
epo:MonetaryValue	epo:hasCurrencyCodeListAgencyName	Name of the agency that maintains the currency code list used. WG approval 13/04/2021	rdfs:Literal [0..*]
epo:MonetaryValue	epo:hasCurrencyCodeListID	Concept scheme URI used for the currency code list. WG approval 13/04/2021	rdfs:Literal [0..*]
epo:SecurityClearanceTerm	epo:hasDeadline	The deadline by which the security clearance must be submitted to the buyer. WG Approval 12/09/2019	xsd:dateTime [0..1]
epo:ReviewDecision	epo:hasDecisionDate	The date of the review decision. Additional information: This attribute corresponds to the BT-787 Review Date in eForms.	xsd:date [0..1]
cccev:InformationConcept cpov:ContactPoint cv:Channel epo:AgentInRole epo:Fund epo:SecurityClearanceTerm epo:SubcontractingEstimate epo:SubcontractTerm epo:System epo:TechniqueUsage epo:ProcurementElement epo:Period	epo:hasDescription	Explanatory text about the instance of the concept. WG Approval 30/09/2019 Explanatory text about the instance of the concept. WG Approval 30/09/2019 Explanatory text about the instance of the concept. WG Approval 30/09/2019 Explanatory text about the instance of the concept. WG Approval 30/09/2019 Explanatory text about the instance of the concept. WG Approval 30/09/2019 Explanatory text about the instance of the concept. WG Approval 30/09/2019 Explanatory text about the instance of the concept. WG Approval 30/09/2019 Explanatory text about the instance of the concept. WG Approval 30/09/2019 Explanatory text about the instance of the concept. WG Approval 30/09/2019 Explanatory text about the instance of the concept. WG Approval 30/09/2019 Explanatory text about the instance of the concept. WG Approval 30/09/2019 Explanatory text about the instance of the concept. WG Approval 30/09/2019	rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..1]
epo:Document	epo:hasDispatchDate	Date of transmission of a record to an organisation. WG Approval 12/05/2020	xsd:date [0..1]
epo:FrameworkAgreementTerm	epo:hasDurationExtensionJustification	The explanation of the reason why the framework agreement has an extended duration. Additional Information: This corresponds in eForms to BT-109 Framework Duration Justification. The justification for exceptional cases when the duration of the framework agreement exceeds the legal limits. Four years in the case of the general procurement Directive, seven years in the case of the defence Directive, and eight years in the case of the sectoral Directive. WG Approval 26/09/2019	rdfs:Literal [0..1]
epo:SubmissionTerm	epo:hasEAuctionURL	The internet address of the electronic auction. Additional Information: This corresponds in eForms to BT-123 Electronic Auction URL.	xsd:anyURI [0..1]
epo:SubmissionStatisticalInformation	epo:hasEEAReceivedTenders	The amount of tenders received from economic operators in other EEA countries other than the country of the buyer. WG Approval 12/12/2019	xsd:integer [0..1]
epo:ContractTerm	epo:hasEInvoicing	Electronic means will be used for invoicing in the post-award process. WG Approval 12/09/2019	xsd:boolean [0..1]
epo:Tender	epo:hasElectronicSubmission	Transmission of tenders is possible by electronic means of communication.	xsd:boolean [0..1]
epo:SubmissionStatisticalInformation	epo:hasElectronicTenders	Electronic Tender Lots received. WG Approval 28/07/2020	xsd:integer [0..1]
epo:ElementChangeDescription epo:ElementModificationDescription epo:ReviewObject	epo:hasElementReference	Reference to the class instance in the current notice. Additional information: This corresponds in eForms to BT-13716 Change Previous Notice Section Identifier, BT-786 Review Notice Section Identifier and BT-1501 Modification Previous Notice Section Identifier. Reference to the class instance in the current notice. Additional information: This corresponds in eForms to BT-13716 Change Previous Notice Section Identifier, BT-786 Review Notice Section Identifier and BT-1501 Modification Previous Notice Section Identifier. Reference to the class instance in the current notice. Additional information: This corresponds in eForms to BT-13716 Change Previous Notice Section Identifier, BT-786 Review Notice Section Identifier and BT-1501 Modification Previous Notice Section Identifier.	xsd:anyURI [1..1] xsd:anyURI [0..1] xsd:anyURI [0..*]
epo:Period	epo:hasEnd	The date and time at which this period ends.	xsd:dateTime [0..1]
cv:Channel	epo:hasEndpoint	The value identifying a communication network node, required to gain access to a service. Additional information Examples: https://data.gov.es/sdg?serviceId=diploma-request mailto:myname@mycompany.com +33 6090 92 81 80 Ext. 3213 This corresponds in eForms to BT-509 Organisation eDelivery Gateway. WG Approval 07/05/2020	xsd:anyURI [0..1]
epo:Contract	epo:hasEntryIntoForceDate	The date on which the contract enters into force. Additional information: This is generally the date on which the fulfilment of the contract begins. This corresponds in eForms to WG approval 05/11/2019	xsd:date [0..1]
epo:ContractTerm	epo:hasEOrdering	Electronic means will be used for requesting and purchasing in the post-award process. WG Approval 12/09/2019	xsd:boolean [0..1]
epo:ContractTerm	epo:hasEPayment	Electronic means must be used for paying. WG Approval 09/11/2021	xsd:boolean [0..1]
epo:ProcessPlanningTerm	epo:hasEstimatedContractNoticePublicationDate	Foreseen date for publication of Contract Notice. Additional information: This corresponds in eForms BT-127 Future Notice.	xsd:date [0..1]
epo:MultipleStageProcedureTerm	epo:hasEstimatedInvitationToExpressInterestDate	The estimated date of dispatch of the invitations to confirm interest. Additional Information: This corresponds in eForms to BT-631 Dispatch Invitation Interest.	xsd:date [0..1]
epo:MultipleStageProcedureTerm	epo:hasEstimatedInvitationToTenderDate	The estimated date of dispatch of the invitations to submit tenders in two (or more) stage procedures. Additional Information: This corresponds in eForms to BT-130 Dispatch Invitation Tender. WG Approval 01/10/2019	xsd:date [0..1]
epo:SubcontractingEstimate	epo:hasEstimatedPercentage	The estimated proportion foreseen to be subcontracted. WG Approval 07/01/2020	xsd:decimal [0..1]
epo:ProcessPlanningTerm	epo:hasEstimatedTenderInvitationDate	The planned date for the dispatch of the invitations to submit tenders. WG Approval 09/11/2021	xsd:date [0..1]
epo:SubmissionStatisticalInformation	epo:hasEstimatedTotalSubcontracts	The estimated amount of work to be subcontracted in the contract resulting from the lot. WG Approval 09/11/2021	xsd:integer [0..1]
epo:SubmissionStatisticalInformation	epo:hasEUReceivedTenders	The amount of tenders received from economic operators in other EU countries other than the country of the buyer.	xsd:integer [1..1]
cpov:ContactPoint	epo:hasFax	The fax number used to reach a person or an organisation.	rdfs:Literal [0..*]
epo:AwardCriterion	epo:hasFixedValue	This corresponds in the eForms to BT-541 Award Criterion Number in association with BT-5422 Award Criterion Number Fixed.	xsd:decimal [0..1]
epo:DesignContestRegimeTerm	epo:hasFollowupContract	Any subsequent service contract will be awarded to the winner or, in the case of a design contest, winners. WG Approval 29/08/2019	xsd:boolean [0..1]
epo:DesignContestRegimeTerm	epo:hasFollowupContractInformation	Further information about follow-up contracts, prizes and payments (for example non-monetary prizes, payments given for participation). WG Approval 03/09/2019	rdfs:Literal [0..*]
epo:ProcurementCriterion	epo:hasFormula	The mathematical equation or any other description used for complicated weighing of criteria (e.g. non-linear weighing, the analytic hierarchy process) when a weighing cannot be expressed per criterion. Additional Information: This corresponds in eForms to BT-543.	rdfs:Literal [0..1]
epo:ProcedureTerm	epo:hasGroupLotEvaluationMethod	Description of how lots and groups of lots are evaluated against one another in the procedure.	rdfs:Literal [0..*]
epo:OrganisationGroup	epo:hasGroupType	Form of collabaration agreement between organisations. WG Approval 09/11/2021	rdfs:Literal [0..*]
epo:SubmissionTerm	epo:hasGuaranteeDescription	Information on the financial commitment required from the economic operator. Additional Information: 1. This information may include the amount and the way of delivering of the guarantee 2. The financial commitment may be retained by the buyer in the case the tenderer withdraws the submitted information (i.e. tender, expression of interest and request for participation, but not request for clarifications) before the award of the contract or does not sign the contract. 3. Usual modalities are bonds, cheques, loans, other. WG Approval 21/07/20	rdfs:Literal [0..*]
epo:Identifier	epo:hasIdentifierValue	The literal identifying an entity, like a person or an object.	rdfs:Literal [1..1]
epo:SubmissionStatisticalInformation	epo:hasInadmissibleTenders	Tenders received that cannot be awarded due to non-compliance to procurement document requirements or having an abnormally low price or cost. <u>Additional Information: </u> Non-compliance with a Procurement Document requirements include exclusion grounds, selection criteria and submission deadline, etc. WG Approval 12/12/2019	xsd:integer [0..1]
epo:ElementConfidentialityDescription	epo:hasInstanceReference	The URI of a given class that is being referred to.	xsd:anyURI [1..1]
cpov:ContactPoint	epo:hasInternetAddress	The website of the organisation.	xsd:anyURI [0..1]
epo:DesignContestRegimeTerm	epo:hasJuryDecisionBinding	Indicates whether the procuring entity is bound to apply the decision of the jury.	xsd:boolean [0..1]
epo:DirectAwardTerm	epo:hasJustification	An explanation about the reasons for using the concept. WG Approval 5/11/2019	rdfs:Literal [0..*]
epo:SubmissionTerm	epo:hasLateSubmissionInformationDescription	A narrative text explaining the content of the economic operator information that can be submitted late. Additional Information This does not apply to requests for clarifications.	rdfs:Literal [0..*]
org:Organization	epo:hasLegalFormType	Note that the codelist provided at national level should be used.	rdfs:Literal [0..1]
org:Organization	epo:hasLegalName	The officially registered name of an organisation. WG Approval 16/11/2021	rdfs:Literal [0..1]
epo:ProcedureTerm	epo:hasLotAwardCombination	The contracting authority reserves the right to award contracts combining lots or groups of lots. Additional Information: This property contains information about the Lots concerned. This property is required by the regulation (EU)-2015-1986 (modeled in the TED Standard Forms). WG approval 23/08/2022	rdfs:Literal [0..1]
epo:ProcedureTerm	epo:hasLotAwardLimit	The total number of lots for which contract(s) can be awarded to one tenderer. (WG Approval 12/12/2018)	xsd:integer [0..1]
org:Organization	epo:hasMainActivityDescription	Self-explanatory text about the Main Activity . Additional information: This field is used when the Main Activity is not available in the controlled list at-voc:main-activity-type . This is necessary in to cover data provided in the TED Standard Forms. It shall be deprecated in the future. WG Approval 06/09/2022	rdfs:Literal [0..1]
epo:Procedure	epo:hasMainFeature	Main features of the procedure and information about where the full rules for the procedure can be found. Additional Information: This information should be given when the procedure is not one of those mentioned in the procurement directives. This can be the case for example for concessions, for social and other specific services, and in case of voluntary publication of procurement procedures below the EU procurement thresholds.	rdfs:Literal [0..*]
epo:ProcedureTerm	epo:hasMaximumLotSubmissionAllowed	The total number of lots for which one Tenderer can submit Tenders. Additional information: This field is used to complement the SubmissionTerms (which are at the Lot level) for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled in the TED Standard Forms). WG approval 12/12/2018	xsd:integer [0..1]
epo:MultipleStageProcedureTerm	epo:hasMaximumNumberOfCandidates	Maximum number of candidates to be invited for the second stage of the procedure. WG Approval 22/08/2019	xsd:integer [0..1]
epo:ProcedureTerm	epo:hasMaximumNumberOfLotsToBeAwarded	The maximum number of lots for which contract(s) can be awarded to one tenderer. Additional information: This field is used to complement the SubmissionTerms (which are at the Lot level) for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled in the TED Standard Forms). WG Approval 22/08/2019	xsd:integer [0..1]
epo:ContractTerm	epo:hasMaximumNumberOfRenewals	The maximum number of times the contract can be renewed. Additional Information By renewing, the buyer reserves the right (i.e. not an obligation) to renew the contract (i.e. extend its duration) without a new procurement procedure. For example, a contract may be valid for one year and the buyer may keep a possibility to renew it (e.g. once, twice) for another three months, if he is content with the services he received. PLEASE REVIEW THIS DEFINITION AGAIN WITH THE WORKING GROUP. It was originally taken from eForms.	xsd:integer [0..1]
epo:FrameworkAgreementTerm	epo:hasMaximumParticipantsNumber	The maximum number of participants in the framework agreement. Additional Information: Maximum number of tenderers who may be awarded a contract within the framework agreement. The number is a positive integer. This corresponds in eForms to BT-113 Framework Maximum Participants Number. WG Approval 2019-02-05	xsd:integer [0..1]
epo:SubcontractTerm	epo:hasMaximumShare	The maximum proportion of something to be distributed. Additional Information: In the case of subcontracting the share may refer to the proportion of works, services or supplies being subcontracted. WG Approval 17/09/2019	xsd:decimal [0..1]
epo:SubmissionStatisticalInformation	epo:hasMediumTenderPerLots	Tenders from medium-sized enterprise. <u>Additional Information:</u> See Commission Recommendation 2003/361/EC.	xsd:integer [0..1]
epo:MultipleStageProcedureTerm	epo:hasMinimumNumberOfCandidates	Minimum number of candidates to be invited for the second stage of the procedure. WG Approval 22/08/2019	xsd:integer [0..1]
epo:SubcontractTerm	epo:hasMinimumShare	The minimum proportion of something to be distributed. Additional Information: In the case of subcontracting the share may refer to the proportion of works, services or supplies being subcontracted. WG Approval 17/09/2019	xsd:decimal [0..1]
epo:SubcontractTerm	epo:hasMinimumSubcontractorsProposedObligation	The minimum percentage of the contract value that the contractor must subcontract. Additional information: This is used for the competitive procedure described in Title III of Directive 2009/81/EC. WG Approval 09/11/2021	xsd:decimal [0..1]
epo:ElementModificationDescription	epo:hasModificationDescription	An explanatory text about this context. Additional Information This corresponds in Standard forms to Field VII.2.1 in F20 This corresponds in eForms to BT-202 . WG Approval 5/11/2019	rdfs:Literal [0..*]
epo:ElementModificationDescription	epo:hasModificationReasonDescription	An explanation about the reasons for using the concept. Additional Information This corresponds in Standard forms to Field VII.2.2.2 and VII.2.2.4 in F20. This corresponds in eForms to BT-201 . WG Approval 5/11/2019	rdfs:Literal [0..*]
cccev:InformationConcept cv:Channel epo:Fund foaf:Agent	epo:hasName	A short text by which a thing is known or referred to. WG Approval 16/11/2021 A short text by which a thing is known or referred to. WG Approval 16/11/2021 A short text by which a thing is known or referred to. WG Approval 16/11/2021 A short text by which a thing is known or referred to. WG Approval 16/11/2021	rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..*] rdfs:Literal [0..*]
epo:ProcedureTerm	epo:hasNationalProcedureRules		xsd:anyURI [0..*]
epo:StrategicProcurement	epo:hasNonAccessibilityCriterionJustification	Reason for not applying accessibility criteria. Additional information: This corresponds in eForma to BT-755 Accessibility Justification. WG Approval 05/03/2019	rdfs:Literal [0..*]
epo:LotAwardOutcome	epo:hasNonAwardedContractNumber	The number the contract would have had if it had been awarded. Additional information: This field is provided to support the data provided in the TED Standard Forms, and it should be discontinued in the future. WG agreement: 06/09/2022	rdfs:Literal [0..1]
epo:LotAwardOutcome	epo:hasNonAwardedContractTitle	The title the contract would have had if it had been awarded. Additional information: This field is provided to support the data provided in the TED Standard Forms, and it should be discontinued in the future. WG agreement: 06/09/2022	rdfs:Literal [0..1]
epo:MultipleStageProcedureTerm	epo:hasNoNegotiationNecessary	The buyer reserves the right to award the contract on the basis of the initial tenders without any further negotiations. Additional information: See Article 29(4) of Directive 2014/24/EU.	xsd:boolean [0..1]
epo:SubmissionTerm	epo:hasNonElectronicSubmissionDescription	Textual explanation of how non-electronic information is to be presented. WG Approval 21/07/2020	rdfs:Literal [0..*]
epo:ReviewRequest	epo:hasNumberOfReviewRequests	The number of requests the buyer received to review any of its decisions.	xsd:integer [1..1]
epo:SubmissionStatisticalInformation	epo:hasNumberOfTenderersInvited	Number of economic operators invited to tender. Additional Information This may be used for single-stage procedures or to indicate the number of candidates invited to tender in multi-stage procedures. WG Approval 01/12/2020	xsd:integer [0..1]
epo:OpeningTerm	epo:hasOpeningDateTime	Date and time for the opening of tenders. WG Approval 12/03/2019	xsd:dateTime [1..1]
epo:OpeningTerm	epo:hasOpeningDescription	Further information about the opening of tenders. Additional Information For example, who may participate in the opening and whether any authorization is needed. WG Approval 12/03/2019	rdfs:Literal [0..*]
epo:OpeningTerm	epo:hasOpeningURL	The identifier of the address of the Opening of Tenders. WG Approval 09/11/2021	xsd:anyURI [0..1]
epo:ContractTerm	epo:hasOptions	The buyer reserves the right (not an obligation) for additional purchases from the contractor (while the contract is valid).	xsd:boolean [0..1]
epo:ContractTerm	epo:hasOptionsDescription	The motivation and details about additional purchases that the buyer may undertake while the contract is valid. WG Approval 09/04/2019	rdfs:Literal [0..*]
org:Organization	epo:hasOrganisationUnit	The name of a subpart of an organisation. Additional Information: E.g. the relevant department of a large organisation.	rdfs:Literal [0..1]
epo:AwardEvaluationTerm	epo:hasOverallCostAwardCriteriaPonderation	The weighting given to cost. Additional Information: This weighting covers usually all cost criteria against price or quality criteria.	xsd:decimal [0..1]
epo:AwardEvaluationTerm	epo:hasOverallPriceAwardCriteriaPonderation	The weighting given to price. Additional Information: This weighting covers usually all price criteria against cost or quality criteria.	xsd:decimal [0..1]
epo:AwardEvaluationTerm	epo:hasOverallQualityAwardCriteriaPonderation	The weighting given to quality. Additional Information: This weighting covers usually all quality criteria against price or cost criteria.	xsd:decimal [0..1]
epo:DesignContestRegimeTerm	epo:hasParticipationPayment	Details on payments to participants WG Approval 09/11/2021	rdfs:Literal [0..1]
epo:ContractTerm	epo:hasPaymentArrangement	Information about financial clauses that will govern some economic aspects of the execution of the contract. Additional Information: These clauses usually refer to financial and payment provisions. This type of information should be structured instead of a free text in order to reuse it an ideal world. Unfortunately this is an information that in the real life no one is willing to provide pro-actively. WG Pending of discussion with eForms	rdfs:Literal [0..*]
epo:ContractTerm	epo:hasPerformanceConditions	The particular conditions and additional information related to the execution of the contract. Additional Information: For example, specific information about the place of performance, intermediary deliverables, compensation for damages, intellectual property rights. WG approval 15-01-2019	rdfs:Literal [0..*]
epo:ContractTerm	epo:hasPlaceOfPerformanceAdditionalInformation	Further details on the location of the execution of the contract. WG Approval 30/07/2019	rdfs:Literal [0..*]
epo:PublicationProvision	epo:hasPreferredPublicationDate	The date the buyer would like to have the record made publicly available. Additional Information: This corresponds in eForms to BT-738 Notice Publication Date Preferred. WG Approval 12/05/2020	xsd:date [0..1]
epo:ElementChangeDescription	epo:hasPreviousVersionOfElementReference	Reference to the class instance in the previous version of the notice, which was changed. Additional information: This corresponds in eForms to BT-13716 Change Previous Notice Section Identifier.	xsd:anyURI [0..1]
epo:Prize	epo:hasPrizeRank	The position of the prize (e.g. first place, second place) in a design contest list of prizes. WG Approval 29/08/2019	xsd:integer [0..1]
epo:ElementChangeDescription	epo:hasProcurementDocumentChangeDate	The date and time of the change. Additional information: This corresponds in eForms to BT-719 Change Procurement Documents Date WG Approval 5/11/2019	xsd:date [0..1]
epo:ElementConfidentialityDescription	epo:hasPropertyReference	The URI of a given attribute (property) that is being referred to.	xsd:anyURI [1..1]
epo:AccessTerm	epo:hasPublicAccessURL	Web page where the procurement documents can be downloaded. Additional Information: This corresponds in the eForms to BT-15 Documents URL. WG Approval 09/03/2021	xsd:anyURI [0..1]
epo:Document	epo:hasPublicationDate	Date of formal issuance of the document. Note: this attribute is equivalent to dct:issued. WG approval 18/11/2021	xsd:date [0..1]
epo:MultipleStageProcedureTerm	epo:hasQualificationSystemRenewalDescription		rdfs:Literal [0..1]
epo:Quantity	epo:hasQuantityValue	The numeric value of the quantity, including decimals.	xsd:decimal [1..1]
epo:SubmissionTerm	epo:hasReceiptDeadline	The time limit for receiving submissions. Additional Information This is the deadline by which the buyer must receive submissions (e.g. tenders, requests to participate, clarifications, etc.) and is not the time at which the information is submitted by the economic operator. WG Approval 21/07/2020	xsd:dateTime [1..1]
epo:SubmissionTerm	epo:hasReceiptExpressionDeadline	Time limit for receipt of expressions of interest. Pending of review by the WG	xsd:dateTime [0..1]
epo:SubmissionStatisticalInformation	epo:hasReceivedMicroTenders	The amount of tenders received from a micro enterprise. <u>Additional Information:</u> See Commission Recommendation 2003/361/EC.	xsd:integer [0..1]
epo:SubmissionStatisticalInformation	epo:hasReceivedNonEEATenders	The amount of tenders received from economic operators in non-EEA countries. WG Approval 12/12/2019 15:20:36	xsd:integer [0..1]
epo:SubmissionStatisticalInformation	epo:hasReceivedNonEUTenders	The amount of tenders received from economic operators in non-EU countries.	xsd:integer [1..1]
epo:SubmissionStatisticalInformation	epo:hasReceivedParticipationRequests	The amount of applications to participate from economic operators. WG Approval 12/12/2019	xsd:integer [0..1]
epo:SubmissionStatisticalInformation	epo:hasReceivedSmallTenders	Tenders from small enterprise. <u>Additional Information:</u> See Commission Recommendation 2003/361/EC.	xsd:integer [0..1]
epo:SubmissionStatisticalInformation	epo:hasReceivedSMETenders	The amount of tenders received from micro, small and medium-sized enterprises. <u>Additional Information:</u> See Commission Recommendation 2003/361/EC. The ReceivedSMETenderLots is used when the size of the company is not exactly knokn. WG Approval 05/03/2020	xsd:integer [0..1]
epo:SubmissionStatisticalInformation	epo:hasReceivedTenders	The total amount of tenders received. WG Approval 12/12/2019	xsd:integer [0..1]
epo:Document	epo:hasReceptionDate	Notes: Date when a record is acknowledged by an organisation. WG Approval 12/05/2020	xsd:date [0..1]
epo:ProcurementObject	epo:hasRecurrenceDescription	Any additional information about the recurrence of the Procurement. Additional Information: For example estimated timing of the Procedure. This corresponds in eForms to BT-95 Recurrence Description. (WG approval 2019-01-16)	rdfs:Literal [0..1]
epo:ContractTerm	epo:hasRenewalDescription	Any other information about the renewal(s). WG approval 16/04/2019	rdfs:Literal [0..*]
epo:ReviewRequest	epo:hasRequestDate	The date when the review request was submitted. Additional information: This attribute corresponds to the BT-787 Review Date in eForms.	xsd:date [0..1]
epo:AccessTerm	epo:hasRestrictedAccessURL	The internet address with information on accessing the restricted (part of the) procurement document. Additional Information: This corresponds in eForms to BT-615 Documents Restricted URL.	xsd:anyURI [0..1]
epo:ReviewTerm	epo:hasReviewDeadline	The time limit for review procedures. WG Approval 09/11/2021	xsd:dateTime [0..1]
epo:ReviewTerm	epo:hasReviewDeadlineInformation	The description of the time limits for review procedures. WG Approval 01/10/2019	rdfs:Literal [0..*]
epo:ReviewIrregularitySummary	epo:hasReviewIrregularityCount	The number of requests for a given irregularity. Additional information: This attribute corresponds in eForms to BT-635 Buyer Review Requests Count.	xsd:integer [1..1]
epo:ReviewTerm	epo:hasReviewProcedure	The description of the method used to request the verification that the procedure has been carried out correctly. WG Approval 09/11/2021	rdfs:Literal [0..*]
epo:ReviewObject	epo:hasReviewURL	The internet address of the documents concerning the review instance. Additional information: This attribute corresponds in eForms to BT-794 Review URL.	xsd:anyURI [0..1]
epo:Identifier	epo:hasSchemeAgencyId	The identification of the agency that maintains the identification scheme.	rdfs:Literal [0..*]
epo:Identifier	epo:hasSchemeAgencyName	The name of the agency that maintains the identification scheme.	rdfs:Literal [0..*]
epo:Identifier	epo:hasSchemeDataURI	The Uniform Resource Identifier that identifies where the identification scheme data is located.	xsd:anyURI [0..1]
epo:Identifier	epo:hasSchemeID	The identification of the identification scheme.	rdfs:Literal [0..*]
epo:Identifier	epo:hasSchemeName	The name of the identification scheme.	rdfs:Literal [0..*]
epo:Identifier	epo:hasSchemeURI	The Uniform Resource Identifier that identifies where the identification scheme is located.	xsd:anyURI [0..1]
epo:Identifier	epo:hasSchemeVersionID	The version of the identification scheme.	rdfs:Literal [0..*]
epo:StrategicProcurement	epo:hasStrategicProcurementDescription	Self-explanatory text about a concept.	rdfs:Literal [0..*]
epo:SubcontractTerm	epo:hasSubcontractingInvolved	List of Subcontractors and the subject matter they cover are required. Additional Information: The tenderer will ned to supply this information in the tender. WG Approval 28/02/2019	xsd:boolean [0..1]
epo:SubcontractTerm	epo:hasSubcontractorsProposedAboveObligation	The maximum percentage of the contract value that the contractor must subcontract. Additional information: This is used for the competitive procedure described in Title III of Directive 2009/81/EC. WG Approval 09/11/2021	xsd:decimal [0..1]
epo:SubcontractingEstimate	epo:hasSubjectMatter	Description of the share of the contract that is to be subcontracted. Additional infromation: This can be an aggregate of several subcontracts. WG Approval 09/11/2021	rdfs:Literal [0..*]
epo:SubmissionTerm	epo:hasSubmissionURL	Additional Information: This corresponds to the eForms BT-18 Submission URL.	xsd:anyURI [0..*]
epo:MultipleStageProcedureTerm	epo:hasSuccessiveReduction	The number of solutions or tenders will be reduced in iterative evaluations for multiple staged procedures. Additional information: This refers to multiple-stage procedures (included two-stage procedures, at least). Open Procedures can be seen as one-stage procedures. WG Approval 22/08/2019	xsd:boolean [0..1]
cccev:Constraint	epo:hasThresholdValue	The cut-off level for a given concept. Additional Information: This value is given as e.g. a minimum score, a maximum number of tenders with the highest score passing (see codelist at-voc:number-threshold).	xsd:decimal [1..1]
epo:AgentInRole epo:ProcurementElement	epo:hasTitle	A short self-descriptive name of the instance of the concept. Additional Information: For example, the title of a planned part that may become a procedure or a lot in the future; the title of a contract, etc. (WG Approval 11-11-2019) A short self-descriptive name of the instance of the concept. Additional Information: For example, the title of a planned part that may become a procedure or a lot in the future; the title of a contract, etc. (WG Approval 11-11-2019)	rdfs:Literal [0..*] rdfs:Literal [0..*]
epo:ReviewRequestSummary	epo:hasTotalNumberOfComplainants	The number of economic operators that requested the buyer to review any of its decisions (e.g. the technical specifications, award decision), as set out in Art. 1(5) of Directive 89/665/EEC and Directive 92/13/EEC. Additional information: This attribute corresponds in eForms to BT-712 Buyer Review Complainants WG Approval 11/04/2019	xsd:integer [0..1]
epo:GreenProcurement	epo:hasTotalVehicles	The number of all vehicles (regardless of whether clean or not) that have either been purchased, leased, rented, hired-purchased or their use has been contractually committed to for the provision of a purchased service. Additional Information In the European Union, the legal requirements and scope for the provision of these vehicles or services are covered by Directive 2009/33/EC. WG Approval 28/07/2020	xsd:integer [0..1]
epo:Quantity	epo:hasUnitDescription	A narrative explanation defining the units of items being counted Additional information: This could be for example individual items or pack or two. WG Approval 09/11/2021	rdfs:Literal [0..*]
epo:SubmissionStatisticalInformation	epo:hasUnverifiedTenders	Offers received for which it has not been verified if they are admissible or inadmissible (e.g. because award criteria have been evaluated for all tenders and admissibility is checked only for the winning tender). WG Approval 28/07/2020	xsd:integer [0..1]
cv:Channel epo:Fund	epo:hasURL	The identifier of a resource. Additional Information For example: 1. The URL of the system from where to access the procurement documents; 2. The URL of the system for the submission of tender documents; 3. The URL of the system from where to download a tool to communicate with the Buyer; 4. The URL of the system used by a Technique to allow Economic Operators to exchange information with the Buyer (e.g. eAuction and DPS Systems) 5. The URL of the system used to exchange information between Buyer and EO for questions and clarifications; WG Approval 30/09/2019 The identifier of a resource. Additional Information For example: 1. The URL of the system from where to access the procurement documents; 2. The URL of the system for the submission of tender documents; 3. The URL of the system from where to download a tool to communicate with the Buyer; 4. The URL of the system used by a Technique to allow Economic Operators to exchange information with the Buyer (e.g. eAuction and DPS Systems) 5. The URL of the system used to exchange information between Buyer and EO for questions and clarifications; WG Approval 30/09/2019	xsd:anyURI [1..1] xsd:anyURI [0..1]
epo:Document	epo:hasVersion	A number that identifies a specific state of a document. WG approval: 18/11/2021	rdfs:Literal [0..1]
epo:ReviewRequest	epo:hasWithdrawalDate	The date and time when the request for review was withdrawn. Additional information: This attribute corresponds in eForms to BT-797 Review Request Withdrawn Date.	xsd:date [0..1]
epo:ReviewRequest	epo:hasWithdrawalReason	The explanation for withdrawing the request for review. Additional information: This attribute corresponds in eForms to BT-798 Review Request Withdrawn Reasons	rdfs:Literal [0..1]
epo:GreenProcurement	epo:hasZeroEmissionVehicles	The number of all zero-emission heavy-duty vehicles that have either been purchased, leased, rented, hired-purchased or their use has been contractually committed to for the provision of a purchased service. Additional Information In the European Union, the legal requirements and scope for the provision of these vehicles or services are covered by Directive 2009/33/EC. WG Approval 28/07/2020	xsd:integer [0..1]
epo:Procedure	epo:isAccelerated	Statement about the fact that the procedure will be reduced due to a state of urgency. Additional Information This modifies the time limit for the receipt of requests to participate or the receipt of tenders. WG Approval 20/08/2019	xsd:boolean [0..1]
cv:Channel	epo:isAdhocChannel	The channel uses tools and devices that are not generally available. Additional Information This corresponds in eForms to BT-724 Tool Atypical.	xsd:boolean [0..1]
epo:SubmissionTerm	epo:isAdvancedElectronicSignatureRequired	Advanced or qualified electronic signature or seal (as defined in Regulation (EU) No 910/2014) is required. The submitted information is required to be signed electronically. Additional Information: Signature can be defined as "data in electronic form which is attached to or logically associated with other data in electronic form and which is used by the signatory to sign. For more details on the meaning and uses of electronic signature you may consult different authoritative sources, a relevant one being for instance the Regulation (EU) 910/2014 on electronic identification and trust services for electronic transactions in the internal market. WG Approval 21/07/2020	xsd:boolean [0..1]
epo:ProcedureTerm	epo:isAwardedByCPB	Procedure is awarded by a Central Purchasing Body.	xsd:boolean [0..1]
epo:ProcurementProcessInformation	epo:isCompetitionTerminated	No further contracts will be awarded in this procedure. Additional Information: This can be instantiated in the post award phase. PIN for Competition needs to be signaled. This field can be used even if no contracts are awarded in the contract award notice. This corresponds in eForms to BT-756 PIN Competition Termination.	xsd:boolean [0..1]
epo:Buyer	epo:isContractingEntity	Role of entities, which: (a) are contracting authorities or public undertakings and which pursue one of the activities referred to in Articles 8 to 14 of the Directive 2014/25/EU. (b) when they are not contracting authorities or public undertakings, have as one of their activities any of the activities referred to in Articles 8 to 14, or any combination thereof and operate on the basis of special or exclusive rights granted by a competent authority of a Member State. Additional Information The indicator is needed in order to discriminate between those contracts where the Contracting Entity acts as a Contracting Authority undergoing the limits and the rules of Directive 24 and those where it acts as a Contracting Entity, with certain relaxed constraints. For example, the Contracting Entities have different thresholds for the application of Directive 24 if compared with Contracting Authorities. WG Approval 28/04/2020	xsd:boolean [0..1]
epo:ProcurementObject	epo:isCoveredByGPA	Specifies whether the Agreement on Government Procurement (GPA) applies. Additional information: The GPA aims to establish a multilateral framework of balanced rights and obligations relating to public contracts with a view to achieving the liberalization and expansion of world trade. This corresponds in the e Forms to BT-115 GPA Coverage. WG Approval 15/10/2019	xsd:boolean [0..1]
epo:Procedure	epo:isDesignContest	A competition which enables the buyer to acquire a plan or design via a jury. Additional information: Design contests have traditionally mostly been used in the fields of town and country planning, architecture and engineering or data processing, other purposes, such as to obtain plans for financial engineering The contest may include or not the award of prizes; WG approval 04-02-2021	xsd:boolean [0..1]
epo:ProcurementProcessInformation	epo:isDPSTerminated	End of the Dynamic Purchase System (DPS). Additional Information: This property can be used in the contract award notice even if no contracts are awarded. WG Approval 22/11/2019	xsd:boolean [0..1]
epo:SubmissionTerm	epo:isGuaranteeRequired	The submitted information must include a financial commitment to be used in case of default. Additional Information: See the additional information provided in the definition of the 'Guarantee Description' element. WG Approval 21/07/20	xsd:boolean [0..1]
epo:Procedure	epo:isJointProcurement	Multiple buyers procure together within the same procedure. Addition Information: In case the joint procurement involves buyers from different countries, the national law is specified by the epo:hasCrossBorderLaw in the ProcedureTerm .	xsd:boolean [0..1]
epo:Business	epo:isListedCompany	Public companies listed on a stock exchange and subject to disclosure requirements (either by stock exchange rules or through law or enforceable means), which impose requirements to ensure adequate transparency of beneficial ownership. <u>Additional Information:</u> In eForms this indicator is used when the nationality of beneficial owner is not provided because the Economic Operator is registered in a regulated market that is subject to disclosure requirements consistent with Union law or subject to equivalent international standards which ensure adequate transparency of ownership information. WG Approval 21/11/2019	xsd:boolean [0..1]
epo:SubmissionTerm	epo:isMultipleTenderSubmissionAllowed	Tenderers may submit more than one competing tenders. WG Approval 10/10/2019	xsd:boolean [0..1]
epo:ProcedureTerm	epo:isOneLotOnlyAllowed	Indicates whether tenders may be submitted for only one Lot. Additional information: This field is used to complement the SubmissionTerms (which are at the Lot level) for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled in the TED Standard Forms). WG approval 23/08/2022	xsd:boolean [0..1]
epo:ElementChangeDescription	epo:isProcurementDocumentChanged	One or more procurement documents have been changed. Additional information: This corresponds in eForms to BT-718 Change Procurement Documents WG Approval 05/11/2019	xsd:boolean [0..1]
epo:AccessTerm	epo:isProcurementDocumentRestricted	The access to certain procurement documents is restricted. Additional Information: This corresponds in eForms to BT-14 Documents Restricted. WG Approval 10/10/2019	xsd:boolean [0..1]
epo:ProcurementObject	epo:isRecurrent	The Procurement being notified is likely to be included in another procedure in the foreseeable future. Additional Information: For example, a regularly re-tendered municipal service. This does not include awarding multiple contracts within a single qualification system, framework agreement, or a dynamic purchasing system. This corresponds in eForms to BT-94 Recurrence. WG Approval 12/05/2020	xsd:boolean [0..1]
epo:ContractTerm	epo:isRenewalIndicator	Indicates whether the contract is subject to a renewal clause. WG Approval 09/11/2021	xsd:boolean [0..1]
epo:ProcurementObject	epo:isSMESuitable	The Lot is suitable for small and medium enterprises (SMEs). Additional Information This allows the buyer to make emphasis on the fact that the procedure has been designed having SMEs in mind. This indicator is also to be reflected in the selection criteria. For example, number of employees and turnover are applicable to the definition of an SME. WG Approval 15/10/2019	xsd:boolean [0..1]
epo:ProcedureTerm	epo:isSubmissionForAllLotsAllowed	Indicates whether tenders may be submitted for all Lots. Additional information: This field is used to complement the SubmissionTerms (which are at the Lot level) for the Procedure level which is covered by the regulation (EU)-2015-1986 (modeled in the TED Standard Forms) WG approval 23/08/2022	xsd:boolean [0..1]
epo:ProcurementProcessInformation	epo:isToBeRelaunched	Indicator of whether the procurement object is to be relaunched. Additional information: This can be instantiated in the post award phase. This corresponds in eForms to BT-634 Procurement Relaunch. WG Approval: 18/01/2022	xsd:boolean [0..1]
epo:SelectionCriterion	epo:isUsedForCandidateRestriction	The criterion will be used to select the candidates to be invited for the second stage of a multistage procedure. Additional Information: This property is only used if a maximum number of candidates was foreseen in the procedure. This corresponds in eForms to BT-40 Selection Criteria Second Stage Invite	xsd:boolean [0..1]
epo:ProcurementObject	epo:isUsingEUFunds	The procurement foresees funding by the Europeanin Union funds such as the European Structural and Investment Funds or grants awarded by the European Union. Additional Information: The funding may cover the whole procurement or part of the procurement. This corresponds in eForms to BT-60 EU Funds. This shall be interpreted in the context of BG-61 EU Funds (which can point to a group of Lots).	xsd:boolean [0..1]
epo:Tender	epo:isVariant	Alternative solution to fulfil the buyer's needs as opposed to solutions indicated in the procurement documents. Additional Information: The permission to offer variants is only allowed if specified in a Contract Notice or a Prior Information Notice that used as a means for calling for a competition. The buyer lays out minimum requirements in the procurement documents that must be respected by tenderers submitting variants. WG Approval 29/05/2019	xsd:boolean [0..1]
epo:ReviewRequest	epo:isWithdrawn	The review request was withdrawn. Additional information: This attribute corresponds in eForms to BT-796 Review Request Withdrawn.	xsd:boolean [0..1]
epo:PurchaseContract	epo:isWithinFrameworkAgreement	A contract resulting from the use of an existing framework agreement. Additional information: This corresponds in Eforms to BT-768 Contract Framework Agreement. This indicator is generally used to differentiate the purchase contract within a framework agreement or a direct purchasing system.	xsd:boolean [1..1]
cpv:Person	foaf:familyName	The hereditary surname of a family.	rdfs:Literal [0..*]
cpv:Person	foaf:givenName	The name(s) that identify the Person within a family with a common surname.	rdfs:Literal [0..*]
cpv:Person	foaf:name	The complete name of the Person as one string.	rdfs:Literal [0..*]
locn:Address	locn:addressArea	The name or names of a geographic area or locality that groups a number of addressable objects for addressing purposes, without being an administrative unit. Additional Information: This would typically be part of a city, a neighbourhood or village, e.g. Montmartre.	rdfs:Literal [0..1]
locn:Address	locn:adminUnitL1	The name or names of a unit of administration related to the exercise of jurisdictional rights, for local, regional and national governance. Level 1 refers to the uppermost administrative unit for the address, almost always a country. Additional Information: Best practice is to use the ISO 3166-1 code but if this is inappropriate for the context, country names should be provided in a consistent manner to reduce ambiguity. For example, either write 'France' or 'FRA' consistently throughout the dataset and avoid mixing the two. The Country controlled vocabulary from the Publications Office can be reused for this.	rdfs:Literal [0..1]
locn:Address	locn:adminUnitL2	The name or names of a unit of administration related to the exercise of jurisdictional rights, for local, regional and national governance. Level 2 refers to the region of the address, usually a county, state or other such area that typically encompasses several localities. Additional Information: Some recommended codelists from the EU Publications Office include: Administrative Territorial Units (ATU), NUTS and Local Administrative Units (LAU). The first arrondissement of Paris is for example expressed as "http://publications.europa.eu/resource/authority/atu/FRA_AR_PAR01" in the ATU controlled vocabulary.	rdfs:Literal [0..1]
locn:Address	locn:fullAddress	The complete address written as a formatted string. Additional Information: Use of this property is recommended as it will not suffer any misunderstandings that might arise through the breaking up of an address into its component parts. This property is analogous to vCard's label property but with two important differences: (1) formatting is not assumed so that, unlike vCard label, it may not be suitable to print this on an address label, (2) vCard's label property has a domain of vCard Address; the fullAddress property has no such restriction. An example of a full address is "Champ de Mars, 5 Avenue Anatole France, 75007 Paris, France".	rdfs:Literal [0..1]
dct:Location	locn:geographicName	A textual description for a Location. Additional Information: The INSPIRE Data Specification on Geographical Names provides a detailed model for describing a 'named place', including methods for providing multiple names in multiple scripts. This is beyond what is necessary for the Core Location Vocabulary but, importantly, the concept of a geographic name used here is consistent. A geographic name is a proper noun applied to a spatial object. Taking the example used in the INSPIRE document (page 15), the following are all valid geographic names for the Greek capital: - "Aθnνa"@gr-Grek (the Greek endonym written in the Greek script) - "Ath&#237;na"@gr-Latn (the standard Romanisation of the endonym) - "Athens"@en (the English language exonym) INSPIRE has a detailed (XML-based) method of providing metadata about a geographic name and in XML-data sets that may be the most appropriate method to follow. When using the Core Location Vocabulary in data sets that are not focussed on environmental/geographical data (the use case for INSPIRE), the Code datatype or a simple language identifier may be used to provide such metadata. The country codes defined in ISO 3166 may be used as geographic names and these are generally preferred over either the long form or short form of a country's name (as they are less error prone). The Publications Office of the European Union recommends the use of ISO 3166-1 codes for countries in all cases except two: - use 'UK' in preference to the ISO 3166 code GB for the United Kingdom; - use 'EL' in preference to the ISO 3166 code GR for Greece. Where a country has changed its name or no longer exists (such as Czechoslovakia, Yugoslavia etc.) use the ISO 3166-3 code.	rdfs:Literal [0..1]
locn:Address	locn:locatorDesignator	A number or a sequence of characters which allows a user or an application to interpret, parse and format the locator within the relevant scope. A locator may include more locator designators. Additional Information: In simpler terms, this is the building number, apartment number, etc. For an address such as "Flat 3, 17 Bridge Street", the locator is "flat 3, 17".	rdfs:Literal [0..1]
locn:Address	locn:locatorName	Proper noun(s) applied to the real world entity identified by the locator. Additional Information: The locator name could be the name of the property or complex, of the building or part of the building, or it could be the name of a room inside a building. The key difference between a locator and a locator name is that the latter is a proper name and is unlikely to include digits. For example, "Shumann, Berlaymont" is a meeting room within the European Commission headquarters for which locator name is more appropriate than locator.	rdfs:Literal [0..1]
locn:Address	locn:postCode	The post/zip code of an address. (INSPIRE's definition is "A code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.") Additional Information: Post codes are common elements in many countries' postal address systems. One of the many post codes of Paris is for example "75000".	rdfs:Literal [0..*]
locn:Address	locn:postName	The key postal division of the address, usually the city. (INSPIRE's definition is "One or more names created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.) For example, "Paris".	rdfs:Literal [0..*]
locn:Address	locn:thoroughfare	An address component that represents the name or names of a passage or way through from one location to another. A thoroughfare is not necessarily a road, it might be a waterway or some other feature. Additional Information: For example, "Avenue des Champs-&#201;lys&#233;es".	rdfs:Literal [0..*]
cpv:Person	person:birthName	Family name of the Person given upon their birth. WG Approval 09/11/2021	rdfs:Literal [0..*]
cpv:Person	person:patronymicName	Name based on the given name of the Person's father. WG Approval 09/11/2021	rdfs:Literal [0..*]
epo:SpecificDuration	time:numericDuration	Value of a temporal extent expressed as a number.	xsd:decimal [1..1]

Predicates (object properties) and definitions

Predicate name	Definition	Domain, Range and Cardinality
cccev:confidentialityLevelType	Security classification assigned to an Evidence e.g. classified, sensitive, public. Additional Information: Classifications should be defined by an organisation/country as an outcome of a security assessment.	cccev:Evidence -> at-voc:confidentiality-level [0..1]
cccev:constrains	Information Concept about which a Constraint expresses a limitation. Additional Information: Information Concepts are tools to make Requirements more machine processable: they allow to provide more detail about a Requirement. This way, Constraints can be made very precise, namely the limit that must be achieved, is a limit on the value for the associated Information Concept. For example, the Information Concept would be the age of a person and the Constraint would be the required age in the context of a specific evaluation.	cccev:Constraint -> cccev:InformationConcept [0..*]
cccev:hasRequirement	A more specific Requirement that is part of the Requirement.	cccev:Requirement -> cccev:Requirement [0..*]
cccev:supportsConcept	Information Concept providing facts found/inferred from the Evidence. Additional Information: Examples of Information Concepts are values found explictly in the evidence such as a birth date or information derived from the Evidence such as "I am older that 18 years" or "this is a FairTrade product".	cccev:Evidence -> cccev:InformationConcept [0..*]
cccev:supportsRequirement	Requirement for which the Evidence provides proof.	cccev:Evidence -> cccev:Requirement [0..*]
cccev:type	Category to which the Requirement belongs.	cccev:Criterion -> at-voc:criterion [0..1]
cv:address	Associates any Resource with the corresponding Address. Additional Information: Asserting the address relationship implies that the Resource has an Address. Associates any Resource with the corresponding Address. Additional Information: Asserting the address relationship implies that the Resource has an Address.	cpov:ContactPoint -> locn:Address [0..1] org:Organization -> locn:Address [0..*]
cv:registeredAddress	The registered address relationship links a Resource with the legally registered Address. Additional Information: It is the address to which formal communications can be sent, such as the postal address.	org:Organization -> locn:Address [0..1]
epo:actsOnBehalfOf	Represents.	epo:ProcurementServiceProvider -> epo:Buyer [1..*]
epo:associatedWith	The document to which a document is associated. WGM 01/03/2022	epo:Document -> epo:Document [0..*]
epo:bindsBuyer	Provides legal constraint on the Buyer.	epo:Contract -> epo:Buyer [0..*]
epo:bindsContractor	Provides legal constraint on the Contractor.	epo:Contract -> epo:Contractor [0..*]
epo:comprisesLotAwardOutcome	Incorporates LotAwardOutcome.	epo:AwardDecision -> epo:LotAwardOutcome [1..*]
epo:comprisesTender	Incorporates Tender.	epo:TenderGroup -> epo:Tender [1..*]
epo:comprisesTenderAwardOutcome	Incorporates TenderAwardOutcome.	epo:LotAwardOutcome -> epo:TenderAwardOutcome [0..*]
epo:concernsLot	Relates to Lot.	epo:ProcurementProcessInformation -> epo:Lot [0..1]
epo:concernsProcedure	Relates to Procedure.	epo:ProcurementProcessInformation -> epo:Procedure [0..1]
epo:concernsReviewSummaryForLot	Relates to Lot review summary. Additional information: This relation corresponds in eForms to BT-13722 Buyer Review Lot Identifier.	epo:ReviewRequestSummary -> epo:Lot [1]
epo:containsModificationsOf	Additional information This relation shall be used between Instances of the SAME type/class. The "modifying-instance" can be minimally instantiated, carrying the fields/information that override the fields in the "modified-instance". This means that the "modifying-instance" (is under-specified) and might violate minimal cardinality restrictions in case they are checked. But the purpose of such an instance is not to be used as a full instance.	owl:Thing -> owl:Thing [0..1]
epo:contextualisedBy	The place of the AgentInRole in the procurement is expressed by a ProcurementObject.	epo:AgentInRole -> epo:ProcurementObject [0..*]
epo:definesBudgetProvider	Relation indicating a ProcedureTerm has a BudgetProvider.	epo:ProcedureTerm -> epo:BudgetProvider [0..1]
epo:definesCatalogueProvider	Relation indicating an AccessTerm has a CatalogueProvider.	epo:AccessTerm -> epo:CatalogueProvider [0..*]
epo:definesCatalogueReceiver	Relation indicating an AccessTerm has a CatalogueReceiver.	epo:AccessTerm -> epo:CatalogueReceiver [0..*]
epo:definesContractDuration	Relation indicating a ContractTerm has a Duration.	epo:ContractTerm -> epo:Duration [0..1]
epo:definesContractPeriod	Relation indicating a ContractTerm has a Period.	epo:ContractTerm -> epo:Period [0..1]
epo:definesInformationProvider	Relation indicating a ProcedureTerm has an information provider.	epo:ProcedureTerm -> epo:AuxiliaryParty [0..*]
epo:definesLotGroup	Relation indicating a ProcedureTerm has a LotGroup.	epo:ProcedureTerm -> epo:LotGroup [0..*]
epo:definesMediator	Relation indicating a ProcedureTerm has a Mediator.	epo:ProcedureTerm -> epo:Mediator [0..1]
epo:definesOfflineAccessProvider	Relation indicating an AccessTerm has an OfflineAccessProvider.	epo:AccessTerm -> epo:OfflineAccessProvider [0..1]
epo:definesOpeningPlace	The place where the tenders will be publicly opened. WG Approval 10-10-2019	epo:OpeningTerm -> locn:Address [0..1]
epo:definesParticipationRequestProcessor	Relation indicating a ParticipationRequestTerm has a ParticipationRequestProcessor.	epo:ParticipationRequestTerm -> epo:ParticipationRequestProcessor [0..1]
epo:definesParticipationRequestReceiver	Relation indicating a ParticipationRequestTerm has a ParticipationRequestReceiver.	epo:ParticipationRequestTerm -> epo:ParticipationRequestReceiver [0..1]
epo:definesPaymentExecutor	Relation indicating a ContractTerm has a PaymentExecutor.	epo:ContractTerm -> epo:PaymentExecutor [0..1]
epo:definesPrize	Relation indicating a DesignContestRegimeTerm has a Prize.	epo:DesignContestRegimeTerm -> epo:Prize [0..*]
epo:definesProcurementProcedureInformationProvider	Relation indicating an AccessTerm has a ProcurementProcedureInformationProvider.	epo:AccessTerm -> epo:ProcurementProcedureInformationProvider [0..1]
epo:definesReviewer	Relation indicating a ReviewTerm has a Reviewer.	epo:ReviewTerm -> epo:Reviewer [0..*]
epo:definesReviewProcedureInformationProvider	Relation indicating a ReviewTerm has a ReviewProcedureInformationProvider.	epo:ReviewTerm -> epo:ReviewProcedureInformationProvider [0..1]
epo:definesSpecificPlaceOfPerformance	Relation indicating a ContractTerm has a specific place of performance.	epo:ContractTerm -> dct:Location [0..*]
epo:definesSubcontractingTerm	Relation indicating a ContractTerm has a SubcontractingTerm.Relation indicating a term has a subterm.	epo:ContractTerm -> epo:SubcontractTerm [0..1]
epo:definesTenderProcessor	Relation indicating a SubmissionTerm has a TenderProcessor.	epo:SubmissionTerm -> epo:TenderProcessor [0..1]
epo:definesTenderReceiver	Relation indicating a SubmissionTerm has a TenderReceiver.	epo:SubmissionTerm -> epo:TenderReceiver [0..1]
epo:delegatesAncillaryActivitiesTo	Entrusts ancillary purchasing activities to ProcurementServiceProvider. Additional Information: Directive 2014/24/EU describes ancillary purchasing activities as activities consisting in the provision of support to purchasing activities, in particular in the following forms: (a) technical infrastructure enabling contracting authorities to award public contracts or to conclude framework agreements for works, supplies or services; (b) advice on the conduct or design of public procurement procedures; (c) preparation and management of procurement procedures on behalf and for the account of the contracting authority concerned;	epo:Buyer -> epo:ProcurementServiceProvider [0..*]
epo:dependsOnBuyer		epo:Awarder -> epo:Buyer [0..1] epo:BudgetProvider -> epo:Buyer [0..1] epo:ParticipationRequestProcessor -> epo:Buyer [0..1] epo:ParticipationRequestReceiver -> epo:Buyer [0..1] epo:TenderProcessor -> epo:Buyer [0..1] epo:TenderReceiver -> epo:Buyer [0..1] epo:PaymentExecutor -> epo:Buyer [0..1]
epo:dependsOnReviewer		epo:ReviewProcedureInformationProvider -> epo:Reviewer [0..1]
epo:dependsOnServiceProvider		epo:BudgetProvider -> epo:ProcurementServiceProvider [0..1] epo:ParticipationRequestProcessor -> epo:ProcurementServiceProvider [0..1] epo:ParticipationRequestReceiver -> epo:ProcurementServiceProvider [0..1] epo:PaymentExecutor -> epo:ProcurementServiceProvider [0..1] epo:TenderProcessor -> epo:ProcurementServiceProvider [0..1] epo:TenderReceiver -> epo:ProcurementServiceProvider [0..1]
epo:dependsOnTenderer		epo:Winner -> epo:Tenderer [0..1]
epo:describesLot		epo:LotAwardOutcome -> epo:Lot [1]
epo:describesLotCompletion		epo:ContractLotCompletionInformation -> epo:Lot [1]
epo:describesLotGroup		epo:LotGroupAwardInformation -> epo:LotGroup [1]
epo:describesNotice		epo:NoticeDescription -> epo:Notice [1]
epo:describesTender		epo:TenderAwardOutcome -> epo:Tender [1]
epo:followsRulesSetBy		epo:PurchaseContract -> epo:FrameworkAgreement [0..1]
epo:foreseesConcession		epo:Tender -> epo:ConcessionEstimate [0..1]
epo:foreseesContractSpecificTerm		epo:ProcurementObject -> epo:ContractSpecificTerm [0..*]
epo:foreseesSubcontracting		epo:Tender -> epo:SubcontractingEstimate [0..*]
epo:foreseesTechnique		epo:PlannedProcurementPart -> epo:TechniqueUsage [0..*]
epo:fulfillsRequirement	The requirement to which the concept meets. WG Approval 09/11/2021 The codelist to be used is at-voc:environmental-impact which is available at http://publications.europa.eu/resource/dataset/environmental-impact The requirement to which the concept meets. WG Approval 09/11/2021 The codelist to be used is at-voc:innovative-acquisition which is available at http://publications.europa.eu/resource/dataset/innovative-acquisition The requirement to which the concept meets. WG Approval 09/11/2021 The codelist to be used is at-voc:social-objective which is available at http://publications.europa.eu/resource/dataset/social-objective	epo:GreenProcurement -> at-voc:environmental-impact [1..*] epo:InnovativeProcurement -> at-voc:innovative-acquisition [1..*] epo:SocialProcurement -> at-voc:social-objective [1..*]
epo:fulfillsStrategicProcurement		epo:ProcurementObject -> epo:StrategicProcurement [0..*]
epo:hasAdditionalClassification	The codelist to be used is at-voc:cpv which is available at http://publications.europa.eu/resource/dataset/cpv The codelist to be used is at-voc:cpv which is available at http://publications.europa.eu/resource/dataset/cpv	epo:Purpose -> at-voc:cpv [0..*] epo:Purpose -> at-voc:cpvsuppl [0..*]
epo:hasAdditionalContractNature	Additional type of acquisition taken into consideration in the contract. WG Approval 11/06/2020 The codelist to be used is at-voc:contract-nature which is available at http://publications.europa.eu/resource/dataset/contract-nature	epo:ContractTerm -> at-voc:contract-nature [0..*]
epo:hasAllegedIrregularityType	Additional information: This relation corresponds in eForms to BT-791 Review Irregularity Type	epo:ReviewRequest -> at-voc:irregularity-type [1..*]
epo:hasAwardCriterionType	Category of award criterion. The codelist to be used is at-voc:award-criterion-type which is available at http://publications.europa.eu/resource/dataset/award-criterion-type	epo:AwardCriterion -> at-voc:award-criterion-type [0..1]
epo:hasAwardedEstimatedValue	The estimated value that can be spent as provided by the Award Decision. <u>Additional Information</u>: This property is used for framework agreements and dynamic purchasing systems. Different cases of awarded values may refer to a lot, the global value of the procedure, or of a combinatorial value of a group of lots. WG Approval 12/12/2019	epo:LotAwardOutcome -> epo:MonetaryValue [0..1]
epo:hasAwardedValue	The value of the procurement provided by the Award Decision. Additional Information: Different cases of awarded values may refer to a lot, the global value of the procedure, or of a combinatorial value of a group of lots. In the case of framework agreements and dynamic purchasing systems this refers to the maximum awarded value. WG Approval 10/12/2019	epo:LotAwardOutcome -> epo:MonetaryValue [0..1]
epo:hasAwardStatus	Indicates whether the lot is awarded, not awarded or still open. WG Approval 03/12/2019 The codelist to be used is at-voc:winner-selection-status which is available at http://publications.europa.eu/resource/dataset/winner-selection-status	epo:LotAwardOutcome -> at-voc:winner-selection-status [0..1]
epo:hasBargainPrice		epo:LotAwardOutcome -> epo:MonetaryValue [0..1]
epo:hasBeneficialOwner	A role of any natural person(s) who ultimately owns or controls the organisation or on whose behalf a transaction or activity is being conducted. Additional Information: This role is defined in the directive EU 2015/849 and it's beyond the scope for public eProcurement domain. WG approval 14/09/2021	epo:Business -> cpv:Person [0..*]
epo:hasBroadPlaceOfPerformance	Geopolitical zone where the contract can be executed. Additional Information Used for setting restrictions that cannot be established with one country code or a geographical zone identifier (like NUTS), because they have a broader scope (geographical, economic, political, other). The codelist to be used is at-voc:other-place-service which is available at http://publications.europa.eu/resource/dataset/other-place-service	epo:ContractTerm -> at-voc:other-place-service [0..1]
epo:hasBusinessSize	The category of the business depending on number of employees and turnover. Additional information: See Commission Recommendation of 6 May 2003 concerning the definition of micro, small and medium-sized enterprises. ELI: http://data.europa.eu/eli/reco/2003/361/oj WG Approval 28/05/2020 The codelist to be used is at-voc:economic-operator-size which is available at http://publications.europa.eu/resource/dataset/economic-operator-size	epo:Business -> at-voc:economic-operator-size [0..1]
epo:hasBuyerLegalType	A category that indicates the right of an organisation to play the role of a buyer. Additional Information: The category also effects the rules that the buyer has to abide to within the public procurement procedure. WG 07/09/2021 The codelist to be used is at-voc:buyer-legal-type which is available at http://publications.europa.eu/resource/dataset/buyer-legal-type	org:Organization -> at-voc:buyer-legal-type [0..1]
epo:hasChangeJustification	Code explaining the change. Additional Information: The codelist to be used is at-voc:change-corrig-justification which is available at http://publications.europa.eu/resource/dataset/change-corrig-justification WG Approval 5/11/2019 The motives for the change. WG 5/11/2019 The codelist to be used is at-voc:change-corrig-justification which is available at http://publications.europa.eu/resource/dataset/change-corrig-justification	epo:ElementChangeDescription -> at-voc:change-corrig-justification [1]
epo:hasConfirmedIrregularityType	Additional information: This relation corresponds in eForms to BT-791 Review Irregularity Type	epo:ReviewDecision -> at-voc:irregularity-type [0..*]
epo:hasConstraint		epo:ProcurementCriterion -> cccev:Constraint [0..*]
epo:hasContactPointInRole		epo:AgentInRole -> cpov:ContactPoint [0..*]
epo:hasContractNatureType	Subject of the acquisition. WG Approval 11/06/2020 The codelist to be used is at-voc:contract-nature which is available at http://publications.europa.eu/resource/dataset/contract-nature	epo:ContractTerm -> at-voc:contract-nature [0..1]
epo:hasCountryCode	The codelist to be used is at-voc:country which is available at http://publications.europa.eu/resource/dataset/country The codelist to be used is at-voc:country which is available at http://publications.europa.eu/resource/dataset/country	dct:Location -> at-voc:country [0..1] locn:Address -> at-voc:country [0..1]
epo:hasCountryOfBirth	The country in which the Person was born. The codelist to be used is at-voc:country which is available at http://publications.europa.eu/resource/dataset/country	cpv:Person -> at-voc:country [0..1]
epo:hasCurrency	The identifier of the currency as in the standard code list used. The codelist to be used is at-voc:currency which is available at http://publications.europa.eu/resource/dataset/currency	epo:MonetaryValue -> at-voc:currency [0..1]
epo:hasDeliveryGateway		org:Organization -> cv:Channel [0..1]
epo:hasDirectAwardJustification	List of reasons for using a procedure which allows awarding contracts directly without publishing a notice. WG Approval 28/05/2020 The codelist to be used is at-voc:direct-award-justification which is available at http://publications.europa.eu/resource/dataset/direct-award-justification	epo:DirectAwardTerm -> at-voc:direct-award-justification [0..1]
epo:hasDocumentRestrictionJustification	An explanation about the reasons why some procurement documents are restricted. Additional Information: This corresponds in eForms to BT-707 Documents Restricted Justification. WG Approval 09/03/2021	epo:AccessTerm -> at-voc:communication-justification [0..1]
epo:hasDPSScope	Explanation as to whether a dps is used and by whom. Additional Information: This corresponds in eForms to BT-766 Dynamic Purchasing System. The codelist to be used is at-voc:dps-usage which is available at http://publications.europa.eu/resource/dataset/dps-usage WG Approval 09/11/2021 Explanation as to whether a dps is used and by whom. WG Approval 09/11/2021 The codelist to be used is at-voc:dps-usage which is available at http://publications.europa.eu/resource/dataset/dps-usage	epo:DynamicPurchaseSystemTechniqueUsage -> at-voc:dps-usage [0..1]
epo:hasECataloguePermission	The extent to which electronic catalogues may be used in tenders. WG Approval 03/10/2019 The codelist to be used is at-voc:permission which is available at http://publications.europa.eu/resource/dataset/permission	epo:SubmissionTerm -> at-voc:permission [0..1]
epo:hasElementChange		epo:NoticeChange -> epo:ElementChangeDescription [1..*]
epo:hasElementConfidentiality	Relation indication that the publication provision applies to a given field of a document.	epo:PublicationProvision -> epo:ElementConfidentialityDescription [1..*]
epo:hasElementDescription		epo:NoticeDescription -> epo:ElementDescription [0..*]
epo:hasElementModification		epo:ContractModification -> epo:ElementModificationDescription [1..*]
epo:hasEstimatedBuyerConcessionRevenue	The expected payments made by the buyer to the economic operator awarded the concession that are not directly related to the use of the concession. <u>Additional Information:</u> For example the public buyer pays a yearly fee to provide a ticketing solution to the public. The fee the public pays for every ticket sold through the solution is not included in this estimation but in the estimation of the user concession revenue. This corresponds to BT-160 in eForms. WG Approval 07/01/2020	epo:ConcessionEstimate -> epo:MonetaryValue [0..1]
epo:hasEstimatedDuration	Relation indicating a Contract has an estimated Duration. Additional Information When the Lot uses a Technique the contract estimated duration applies to the Technique.	epo:Contract -> epo:Duration [0..1]
epo:hasEstimatedUserConcessionRevenue	The estimated revenue coming from the use of the concession. Additional Information: Revenues are for example fees and fines. For example, the fees and fines coming from the cars using a motorway. This corresponds to BT-162 in eForms.	epo:ConcessionEstimate -> epo:MonetaryValue [0..1]
epo:hasEstimatedValue	A forecast of the value of the procurement before competition. Additional Information: Different cases of estimated values may refer to a lot, the global value of the procedure, or of a combinatorial value of a group of lots. The forecast is calculated by the buyer and covers all revenues whether coming from the buyer or third parties. See for example recital (19), Article 5 of Directive 2014/24/EU and other articles from the rest of Directives about procurement. In the case of framework agreements and dynamic purchasing systems this refers to the maximum estimated value. This property corresponds to BT-27 in eForms (for Lot and Procedure) and can be used for BT-157 (for LotGroup). <b> </b><b>WG Approval 05/12/2019</b> A forecast of the value of the procurement before competition. Additional Information Different cases of estimated values may refer to a lot, the global value of the procedure, or of a combinatorial value of a group of lots. The forecast is calculated by the buyer and covers all revenues whether coming from the buyer or third parties. See for example recital (19), Article 5 of Directive 2014/24/EU and other articles from the rest of Directives about procurement. In the case of lots or groups of lots using framework agreements and dynamic purchasing systems this refers to the maximum estimated value. <b> </b>This property corresponds to BT-27 in eForms (for Lot and Procedure) and can be used for BT-157 (for LotGroup). <b> </b><b>WG Approval 05/12/2019</b>	epo:ProcurementObject -> epo:MonetaryValue [0..1] epo:LotGroup -> epo:MonetaryValue [0..1]
epo:hasESubmissionPermission	The requirements as to what extent electronic submission is allowed. WG Approval 03/10/2019 The codelist to be used is at-voc:permission which is available at http://publications.europa.eu/resource/dataset/permission	epo:SubmissionTerm -> at-voc:permission [0..1]
epo:hasFinancialOfferValue	The value offered by the Tenderer for a Lot. Additional Information: This value is normally the one awarded for a winning Tender Lot. In case of negotiated procedures the original financial value may be reviewed and the offer updated. This corresponds to BT-720 in eForms.	epo:Tender -> epo:MonetaryValue [0..1]
epo:hasFixedValueType	The method to interpret the fixed value as pertaining to a total or unit. WG Approval 17/09/2019 The codelist to be used is at-voc:number-fixed which is available at http://publications.europa.eu/resource/dataset/number-fixed	epo:AwardCriterion -> at-voc:number-fixed [0..1]
epo:hasFormType	A categorisation of the steps in which the Notice is used. WG Approval 12/05/2020 The codelist to be used is at-voc:form-type which is available at http://publications.europa.eu/resource/dataset/form-type	epo:Notice -> at-voc:form-type [0..1]
epo:hasFrameworkAgreementEstimatedValue	This refers to BT-660 in eForms.	epo:LotAwardOutcome -> epo:MonetaryValue [0..1]
epo:hasFrameworkAgreementMaximumValue	This refers to BT-709 in eForms.	epo:LotAwardOutcome -> epo:MonetaryValue [0..1]
epo:hasFrameworkAgreementType	The form of framework agreement used in a procurement procedure. Addition information: A concept to distinguish the different types of framework agreement, which are: 1. Framework agreement without reopening of competition, 2. Framework agreement with reopening of competition, or 3. Framework agreement partly without reopening of competition. WG Approval 19/09/2019 The codelist to be used is at-voc:framework-agreement which is available at http://publications.europa.eu/resource/dataset/framework-agreement	epo:FrameworkAgreementTerm -> at-voc:framework-agreement [1]
epo:hasGroupFrameworkAgreementAwardedValue	This corresponds to BT-156 in the eForms.	epo:LotGroupAwardInformation -> epo:MonetaryValue [0..1]
epo:hasHighestReceivedTenderValue	Amount of the Tender with the highest value. Additional Information The value must correspond to an admissible tender. For example, tenders compliant with the procurement document requirements, not having an abnormally low price or cost, etc. WG Approval 12/12/2019	epo:SubmissionStatisticalInformation -> epo:MonetaryValue [0..1]
epo:hasID	A unique identifier of the instance of the concept. Additional Information: For example, in the case of the Procurement Identifier, this could be the European Public Procurement Identifier, and/or any other identifier provided by the buyer, the service provider or any other stakeholder. WG Approval 12/11/2019 A unique identifier of the instance of the concept. Additional Information For example, in the case of the Procurement Identifier, this could be the European Public Procurement Identifier, and/or any other identifier provided by the buyer, the service provider or any other stakeholder. WG Approval 12/11/2019 A unique identifier of the instance of the concept. Additional Information For example, in the case of the Procurement Identifier, this could be the European Public Procurement Identifier, and/or any other identifier provided by the buyer, the service provider or any other stakeholder. WG Approval 12/11/2019 A unique identifier of the instance of the concept. Additional Information: For example, in the case of the Procurement Identifier, this could be the European Public Procurement Identifier, and/or any other identifier provided by the buyer, the service provider or any other stakeholder. WG Approval 12/11/2019 A unique identifier of the instance of the concept. Additional Information For example, in the case of the Procurement Identifier, this could be the European Public Procurement Identifier, and/or any other identifier provided by the buyer, the service provider or any other stakeholder. WG Approval 12/11/2019 A unique identifier of the instance of the concept. Additional Information For example, in the case of the Procurement Identifier, this could be the European Public Procurement Identifier, and/or any other identifier provided by the buyer, the service provider or any other stakeholder. WG Approval 12/11/2019 A unique identifier of the instance of the concept. Additional Information For example, in the case of the Procurement Identifier, this could be the European Public Procurement Identifier, and/or any other identifier provided by the buyer, the service provider or any other stakeholder. WG Approval 12/11/2019	cccev:InformationConcept -> epo:Identifier [0..1] epo:Document -> epo:Identifier [0..*] epo:Fund -> epo:Identifier [0..1] foaf:Agent -> epo:Identifier [0..*] epo:ProcurementObject -> epo:Identifier [1]
epo:hasIrregularityType	Additional information: This relation corresponds in eForms to BT-636 Buyer Review Requests Irregularity Type	epo:ReviewIrregularitySummary -> at-voc:irregularity-type [1]
epo:hasItemCountryOfOrigin	The source country of the product or service. Additional Information: The country of origin can be provided by the buyer as a requirement or by the tenderer information of the item to be provided. WG Approval 07/01/2020 The codelist to be used is at-voc:country which is available at http://publications.europa.eu/resource/dataset/country	epo:Tender -> at-voc:country [0..*]
epo:hasLanguage	Language in which the submitted information is to be expressed. WG Approval 21/07/2020 The codelist to be used is at-voc:language which is available at http://publications.europa.eu/resource/dataset/language	epo:SubmissionTerm -> at-voc:language [0..*]
epo:hasLateSubmissionPermission	Whether economic operator-related information can be supplemented even after the submission deadline. Additional Information This is specific to the information on the economic operator and not the actual offer. This does not apply to the requests for clarification. WG Approval 21/07/2020 The codelist to be used is at-voc:missing-info-submission which is available at http://publications.europa.eu/resource/dataset/missing-info-submission	epo:SubmissionTerm -> at-voc:missing-info-submission [0..1]
epo:hasLegalBasis	The legal basis under which the procurement procedure takes place. Additional Information: For example European Directives or Regulations, national law WG 09/11/2021 The codelist to be used is at-voc:legal-basis which is available at http://publications.europa.eu/resource/dataset/legal-basis The legal basis under which the procurement procedure takes place. Additional Information: For example European Directives or Regulations, national law WG 09/11/2021 The codelist to be used is at-voc:legal-basis which is available at http://publications.europa.eu/resource/dataset/legal-basis The legal basis under which the procurement procedure takes place. Additional Information: For example European Directives or Regulations, national law WG 09/11/2021 The codelist to be used is at-voc:legal-basis which is available at http://publications.europa.eu/resource/dataset/legal-basis	epo:Notice -> at-voc:legal-basis [0..1] epo:PlannedProcurementPart -> at-voc:legal-basis [0..*] epo:Procedure -> at-voc:legal-basis [0..*]
epo:hasLegalRegime		epo:Procedure -> at-voc-new:legal-regime [0..*]
epo:hasLowestReceivedTenderValue	Amount of the Tender with the lowest value. Additional Information The value must correspond to an admissible tender. For example, tenders compliant with the procurement document requirements, not having an abnormally low price or cost, etc. WG Approval 12/12/2019	epo:SubmissionStatisticalInformation -> epo:MonetaryValue [0..1]
epo:hasMainActivity	The principal sectoral area in which an organisation operates. Additional information: The activities associated with buyers are derived from the top level of the Classification of the functions of the government (COFOG) from the United Nations Statistics Division. The activities associated with buyer are derived from sectors explicitly falling within the sectoral directive (2014/25/EU Art. 8 - Art. 14). WG Approval 05/05/2020 The codelist to be used is at-voc:main-activity which is available at http://publications.europa.eu/resource/dataset/main-activity	org:Organization -> at-voc:main-activity [0..1]
epo:hasMainClassification	The codelist to be used is at-voc:cpv which is available at http://publications.europa.eu/resource/dataset/cpv	epo:Purpose -> at-voc:cpvsuppl [0..*] epo:Purpose -> at-voc:cpv [1..*]
epo:hasMaximumFrameworkAgreementAwardedValue	The maximum value which can be spent through all the framework agreements announced in this notice, including options and renewals of contracts. Additional information: The value provided is a threshold value that implicity means that it cannot be exceeded however it may not be reached during the execution of a contract. The Framework Agreements in a CAN are to be traced back and added to provide this value. This corresponds to the BT-118 in eForms. WG Approval 03/12/2019	epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]
epo:hasMember		epo:OrganisationGroup -> org:Organization [1..*]
epo:hasModficationJustification	Additional Information This corresponds in Standard forms to Field VII.2.2.1 and VII.2.2.3 in F20 . This corresponds in eForms to BT-200. Explanation of why a contract was modified. WG Approval 09/11/2021 The codelist to be used is at-voc:modification-justification which is available at http://publications.europa.eu/resource/dataset/modification-justification	epo:ElementModificationDescription -> at-voc:modification-justification [1]
epo:hasNationality	The codelist to be used is at-voc:country which is available at http://publications.europa.eu/resource/dataset/country	cpv:Person -> at-voc:country [0..*]
epo:hasNonAwardJustification	On hold; Enumeration. The codelist to be used is at-voc:non-award-justification which is available at http://publications.europa.eu/resource/dataset/non-award-justification	epo:LotAwardOutcome -> at-voc:non-award-justification [0..1]
epo:hasNonElectronicSubmissionJustification	Reason for not accepting electronic information. WG Approval 21/07/2020 The codelist to be used is at-voc:communication-justification which is available at http://publications.europa.eu/resource/dataset/communication-justification	epo:SubmissionTerm -> at-voc:communication-justification [0..*]
epo:hasNonPublicationJustification	The reason why data is not published. WG Approval 11/06/2020 The codelist to be used is at-voc:non-publication-justification which is available at http://publications.europa.eu/resource/dataset/non-publication-justification	epo:ElementConfidentialityDescription -> at-voc:non-publication-justification [1]
epo:hasNoticeType		epo:Notice -> at-voc:notice-type [1]
epo:hasNotificationContentType	A categorisation of templates for sets of Procurement information to be conveyed in Notices. WG Approval 12/05/2020	epo:Notice -> at-voc-new:notification-phases-content-types [0..1]
epo:hasNutsCode	The codelist to be used is at-voc:nuts which is available at http://publications.europa.eu/resource/dataset/nuts The codelist to be used is at-voc:nuts which is available at http://publications.europa.eu/resource/dataset/nuts	dct:Location -> at-voc:nuts [0..1] locn:Address -> at-voc:nuts [0..1]
epo:hasOfficialLanguage	The language(s) in which the instances of the given concepts are officially available. These linguistic versions are equally legally valid. WG Approval 03/10/2019 The codelist to be used is at-voc:language which is available at http://publications.europa.eu/resource/dataset/language	epo:Document -> at-voc:language [1..*]
epo:hasOverallMaximumValue	Establishes the maximum value for the Framework Agreement, either for the lots specified in the Framework Agreement Lots or for all the lots of the procedure.	epo:FrameworkAgreementTerm -> epo:MonetaryValue [0..1]
epo:hasPaymentValue	Additional Information: This corresponds to BT-779 in eForms.	epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1]
epo:hasPenaltyValue	Additional Information: This corresponds to BT-782 in eForms.	epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1]
epo:hasPerformingStaffQualificationInformation	Explanation as to if and/or when information of the persons to carry out the contract is to be provided. WG Approval 09/11/2021 The codelist to be used is at-voc:requirement-stage which is available at http://publications.europa.eu/resource/dataset/requirement-stage	epo:Lot -> at-voc:requirement-stage [0..*]
epo:hasPlannedDuration		epo:PlannedProcurementPart -> epo:Duration [0..1]
epo:hasPlannedPeriod		epo:PlannedProcurementPart -> epo:Period [0..1]
epo:hasPrimaryContactPoint		org:Organization -> cpov:ContactPoint [0..*]
epo:hasPrizeValue	The monetary value of a prize, if any, for the winner (or runners-up) of the design contest. Additional Information: This corresponds to BT-644 in eForms. WG Approval 29/08/2019	epo:Prize -> epo:MonetaryValue [0..1]
epo:hasProcedureType	Identification of the Procedure used. WG Approval 09/06/2020 The codelist to be used is at-voc:procurement-procedure-type which is available at http://publications.europa.eu/resource/dataset/procurement-procedure-type	epo:Procedure -> at-voc:procurement-procedure-type [1]
epo:hasProcurementHighestReceivedTenderValue	The highest received tender value for the procurement. Additional Information: This corresponds to section II.1.7.3. according to Regulation (EU) 2015/1986.	epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]
epo:hasProcurementLowestReceivedTenderValue	The lowest received tender value for the procurement. Additional Information: This corresponds to section II.1.7.2. according to Regulation (EU) 2015/1986.	epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]
epo:hasProcurementScopeDividedIntoLot		epo:Procedure -> epo:Lot [1..*]
epo:hasPurpose	Relation indicating a procurement part has a puropse.	epo:ProcurementObject -> epo:Purpose [0..1]
epo:hasQualificationSystemDuration		epo:MultipleStageProcedureTerm -> epo:Duration [0..1]
epo:hasQualificationSystemPeriod		epo:MultipleStageProcedureTerm -> epo:Period [0..1]
epo:hasReceivedSubmissionType		epo:SubmissionStatisticalInformation -> at-voc:received-submission-type [0..1]
epo:hasRemedyValue	Additional information: This relation corresponds in eForms to BT-793 Review Remedy Value.	epo:ReviewObject -> epo:MonetaryValue [0..1]
epo:hasReservedExecution	The execution of the contract is restricted to the framework of sheltered employment programmes. WG Approval 12/09/2019 The codelist to be used is at-voc:applicability which is available at http://publications.europa.eu/resource/dataset/applicability	epo:ContractTerm -> at-voc:applicability [1]
epo:hasReservedProcurement	Explanation as to whether a procurement may be reserved for the participation of certain types of organisation. The codelist to be used is at-voc:reserved-procurement which is available at http://publications.europa.eu/resource/dataset/reserved-procurement WG Approval 09/11/2021 Explanation as to whether a procurement may be reserved for the participation of certain types of organisation. WG Approval 09/11/2021 The codelist to be used is at-voc:reserved-procurement which is available at http://publications.europa.eu/resource/dataset/reserved-procurement	epo:Lot -> at-voc:reserved-procurement [0..*]
epo:hasRestatedAwardedValue		epo:LotAwardOutcome -> epo:MonetaryValue [0..1]
epo:hasRestatedEstimatedValue	A forecast of the value of the procurement before competition, which is repeated in the contract award notice. Additional Information: This property should be equivalent to the epo:hasEstimatedValue. It is created, however because the existent data model two different fields (with the same conceptual meaning) and therefore the values may differ. This property is required by the regulation (EU)-2015-1986 (modeled in the TED Standard Forms). WG Approval 23/08/2022	epo:Lot -> epo:MonetaryValue [0..1]
epo:hasReviewDecisionType	Additional information: This relation corresponds in eForms to BT-790 Review Decision Type.	epo:ReviewDecision -> at-voc:review-decision-type [0..*]
epo:hasReviewIrregularitySummary	Additional information: This relation corresponds in eForms to BG-613 Buyer Review Requests	epo:ReviewRequestSummary -> epo:ReviewIrregularitySummary [0..*]
epo:hasSelectionCriteriaUsage	Additional Information: This corresponds in eForms to BT-748 Selection Criteria Used.	epo:SelectionCriterion -> at-voc:usage [0..1]
epo:hasSelectionCriterionType	The classification of the selection criteria. Additional Information: This corresponds in eForms to BT-747 Selection Criteria Type. The codelist to be used is at-voc:selection-criterion which is available at http://publications.europa.eu/resource/dataset/selection-criterion WG Approval 09/11/2021	epo:SelectionCriterion -> at-voc:selection-criterion [0..1]
epo:hasSubcontractingEstimatedValue	The estimated value of a single subcontract. This relates to BT-553 in eForms. WG Approval 01/09/2020	epo:SubcontractingEstimate -> epo:MonetaryValue [0..1]
epo:hasSubcontractingObligation	The requirement the tender must meet with regard to subcontracting parts of the contract. WG Approval 09/11/2021 The codelist to be used is at-voc:subcontracting-obligation which is available at http://publications.europa.eu/resource/dataset/subcontracting-obligation	epo:SubcontractTerm -> at-voc:subcontracting-obligation [0..*]
epo:hasTenderSubcontractingInformation	The information about subcontracting that must be indicated in the tender. WG Approval 10/10/2019 The codelist to be used is at-voc:subcontracting-indication which is available at http://publications.europa.eu/resource/dataset/subcontracting-indication	epo:SubmissionTerm -> at-voc:subcontracting-indication [0..*]
epo:hasThresholdType	The method to interpret the threshold value as minimum or a maximum. WG Approval 17/09/2019 The codelist to be used is at-voc:number-threshold which is available at http://publications.europa.eu/resource/dataset/number-threshold	cccev:Constraint -> at-voc:number-threshold [0..*]
epo:hasTimePeriod	The codelist to be used is at-voc:timeperiods which is available at http://publications.europa.eu/resource/dataset/timeperiod	epo:Period -> at-voc:timeperiod [1..*]
epo:hasTotalAwardedValue	The awarded value of all lots announced in this notice, including options and renewals. Additional information: The values of the individual Lots awarded under a framework agreement and mentioned in this notice are included. The values of the individual lots announced in a CAN are to be traced back and added to provide this value. This corresponds to the BT-161 in eForms. WG Approval 03/12/2019	epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]
epo:hasTotalQuantity	The number of units required. Additional Information: The quantity needs to go along with the unit.	epo:Purpose -> epo:Quantity [0..1]
epo:hasTotalValue		epo:TenderGroup -> epo:MonetaryValue [1]
epo:hasUnitCode		epo:Quantity -> at-voc:measurement-unit [1]
epo:hasUnofficialLanguage	The language translation(s) in which the instances of the given concepts are available. These linguistic versions are not an official translation, they are provided only for information. WG Approval 03/10/2019 The codelist to be used is at-voc:language which is available at http://publications.europa.eu/resource/dataset/language	epo:Document -> at-voc:language [0..*]
epo:hasUsage	The codelist to be used is at-voc:usage which is available at http://publications.europa.eu/resource/dataset/usage	epo:TechniqueUsage -> at-voc:usage [0..1]
epo:hasUUID	A universally unique identifier for an instance of this document. WG Approval 12/05/2020	epo:Document -> epo:Identifier [0..1]
epo:hasValidityPeriod	The property indicating when the ItemCertificate is in force. WG approval 26/07/2022	epo:SubmissionTerm -> epo:Period [0..1] epo:TechniqueUsage -> epo:Period [0..1]
epo:hasVariantPermission	The obligation or possibility for tenderers to submit variants or not. Additional Information: Variants are alternative ways to fulfil the buyer's needs as opposed to solutions indicated in the procurement documents. eForms: Whether tenderers are required, allowed or forbidden to submit tenders which fulfil the buyer's needs differently than as proposed in the procurement documents. Additional Information: Further conditions for submitting variant tenders are in the procurement documents. The codelist to be used is at-voc:permission which is available at http://publications.europa.eu/resource/dataset/permission	epo:SubmissionTerm -> at-voc:permission [0..1]
epo:hasWeightValueType	No definition. Waiting on CCCEV alignment. The codelist to be used is at-voc:number-weight which is available at http://publications.europa.eu/resource/dataset/number-weight	epo:ProcurementCriterion -> at-voc:number-weight [0..1]
epo:includesAccessibilityCriterion	Explanation as to whether accessibility Criterion are used or not. WG Approval 09/11/2021 The code list to be used is at:voc:accessibility which is available at http://publications.europa.eu/resource/dataset/accessibility	epo:StrategicProcurement -> at-voc:accessibility [0..*]
epo:includesLot		epo:Contract -> epo:Lot [1..*]
epo:includesTender	Additional information: This corresponds in eForms to BT-3202 Contract Tender Identifier.	epo:Contract -> epo:Tender [0..*]
epo:indicatesAwardOfLotToWinner	Reveals the winner to whom the tender award outcome is attributed.	epo:TenderAwardOutcome -> epo:Winner [0..1]
epo:involvesBuyer		epo:Procedure -> epo:Buyer [0..*]
epo:involvesProcurementDocument		epo:AccessTerm -> epo:ProcurementDocument [1]
epo:isAdoptedByBuyer		epo:LotAwardOutcome -> epo:Buyer [0..1]
epo:isBasedOnImplementingRegulation	Indicates under which regulation a notice is created. WG Acceptance 06/09/2022	epo:Notice -> at-voc:legal-basis [0..1]
epo:isBeneficialOwnerOf	A role of any natural person(s) who ultimately owns or controls the organisation or on whose behalf a transaction or activity is being conducted. Additional Information: This role is defined in the directive EU 2015/849 and it's beyond the scope for public eProcurement domain. WG approval 14/09/2021	epo:Business [,0..*] <- cpv:Person
epo:isExecutedByProcurementServiceProvider		epo:Procedure -> epo:ProcurementServiceProvider [0..1]
epo:isFundedBy	Additional information: This corresponds in eForms to BG - 61 EU Funds (specified per Lot) and to BG - 611 Contract EU Funds (applied per Contract lot) Funds may change between the lot and the contract, for example in the case of an emergency crisis, a contract may be financed by a budget that was not foreseen in the call.	epo:ProcurementObject -> epo:Fund [0..*]
epo:isOwnedByAgent		epo:System -> foaf:Agent [0..1]
epo:isResponsibilityOfBuyer	The buyer in charge of the procedure. Additional Information: In case there are multiple buyers, it may be the case that one or more buyers are in charge of the procedure.	epo:Procedure -> epo:Buyer [0..*]
epo:isSubjectToGrouping		epo:Tender -> epo:LotGroup [0..1]
epo:isSubjectToLotSpecificTerm		epo:Lot -> epo:LotSpecificTerm [0..*]
epo:isSubjectToProcedureSpecificTerm		epo:Procedure -> epo:ProcedureSpecificTerm [1..*]
epo:isSubjectToTerm		epo:ProcurementObject -> epo:Term [0..*]
epo:isSubmitedBy	Relation indicating the submission of a tender by an economic operator. WG approval 18/05/2021	epo:Tender -> epo:Tenderer [0..1]
epo:isSubmittedForLot		epo:Tender -> epo:Lot [1]
epo:isSubmittedForLotGroup		epo:TenderGroup -> epo:LotGroup [1]
epo:leadBy		epo:OrganisationGroup -> org:Organization [0..1]
epo:ownsSystem		epo:System [,0..*] <- foaf:Agent
epo:paidReviewRequestFee	Additional information: This relation corresponds in eForms to BT-795 Review Request Fee.	epo:ReviewRequest -> epo:MonetaryValue [0..1]
epo:playedBy		epo:AgentInRole -> foaf:Agent [1]
epo:playedByBusiness		epo:OfferingParty -> epo:Business [1]
epo:providesRulingOnRemedy	States the measures to be taken after a review procedure.	epo:ReviewDecision -> at-voc:remedy-type [0..*]
epo:refersToContract		epo:ContractLotCompletionInformation -> epo:Contract [1]
epo:refersToNotice		epo:Notice -> epo:Notice [0..1]
epo:refersToOriginalNotice		epo:ContractModification -> epo:Notice [0..1]
epo:refersToPlannedPart		epo:AccessTerm -> epo:PlannedProcurementPart [0..*] epo:ProcurementObject -> epo:PlannedProcurementPart [0..1]
epo:refersToPrevious		epo:Document -> epo:Document [0..*]
epo:refersToPreviousNotice	Additional information: This corresponds in eForms to BT-758 Change Notice Version Identifier.	epo:NoticeChange -> epo:Notice [0..1]
epo:refersToPreviousProcedure	Reference to a previous procedure. Additional Information: In the case of Direct Award Terms, this property points to a previous Procedure justifying the use of Direct Award without a prior publication. This corresponds in the eForms to BT-1252 Direct Award Justification Previous Procedure Identifier	epo:DirectAwardTerm -> epo:Procedure [0..1]
epo:refersToPreviousProcedureLot	Reference to one or more Lots in a previous procedure. Additional Information: In the case of Direct Award Terms, this property points to a previous Procedure justifying the use of Direct Award without a prior publication. This corresponds in the eForms to BT-1252 Direct Award Justification Previous Procedure Identifier WG Approval 22/11/2019 14:33:55	epo:DirectAwardTerm -> epo:Lot [0..*]
epo:refersToPreviousReview	Additional information: This relation corresponds in eForms to BT-785 "Review Previous Identifier".	epo:ReviewObject -> epo:ReviewObject [0..1]
epo:refersToProcedure		epo:Notice -> epo:Procedure [1]
epo:requestsRemedyType	Additional information: This relation corresponds in eForms to BT-792 Review Remedy Type	epo:ReviewRequest -> at-voc:remedy-type [0..*]
epo:resolvesReviewRequest		epo:ReviewDecision -> epo:ReviewRequest [1]
epo:resultsFromLotAwardOutcome		epo:Contract -> epo:LotAwardOutcome [0..*]
epo:setsGroupingContextForLot		epo:LotGroup -> epo:Lot [1..*]
epo:signedByBuyer		epo:Contract -> epo:Buyer [0..*]
epo:signedByContractor		epo:Contract -> epo:Contractor [0..*]
epo:specifiesAwardCriterion		epo:LotGroup -> epo:AwardCriterion [0..*] epo:Lot -> epo:AwardCriterion [0..*]
epo:specifiesExclusionGround		epo:Procedure -> epo:ExclusionGround [0..*]
epo:specifiesSelectionCriteria		epo:LotGroup -> epo:SelectionCriterion [0..*]
epo:specifiesSelectionCriterion		epo:Lot -> epo:SelectionCriterion [0..*]
epo:specifiesSubcontractors		epo:Tender -> epo:Subcontractor [0..*]
epo:substantiatesExclusionGround		epo:Tenderer -> epo:ExclusionGround [0..1]
epo:summarisesInformationForLotAwardOutcome	Relates to Lot submission.	epo:SubmissionStatisticalInformation -> epo:LotAwardOutcome [1]
epo:usesChannel		epo:ProcurementObject -> cv:Channel [0..*]
epo:usesTechnique		epo:ProcurementObject -> epo:TechniqueUsage [0..*]
legal:registeredAddress	The registered address relationship links a Resource with the legally registered Address. Additional Information: It is the address to which formal communications can be sent, such as the postal address.	cpv:Person -> locn:Address [0..1]
locn:address		dct:Location -> locn:Address [0..1]
locn:addressID	A globally unique identifier for each instance of an Address. Additional Information: The concept of adding a globally unique identifier for each instance of an address is a crucial part of the INSPIRE data spec. A number of EU countries have already implemented an ID (a UUID) in their Address Register/gazetteer, among them Denmark. OASIS xAL also includes an address identifier. It is the address Identifier that allows an address to be represented in a format other than INSPIRE whilst remaining conformant to the Core Vocabulary. The INSPIRE method of representing addresses is very detailed, designed primarily for use in databases of addresses. Whilst data that is published in full conformance with the INSPIRE data structure can be made available using the Location Core Vocabulary the reverse is not true since the Core Vocabulary allows much greater flexibility. Many datasets that include address data as one piece of information about something else are likely to have that data in simpler formats. These might be tailored to the specific need of the dataset, follow a national norm, or make use of a standard like vCard. To provide maximum flexibility in the Core Vocabulary, whilst remaining interoperable with INSPIRE Address Guidelines (which EU Member States are obliged to use), the Location Core Vocabulary provides the extra property of full address and makes use of INSPIRE's addressID.	locn:Address -> epo:Identifier [0..1]
locn:geographicIdentifier	A URI that identifies the Location. Additional Information: GeoNames.org provides stable, widely recognised identifiers for more than 10 million geographical names that can be used as links to further information. For example, http://sws.geonames.org/593116/ identifies the Lithuanian capital Vilnius. Unfortunately these URIs cannot easily be automatically deduced since the URI scheme uses simple numeric codes. Finding a GeoNames identifier for a Location is almost always a manual process. Where such identifiers are known or can be found, however, it is recommended that they be used. Where the Location Class is used to identify a country, if the geonames URI is not known, the recommendation is to use DBpedia URIs of the form http://dbpedia.org/resource/ISO_3166-1:XX where XX is the ISO 3166 two character code for the country. The EU's Publication Office diverges from ISO 3166-1 and uses EL and UK for Greece and the United Kingdom respectively. DBpedia sticks to the ISO codes and so the correct URIs for these countries are: - http://dbpedia.org/resource/ISO_3166-1:GR - http://dbpedia.org/resource/ISO_3166-1:GB even when the geographic name is given as EL or UK. The use of a URIs has added advantages: - it can be used by automated systems to look up additional data (linked data); - a triple store may store only one copy of the URI, whereas if a string is used, a copy of that string is always stored for each and every person in the database. Thus, in large data sets, the saving on memory capacity and the improvement in transmission efficiency can be substantial.	dct:Location -> epo:Identifier [0..1]
locn:geometry		dct:Location -> locn:Geometry [0..1]
person:placeOfBirth	The Location where the Person was born.	cpv:Person -> dct:Location [0..1]
person:placeOfDeath	The Location where the Person died.	cpv:Person -> dct:Location [0..1]
time:unitType		epo:SpecificDuration -> time:TemporalUnit [1]