From bfd13bf637b5cef3867ac3dd7f26309571d9d815 Mon Sep 17 00:00:00 2001 From: github-actions Date: Mon, 24 Jun 2024 13:33:21 +0000 Subject: [PATCH] Adding convention report and glossary files --- glossary/ePO_combined_glossary.html | 781 +- glossary/ePO_core_glossary.html | 9219 +++++++++++------ .../ePO_core_convention_report.html | 8066 ++++++++++++-- 3 files changed, 13677 insertions(+), 4389 deletions(-) diff --git a/glossary/ePO_combined_glossary.html b/glossary/ePO_combined_glossary.html index 08654797..1267785d 100644 --- a/glossary/ePO_combined_glossary.html +++ b/glossary/ePO_combined_glossary.html @@ -2614,7 +2614,7 @@

Attributes (datatype rdf:PlainLiteral [0..*] - epo-ord:DeliveryAgreement
epo-ord:TaxInformation
cccev:Evidence
cccev:InformationConcept
cccev:Requirement
cpov:ContactPoint
cv:Channel
epo:AgentInRole
epo:Document
epo:ElectronicSignature
epo:Fund
epo:NonDisclosureAgreementTerm
epo:SecurityClearanceTerm
epo:SubcontractingEstimate
epo:SubcontractTerm
epo:System
epo:Technique
epo:LotGroup
epo:ProcurementElement
epo:TenderGroup
cccev:EvidenceTypeList
eli:LegalExpression
eli:LegalResource
epo-cat:Line
epo-cat:Item
epo-ful:TemperatureSpecification
epo-ful:TransportEquipment
epo-ful:ShipmentInformation
epo-sub:CertificateInformation
+ cccev:Evidence
cccev:InformationConcept
cccev:Requirement
cpov:ContactPoint
cv:Channel
epo:AgentInRole
epo:Document
epo:ElectronicSignature
epo:Fund
epo:NonDisclosureAgreementTerm
epo:SecurityClearanceTerm
epo:SubcontractingEstimate
epo:SubcontractTerm
epo:System
epo:Technique
epo:LotGroup
epo:ProcurementElement
epo:TenderGroup
epo-cat:Line
epo-cat:Item
epo-ord:DeliveryAgreement
epo-ord:TaxInformation
epo-ful:ShipmentInformation
epo-ful:TemperatureSpecification
epo-ful:TransportEquipment
cccev:EvidenceTypeList
eli:LegalExpression
eli:LegalResource
epo-sub:CertificateInformation
dct:description An account of the resource. @@ -2628,8 +2628,7 @@

Attributes (datatype Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. - WG Approval 30/05/2023 - An account of the resource. + WG Approval 30/05/2023 An account of the resource. Additional Information: Description may include but is not limited to: an abstract, a table of contents, a @@ -2659,7 +2658,8 @@

Attributes (datatype Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. - WG Approval 30/05/2023 An account of the resource. + WG Approval 30/05/2023 + An account of the resource. Additional Information: Description may include but is not limited to: an abstract, a table of contents, a @@ -2671,14 +2671,14 @@

Attributes (datatype Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. - WG Approval 30/05/2023 - An account of the resource. + WG Approval 30/05/2023 An account of the resource. Additional Information: Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. - WG Approval 30/05/2023 An account of the resource. + WG Approval 30/05/2023 + An account of the resource. Additional Information: Description may include but is not limited to: an abstract, a table of contents, a @@ -2690,8 +2690,7 @@

Attributes (datatype Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. - WG Approval 30/05/2023 - An account of the resource. + WG Approval 30/05/2023 An account of the resource. Additional Information: Description may include but is not limited to: an abstract, a table of contents, a @@ -2715,7 +2714,8 @@

Attributes (datatype Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. - WG Approval 30/05/2023 An account of the resource. + WG Approval 30/05/2023 + An account of the resource. Additional Information: Description may include but is not limited to: an abstract, a table of contents, a @@ -2740,8 +2740,7 @@

Attributes (datatype Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. - WG Approval 30/05/2023 - An account of the resource. + WG Approval 30/05/2023 An account of the resource. Additional Information: Description may include but is not limited to: an abstract, a table of contents, a @@ -2760,8 +2759,7 @@

Attributes (datatype Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. - WG Approval 30/05/2023 - An account of the resource. + WG Approval 30/05/2023 An account of the resource. Additional Information: Description may include but is not limited to: an abstract, a table of contents, a @@ -2785,13 +2783,15 @@

Attributes (datatype Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. - WG Approval 30/05/2023 An account of the resource. + WG Approval 30/05/2023 + An account of the resource. Additional Information: Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource. - WG Approval 30/05/2023 An account of the resource. + WG Approval 30/05/2023 + An account of the resource. Additional Information: Description may include but is not limited to: an abstract, a table of contents, a @@ -2799,7 +2799,7 @@

Attributes (datatype WG Approval 30/05/2023 - rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [1..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [1..1]
rdfs:Literal [0..*]
rdfs:Literal [1..1]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
+ rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [1..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [1..1]
rdfs:Literal [0..*]
rdfs:Literal [1..1]
rdf:PlainLiteral [0..1]
eli:LegalExpression
eli:LegalResource
@@ -2826,7 +2826,7 @@

Attributes (datatype xsd:dateTime [0..1] - epo:AgentInRole
epo:Document
epo:Fund
foaf:Agent
epo:LotGroup
epo:ProcurementElement
epo:TenderGroup
eli:LegalExpression
epo-cat:Brand
epo-cat:ItemModel
epo-cat:Item
+ epo:AgentInRole
epo:Document
epo:Fund
foaf:Agent
epo:LotGroup
epo:ProcurementElement
epo:TenderGroup
epo-cat:Brand
epo-cat:ItemModel
epo-cat:Item
eli:LegalExpression
dct:title A name given to the resource. @@ -2848,15 +2848,15 @@

Attributes (datatype WG approval 30/05/2023 A name given to the resource. WG approval 30/05/2023 - A name given to the resource. A name given to the resource. + A name given to the resource. WG approval 30/05/2023 A name given to the resource. WG approval 30/05/2023 A name given to the resource. - WG approval 30/05/2023 - rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdfs:Literal [1..*]
rdf:PlainLiteral [1..1]
rdf:PlainLiteral [1..1]
rdf:PlainLiteral [1..1]
+ WG approval 30/05/2023 A name given to the resource. + rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [1..1]
rdf:PlainLiteral [1..1]
rdf:PlainLiteral [1..1]
rdfs:Literal [1..*]
eli:LegalExpression
eli:LegalResource
@@ -5175,7 +5175,7 @@

Attributes (datatype rdf:PlainLiteral [0..1] - epo-ful:AbstractContainer
epo-ful:ShipmentStage
epo-ful:Consignment
+ epo-ful:AbstractContainer
epo-ful:Consignment
epo-ful:ShipmentStage
epo-ful:isHazardousRisk xsd:boolean [0..1]
xsd:boolean [0..1]
xsd:boolean [0..1]
@@ -5528,8 +5528,8 @@

Predicates (object p the service provider or any other stakeholder. WG Approval 12/11/2019 - Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. - cccev:Evidence -> adms:Identifier [1]
cccev:InformationConcept -> adms:Identifier [0..1]
cccev:Requirement -> adms:Identifier [0..1]
dct:Location -> adms:Identifier [0..1]
epo:Document -> adms:Identifier [0..*]
epo:Fund -> adms:Identifier [0..1]
epo:Project -> adms:Identifier [0..1]
foaf:Agent -> adms:Identifier [0..*]
epo:LotGroup -> adms:Identifier [0..1]
epo:ProcurementElement -> adms:Identifier [1]
epo:TenderGroup -> adms:Identifier [0..1]
cccev:EvidenceType -> adms:Identifier [0..1]
epo-ful:Consignment -> adms:Identifier [0..1]
epo-ful:TransportEquipment -> adms:Identifier [0..1]
epo-ful:ShipmentStage -> adms:Identifier [0..1]
epo-ful:TransportEquipmentSeal -> adms:Identifier [0..1]
cccev:EvidenceTypeList -> adms:Identifier [0..1]
epo-ful:ShipmentInformation -> adms:Identifier [0..1]
epo-cat:Line -> adms:Identifier [0..1]
epo-ful:AbstractContainer -> adms:Identifier [0..1]
cccev:EvidenceType -> adms:Identifier [0..1]
cccev:EvidenceTypeList -> adms:Identifier [0..1]
epo-cat:Line -> adms:Identifier [0..1]
epo-ful:AbstractContainer -> adms:Identifier [0..1]
epo-ful:TransportEquipmentSeal -> adms:Identifier [0..1]
epo-ful:ShipmentStage -> adms:Identifier [0..1]
epo-ful:TransportEquipment -> adms:Identifier [0..1]
epo-ful:Consignment -> adms:Identifier [0..1]
epo-ful:ShipmentInformation -> adms:Identifier [0..1]
+ Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. + cccev:Evidence -> adms:Identifier [1]
cccev:InformationConcept -> adms:Identifier [0..1]
cccev:Requirement -> adms:Identifier [0..1]
dct:Location -> adms:Identifier [0..1]
epo:Document -> adms:Identifier [0..*]
epo:Fund -> adms:Identifier [0..1]
epo:Project -> adms:Identifier [0..1]
foaf:Agent -> adms:Identifier [0..*]
epo:LotGroup -> adms:Identifier [0..1]
epo:ProcurementElement -> adms:Identifier [1]
epo:TenderGroup -> adms:Identifier [0..1]
cccev:EvidenceType -> adms:Identifier [0..1]
epo-ful:Consignment -> adms:Identifier [0..1]
epo-ful:TransportEquipment -> adms:Identifier [0..1]
epo-ful:ShipmentStage -> adms:Identifier [0..1]
epo-ful:TransportEquipmentSeal -> adms:Identifier [0..1]
cccev:EvidenceTypeList -> adms:Identifier [0..1]
epo-ful:ShipmentInformation -> adms:Identifier [0..1]
epo-cat:Line -> adms:Identifier [0..1]
epo-ful:AbstractContainer -> adms:Identifier [0..1]
cccev:confidentialityLevelType @@ -5543,14 +5543,9 @@

Predicates (object p Additional Information: - Classifications should be defined by an organisation/country as an outcome of a security - assessment. 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:access-rights [0..1]
epo-sub:Response -> at-voc:access-rights []
epo-sub:Response -> at-voc:access-rights []
+ cccev:Evidence -> at-voc:access-rights [0..1]
epo-sub:Response -> at-voc:access-rights []
cccev:constrains @@ -5578,14 +5573,10 @@

Predicates (object p cccev:hasEvidenceTypeList Evidence Type List that specifies the Evidence Types that are needed to meet the Requirement. - Additional Information: - One or several Lists of Evidence Types can support a Requirement. At least one of - them must be satisfied by the response to the Requirement. Evidence Type List that specifies the Evidence Types that are needed to meet the Requirement. - Additional Information: One or several Lists of Evidence Types can support a Requirement. At least one of them must be satisfied by the response to the Requirement. - cccev:Requirement -> cccev:EvidenceTypeList [0..*]
cccev:Requirement -> cccev:EvidenceTypeList [0..*]
+ cccev:Requirement -> cccev:EvidenceTypeList [0..*] cccev:hasRequirement @@ -5596,14 +5587,6 @@

Predicates (object p cccev:isDerivedFrom Reference Framework on which the Requirement is based, such as a law or regulation. - Additional Information: - The relation between a parent Requirement and a sub-Requirement can be complex. Therefore, - qualified relations (see hasQualifiedRelation) can be used to represent this relationship - on its own and qualify it with additional information such as a date, a place. This - is left to implementers. In the case where the purpose is to link the two Requirements - without additional information, the simple relationship as proposed here can be directly - used. Reference Framework on which the Requirement is based, such as a law or regulation. - Additional Information: The relation between a parent Requirement and a sub-Requirement can be complex. Therefore, qualified relations (see hasQualifiedRelation) can be used to represent this relationship @@ -5611,12 +5594,12 @@

Predicates (object p is left to implementers. In the case where the purpose is to link the two Requirements without additional information, the simple relationship as proposed here can be directly used. - cccev:Requirement -> eli:LegalResource []
cccev:Requirement -> eli:LegalResource []
+ cccev:Requirement -> eli:LegalResource [] cccev:providesValueFor - Information Concept for which the Supported Value provides a value. Information Concept for which the Supported Value provides a value. - cccev:SupportedValue -> cccev:InformationConcept [0..*]
cccev:SupportedValue -> cccev:InformationConcept [0..*]
+ Information Concept for which the Supported Value provides a value. + cccev:SupportedValue -> cccev:InformationConcept [0..*] cccev:specifiesEvidenceType @@ -5640,25 +5623,19 @@

Predicates (object p cccev:supportsValue - Supported Value that the Evidence contains. Supported Value that the Evidence contains. Supported Value that the Evidence contains. - cccev:Evidence -> cccev:SupportedValue [0..*]
epo-sub:Response -> cccev:SupportedValue [0..*]
cccev:Evidence -> cccev:SupportedValue [0..*]
+ Supported Value that the Evidence contains. Supported Value that the Evidence contains. + cccev:Evidence -> cccev:SupportedValue [0..*]
epo-sub:Response -> cccev:SupportedValue [0..*]
cccev:validityPeriodConstraint Temporal condition on the validity period of the Evidence Type. - Additional Information: - E.g. A Belgian birth evidence is valid for X months after emission. To express constraints - on the validity period that must hold when assessing the evidence (e.g. the certificate - of good conduct cannot be issued more than 3 months ago), we refer to the Constraint - class. Temporal condition on the validity period of the Evidence Type. - Additional Information: E.g. A Belgian birth evidence is valid for X months after emission. To express constraints on the validity period that must hold when assessing the evidence (e.g. the certificate of good conduct cannot be issued more than 3 months ago), we refer to the Constraint class. - cccev:EvidenceType -> epo:Period [0..*]
cccev:EvidenceType -> epo:Period [0..*]
+ cccev:EvidenceType -> epo:Period [0..*] cv:registeredAddress @@ -5676,12 +5653,9 @@

Predicates (object p dct:conformsTo An established standard to which the described resource conforms. - Additional Information: - Examples of characteristics could be the layout or the configuration of the Evidence. An established standard to which the described resource conforms. - Additional Information: Examples of characteristics could be the layout or the configuration of the Evidence. - cccev:Evidence -> cccev:EvidenceType [0..*]
cccev:Evidence -> cccev:EvidenceType [0..*]
+ cccev:Evidence -> cccev:EvidenceType [0..*] dct:hasPart @@ -5716,8 +5690,8 @@

Predicates (object p dct:language - A language of the resource. A language of the resource. - eli:LegalExpression -> at-voc:language [1..*]
eli:LegalExpression -> at-voc:language [1..*]
+ A language of the resource. + eli:LegalExpression -> at-voc:language [1..*] dct:replaces @@ -5778,95 +5752,89 @@

Predicates (object p in a registry. Schema describing the URI of an ELI instance. ELI uses URI template specifications (IETF RFC 6570). Schemes should be associated with member states and will be published - in a registry. - Schema describing the URI of an ELI instance. ELI uses URI template specifications - (IETF RFC 6570). Schemes should be associated with member states and will be published - in a registry. - Schema describing the URI of an ELI instance. ELI uses URI template specifications - (IETF RFC 6570). Schemes should be associated with member states and will be published in a registry. - eli:LegalResourceSubdivision -> adms:Identifier [0..*]
eli:LegalExpression -> adms:Identifier [0..*]
eli:LegalExpression -> adms:Identifier [0..*]
eli:LegalResourceSubdivision -> adms:Identifier [0..*]
+ eli:LegalResourceSubdivision -> adms:Identifier [0..*]
eli:LegalExpression -> adms:Identifier [0..*]
epo:actsOnBehalfOf - Represents. - epo:ProcurementServiceProvider -> epo:Buyer [1..*]
epo-sub:LegalRepresentative -> epo:OfferingParty [0..1]
epo-sub:LegalRepresentative -> epo:OfferingParty [0..1]
+ Represents. + epo:ProcurementServiceProvider -> epo:Buyer [1..*]
epo-sub:LegalRepresentative -> epo:OfferingParty [0..1]
epo:amendsContract - - epo-con:ContractAmendment -> epo:Contract [1]
epo-con:ContractAmendment -> epo:Contract [1]
+ + epo-con:ContractAmendment -> epo:Contract [1] epo:announcesAwardDecision - - epo-not:ResultNotice -> epo:AwardDecision [0..*]
epo-not:DirectAwardPrenotificationNotice -> epo:AwardDecision [0..*]
epo-not:DirectAwardPrenotificationNotice -> epo:AwardDecision [0..*]
epo-not:ResultNotice -> epo:AwardDecision [0..*]
+ + epo-not:ResultNotice -> epo:AwardDecision [0..*]
epo-not:DirectAwardPrenotificationNotice -> epo:AwardDecision [0..*]
epo:announcesCompletionOfContract - - epo-not:CompletionNotice -> epo:Contract [1]
epo-not:CompletionNotice -> epo:Contract [1]
+ + epo-not:CompletionNotice -> epo:Contract [1] epo:announcesContract - - epo-not:DirectAwardPrenotificationNotice -> epo:Contract [0..*]
epo-not:ResultNotice -> epo:Contract [0..*]
epo-not:DirectAwardPrenotificationNotice -> epo:Contract [0..*]
epo-not:ResultNotice -> epo:Contract [0..*]
+ + epo-not:DirectAwardPrenotificationNotice -> epo:Contract [0..*]
epo-not:ResultNotice -> epo:Contract [0..*]
epo:announcesContractAmendment - - epo-not:ContractModificationNotice -> epo-con:ContractAmendment [1]
epo-not:ContractModificationNotice -> epo-con:ContractAmendment [1]
+ + epo-not:ContractModificationNotice -> epo-con:ContractAmendment [1] epo:announcesLot - - epo-not:DirectAwardPrenotificationNotice -> epo:Lot [1..*]
epo-not:CompetitionNotice -> epo:Lot [1..*]
epo-not:CompetitionNotice -> epo:Lot [1..*]
epo-not:DirectAwardPrenotificationNotice -> epo:Lot [1..*]
+ + epo-not:DirectAwardPrenotificationNotice -> epo:Lot [1..*]
epo-not:CompetitionNotice -> epo:Lot [1..*]
epo:announcesLotGroup - - epo-not:CompetitionNotice -> epo:LotGroup [0..*]
epo-not:DirectAwardPrenotificationNotice -> epo:LotGroup [0..*]
epo-not:CompetitionNotice -> epo:LotGroup [0..*]
epo-not:DirectAwardPrenotificationNotice -> epo:LotGroup [0..*]
+ + epo-not:CompetitionNotice -> epo:LotGroup [0..*]
epo-not:DirectAwardPrenotificationNotice -> epo:LotGroup [0..*]
epo:announcesLotGroupAwardInformation - - epo-not:DirectAwardPrenotificationNotice -> epo:LotGroupAwardInformation [0..*]
epo-not:ResultNotice -> epo:LotGroupAwardInformation [0..*]
epo-not:DirectAwardPrenotificationNotice -> epo:LotGroupAwardInformation [0..*]
epo-not:ResultNotice -> epo:LotGroupAwardInformation [0..*]
+ + epo-not:DirectAwardPrenotificationNotice -> epo:LotGroupAwardInformation [0..*]
epo-not:ResultNotice -> epo:LotGroupAwardInformation [0..*]
epo:announcesNoticeAwardInformation - - epo-not:DirectAwardPrenotificationNotice -> epo:NoticeAwardInformation [0..1]
epo-not:ResultNotice -> epo:NoticeAwardInformation [0..1]
epo-not:DirectAwardPrenotificationNotice -> epo:NoticeAwardInformation [0..1]
epo-not:ResultNotice -> epo:NoticeAwardInformation [0..1]
+ + epo-not:DirectAwardPrenotificationNotice -> epo:NoticeAwardInformation [0..1]
epo-not:ResultNotice -> epo:NoticeAwardInformation [0..1]
epo:announcesPlannedProcurementPart - - epo-not:PlanningNotice -> epo:PlannedProcurementPart [0..*]
epo-not:PlanningNotice -> epo:PlannedProcurementPart [0..*]
+ + epo-not:PlanningNotice -> epo:PlannedProcurementPart [0..*] epo:announcesProcedure - - epo-not:DirectAwardPrenotificationNotice -> epo:Procedure [1]
epo-not:CompetitionNotice -> epo:Procedure [1]
epo-not:CompetitionNotice -> epo:Procedure [1]
epo-not:DirectAwardPrenotificationNotice -> epo:Procedure [1]
+ + epo-not:DirectAwardPrenotificationNotice -> epo:Procedure [1]
epo-not:CompetitionNotice -> epo:Procedure [1]
epo:announcesReviewObject - - epo-not:CompletionNotice -> epo:ReviewObject [1..*]
epo-not:CompletionNotice -> epo:ReviewObject [1..*]
+ + epo-not:CompletionNotice -> epo:ReviewObject [1..*] epo:announcesRole - - epo-not:DirectAwardPrenotificationNotice -> epo:AgentInRole [1..*]
epo-not:ContractModificationNotice -> epo:AgentInRole [0..*]
epo-not:PlanningNotice -> epo:AgentInRole [1..*]
epo-not:CompetitionNotice -> epo:AgentInRole [1..*]
epo-not:CompletionNotice -> epo:AgentInRole [0..*]
epo-not:CompetitionNotice -> epo:AgentInRole [1..*]
epo-not:CompletionNotice -> epo:AgentInRole [0..*]
epo-not:ContractModificationNotice -> epo:AgentInRole [0..*]
epo-not:DirectAwardPrenotificationNotice -> epo:AgentInRole [1..*]
epo-not:PlanningNotice -> epo:AgentInRole [1..*]
+ + epo-not:DirectAwardPrenotificationNotice -> epo:AgentInRole [1..*]
epo-not:ContractModificationNotice -> epo:AgentInRole [0..*]
epo-not:PlanningNotice -> epo:AgentInRole [1..*]
epo-not:CompetitionNotice -> epo:AgentInRole [1..*]
epo-not:CompletionNotice -> epo:AgentInRole [0..*]
epo:answersExclusionGround - - epo-sub:ESPDResponse -> epo:ExclusionGround [1]
epo-sub:ESPDResponse -> epo:ExclusionGround [1]
+ + epo-sub:ESPDResponse -> epo:ExclusionGround [1] epo:answersSelectionCriteria - - epo-sub:ESPDResponse -> epo:SelectionCriterion [1]
epo-sub:ESPDResponse -> epo:SelectionCriterion [1]
+ + epo-sub:ESPDResponse -> epo:SelectionCriterion [1] epo:associatedWith @@ -5949,12 +5917,9 @@

Predicates (object p epo:concernsProcedure Relates to Procedure. Relates to Procedure. - WG approval 05/03/2024 - Relates to Procedure. - WG approval 05/03/2024 - epo:ProcurementProcessInformation -> epo:Procedure [0..1]
epo-acc:ESPDRequest -> epo:Procedure [1]
epo-acc:ESPDRequest -> epo:Procedure [1]
+ epo:ProcurementProcessInformation -> epo:Procedure [0..1]
epo-acc:ESPDRequest -> epo:Procedure [1]
epo:concernsReviewSummaryForLot @@ -6116,8 +6081,8 @@

Predicates (object p epo:describesDirectAwardPrenotificationNotice - - epo:NoticeAwardInformation -> epo-not:DirectAwardPrenotificationNotice [0..1]
epo:NoticeAwardInformation -> epo-not:DirectAwardPrenotificationNotice [0..1]
+ + epo:NoticeAwardInformation -> epo-not:DirectAwardPrenotificationNotice [0..1] epo:describesLotCompletion @@ -6131,8 +6096,8 @@

Predicates (object p epo:describesResultNotice - - epo:NoticeAwardInformation -> epo-not:ResultNotice [0..1]
epo:NoticeAwardInformation -> epo-not:ResultNotice [0..1]
+ + epo:NoticeAwardInformation -> epo-not:ResultNotice [0..1] epo:distributesOffer @@ -6291,11 +6256,9 @@

Predicates (object p epo:hasBatchID The identifier assigned to a specific batch of the produced Item. - WG Approval 16/05/2023 - The identifier assigned to a specific batch of the produced Item. WG Approval 16/05/2023 - epo-cat:Batch -> adms:Identifier [0..1]
epo-cat:Batch -> adms:Identifier [0..1]
+ epo-cat:Batch -> adms:Identifier [0..1] epo:hasBeneficialOwner @@ -6337,12 +6300,9 @@

Predicates (object p epo:hasBuyerItemID The general identifier assigned to the concept as defined by the Buyer.​ - WG approval 16/05/2023 - The general identifier assigned to the concept as defined by the Buyer.​ - WG approval 16/05/2023 - epo-cat:Item -> adms:Identifier [0..1]
epo-cat:Item -> adms:Identifier [0..1]
+ epo-cat:Item -> adms:Identifier [0..1] epo:hasBuyerLegalType @@ -6364,10 +6324,8 @@

Predicates (object p WG approval 30/05/2023 Relation to the proof of conformance. - WG approval 30/05/2023 Relation to the proof of conformance. - WG approval 30/05/2023 - foaf:Person -> epo:Certificate [0..*]
org:Organization -> epo:Certificate [0..*]
epo-cat:Item -> epo:Certificate [0..*]
epo-cat:Item -> epo:Certificate [0..*]
+ foaf:Person -> epo:Certificate [0..*]
org:Organization -> epo:Certificate [0..*]
epo-cat:Item -> epo:Certificate [0..*]
epo:hasChangeJustification @@ -6459,8 +6417,8 @@

Predicates (object p epo:hasDocumentStatus - https://test-docs.peppol.eu/logistics/transport-execution/codelist/DocumentStatusCode/ https://test-docs.peppol.eu/logistics/transport-execution/codelist/DocumentStatusCode/ - epo-cat:PostAwardDocument -> at-voc-new:document-status [0..1]
epo-cat:PostAwardDocument -> at-voc-new:document-status [0..1]
+ https://test-docs.peppol.eu/logistics/transport-execution/codelist/DocumentStatusCode/ + epo-cat:PostAwardDocument -> at-voc-new:document-status [0..1] epo:hasDPSScope @@ -6673,7 +6631,7 @@

Predicates (object p epo:hasImplementingRegulation - epo-not:eFormsNotice -> (EU) 2019/1780 [0..1]
epo-not:StandardFormsNotice -> (EU) 2015/1986 [0..1]
+ epo-not:StandardFormsNotice -> (EU) 2015/1986 [0..1]
epo-not:eFormsNotice -> (EU) 2019/1780 [0..1]
epo:hasInternalIdentifier @@ -6708,13 +6666,8 @@

Predicates (object p Additional information: For example the GTIN scheme (Global Trade Item Number). - WG approval 16/05/2023 The general identifier assigned to the concept based on a standard scheme.​ - - Additional information: - For example the GTIN scheme (Global Trade Item Number). - WG approval 16/05/2023 - epo-cat:Item -> adms:Identifier [0..*]
epo-cat:Item -> adms:Identifier [0..*]
+ epo-cat:Item -> adms:Identifier [0..*] epo:hasLabelType @@ -6767,7 +6720,7 @@

Predicates (object p The codelist to be used is at-voc:legal-basis which is available at http://publications.europa.eu/resource/dataset/legal-basis - epo:ProcurementObject -> at-voc:legal-basis [0..*]
epo-not:VEAT-D81 -> Directive 81 [0..1]
epo-not:PINProfile-D81 -> Directive 81 [0..1]
epo-not:Notice6 -> Directive 81 [0..1]
epo-not:PINDefence-D81 -> Directive 81 [0..1]
epo-not:Subcontract-D81 -> Directive 81 [0..1]
epo-not:Notice27 -> Directive 81 [0..1]
epo-not:Notice22 -> Directive 81 [0..1]
epo-not:CNDefence-D81 -> Directive 81 [0..1]
epo-not:Notice18 -> Directive 81 [0..1]
epo-not:CANDefence-D81 -> Directive 81 [0..1]
epo-not:Notice3 -> Directive 81 [0..1]
epo-not:Notice9 -> Directive 81 [0..1]
epo-not:Notice31 -> Directive 81 [0..1]
epo-not:Modification-D25 -> Directive 25 [0..1]
epo-not:Notice26 -> Directive 25 [0..1]
epo-not:CNSocial-D25 -> Directive 25 [0..1]
epo-not:PIN-CFCSocial-D25 -> Directive 25 [0..1]
epo-not:PINOnly-D25 -> Directive 25 [0..1]
epo-not:Notice2 -> Directive 25 [0..1]
epo-not:PINProfile-D25 -> Directive 25 [0..1]
epo-not:PIN-RTL-D25 -> Directive 25 [0..1]
epo-not:Notice37 -> Directive 25 [0..1]
epo-not:VEAT-D25 -> Directive 25 [0..1]
epo-not:CANSocialNotice-D25 -> Directive 25 [0..1]
epo-not:QSNotice-D25 -> Directive 25 [0..1]
epo-not:QS-D25 -> Directive 25 [0..1]
epo-not:DesignContestResult-D25 -> Directive 25 [0..1]
epo-not:CNSocialNotice-D25 -> Directive 25 [0..1]
epo-not:Notice34 -> Directive 25 [0..1]
epo-not:Notice24 -> Directive 25 [0..1]
epo-not:CANSocial-D25 -> Directive 25 [0..1]
epo-not:Notice30 -> Directive 25 [0..1]
epo-not:Notice8 -> Directive 25 [0..1]
epo-not:Notice13 -> Directive 25 [0..1]
epo-not:Notice5 -> Directive 25 [0..1]
epo-not:Notice39 -> Directive 25 [0..1]
epo-not:Notice21 -> Directive 25 [0..1]
epo-not:Notice15 -> Directive 25 [0..1]
epo-not:Notice17 -> Directive 25 [0..1]
epo-not:DesignContest-D25 -> Directive 25 [0..1]
epo-not:Notice11 -> Directive 25 [0..1]
epo-not:PIN-CFCSocialNotice-D25 -> Directive 25 [0..1]
epo-not:Notice10 -> Directive 24 [0..1]
epo-not:SocialAndOtherSpecificServices-D24 -> Directive 24 [0..1]
epo-not:VEAT-D24 -> Directive 24 [0..1]
epo-not:PINOnly-D24 -> Directive 24 [0..1]
epo-not:Notice25 -> Directive 24 [0..1]
epo-not:Notice23 -> Directive 24 [0..1]
epo-not:CNStandard-D24 -> Directive 24 [0..1]
epo-not:PIN-CFCStandard-D24 -> Directive 24 [0..1]
epo-not:Notice29 -> Directive 24 [0..1]
epo-not:Notice38 -> Directive 24 [0..1]
epo-not:Notice36 -> Directive 24 [0..1]
epo-not:Notice1 -> Directive 24 [0..1]
epo-not:DesignContestResult-D24 -> Directive 24 [0..1]
epo-not:Notice33 -> Directive 24 [0..1]
epo-not:CANStandard-D24 -> Directive 24 [0..1]
epo-not:DesignContest-D24 -> Directive 24 [0..1]
epo-not:PIN-RTL-D24 -> Directive 24 [0..1]
epo-not:Notice20 -> Directive 24 [0..1]
epo-not:PINProfile-D24 -> Directive 24 [0..1]
epo-not:Notice12 -> Directive 24 [0..1]
epo-not:Notice4 -> Directive 24 [0..1]
epo-not:Notice16 -> Directive 24 [0..1]
epo-not:Notice7 -> Directive 24 [0..1]
epo-not:VEAT-D23 -> Directive 23 [0..1]
epo-not:Notice35 -> Directive 23 [0..1]
epo-not:Modification-D23 -> Directive 23 [0..1]
epo-not:Notice32 -> Directive 23 [0..1]
epo-not:Notice19 -> Directive 23 [0..1]
epo-not:ConcessionNotice-D23 -> Directive 23 [0..1]
epo-not:ConcessionAwardNotice-D23 -> Directive 23 [0..1]
epo-not:Notice40 -> Directive 23 [0..1]
epo-not:Notice28 -> Directive 23 [0..1]
epo-not:SocialAndOtherSpecificServices-D23 -> Directive 23 [0..1]
epo-not:Notice14 -> Directive 23 [0..1]
+ epo:ProcurementObject -> at-voc:legal-basis [0..*]
epo-not:VEAT-D23 -> Directive 23 [0..1]
epo-not:Notice35 -> Directive 23 [0..1]
epo-not:Modification-D23 -> Directive 23 [0..1]
epo-not:Notice32 -> Directive 23 [0..1]
epo-not:Notice19 -> Directive 23 [0..1]
epo-not:ConcessionNotice-D23 -> Directive 23 [0..1]
epo-not:ConcessionAwardNotice-D23 -> Directive 23 [0..1]
epo-not:Notice40 -> Directive 23 [0..1]
epo-not:Notice28 -> Directive 23 [0..1]
epo-not:SocialAndOtherSpecificServices-D23 -> Directive 23 [0..1]
epo-not:Notice14 -> Directive 23 [0..1]
epo-not:Notice10 -> Directive 24 [0..1]
epo-not:SocialAndOtherSpecificServices-D24 -> Directive 24 [0..1]
epo-not:VEAT-D24 -> Directive 24 [0..1]
epo-not:PINOnly-D24 -> Directive 24 [0..1]
epo-not:Notice25 -> Directive 24 [0..1]
epo-not:Notice23 -> Directive 24 [0..1]
epo-not:CNStandard-D24 -> Directive 24 [0..1]
epo-not:PIN-CFCStandard-D24 -> Directive 24 [0..1]
epo-not:Notice29 -> Directive 24 [0..1]
epo-not:Notice38 -> Directive 24 [0..1]
epo-not:Notice36 -> Directive 24 [0..1]
epo-not:Notice1 -> Directive 24 [0..1]
epo-not:DesignContestResult-D24 -> Directive 24 [0..1]
epo-not:Notice33 -> Directive 24 [0..1]
epo-not:CANStandard-D24 -> Directive 24 [0..1]
epo-not:DesignContest-D24 -> Directive 24 [0..1]
epo-not:PIN-RTL-D24 -> Directive 24 [0..1]
epo-not:Notice20 -> Directive 24 [0..1]
epo-not:PINProfile-D24 -> Directive 24 [0..1]
epo-not:Notice12 -> Directive 24 [0..1]
epo-not:Notice4 -> Directive 24 [0..1]
epo-not:Notice16 -> Directive 24 [0..1]
epo-not:Notice7 -> Directive 24 [0..1]
epo-not:Modification-D25 -> Directive 25 [0..1]
epo-not:Notice26 -> Directive 25 [0..1]
epo-not:CNSocial-D25 -> Directive 25 [0..1]
epo-not:PIN-CFCSocial-D25 -> Directive 25 [0..1]
epo-not:PINOnly-D25 -> Directive 25 [0..1]
epo-not:Notice2 -> Directive 25 [0..1]
epo-not:PINProfile-D25 -> Directive 25 [0..1]
epo-not:PIN-RTL-D25 -> Directive 25 [0..1]
epo-not:Notice37 -> Directive 25 [0..1]
epo-not:VEAT-D25 -> Directive 25 [0..1]
epo-not:CANSocialNotice-D25 -> Directive 25 [0..1]
epo-not:QSNotice-D25 -> Directive 25 [0..1]
epo-not:QS-D25 -> Directive 25 [0..1]
epo-not:DesignContestResult-D25 -> Directive 25 [0..1]
epo-not:CNSocialNotice-D25 -> Directive 25 [0..1]
epo-not:Notice34 -> Directive 25 [0..1]
epo-not:Notice24 -> Directive 25 [0..1]
epo-not:CANSocial-D25 -> Directive 25 [0..1]
epo-not:Notice30 -> Directive 25 [0..1]
epo-not:Notice8 -> Directive 25 [0..1]
epo-not:Notice13 -> Directive 25 [0..1]
epo-not:Notice5 -> Directive 25 [0..1]
epo-not:Notice39 -> Directive 25 [0..1]
epo-not:Notice21 -> Directive 25 [0..1]
epo-not:Notice15 -> Directive 25 [0..1]
epo-not:Notice17 -> Directive 25 [0..1]
epo-not:DesignContest-D25 -> Directive 25 [0..1]
epo-not:Notice11 -> Directive 25 [0..1]
epo-not:PIN-CFCSocialNotice-D25 -> Directive 25 [0..1]
epo-not:VEAT-D81 -> Directive 81 [0..1]
epo-not:PINProfile-D81 -> Directive 81 [0..1]
epo-not:Notice6 -> Directive 81 [0..1]
epo-not:PINDefence-D81 -> Directive 81 [0..1]
epo-not:Subcontract-D81 -> Directive 81 [0..1]
epo-not:Notice27 -> Directive 81 [0..1]
epo-not:Notice22 -> Directive 81 [0..1]
epo-not:CNDefence-D81 -> Directive 81 [0..1]
epo-not:Notice18 -> Directive 81 [0..1]
epo-not:CANDefence-D81 -> Directive 81 [0..1]
epo-not:Notice3 -> Directive 81 [0..1]
epo-not:Notice9 -> Directive 81 [0..1]
epo-not:Notice31 -> Directive 81 [0..1]
epo:hasLegalIdentifier @@ -6818,20 +6771,16 @@

Predicates (object p epo:hasManufacturerID The manufacturer's identifier for the item. - The manufacturer's identifier for the item. - epo-cat:Manufacturer -> adms:Identifier [0..1]
epo-cat:Manufacturer -> adms:Identifier [0..1]
+ epo-cat:Manufacturer -> adms:Identifier [0..1] epo:hasManufacturerItemID The general identifier assigned to the concept as defined by the Manufacturer. ​ - WG approval 16/05/2023 - The general identifier assigned to the concept as defined by the Manufacturer. ​ - WG approval 16/05/2023 - epo-cat:Item -> adms:Identifier [0..1]
epo-cat:Item -> adms:Identifier [0..1]
+ epo-cat:Item -> adms:Identifier [0..1] epo:hasMaximumFrameworkAgreementAwardedValue @@ -6869,25 +6818,11 @@

Predicates (object p 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 - - 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. - epo-con:ContractModificationInformation -> at-voc:modification-justification [1]
epo-con:ContractModificationInformation -> at-voc:modification-justification [1]
+ epo-con:ContractModificationInformation -> at-voc:modification-justification [1] epo:hasNationality @@ -7036,8 +6971,8 @@

Predicates (object p epo:hasRejectedQuantity - - epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
+ + epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1] epo:hasRemedyValue @@ -7119,21 +7054,16 @@

Predicates (object p epo:hasSellerItemID The general identifier assigned to the concept as defined by the Seller.​ - WG approval 16/05/2023 - The general identifier assigned to the concept as defined by the Seller.​ - WG approval 16/05/2023 - epo-cat:Item -> adms:Identifier [0..1]
epo-cat:Item -> adms:Identifier [0..1]
+ epo-cat:Item -> adms:Identifier [0..1] epo:hasSerialID The identifier assigned to the specific instance of the produced concept. - WG Approval 16/05/2023 - The identifier assigned to the specific instance of the produced concept. WG Approval 16/05/2023 - epo-cat:Item -> adms:Identifier [0..1]
epo-cat:Item -> adms:Identifier [0..1]
+ epo-cat:Item -> adms:Identifier [0..1] epo:hasStartDate @@ -7241,8 +7171,8 @@

Predicates (object p epo:hasTotalValue - - epo-con:Deliverable -> epo:MonetaryValue [0..1]
epo:TenderGroup -> epo:MonetaryValue [0..1]
epo-con:Deliverable -> epo:MonetaryValue [0..1]
+ + epo:TenderGroup -> epo:MonetaryValue [0..1]
epo-con:Deliverable -> epo:MonetaryValue [0..1]
epo:hasUnitCode @@ -7271,12 +7201,9 @@

Predicates (object p WG Approval 12/05/2020 A universally unique identifier for an instance of this document. - WG Approval 12/05/2020 - A universally unique identifier for an instance of this document. - WG Approval 12/05/2020 - epo:Document -> adms:Identifier [0..1]
epo-cat:CatalogueResponseLine -> adms:Identifier [1]
epo-cat:CatalogueResponseLine -> adms:Identifier [1]
+ epo:Document -> adms:Identifier [0..1]
epo-cat:CatalogueResponseLine -> adms:Identifier [1]
epo:hasValidityPeriod @@ -7287,10 +7214,8 @@

Predicates (object p WG approval 30/05/2023 The relation indicating until when a given instance of a concept is applicable. - WG approval 30/05/2023 The relation indicating until when a given instance of a concept is applicable. - WG approval 30/05/2023 - cccev:Evidence -> epo:Period [0..1]
epo:Technique -> epo:Period [0..1]
epo-cat:Catalogue -> epo:Period [0..1]
epo-cat:Catalogue -> epo:Period [0..1]
+ cccev:Evidence -> epo:Period [0..1]
epo:Technique -> epo:Period [0..1]
epo-cat:Catalogue -> epo:Period [0..1]
epo:hasVariantPermission @@ -7389,15 +7314,11 @@

Predicates (object p epo:isCalculatedOn The monetary amount to which the multiplier factor is applied in calculating the amount - of this allowance or charge. - - The monetary amount to which the multiplier factor is applied in calculating the amount - of this allowance or charge. The monetary amount to which the multiplier factor is applied in calculating the amount of this allowance or charge. The monetary amount to which the multiplier factor is applied in calculating the amount of this allowance or charge. - epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [0..1]
epo-ord:TaxInformation -> epo:MonetaryValue [0..1]
epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [0..1]
epo-ord:TaxInformation -> epo:MonetaryValue [0..1]
+ epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [0..1]
epo-ord:TaxInformation -> epo:MonetaryValue [0..1]
epo:isExecutedByProcurementServiceProvider @@ -7494,8 +7415,8 @@

Predicates (object p epo:isSupportedBy - - epo:Tender -> epo-sub:ESPDResponse [1]
epo:Tender -> epo-sub:ESPDResponse [1]
+ + epo:Tender -> epo-sub:ESPDResponse [1] epo:leadBy @@ -7521,8 +7442,8 @@

Predicates (object p epo:playedBy - - epo:AgentInRole -> foaf:Agent [1]
epo:JuryMember -> person:Person [0..1]
epo-ful:TransportMeansOperator -> foaf:Person [0..1]
epo-ful:TransportMeansOperator -> foaf:Person [0..1]
+ + epo:AgentInRole -> foaf:Agent [1]
epo:JuryMember -> person:Person [0..1]
epo-ful:TransportMeansOperator -> foaf:Person [0..1]
epo:providesContractTotalPaymentValue @@ -7545,8 +7466,8 @@

Predicates (object p epo:refersToAwardDecision - - epo-not:CompletionNotice -> epo:AwardDecision [0..*]
epo-not:ContractModificationNotice -> epo:AwardDecision [0..*]
epo-not:CompletionNotice -> epo:AwardDecision [0..*]
epo-not:ContractModificationNotice -> epo:AwardDecision [0..*]
+ + epo-not:CompletionNotice -> epo:AwardDecision [0..*]
epo-not:ContractModificationNotice -> epo:AwardDecision [0..*]
epo:refersToContract @@ -7555,23 +7476,23 @@

Predicates (object p epo:refersToContractToBeModified - - epo-not:ContractModificationNotice -> epo:Contract [1]
epo-not:ContractModificationNotice -> epo:Contract [1]
+ + epo-not:ContractModificationNotice -> epo:Contract [1] epo:refersToLot - - epo:Notice -> epo:Lot [1..*]
epo-not:CompletionNotice -> epo:Lot [1..*]
epo-not:ContractModificationNotice -> epo:Lot [1..*]
epo-not:ResultNotice -> epo:Lot [1..*]
epo-not:CompletionNotice -> epo:Lot [1..*]
epo-not:ContractModificationNotice -> epo:Lot [1..*]
epo-not:ResultNotice -> epo:Lot [1..*]
+ + epo:Notice -> epo:Lot [1..*]
epo-not:CompletionNotice -> epo:Lot [1..*]
epo-not:ContractModificationNotice -> epo:Lot [1..*]
epo-not:ResultNotice -> epo:Lot [1..*]
epo:refersToLotGroup - - epo-not:ContractModificationNotice -> epo:LotGroup [0..*]
epo-not:ResultNotice -> epo:LotGroup [0..*]
epo-not:CompletionNotice -> epo:LotGroup [0..*]
epo-not:CompletionNotice -> epo:LotGroup [0..*]
epo-not:ContractModificationNotice -> epo:LotGroup [0..*]
epo-not:ResultNotice -> epo:LotGroup [0..*]
+ + epo-not:ContractModificationNotice -> epo:LotGroup [0..*]
epo-not:ResultNotice -> epo:LotGroup [0..*]
epo-not:CompletionNotice -> epo:LotGroup [0..*]
epo:refersToLotGroupAwardInformation - - epo-not:CompletionNotice -> epo:LotGroupAwardInformation [0..*]
epo-not:ContractModificationNotice -> epo:LotGroupAwardInformation [0..*]
epo-not:CompletionNotice -> epo:LotGroupAwardInformation [0..*]
epo-not:ContractModificationNotice -> epo:LotGroupAwardInformation [0..*]
+ + epo-not:CompletionNotice -> epo:LotGroupAwardInformation [0..*]
epo-not:ContractModificationNotice -> epo:LotGroupAwardInformation [0..*]
epo:refersToNotice @@ -7580,8 +7501,8 @@

Predicates (object p epo:refersToNoticeAwardInformation - - epo-not:ContractModificationNotice -> epo:NoticeAwardInformation [0..1]
epo-not:CompletionNotice -> epo:NoticeAwardInformation [0..1]
epo-not:CompletionNotice -> epo:NoticeAwardInformation [0..1]
epo-not:ContractModificationNotice -> epo:NoticeAwardInformation [0..1]
+ + epo-not:ContractModificationNotice -> epo:NoticeAwardInformation [0..1]
epo-not:CompletionNotice -> epo:NoticeAwardInformation [0..1]
epo:refersToPlannedPart @@ -7634,23 +7555,23 @@

Predicates (object p epo:refersToProcedure - - epo:Notice -> epo:Procedure [1]
epo-not:ResultNotice -> epo:Procedure [1]
epo-not:ContractModificationNotice -> epo:Procedure [1]
epo-not:CompletionNotice -> epo:Procedure [1]
epo-not:CompletionNotice -> epo:Procedure [1]
epo-not:ContractModificationNotice -> epo:Procedure [1]
epo-not:ResultNotice -> epo:Procedure [1]
+ + epo:Notice -> epo:Procedure [1]
epo-not:ResultNotice -> epo:Procedure [1]
epo-not:ContractModificationNotice -> epo:Procedure [1]
epo-not:CompletionNotice -> epo:Procedure [1]
epo:refersToProject - - epo-ord:Order -> epo:Project [0..1]
epo-ord:Order -> epo:Project [0..1]
+ + epo-ord:Order -> epo:Project [0..1] epo:refersToRole - - epo-not:CompletionNotice -> epo:AgentInRole [0..*]
epo-not:CompletionNotice -> epo:AgentInRole [0..*]
+ + epo-not:CompletionNotice -> epo:AgentInRole [0..*] epo:relatesToEFormSectionIdentifier - - epo-con:ContractModificationInformation -> adms:Identifier [0..1]
epo:ChangeInformation -> adms:Identifier [1..*]
epo:NonPublishedInformation -> adms:Identifier [1..*]
epo-con:ContractModificationInformation -> adms:Identifier [0..1]
+ + epo:ChangeInformation -> adms:Identifier [1..*]
epo:NonPublishedInformation -> adms:Identifier [1..*]
epo-con:ContractModificationInformation -> adms:Identifier [0..1]
epo:requestsRemedyType @@ -7700,8 +7621,8 @@

Predicates (object p epo:specifiesBuyer - - epo-ord:Order -> epo:Buyer [1]
epo-cat:Catalogue -> epo:Buyer [0..*]
epo-ord:Order -> epo:Buyer [1]
epo-cat:Catalogue -> epo:Buyer [0..*]
+ + epo-cat:Catalogue -> epo:Buyer [0..*]
epo-ord:Order -> epo:Buyer [1]
epo:specifiesCarrier @@ -7710,13 +7631,13 @@

Predicates (object p epo:specifiesCatalogueProvider - - epo-cat:Catalogue -> epo:CatalogueProvider [0..1]
epo-cat:CatalogueResponse -> epo:CatalogueProvider [1]
epo-cat:Catalogue -> epo:CatalogueProvider [0..1]
epo-cat:CatalogueResponse -> epo:CatalogueProvider [1]
+ + epo-cat:Catalogue -> epo:CatalogueProvider [0..1]
epo-cat:CatalogueResponse -> epo:CatalogueProvider [1]
epo:specifiesCatalogueReceiver - - epo-cat:Catalogue -> epo:CatalogueReceiver [0..1]
epo-cat:CatalogueResponse -> epo:CatalogueReceiver [1]
epo-cat:Catalogue -> epo:CatalogueReceiver [0..1]
epo-cat:CatalogueResponse -> epo:CatalogueReceiver [1]
+ + epo-cat:Catalogue -> epo:CatalogueReceiver [0..1]
epo-cat:CatalogueResponse -> epo:CatalogueReceiver [1]
epo:specifiesCleanVehicleDirectiveContractType @@ -7730,13 +7651,13 @@

Predicates (object p epo:specifiesDeliverable - - epo:Contract -> epo-con:Deliverable [0..*]
epo:Contract -> epo-con:Deliverable [0..*]
+ + epo:Contract -> epo-con:Deliverable [0..*] epo:specifiesDespatcher - - epo-ord:Order -> epo-ful:Despatcher [0..1]
epo-ord:Order -> epo-ful:Despatcher [0..1]
+ + epo-ord:Order -> epo-ful:Despatcher [0..1] epo:specifiesFreightForwarder @@ -7755,13 +7676,13 @@

Predicates (object p epo:specifiesProcurementCriterion - - epo-acc:ESPDRequest -> epo:ProcurementCriterion [1..*]
epo:Lot -> epo:ProcurementCriterion [0..*]
epo:LotGroup -> epo:ProcurementCriterion [0..*]
epo-acc:ESPDRequest -> epo:ProcurementCriterion [1..*]
+ + epo-acc:ESPDRequest -> epo:ProcurementCriterion [1..*]
epo:Lot -> epo:ProcurementCriterion [0..*]
epo:LotGroup -> epo:ProcurementCriterion [0..*]
epo:specifiesSeller - - epo-ord:Order -> epo-ord:Seller [1]
epo-cat:Catalogue -> epo-ord:Seller [0..*]
epo-cat:Catalogue -> epo-ord:Seller [0..*]
+ + epo-cat:Catalogue -> epo-ord:Seller [0..*]
epo-ord:Order -> epo-ord:Seller [1]
epo:specifiesSubcontractors @@ -7783,8 +7704,8 @@

Predicates (object p epo:updatesContractValue - - epo-con:ContractAmendment -> epo:MonetaryValue [0..1]
epo-con:ContractAmendment -> epo:MonetaryValue [0..1]
+ + epo-con:ContractAmendment -> epo:MonetaryValue [0..1] epo:usesChannel @@ -7800,10 +7721,8 @@

Predicates (object p epo-acc:refersToNotice Reference to a Notice. - WG approval 12/03/2024 Reference to a Notice. - WG approval 12/03/2024 - epo-acc:ESPDRequest -> epo:Notice [0..*]
epo-acc:ESPDRequest -> epo:Notice [0..*]
+ epo-acc:ESPDRequest -> epo:Notice [0..*] epo-cat:comprisesCatalogueLine @@ -7822,8 +7741,8 @@

Predicates (object p epo-cat:foreseesPackage - - epo-cat:CatalogueLine -> epo-ful:Package [0..1]
epo-cat:CatalogueLine -> epo-ful:Package [0..1]
+ + epo-cat:CatalogueLine -> epo-ful:Package [0..1] epo-cat:hasAccessoryItem @@ -7846,21 +7765,15 @@

Predicates (object p WG approval 26/07/2022 The predetermined monetary value charged in addition to the price. - WG approval 26/07/2022 - - The predetermined monetary value charged in addition to the price. - - WG approval 26/07/2022 The predetermined monetary value charged in addition to the price. - WG approval 26/07/2022 - epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [1]
epo-ord:TaxInformation -> epo:MonetaryValue [0..1]
epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [1]
epo-ord:TaxInformation -> epo:MonetaryValue [0..1]
+ epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [1]
epo-ord:TaxInformation -> epo:MonetaryValue [0..1]
epo-cat:hasBaseQuantity - The quantity at which the net monetary value applies. The quantity at which the net monetary value applies. - epo-cat:Price -> epo:Quantity [0..1]
epo-cat:Price -> epo:Quantity [0..1]
+ The quantity at which the net monetary value applies. + epo-cat:Price -> epo:Quantity [0..1] epo-cat:hasBrand @@ -7871,10 +7784,8 @@

Predicates (object p epo-cat:hasCatalogueLineValidity The relation indicating until when a Catalogue Line instance is applicable. - WG approval 21/09/2023 The relation indicating until when a Catalogue Line instance is applicable. - WG approval 21/09/2023 - epo-cat:CatalogueLine -> epo:Period [0..1]
epo-cat:CatalogueLine -> epo:Period [0..1]
+ epo-cat:CatalogueLine -> epo:Period [0..1] epo-cat:hasChargeInformation @@ -7902,17 +7813,9 @@

Predicates (object p 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 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 - epo-cat:Item -> at-voc:country [0..1]
epo-cat:Item -> at-voc:country [0..1]
+ epo-cat:Item -> at-voc:country [0..1] epo-cat:hasDeliveryClassification @@ -7922,9 +7825,8 @@

Predicates (object p epo-cat:hasDeliveryLocation Location delivery area where the Item can be ordered to the given price. - Location delivery area where the Item can be ordered to the given price. - epo-cat:Price -> dct:Location [0..1]
epo-cat:Price -> dct:Location [0..1]
+ epo-cat:Price -> dct:Location [0..1] epo-cat:hasDocumentType @@ -7935,19 +7837,15 @@

Predicates (object p epo-cat:hasExpectedDeliveryTime The expected amount of time between the order and delivery of an item. - WG approval 26/07/2022 - The expected amount of time between the order and delivery of an item. - WG approval 26/07/2022 - epo-cat:Price -> epo:Duration [0..1]
epo-cat:Price -> epo:Duration [0..1]
+ epo-cat:Price -> epo:Duration [0..1] epo-cat:hasExternalSpecification URI reference to external item information or specifications, e.g. web address. - URI reference to external item information or specifications, e.g. web address. - epo-cat:Item -> epo:Document []
epo-cat:Item -> epo:Document []
+ epo-cat:Item -> epo:Document [] epo-cat:hasHazardousItemUNDGCode @@ -7975,20 +7873,16 @@

Predicates (object p epo-cat:hasMaximumOrderQuantity The maximum number of orderable units that can be ordered according to details provided - in the catalogue line, such as price. - The maximum number of orderable units that can be ordered according to details provided in the catalogue line, such as price. - epo-cat:CatalogueLine -> epo:Quantity [0..1]
epo-cat:CatalogueLine -> epo:Quantity [0..1]
+ epo-cat:CatalogueLine -> epo:Quantity [0..1] epo-cat:hasMinimumQuantityGuaranteedForDelivery The minimum quantity of an item that is guaranteed by the seller to be delivered. - The minimum quantity of an item that is guaranteed by the seller to be delivered. - - epo-cat:CatalogueLine -> epo:Quantity [0..1]
epo-cat:CatalogueLine -> epo:Quantity [0..1]
+ epo-cat:CatalogueLine -> epo:Quantity [0..1] epo-cat:hasModel @@ -7998,31 +7892,20 @@

Predicates (object p epo-cat:hasNetMonetaryValue The price amount of an Item exclusive of taxes and after substracting price discounts. - The price amount of an Item exclusive of taxes and after substracting price discounts. - epo-cat:Price -> epo:MonetaryValue [1]
epo-cat:Price -> epo:MonetaryValue [1]
+ epo-cat:Price -> epo:MonetaryValue [1] epo-cat:hasNetQuantity The net quantity of the item that is contained in each consumable unit, excluding - any packaging materials. - The net quantity of the item that is contained in each consumable unit, excluding any packaging materials. - epo-cat:Item -> epo:Quantity [0..1]
epo-cat:Item -> epo:Quantity [0..1]
+ epo-cat:Item -> epo:Quantity [0..1] epo-cat:hasOrderabableUnitFactorRate The factor by which the base unit of the price can be converted to orderable unit. - Additional information: - This is needed when the base price is provided different than the orderable unit. - For example, when selling paper, the price may be set per page, but the orderable - unit is a package of 500 pieces. Therefore the price needs to be converted to the - orderable unit. - - The factor by which the base unit of the price can be converted to orderable unit. - Additional information: This is needed when the base price is provided different than the orderable unit. For example, when selling paper, the price may be set per page, but the orderable @@ -8030,7 +7913,7 @@

Predicates (object p orderable unit. - epo-cat:Price -> epo:Quantity [0..1]
epo-cat:Price -> epo:Quantity [0..1]
+ epo-cat:Price -> epo:Quantity [0..1] epo-cat:hasOrderableUnit @@ -8039,8 +7922,8 @@

Predicates (object p epo-cat:hasPrice - - epo-ord:OrderLine -> epo-cat:Price [0..1]
epo-ord:OrderLine -> epo-cat:Price [0..1]
epo-cat:CatalogueLine -> epo-cat:Price [1..*]
+ + epo-ord:OrderLine -> epo-cat:Price [0..1]
epo-cat:CatalogueLine -> epo-cat:Price [1..*]
epo-cat:hasPriceType @@ -8050,9 +7933,8 @@

Predicates (object p epo-cat:hasPriceValidity The period of time when the Item can be ordered to the given price. - The period of time when the Item can be ordered to the given price. - epo-cat:Price -> epo:Period [1]
epo-cat:Price -> epo:Period [1]
+ epo-cat:Price -> epo:Period [1] epo-cat:hasQualifiedItemRelation @@ -8067,24 +7949,18 @@

Predicates (object p For example, the (0173-1#02-AAA026#007) drilling diameter of an item has value of 12 inches. - WG approval 28/07/2022 Qualified value of the property, which is defined in a classification scheme. - - Additional Information: - For example, the (0173-1#02-AAA026#007) drilling diameter of an item has value of - 12 inches. - WG approval 28/07/2022 - epo-cat:ItemProperty -> epo:Quantity [0..1]
epo-cat:ItemProperty -> epo:Quantity [0..1]
+ epo-cat:ItemProperty -> epo:Quantity [0..1] epo-cat:hasQuantity - - epo-con:Deliverable -> epo:Quantity [0..1]
epo-ord:OrderLine -> epo:Quantity [1]
epo-ord:OrderLine -> epo:Quantity [1]
epo-con:Deliverable -> epo:Quantity [0..1]
+ + epo-ord:OrderLine -> epo:Quantity [1]
epo-con:Deliverable -> epo:Quantity [0..1]
epo-cat:hasQuantityThreshold - The minimum quantity of the item that can be ordered to the given net monetary value. The minimum quantity of the item that can be ordered to the given net monetary value. - epo-cat:Price -> epo:Quantity [0..1]
epo-cat:Price -> epo:Quantity [0..1]
+ The minimum quantity of the item that can be ordered to the given net monetary value. + epo-cat:Price -> epo:Quantity [0..1] epo-cat:hasSpecification @@ -8101,13 +7977,13 @@

Predicates (object p epo-cat:hasTaxCategory - - epo-ord:TaxInformation -> at-voc-new:tax-category [0..1]
epo-ord:TaxInformation -> at-voc-new:tax-category [0..1]
+ + epo-ord:TaxInformation -> at-voc-new:tax-category [0..1] epo-cat:hasTaxScheme - - epo-ord:TaxInformation -> at-voc-new:tax-scheme [0..1]
epo-ord:TaxInformation -> at-voc-new:tax-scheme [0..1]
+ + epo-ord:TaxInformation -> at-voc-new:tax-scheme [0..1] epo-cat:hasTransactionConditionsCode @@ -8138,8 +8014,8 @@

Predicates (object p epo-cat:isSubordinatedToContract - - epo-cat:Catalogue -> epo:Contract [0..1]
epo-cat:Catalogue -> epo:Contract [0..1]
+ + epo-cat:Catalogue -> epo:Contract [0..1] epo-cat:refersToCatalogue @@ -8158,8 +8034,8 @@

Predicates (object p epo-cat:specifiesChargeInformation - - epo-ord:Order -> epo-cat:ChargeInformation [0..*]
epo-ord:Order -> epo-cat:ChargeInformation [0..*]
+ + epo-ord:Order -> epo-cat:ChargeInformation [0..*] epo-cat:specifiesItem @@ -8168,13 +8044,13 @@

Predicates (object p epo-ful:agreedByBuyer - - epo-ful:ShipmentAgreement -> epo:Buyer [1..*]
epo-ful:ShipmentAgreement -> epo:Buyer [1..*]
+ + epo-ful:ShipmentAgreement -> epo:Buyer [1..*] epo-ful:agreedBySeller - - epo-ful:ShipmentAgreement -> epo-ord:Seller [1..*]
epo-ful:ShipmentAgreement -> epo-ord:Seller [1..*]
+ + epo-ful:ShipmentAgreement -> epo-ord:Seller [1..*] epo-ful:comprisesDespatchLine @@ -8205,40 +8081,38 @@

Predicates (object p epo-ful:hasAllowanceChargeReason https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL5189/ - https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL7161/ https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL5189/ - https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL7161/ - epo-ord:AllowanceChargeInformation -> at-voc-new:allowance-charge-reason [0..1]
epo-ord:AllowanceChargeInformation -> at-voc-new:allowance-charge-reason [0..1]
+ epo-ord:AllowanceChargeInformation -> at-voc-new:allowance-charge-reason [0..1] epo-ful:hasAssociatedDocument - - epo-ful:ReceiptAdvice -> epo:Document [0..1]
epo-ful:DespatchAdvice -> epo:Document [0..1]
epo-ful:DespatchLine -> epo:Document [0..1]
epo-ful:DespatchLine -> epo:Document [0..1]
epo-ful:DespatchAdvice -> epo:Document [0..1]
epo-ful:ReceiptAdvice -> epo:Document [0..1]
+ + epo-ful:ReceiptAdvice -> epo:Document [0..1]
epo-ful:DespatchAdvice -> epo:Document [0..1]
epo-ful:DespatchLine -> epo:Document [0..1]
epo-ful:hasCarrierConsignmentID - - epo-ful:Consignment -> adms:Identifier [0..1]
epo-ful:Consignment -> adms:Identifier [0..1]
+ + epo-ful:Consignment -> adms:Identifier [0..1] epo-ful:hasChargeableWeight - - epo-ful:Consignment -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
+ + epo-ful:Consignment -> epo:Quantity [0..1] epo-ful:hasConsigneeConsignmentID - - epo-ful:Consignment -> adms:Identifier [0..1]
epo-ful:Consignment -> adms:Identifier [0..1]
+ + epo-ful:Consignment -> adms:Identifier [0..1] epo-ful:hasConsignmentDeclaredStatisticsValue - - epo-ful:Consignment -> epo:MonetaryValue [0..1]
epo-ful:Consignment -> epo:MonetaryValue [0..1]
+ + epo-ful:Consignment -> epo:MonetaryValue [0..1] epo-ful:hasConsignmentFreeOnBoardValue - - epo-ful:Consignment -> epo:MonetaryValue [0..1]
epo-ful:Consignment -> epo:MonetaryValue [0..1]
+ + epo-ful:Consignment -> epo:MonetaryValue [0..1] epo-ful:hasConsignmentInvoiceValue @@ -8246,19 +8120,14 @@

Predicates (object p Additional Information: - This is a logistics information needed for logistics, security measures, customs check, - etc. Declared amount of the Consignment. - - Additional Information: - This is a logistics information needed for logistics, security measures, customs check, etc. - epo-ful:Consignment -> epo:MonetaryValue [0..1]
epo-ful:Consignment -> epo:MonetaryValue [0..1]
+ epo-ful:Consignment -> epo:MonetaryValue [0..1] epo-ful:hasDeclaredStatisticalValue - - epo-ful:GoodsItem -> epo:MonetaryValue [0..*]
epo-ful:GoodsItem -> epo:MonetaryValue [0..*]
+ + epo-ful:GoodsItem -> epo:MonetaryValue [0..*] epo-ful:hasDepartureShipmentInformation @@ -8273,33 +8142,33 @@

Predicates (object p epo-ful:hasDespatchedQuantity - Quantity despatched for delivered. Quantity despatched for delivered. - epo-ful:DespatchLine -> epo:Quantity [1]
epo-ful:DespatchLine -> epo:Quantity [1]
+ Quantity despatched for delivered. + epo-ful:DespatchLine -> epo:Quantity [1] epo-ful:hasEstimatedDeliveryPeriod - - epo-ful:ShipmentInformation -> epo:Period [0..1]
epo-ful:ShipmentInformation -> epo:Period [0..1]
+ + epo-ful:ShipmentInformation -> epo:Period [0..1] epo-ful:hasFreightAllowanceCharge - - epo-ful:Consignment -> epo-cat:ChargeInformation [0..*]
epo-ful:Consignment -> epo-cat:ChargeInformation [0..*]
+ + epo-ful:Consignment -> epo-cat:ChargeInformation [0..*] epo-ful:hasFreightForwarderConsignmentID - - epo-ful:Consignment -> adms:Identifier [0..1]
epo-ful:Consignment -> adms:Identifier [0..1]
+ + epo-ful:Consignment -> adms:Identifier [0..1] epo-ful:hasGrossVolume - - epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
+ + epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
epo-ful:hasGrossWeight - - epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
+ + epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
epo-ful:hasHandlingInstructionCode @@ -8308,18 +8177,18 @@

Predicates (object p epo-ful:hasHeight - - epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:AbstractContainer -> epo:Quantity [0..1]
+ + epo-ful:AbstractContainer -> epo:Quantity [0..1] epo-ful:hasLength - - epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:AbstractContainer -> epo:Quantity [0..1]
+ + epo-ful:AbstractContainer -> epo:Quantity [0..1] epo-ful:hasLoadingLength - - epo-ful:Consignment -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
+ + epo-ful:Consignment -> epo:Quantity [0..1] epo-ful:hasMainCarriageShipmentStage @@ -8328,23 +8197,23 @@

Predicates (object p epo-ful:hasMaximumTemperature - - epo-ful:TemperatureSpecification -> epo:Quantity [0..1]
epo-ful:TemperatureSpecification -> epo:Quantity [0..1]
+ + epo-ful:TemperatureSpecification -> epo:Quantity [0..1] epo-ful:hasMinimumTemperature - - epo-ful:TemperatureSpecification -> epo:Quantity [0..1]
epo-ful:TemperatureSpecification -> epo:Quantity [0..1]
+ + epo-ful:TemperatureSpecification -> epo:Quantity [0..1] epo-ful:hasNetVolume - - epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:AbstractContainer -> epo:Quantity [0..1]
+ + epo-ful:AbstractContainer -> epo:Quantity [0..1] epo-ful:hasNetWeight - - epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
+ + epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
epo-ful:hasOnCarriageShipmentStage @@ -8353,13 +8222,13 @@

Predicates (object p epo-ful:hasOutstandingQuantity - - epo-ful:DespatchLine -> epo:Quantity [0..1]
epo-ful:DespatchLine -> epo:Quantity [0..1]
+ + epo-ful:DespatchLine -> epo:Quantity [0..1] epo-ful:hasOversupplyQuantity - - epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
+ + epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1] epo-ful:hasPackagingType @@ -8373,8 +8242,8 @@

Predicates (object p epo-ful:hasReceivedQuantity - - epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
+ + epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1] epo-ful:hasRejectReason @@ -8393,8 +8262,8 @@

Predicates (object p epo-ful:hasShortQuantity - - epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
+ + epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1] epo-ful:hasSizeType @@ -8408,8 +8277,8 @@

Predicates (object p epo-ful:hasTotalGoodsItemQuantity - - epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
+ + epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
epo-ful:hasTraceID @@ -8418,20 +8287,14 @@

Predicates (object p Additional information: An example is the EPC number used in RFID. - WG approval 21/09/2023 - The identifier used for tracking the goods item - - Additional information: - An example is the EPC number used in RFID. - WG approval 21/09/2023 - epo-ful:GoodsItem -> adms:Identifier [0..1]
epo-ful:GoodsItem -> adms:Identifier [0..1]
+ epo-ful:GoodsItem -> adms:Identifier [0..1] epo-ful:hasTrackingID - - epo-ord:DeliveryInformation -> adms:Identifier [0..1]
epo-ord:DeliveryInformation -> adms:Identifier [0..1]
+ + epo-ord:DeliveryInformation -> adms:Identifier [0..1] epo-ful:hasTransportEquipmentSeal @@ -8445,8 +8308,8 @@

Predicates (object p epo-ful:hasTransportHandlingUnitQuantity - - epo-ful:Consignment -> epo:Quantity [0..1]
epo-ful:Consignment -> epo:Quantity [0..1]
+ + epo-ful:Consignment -> epo:Quantity [0..1] epo-ful:hasTransportMeansType @@ -8460,18 +8323,18 @@

Predicates (object p epo-ful:hasVehicleID - - epo-ful:TransportMeans -> adms:Identifier [1]
epo-ful:TransportMeans -> adms:Identifier [1]
+ + epo-ful:TransportMeans -> adms:Identifier [1] epo-ful:hasVehicleSegmentID - - epo-ful:TransportMeans -> adms:Identifier [0..1]
epo-ful:TransportMeans -> adms:Identifier [0..1]
+ + epo-ful:TransportMeans -> adms:Identifier [0..1] epo-ful:hasWidth - - epo-ful:AbstractContainer -> epo:Quantity [0..1]
epo-ful:AbstractContainer -> epo:Quantity [0..1]
+ + epo-ful:AbstractContainer -> epo:Quantity [0..1] epo-ful:isSpecificToDespatchLine @@ -8502,8 +8365,8 @@

Predicates (object p epo-ful:refersToDeliveryInformation - - epo-ful:ShipmentInformation -> epo-ord:DeliveryInformation [1]
epo-ful:ShipmentInformation -> epo-ord:DeliveryInformation [1]
+ + epo-ful:ShipmentInformation -> epo-ord:DeliveryInformation [1] epo-ful:refersToDespatchLine @@ -8512,13 +8375,13 @@

Predicates (object p epo-ful:refersToOrder - - epo-ful:DespatchAdvice -> epo-ord:Order [0..1]
epo-ful:DespatchAdvice -> epo-ord:Order [0..1]
+ + epo-ful:DespatchAdvice -> epo-ord:Order [0..1] epo-ful:refersToOrderLine - - epo-ful:DespatchLine -> epo-ord:OrderLine [0..1]
epo-ful:DespatchLine -> epo-ord:OrderLine [0..1]
+ + epo-ful:DespatchLine -> epo-ord:OrderLine [0..1] epo-ful:refersToShipmentAgreement @@ -8532,33 +8395,33 @@

Predicates (object p epo-ful:specifiesBuyer - - epo-ful:ReceiptAdvice -> epo:Buyer [0..1]
epo-ful:ReceiptAdvice -> epo:Buyer [0..1]
+ + epo-ful:ReceiptAdvice -> epo:Buyer [0..1] epo-ful:specifiesConsignee - - epo-ful:DespatchAdvice -> epo-ord:Consignee [1..*]
epo-ful:ReceiptAdvice -> epo-ord:Consignee [1..*]
epo-ful:DespatchAdvice -> epo-ord:Consignee [1..*]
epo-ful:ReceiptAdvice -> epo-ord:Consignee [1..*]
+ + epo-ful:DespatchAdvice -> epo-ord:Consignee [1..*]
epo-ful:ReceiptAdvice -> epo-ord:Consignee [1..*]
epo-ful:specifiesDespatcher - epo-ful:ReceiptAdvice -> epo-ful:Despatcher [1]
epo-ful:DespatchAdvice -> epo-ful:Despatcher [1..*]
+ epo-ful:DespatchAdvice -> epo-ful:Despatcher [1..*]
epo-ful:ReceiptAdvice -> epo-ful:Despatcher [1]
epo-ful:specifiesOriginator - - epo-ful:DespatchAdvice -> epo-ord:Originator [0..*]
epo-ful:DespatchAdvice -> epo-ord:Originator [0..*]
+ + epo-ful:DespatchAdvice -> epo-ord:Originator [0..*] epo-ful:specifiesPlaceOfDespatch - - epo-ful:ShipmentInformation -> dct:Location [0..1]
epo-ful:ShipmentInformation -> dct:Location [0..1]
+ + epo-ful:ShipmentInformation -> dct:Location [0..1] epo-ful:specifiesSeller - - epo-ful:ReceiptAdvice -> epo-ord:Seller [0..1]
epo-ful:ReceiptAdvice -> epo-ord:Seller [0..1]
+ + epo-ful:ReceiptAdvice -> epo-ord:Seller [0..1] epo-ful:specifiesShipment @@ -8587,8 +8450,8 @@

Predicates (object p epo-not:announcesRole - - epo-not:ResultNotice -> epo:AgentInRole [0..*]
epo-not:ResultNotice -> epo:AgentInRole [0..*]
+ + epo-not:ResultNotice -> epo:AgentInRole [0..*] epo-not:hasLegalBasis @@ -8597,8 +8460,8 @@

Predicates (object p epo-not:refersToRole - - epo-not:ResultNotice -> epo:AgentInRole [1..*]
epo-not:ResultNotice -> epo:AgentInRole [1..*]
+ + epo-not:ResultNotice -> epo:AgentInRole [1..*] epo-ord:comprisesOrderLine @@ -8617,8 +8480,8 @@

Predicates (object p epo-ord:concernsContract - - epo-ord:ContractInformation -> epo:Contract [1]
epo-ord:ContractInformation -> epo:Contract [1]
+ + epo-ord:ContractInformation -> epo:Contract [1] epo-ord:concernsOriginator @@ -8627,87 +8490,86 @@

Predicates (object p epo-ord:concernsOriginatorRequest - - epo-ord:OriginatorInformation -> epo:OriginatorRequest [0..1]
epo-ord:OriginatorInformation -> epo:OriginatorRequest [0..1]
+ + epo-ord:OriginatorInformation -> epo:OriginatorRequest [0..1] epo-ord:hasAcceptanceStatus - - epo-ord:OrderResponseInformation -> at-voc-new:ResponseStatus [1]
epo-cat:CatalogueResponseInformation -> at-voc-new:ResponseStatus [1]
epo-cat:CatalogueResponseInformation -> at-voc-new:ResponseStatus [1]
+ + epo-cat:CatalogueResponseInformation -> at-voc-new:ResponseStatus [1]
epo-ord:OrderResponseInformation -> at-voc-new:ResponseStatus [1]
epo-ord:hasAmountDueForPayment - - epo-ord:Order -> epo:MonetaryValue [1]
epo-ord:Order -> epo:MonetaryValue [1]
+ + epo-ord:Order -> epo:MonetaryValue [1] epo-ord:hasDeliveryPeriod - - epo-ord:DeliveryInformation -> epo:Period [0..1]
epo-ord:OrderResponseInformation -> epo:Period [0..1]
epo-ord:OrderResponseInformation -> epo:Period [0..1]
epo-ord:DeliveryInformation -> epo:Period [0..1]
+ + epo-ord:OrderResponseInformation -> epo:Period [0..1]
epo-ord:DeliveryInformation -> epo:Period [0..1]
epo-ord:hasPrepaidAmount - - epo-ord:Order -> epo:MonetaryValue [0..1]
epo-ord:Order -> epo:MonetaryValue [0..1]
+ + epo-ord:Order -> epo:MonetaryValue [0..1] epo-ord:hasPriceDiscountInformation - - epo-cat:Price -> epo-ord:AllowanceInformation [0..1]
epo-cat:Price -> epo-ord:AllowanceInformation [0..1]
+ + epo-cat:Price -> epo-ord:AllowanceInformation [0..1] epo-ord:hasRoundingAmount - - epo-ord:Order -> epo:MonetaryValue [0..1]
epo-ord:Order -> epo:MonetaryValue [0..1]
+ + epo-ord:Order -> epo:MonetaryValue [0..1] epo-ord:hasSellerOrderID - - epo-ord:Order -> adms:Identifier [0..1]
epo-ord:Order -> adms:Identifier [0..1]
+ + epo-ord:Order -> adms:Identifier [0..1] epo-ord:hasTaxInformation - - epo-ord:AllowanceChargeInformation -> epo-ord:TaxInformation [0..1]
epo-cat:Item -> epo-ord:TaxInformation [0..*]
epo:Contract -> epo-ord:TaxInformation [0..1]
epo:Contract -> epo-ord:TaxInformation [0..1]
epo-cat:Item -> epo-ord:TaxInformation [0..*]
+ + epo:Contract -> epo-ord:TaxInformation [0..1]
epo-cat:Item -> epo-ord:TaxInformation [0..*]
epo-ord:AllowanceChargeInformation -> epo-ord:TaxInformation [0..1]
epo-ord:hasTotalAllowanceAmount - - epo-ord:Order -> epo:MonetaryValue [0..1]
epo-ord:Order -> epo:MonetaryValue [0..1]
+ + epo-ord:Order -> epo:MonetaryValue [0..1] epo-ord:hasTotalChargeAmount - - epo-ord:Order -> epo:MonetaryValue [0..1]
epo-ord:Order -> epo:MonetaryValue [0..1]
+ + epo-ord:Order -> epo:MonetaryValue [0..1] epo-ord:hasTotalLineAmount - - epo-ord:Order -> epo:MonetaryValue [1]
epo-ord:Order -> epo:MonetaryValue [1]
+ + epo-ord:Order -> epo:MonetaryValue [1] epo-ord:hasTotalTaxExclusiveAmount - - epo-ord:Order -> epo:MonetaryValue [0..1]
epo-ord:Order -> epo:MonetaryValue [0..1]
+ + epo-ord:Order -> epo:MonetaryValue [0..1] epo-ord:hasTotalTaxInclusiveAmount - - epo-ord:Order -> epo:MonetaryValue [0..1]
epo-ord:Order -> epo:MonetaryValue [0..1]
+ + epo-ord:Order -> epo:MonetaryValue [0..1] epo-ord:implementsContract - - epo-ord:OrderResponse -> epo:Contract [0..1]
epo-ord:OrderResponse -> epo:Contract [0..1]
+ + epo-ord:OrderResponse -> epo:Contract [0..1] epo-ord:isSpecificToOrderLine Information that is particular to one or multiple Order Lines. - Information that is particular to one or multiple Order Lines. Information that is particular to one or multiple Order Lines. Information that is particular to one or multiple Order Lines. - Information that is particular to one or multiple Order Lines. Information that is particular to one or multiple Order Lines. + Information that is particular to one or multiple Order Lines. Information that is particular to one or multiple Order Lines. Information that is particular to one or multiple Order Lines. - epo-ord:AllowanceInformation -> epo-ord:OrderLine [0..*]
epo-ord:ContractInformation -> epo-ord:OrderLine [0..*]
epo-ord:DeliveryInformation -> epo-ord:OrderLine [0..*]
epo-cat:ChargeInformation -> epo-ord:OrderLine [0..*]
epo-ord:OriginatorInformation -> epo-ord:OrderLine [0..*]
epo-cat:ChargeInformation -> epo-ord:OrderLine [0..*]
+ epo-cat:ChargeInformation -> epo-ord:OrderLine [0..*]
epo-ord:AllowanceInformation -> epo-ord:OrderLine [0..*]
epo-ord:ContractInformation -> epo-ord:OrderLine [0..*]
epo-ord:DeliveryInformation -> epo-ord:OrderLine [0..*]
epo-ord:OriginatorInformation -> epo-ord:OrderLine [0..*]
epo-ord:isSpecificToOrderResponseLine @@ -8727,26 +8589,19 @@

Predicates (object p epo-ord:refersToCatalogue - Additional information: - If an order refers to multiple catalogues then all these catalogues ideally are subordinated - to the same contract. - Some countries however may allow multiple contracts per order (i.e Italy). Additional information: If an order refers to multiple catalogues then all these catalogues ideally are subordinated to the same contract. Some countries however may allow multiple contracts per order (i.e Italy). - epo-ord:Order -> epo-cat:Catalogue [0..*]
epo-ord:Order -> epo-cat:Catalogue [0..*]
+ epo-ord:Order -> epo-cat:Catalogue [0..*] epo-ord:refersToCatalogueLine - Additional Information: - The reference to the catalogue line is for information only, to trace the source of - the information provided in the order line. Additional Information: The reference to the catalogue line is for information only, to trace the source of the information provided in the order line. - epo-ord:OrderLine -> epo-cat:CatalogueLine [0..1]
epo-ord:OrderLine -> epo-cat:CatalogueLine [0..1]
+ epo-ord:OrderLine -> epo-cat:CatalogueLine [0..1] epo-ord:specifiesAllowanceInformation @@ -8755,8 +8610,8 @@

Predicates (object p epo-ord:specifiesBuyer - - epo-ord:OrderResponse -> epo:Buyer [0..1]
epo-ord:OrderResponse -> epo:Buyer [0..1]
+ + epo-ord:OrderResponse -> epo:Buyer [0..1] epo-ord:specifiesContractInformation @@ -8766,8 +8621,8 @@

Predicates (object p epo-ord:specifiesDeliveryAgreementLocation - - epo-ord:DeliveryAgreement -> dct:Location [0..1]
epo-ord:DeliveryAgreement -> dct:Location [0..1]
+ + epo-ord:DeliveryAgreement -> dct:Location [0..1] epo-ord:specifiesDeliveryInformation @@ -8791,8 +8646,8 @@

Predicates (object p epo-ord:specifiesPlaceOfDelivery - - epo-ord:DeliveryInformation -> dct:Location [0..1]
epo-ord:DeliveryInformation -> dct:Location [0..1]
+ + epo-ord:DeliveryInformation -> dct:Location [0..1] epo-ord:specifiesSeller @@ -8808,23 +8663,17 @@

Predicates (object p epo-sub:answersQuestion Relation indicating that the Response replies to a question. - WG approval 12/03/2024 Relation indicating that the Response replies to a question. - WG approval 12/03/2024 - epo-sub:Response -> cccev:InformationRequirement [0..*]
epo-sub:Response -> cccev:InformationRequirement [0..*]
+ epo-sub:Response -> cccev:InformationRequirement [0..*] epo-sub:concernsOrganisation Relates to Organization. - WG approval 05/03/2024 - - Relates to Organization. - WG approval 05/03/2024 - epo-sub:NationalPreQualificationData -> org:Organization [1]
epo-sub:NationalPreQualificationData -> org:Organization [1]
+ epo-sub:NationalPreQualificationData -> org:Organization [1] epo-sub:hasMandate @@ -8844,28 +8693,22 @@

Predicates (object p epo-sub:isReinforcedBy Relation indicating an Evidence that supports the Response. - WG approval 12/03/2024 Relation indicating an Evidence that supports the Response. - WG approval 12/03/2024 - epo-sub:Response -> cccev:Evidence [0..*]
epo-sub:Response -> cccev:Evidence [0..*]
+ epo-sub:Response -> cccev:Evidence [0..*] epo-sub:providesInformationOn Offers information about an instance of a concept. - WG approval 05/03/2024 Offers information about an instance of a concept. - WG approval 05/03/2024 - epo-sub:ESPDResponse -> org:Organization [0..*]
epo-sub:ESPDResponse -> org:Organization [0..*]
+ epo-sub:ESPDResponse -> org:Organization [0..*] epo-sub:providesOrganisationEmployeeQuantity The number of people hired by the Organization. - WG approval 05/03/2024 The number of people hired by the Organization. - WG approval 05/03/2024 - epo-sub:NationalPreQualificationData -> epo:Quantity [0..1]
epo-sub:NationalPreQualificationData -> epo:Quantity [0..1]
+ epo-sub:NationalPreQualificationData -> epo:Quantity [0..1] epo-sub:providesOrganisationFinancialCapability @@ -8874,33 +8717,23 @@

Predicates (object p Additional information: Used to represent the general Turnover of the Organization (for statistical purposes). - WG approval 05/03/2024 A monetary amount representing the financial capability of the Organization. - - Additional information: - Used to represent the general Turnover of the Organization (for statistical purposes). - WG approval 05/03/2024 - epo-sub:NationalPreQualificationData -> epo:MonetaryValue [0..1]
epo-sub:NationalPreQualificationData -> epo:MonetaryValue [0..1]
+ epo-sub:NationalPreQualificationData -> epo:MonetaryValue [0..1] epo-sub:providesOrganisationPreQualificationListingIdentifier The identifier assigned to an economic operator in a national pre-qualification system or official list. - WG approval 05/03/2024 The identifier assigned to an economic operator in a national pre-qualification system - or official list. - WG approval 05/03/2024 - epo-sub:NationalPreQualificationData -> adms:Identifier [0..*]
epo-sub:NationalPreQualificationData -> adms:Identifier [0..*]
+ epo-sub:NationalPreQualificationData -> adms:Identifier [0..*] epo-sub:refersToApplicablePeriod Relation indicating the period to which the Response shall apply. - WG approval 12/03/2024 Relation indicating the period to which the Response shall apply. - WG approval 12/03/2024 - epo-sub:Response -> epo:Period [0..1]
epo-sub:Response -> epo:Period [0..1]
+ epo-sub:Response -> epo:Period [0..1] epo-sub:refersToOtherESPDResponse @@ -8913,10 +8746,8 @@

Predicates (object p epo-sub:relatesToESPDRequest Is about an European Single Procurement Document (ESPD) Request. - WG approval 05/03/2024 Is about an European Single Procurement Document (ESPD) Request. - WG approval 05/03/2024 - epo-sub:ESPDResponse -> epo-acc:ESPDRequest [1]
epo-sub:ESPDResponse -> epo-acc:ESPDRequest [1]
+ epo-sub:ESPDResponse -> epo-acc:ESPDRequest [1] epo-sub:specifiesResponse @@ -8929,10 +8760,8 @@

Predicates (object p epo-sub:summarisesInformationAboutCertificate Relation indicating the Certificate that the information refers to. - WG approval 12/03/2024 Relation indicating the Certificate that the information refers to. - WG approval 12/03/2024 - epo-sub:CertificateInformation -> epo:Certificate [1]
epo-sub:CertificateInformation -> epo:Certificate [1]
+ epo-sub:CertificateInformation -> epo:Certificate [1] locn:address diff --git a/glossary/ePO_core_glossary.html b/glossary/ePO_core_glossary.html index a2ce502b..1267785d 100644 --- a/glossary/ePO_core_glossary.html +++ b/glossary/ePO_core_glossary.html @@ -90,6 +90,28 @@

Class names and defi used to exchange it: a pdf document, a video, a recording, etc. + + cccev:EvidenceType + Information about the characteristics of an Evidence. + + Additional Information: + The Evidence Type and the characteristics it describes are not concrete individual + responses to a Requirement (i.e. Evidence), but descriptions about the desired form, + content, source and/or other characteristics that an actual response should have and + provide (e.g. membership of a class of Evidences). + + + cccev:EvidenceTypeList + Group of Evidence Types for conforming to a Requirement. + + Additional Information: + An Evidence Type List is satisfied, if and only if, for all included Evidence Types + in this List, corresponding conformant Evidence(s) are supporting the Requirement + having this List. The Evidence Type List describes thus an AND condition on the different + Evidence Types within the list and an OR condition between two or more Evidence Type + Lists. Combinations of alternative Lists can be provided for a respondent of a Requirement + to choose amongst them. + cccev:InformationConcept Piece of information that the Evidence provides or the Requirement needs. @@ -143,6 +165,27 @@

Class names and defi To stay consistent to how identification is realised in the eProcurement ontology, we switch to using `adms:identifier` instead of `dct:identifier` as per CCCEV specification. + + cccev:SupportedValue + Value for an Information Concept that is provided by an Evidence. + + Additional Information: + The notion of Supported Value is closely related to actual data exchange between two + parties: (a) the Requirement processor, i.e. the Agent setting out Requirements for + an objective and processing the supplied Evidences in the context of the Requirements, + and (b) the Evidence provider, i.e. the Agent supplying information to an information + request expressed as Requirements. The Requirement processor has expressed its expectations + (both business as technical) for the information it wants to recieve as an Information + Concept. The Evidence provider is able to supply information for that Information + Concept, but its native data representation might not be coherent with the expectations + set by the Requirement processor. The Supported Value is bridging both. The Evidence + provider can either provide a derived value (fact) from its native data representation + that complies with the Information Concept expectations. Or it can provide a query + in an agreed language between Evidence provider and Requirement processor that allows + the Requirement processor to retrieve the value from the native data representation. + Implementers are free to choose their language. It is recommended to document the + made agreements well. + cpov:ContactPoint Information (e.g. e-mail address, telephone number) of a Person or department through @@ -195,6 +238,50 @@

Class names and defi An identifiable geographic place or named place. + + eli:LegalExpression + The intellectual realisation of a legal resource in the form of a "sequence of signs" + (typically alpha-numeric characters in a legal context). + For example, any version of the legal resource whose content is specified and different + from others for any reason: language, versions, etc.; + + Note that ELI ontology accommodates different point of view on what should be considered + a new legal resource, or a new legal expression of the same resource. Typically, a + consolidated version can be viewed, in the context of ELI, either as separate legal + resource (linked to original version and previous consolidated version using corresponding + ELI relations), or as a different legal expression of the same legal resource. + + + + eli:LegalResource + A work in a legislative corpus. This applies to acts that have been legally enacted + (whether or not they are still in force). + For example, the abstract concept of the legal resource; e.g. "act 3 of 2005" (adapted + from Akoma Ntoso) + + A legal resource can represent a legal act or any component of a legal act, like an + article. Legal resources can be linked together using properties defined in the model. + + Note that ELI ontology accommodates different point of view on what should be considered + a new legal resource, or a new legal expression of the same resource. Typically, a + consolidated version can be viewed, in the context of ELI, either as separate legal + resource (linked to original version and previous consolidated version using corresponding + ELI relations), or as a different legal expression of the same legal resource. + + + + eli:LegalResourceSubdivision + A component of a legal act, at an arbitrary level of precision, like a chapter, an + article, an alinea, a paragraph or an list item. + + + eli:Work + Any distinct intellectual creation (i.e., the intellectual content), in the context + of ELI. + + The substance of Work is ideas. + + epo:AccessTerm Conditions and stipulations about where and how to access the Procurement Documents. @@ -1364,4373 +1451,7317 @@

Class names and defi WG approval 05/08/2021 (revised 26/10/2021) - foaf:Agent - A Person, an Organisation, or a System that acts in Procurement or have the power - to act in Procurement. + epo-acc:ESPDRequest + An updated self-declaration used by the economic operator as a preliminary evidence + in replacement of certificates issued by public authorities or third parties confirming + that the economic operator fulfils the Exclusion Grounds and the Selection Criteria + set out by the Buyer for a specific Procurement. - WG Approval 28/04/2020 + WG Approval 05/03/2024 - foaf:Person - The Person class represents people. Something is a Person if it is a Person. We don't - nitpick 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. + epo-cat:Batch + A production Lot in which the Item instances were produced. + + WG Acceptance 10/03/2022 + - locn:Address - The particulars of the place where a Person or an Organisation is located. + epo-cat:Brand + Name given by an organisation to its product or service, or range of products or services. - 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.". + Additional information: + Brand name allows economic operators to distinctively describe an item in their eCatalogue. + This may be different from the "item name". + WG acceptance 10/03/2022 + + + + epo-cat:Catalogue + A Document describing a set of Items offered for purchase that can be processed in + an electronic way. + + + + epo-cat:CatalogueLine + Aggregated information about the Terms and specifications for procuring an Item. - 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. + Details about an Item, like Prices, packaging, discounts, special promotions, etc. + + + TC 440: + + Detailed information of an Item, Price and its composition in a Catalogue. + + Composition: e.g. information referring to its description, how to order it, what + it is made of, properties, delivery conditions, etc. - 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). - - - - person:Person - A individual human being who may be dead or alive, but not imaginary. - time:Duration - Duration of a temporal extent expressed as a number scaled by a temporal unit. + epo-cat:CatalogueResponse + - - -

Attributes (datatype properties) names and definitions

- - - - - - + + - - - - - - + + - - - + - + Charge category indicates the nature of the tax/duty/fee, for example VAT, CAR, etc. + Charge category modifier may be used in case different levels, exemptions or other + modifications apply. + The charge can be fixed or relative to the price. + + WG approval 16/05/2023 - - - + - + For example, AllowanceChargeInformation may be associated to the Order or the Catalogue + (either at the Line level or at the Document level), amongst others. + + WG approval 16/05/2023 - - - + - + An Item can be an atomic Thing or a composition of things that together are seen as + a unit, e.g. a tetrabrik of milk or an indivisible package of six tetrabriks. + + No distinction is provided between services, goods and works to leave room for innovation. + + WG approval 30/06/2022 - - - + - - - - + - - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - + Additional information: + Consignment it is a Transport Agreement. They do not care about the content of what + is being shipped. (only if there are dangerous goods, and temperature requirements). + How to move from place a to place B. - - - - + + - - - + - + Additional Information: + The Role is carried out by the Supplier or on behalf of the Supplier. + Despatcher is also known as Despatch Party, Consignor, Deliverer. - - + - - - + - - - - - + + - - + + + + + - - - + - - - - - + + - - - + - - - - + - + Addition Information + This represents the "where" and "when". - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - + - - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - + + + + + + + + + - - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - + - - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - + - - - - - + + - - - - + + - - - - + + - - - - + + - - + - - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - + - - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - - - + + - - + - - - - - + + - - - - + + - - - - + + - - - + + + + + + + + + + + + + - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - + + + + + + + + + + + + + + + + + - + (WG approval 27/03/2019) - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - - - + - + WG approval 16/05/2023 - - - + - + WG approval 16/05/2023 + - - - + - - - - + + + + + + + + + - + WG approval 16/05/2023 + - - - + - - - - + - + WG approval 20/04/2023 - - - + - + Additional Information: + The Order Response is used to inform on the acceptance or rejection of an Order or + to make a counter-offer. + + WG approval 20/04/2023 + - - - + + + + + - + WG approval 20/04/2023 - - - + - + - - - - + + - - - + - + WG acceptance 08/09/2022 - - - + - - - - + + + + + + + + + - + WG approval 05/03/2024 - - - + - + WG approval 05/03/2024 - - - + - + WG approval 05/03/2024 - - - + - + WG approval 05/03/2024 - - - - + + - - - - + + - - - - + + - - - + - - - - - - - + + 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. - - - - + + - - - + - - - - - + + - - - - + + + +
Class nameAttribute nameDefinitionData type / cardinalityepo-cat:CatalogueResponseInformation
adms:Identifieradms:schemaAgencyThe name of the agency that issued the identifier.rdf:PlainLiteral [0..*]epo-cat:CatalogueResponseLine
cccev:Criterioncccev:biasParameter used to adjust the evaluation of the Criterion. + epo-cat:ChargeInformationInformation about tax, fee or duty imposed. 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:Criterioncccev:weightRelative importance of the Criterion. + epo-cat:InformationHubGrouping of data that may be associated to various concepts. 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:Criterioncccev:weightingConsiderationDescriptionExplanation of how the weighting of a Criterion is to be used. + epo-cat:ItemA product, work, service or any combination of them. 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.rdf:PlainLiteral [0..1]
cpov:ContactPointcpov:emailThe email of the Organisation. + epo-cat:ItemAccessoryRelationCombination of two Items where the former enhances the latter. + WG Approval: 30/06/2022 rdf:PlainLiteral [0..*]
cpov:ContactPointcpov:telephoneA telephone number through which the Contact Point can be contacted. + epo-cat:ItemComplementaryRelationCombination of two Items which mutually enhance one another. + + WG Approval: 30/06/2022 + rdf:PlainLiteral [0..*]
person:Personcv:birthDateThe point in time on which the Person was born.xsd:date [0..1]epo-cat:ItemCompositionInclusion of an Item into in the described Item. + + Additional Information: + The Item is provided with its components, however, the component Items may also be + provided separately. + For example, a bicycle has wheels as components, but they may be provided as spare + parts as well. + This relation is useful to describe different package levels of an item or hierarchies + of Items. + + WG Approval: 19/05/2022 + + +
locn:Geometrycv:coordinatesThe coordinate list.rdf:PlainLiteral [0..*]epo-cat:ItemModelA specific design or version of a product or service. + + Additional information: + This class is meant as a reusable reference to the model name rather than as a set + of specifications of an Item of this particular model. + + WG acceptance 10/03/2022 + +
locn:Geometrycv:latitudeThe latitude.rdf:PlainLiteral [0..*]epo-cat:ItemPropertyConstruct meant to represent the association between an attribute defined in an external + classification scheme and the value ascribed to it. + + WG approval 26/07/2022
locn:Geometrycv:longitudeThe longitude.rdf:PlainLiteral [0..*]epo-cat:ItemRelationConnection between two Items. + + WG Approval: 30/06/2022 +
person:Persondct:alternativeAny name by which an individual is known other than their full name. - WG 09/11/2021rdf:PlainLiteral [0..*]epo-cat:ItemReplacementSupplantment, displacement or suspension of an Item by the described Item. + + WG Approval: 30/06/2022 +
cccev:Evidence
cccev:InformationConcept
cccev:Requirement
cpov:ContactPoint
cv:Channel
epo:AgentInRole
epo:Document
epo:ElectronicSignature
epo:Fund
epo:NonDisclosureAgreementTerm
epo:SecurityClearanceTerm
epo:SubcontractingEstimate
epo:SubcontractTerm
epo:System
epo:Technique
epo:LotGroup
epo:ProcurementElement
epo:TenderGroup
dct:descriptionAn account of the resource. + epo-cat:ItemRequirementNecessity of an Item by the described item. Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + The described item is provided without other items that are required for proper functionality. - WG Approval 30/05/2023 An account of the resource. + For example, a printer cannot be used without ink cartridge; or a Server cannot be + used without its installation. - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + WG Approval: 19/05/2022 - WG Approval 30/05/2023 An account of the resource. +
epo-cat:Line
epo-cat:ManufacturerThe Producer of goods or provider of services. Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + Also, known as Supplier and Manufacturer. - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + We do not care who provides these service or products we care with whom Business is + done. - WG Approval 30/05/2023 An account of the resource. + PEPPOL - Invoice: + The Supplier is the Legal Person or Organisation who provides a product and/or service. - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + PEPPOL - Order: The supplier is the legal person or organisation who provides a product + or service. + Examples of supplier roles: seller, despatch party, creditor, economic operator. - WG Approval 30/05/2023 An account of the resource. +
epo-cat:PostAwardDocument
epo-cat:PriceAmount of money required or given in exchange for Items. - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + Additional information: + The Price excludes any charges (such as taxes, duties and fees) and discounts. - WG Approval 30/05/2023 An account of the resource. + WG approval 26/07/2022
epo-cat:ProductSpecificationDocument providing information about an Item. - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + WG approval 07/04/2022 - WG Approval 30/05/2023 - An account of the resource. +
epo-con:ContractAmendmentA change to an existing Contract that is agreed by the contracting parties.
epo-con:ContractModificationInformation
epo-con:Deliverable
epo-ful:AbstractContainer
epo-ful:CarrierThe Role of an Agent who handles the physical Delivery/Transportation of the (Despatched) + Shipment. Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. + This Role is also known as Deliverer. - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. + WG approval: 11/10/2022
epo-ful:ConsignmentA batch of goods destined for or delivered to someone. - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 - An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 - An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 An account of the resource. - - Additional Information: - Description may include but is not limited to: an abstract, a table of contents, a - graphical representation, or a free-text account of the resource. - - WG Approval 30/05/2023 - rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [1..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
epo:Documentdct:issuedDate of formal issuance of the resource. - - Additional information: - This is generally used for modules other than eNotice. - The xsd:dateTime here means that we can provide either xsd:date, xsd:dateTime, or - xsd:timeStamp or any other variant of time expression. This extension needs to be - encoded/automated in the ontology and in the application profile. - Why is it like this? Because UML cannot handle such expressions of disjunctive property - ranges. - - WG approval 26/01/2023xsd:dateTime [0..1]epo-ful:DespatchAdvice
epo:AgentInRole
epo:Document
epo:Fund
foaf:Agent
epo:LotGroup
epo:ProcurementElement
epo:TenderGroup
dct:titleA name given to the resource. - - WG approval 30/05/2023 - A name given to the resource. - - WG approval 30/05/2023 - - A name given to the resource. - - WG approval 30/05/2023 - A name given to the resource. - - WG approval 30/05/2023 A name given to the resource. + epo-ful:DespatcherRole of an Agent who sends the goods or notifies of the service or works execution. - WG approval 30/05/2023 - A name given to the resource. - - WG approval 30/05/2023 A name given to the resource. - WG approval 30/05/2023 - rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
epo:SelectionCriteriaSummaryepo:describesMinimumLevelOfStandardsepo-ful:DespatchLine rdf:PlainLiteral [0..1]
epo:ParticipationConditionsSummaryepo:describesObjectiveParticipationRulesepo-ful:FreightForwarder rdf:PlainLiteral [0..1]
epo:ProfessionalSuitabilitySummaryepo:describesProfessionrdf:PlainLiteral [0..1]epo-ful:GoodsItemAn Item including its initial packaging during transportation. + + Additional information: + For example, the Item being bought is the computer. The weight of the computer is + X. + The weight of the Goods Item is the weight of the computer plus the weight of the + initial packaging. + During transportation you have for example trace ID which is applied to the GoodsItem, + rather than on the Item itself. + The declared statistical value can only apply once you have a GoodsItem. + + WG approval 30/03/2023
epo:ProfessionalSuitabilitySummaryepo:describesProfessionRelevantLawepo-ful:NotifierThe party to be notified upon arrival of goods and when special occurrences (usually + pre-defined) take place during a transportation service. (UBL) +
epo-ful:Package rdf:PlainLiteral [0..1]
epo:ParticipationConditionsSummaryepo:describesVerificationMethodepo-ful:ReceiptAdvice rdf:PlainLiteral [0..1]
epo:SubmissionStatisticalInformationepo:hasAbnormallyLowTendersTenders 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-ful:ReceiptAdviceLine
epo:Procedureepo:hasAcceleratedProcedureJustificationThe reasons why the procedure is accelerated. + epo-ful:ShipmentAgreementThe Commercial Agreement between the Commercial Parties. Additional Information: - A procedure is accelerated to cover needs of extraordinary circumstances ie earthquake - relief. - - WG Approval 09/06/2020 - + It describes items being shipped. What is being moved. rdf:PlainLiteral [0..*]
epo:NonPublishedInformationepo:hasAccessibilityDateThe date at which unpublished data shall be published. + epo-ful:ShipmentInformationThe Transportation of an identifiable collection of Goods Items from one party (the + Despatch Party) to another party (the Consignee) via one or more modes of transport. - WG Approval 11/06/2020xsd:date [0..1]
epo:Documentepo:hasAccessURLLocation where the resource can be accessed. - - WG approval 07/04/2022xsd:anyURI [0..*]epo-ful:ShipmentStage
epo:Buyerepo:hasActivityDescriptionIn 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. - rdf:PlainLiteral [0..*]epo-ful:TemperatureSpecification
epo:ChangeInformation
epo:Notice
epo:ProcurementCriterion
epo:ProcurementObject
epo:hasAdditionalInformationSupplementary data about the instance of the concept. - - WG Approval 15/10/2019 - Supplementary data about the instance of the concept. - - WG Approval 15/10/2019 Supplementary data about the instance of the concept. - - WG Approval 15/10/2019 Supplementary data about the instance of the concept. - - WG Approval 15/10/2019rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
epo-ful:TransportEquipment
epo:AccessTermepo:hasAdditionalInformationDeadlineThe 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-ful:TransportEquipmentSeal
epo:AwardDecisionepo:hasAdditionalNonAwardJustificationFurther justification for the non award . - - Additional information: - This is generally used when the non award reason code is set to "Other". - - WG: 18/01/2022rdf:PlainLiteral [0..1]epo-ful:TransportHandlingUnitA description of Individual Handling Units in which the Line Items are packed.
cv:Channelepo:hasAddressURLepo-ful:TransportMeans xsd:anyURI [0..1]
foaf:Agentepo:hasAliasAcronym or alternative name of the Agent. - WG Approval 25/03/2021rdf:PlainLiteral [0..*]epo-ful:TransportMeansOperator
epo:MonetaryValueepo:hasAmountValueThe numeric value of the amount, including decimals.xsd:decimal [1..1]epo-not:CANDefence-D81
epo:AwardEvaluationTermepo:hasAwardCriteriaEvaluationFormulaThe 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.rdf:PlainLiteral [0..*]epo-not:CANSocial-D25
epo:AwardEvaluationTermepo:hasAwardCriteriaOrderJustificationThe 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.rdf:PlainLiteral [0..1]epo-not:CANSocialNotice
epo:AwardCriterionepo:hasAwardCriteriaStatedInProcurementDocumentsxsd:boolean [1..1]epo-not:CANSocialNotice-D25Additional information: + Social and other specific services – utilities +
epo:ProcessPlanningTermepo:hasAwardDateScheduledPlanned date for the award decision. - WG Approval 09/11/2021xsd:date [0..1]epo-not:CANStandard-D24
epo:AwardDecisionepo:hasAwardDecisionDateThe official date of the award decision. - - Additional Information: - This corresponds in eForms to BT-1451 Winner Decision Date. - - WG Approval 09/01/2020 - xsd:dateTime [0..1]epo-not:CANStandardNotice
epo:TenderAwardOutcomeepo:hasAwardRankThe 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-not:CNDefence-D81
epo:Periodepo:hasBeginningThe date and time on which this period begins.xsd:dateTime [0..1]epo-not:CNSocial-D25
epo:FrameworkAgreementTermepo:hasBuyerCategoryDescriptionA 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-06rdf:PlainLiteral [0..*]epo-not:CNSocialNotice
org:Organizationepo:hasBuyerLegalTypeDescriptionSelf-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/2022rdf:PlainLiteral [0..1]epo-not:CNSocialNotice-D25Additional information: + Social and other specific services – utilities +
epo:Buyerepo:hasBuyerProfileWebsite 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. + epo-not:CNStandard-D24
epo-not:CNStandardNotice
epo-not:CompetitionNoticeAn announcement of the launch of a Procurement Procedure by a Procuring Entity. - WG approval 04/05/2018 + WG approval 18/05/2018 xsd:anyURI [0..1]
epo:ConcessionEstimateepo:hasCalculationMethodFormula for obtaining values. - - Additional Information: - The possible values are monetary values, ranking scores, criterion weighting. - - WG Approval 25/05/2018rdf:PlainLiteral [0..1]epo-not:CompletionNoticeAn announcement of the end of a Procurement by a Buyer.
epo:Certificateepo:hasCertificationNumberThe unique identifier of the certificate. - - WG approval 26/07/2022rdf:PlainLiteral [0..1]epo-not:ConcessionAwardNotice-D23
epo:ChangeInformationepo:hasChangeDescriptionExplanatory text about the instance of the concept. - - WG Approval 30/09/2019rdf:PlainLiteral [0..*]epo-not:ConcessionNotice-D23
epo:ChangeInformationepo:hasChangeReasonDescriptionExplanatory text about why the element is altered. - - Additional information: - This corresponds in eForms to BT-762 Change Reason Description.rdf:PlainLiteral [0..*]epo-not:ContractModificationNoticeAn announcement of the Modification Of a Contract/Concession during its term by a + Procuring Entity.
epo:VehicleInformationepo:hasCleanVehiclesThe 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-not:DesignContest-D24
epo:QualificationCriteriaSummaryepo:hasConditionVerificationMethodepo-not:DesignContest-D25 rdf:PlainLiteral [0..*]
epo:NonPublishedInformationepo:hasConfidentialityJustificationA 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 - rdf:PlainLiteral [0..1]epo-not:DesignContestNotice
cpov:ContactPointepo:hasContactNameA short text by which a contact is known or referred to. - - WG Approval: 27/01/2022rdf:PlainLiteral [0..1]epo-not:DesignContestResult-D24
epo:Contractepo:hasContractConclusionDateThe 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/2020xsd:date [0..1]epo-not:DesignContestResult-D25
epo:ProcedureTermepo:hasCrossBorderLawThe 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.rdf:PlainLiteral [0..*]epo-not:DesignContestResultNotice
epo:MonetaryValueepo:hasCurrencyCodeListAgencyIDIdentifier of the agency that maintains the currency code list used. - WG approval 13/04/2021rdf:PlainLiteral [0..*]epo-not:DirectAwardPrenotificationNoticeNotice which sets out the Buyer's purchasing intention to award a Contract without + prior notification of Competition.
epo:MonetaryValueepo:hasCurrencyCodeListAgencyNameName of the agency that maintains the currency code list used. - WG approval 13/04/2021rdf:PlainLiteral [0..*]epo-not:eFormsNotice
epo:MonetaryValueepo:hasCurrencyCodeListIDConcept scheme URI used for the currency code list. - WG approval 13/04/2021rdf:PlainLiteral [0..*]epo-not:Modification-D23
epo:SecurityClearanceTermepo:hasDeadlineThe deadline by which the security clearance must be submitted to the buyer. - - WG Approval 12/09/2019 - - xsd:dateTime [0..1]epo-not:Modification-D24
epo:ReviewDecisionepo:hasDecisionDateThe date of the review decision. - - Additional information: - This attribute corresponds to the BT-787 Review Date in eForms. - xsd:date [0..1]epo-not:Modification-D25
epo:DesignContestRegimeTermepo:hasDescriptionOfPrizesepo-not:Notice1 rdf:PlainLiteral [0..1]
epo:Documentepo:hasDispatchDateDate and time of transmission of a record to an Organization. - - WG Approval 31/08/2023xsd:dateTime [0..1]epo-not:Notice10
epo:FrameworkAgreementTermepo:hasDurationExtensionJustificationThe 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/2019rdf:PlainLiteral [0..1]epo-not:Notice11
epo:SubmissionTermepo:hasEAuctionURLThe internet address of the electronic auction. - - Additional Information: - - This corresponds in eForms to BT-123 Electronic Auction URL.xsd:anyURI [0..1]epo-not:Notice12
epo:SubmissionStatisticalInformationepo:hasEEAReceivedTendersThe amount of tenders received from economic operators in other EEA countries other - than the country of the buyer. - - WG Approval 12/12/2019xsd:integer [0..1]epo-not:Notice13
epo:Noticeepo:hasEFormsSubtypeepo-not:Notice14 xsd:integer [0..1]
epo:ContractTermepo:hasEInvoicingElectronic means will be used for invoicing in the post-award process. - - Additional Information: - This attribute is used for standard form mappings. - - WG Approval 12/09/2019 - xsd:boolean [0..1]epo-not:Notice15
epo:Tenderepo:hasElectronicSubmissionTransmission of tenders is possible by electronic means of communication. xsd:boolean [0..1]epo-not:Notice16
epo:SubmissionStatisticalInformationepo:hasElectronicTendersElectronic Tender Lots received. - - WG Approval 28/07/2020 - xsd:integer [0..1]epo-not:Notice17
epo:ReviewObjectepo:hasElementReferenceReference 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 [0..*]epo-not:Notice18
epo:Periodepo:hasEndThe date and time at which this period ends.xsd:dateTime [0..1]epo-not:Notice19
epo:Contractepo:hasEntryIntoForceDateThe date on which the contract enters into force. - - Additional information: - - This is generally the date on which the fulfillment of the contract begins. - - This corresponds in eForms to - - WG approval 05/11/2019xsd:date [0..1]epo-not:Notice2
epo:ContractTermepo:hasEOrderingElectronic means will be used for requesting and purchasing in the post-award process. - - WG Approval 12/09/2019 - - xsd:boolean [0..1]epo-not:Notice20
epo:ContractTermepo:hasEPaymentElectronic means must be used for paying. - WG Approval 09/11/2021 - xsd:boolean [0..1]epo-not:Notice21
epo:Noticeepo:hasESenderDispatchDateThe date and time the notice was transmitted electronically by the eSender to the - Publications Office of the European Union. - - Additional Information: - Typically, eSenders include national Official Journals, Buyers sending a large number - of electronic Notices, public or private bodies acting on behalf of Buyers and eProcurement - software developers. - - WG approval 20/06/2023xsd:dateTime [0..1]epo-not:Notice22
epo:ProcessPlanningTermepo:hasEstimatedContractNoticePublicationDateForeseen date for publication of Contract Notice. - - Additional information: - This corresponds in eForms BT-127 Future Notice. - - xsd:date [0..1]epo-not:Notice23
epo:MultipleStageProcedureTermepo:hasEstimatedInvitationToExpressInterestDateThe 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-not:Notice24
epo:MultipleStageProcedureTermepo:hasEstimatedInvitationToTenderDateThe 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/2019xsd:date [0..1]epo-not:Notice25
epo:SubcontractingEstimateepo:hasEstimatedPercentageThe estimated proportion foreseen to be subcontracted. - - WG Approval 07/01/2020xsd:decimal [0..1]epo-not:Notice26
epo:ProcessPlanningTermepo:hasEstimatedTenderInvitationDateThe planned date for the dispatch of the invitations to submit tenders. - WG Approval 09/11/2021xsd:date [0..1]epo-not:Notice27
epo:SubmissionStatisticalInformationepo:hasEstimatedTotalSubcontractsThe estimated amount of work to be subcontracted in the contract resulting from the - lot. - WG Approval 09/11/2021xsd:integer [0..1]epo-not:Notice28
epo:SubmissionStatisticalInformationepo:hasEUReceivedTendersThe amount of tenders received from economic operators in other EU countries other - than the country of the buyer.xsd:integer [0..1]epo-not:Notice29
cpov:ContactPointepo:hasFaxThe fax number used to reach a person or an organisation.rdf:PlainLiteral [0..*]epo-not:Notice3
epo:AwardCriterionepo:hasFixedValueThis corresponds in the eForms to BT-541 Award Criterion Number in association with - BT-5422 Award Criterion Number Fixed.xsd:decimal [0..1]epo-not:Notice30
epo:DesignContestRegimeTermepo:hasFollowupContractAny 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-not:Notice31
epo:DesignContestRegimeTermepo:hasFollowupContractInformationFurther information about follow-up contracts, prizes and payments (for example non-monetary - prizes, payments given for participation). - - WG Approval 03/09/2019rdf:PlainLiteral [0..*]epo-not:Notice32
epo:Noticeepo:hasFormNumberepo-not:Notice33 rdf:PlainLiteral [0..1]
epo:ProcurementCriterionepo:hasFormulaThe 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.rdf:PlainLiteral [0..1]epo-not:Notice34
epo:ProcedureTermepo:hasGroupLotEvaluationMethodDescription of how lots and groups of lots are evaluated against one another in the - procedure. - - - - rdf:PlainLiteral [0..*]epo-not:Notice35
epo:OrganisationGroupepo:hasGroupTypeForm of collaboration agreement between organisations. - - Additional Information: - This is not a legal type; not to be mistaken with epo:hasLegalFormType which may also - be used for Organisation Groups. - - WG Approval 09/11/2021rdf:PlainLiteral [0..*]epo-not:Notice36
epo:SubmissionTermepo:hasGuaranteeDescriptionInformation 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 - rdf:PlainLiteral [0..*]epo-not:Notice37
epo:SubmissionStatisticalInformationepo:hasInadmissibleTendersTenders 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/2019xsd:integer [0..1]epo-not:Notice38
cpov:ContactPoint
org:Organization
epo:hasInternetAddressThe main web page used by the instance of the concept. - - WG Approval 01/06/2023 - - The main web page used by the instance of the concept. - - WG Approval 01/06/2023 - xsd:anyURI [0..1]
xsd:anyURI [0..*]
epo-not:Notice39
epo:DirectAwardTermepo:hasJustificationAn explanation about the reasons for using the concept. - WG Approval 5/11/2019 - rdf:PlainLiteral [0..*]epo-not:Notice4
epo:SubmissionTermepo:hasLateSubmissionInformationDescriptionA 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. - rdf:PlainLiteral [0..*]epo-not:Notice40
epo:ProcurementObjectepo:hasLegalBasisDescriptionepo-not:Notice5 rdf:PlainLiteral [0..*]
epo:ContractTermepo:hasLegalFormRequirementThe legal form to be taken by a Contractor. - - Additional Information: - Generally, this is defined to cover the case where an Organisation Group is involved. - Note that the codelist provided at national level should be used.rdf:PlainLiteral [0..1]epo-not:Notice6
org:Organizationepo:hasLegalFormTypeThe classification of an Organisation according to legislation. - - Additional Information: - Generally, this is defined for Tenderers who want to submit as an Organisation Group. - Note that the codelist provided at national level should be used. - rdf:PlainLiteral [0..1]epo-not:Notice7
org:Organizationepo:hasLegalNameThe officially registered name of an organisation. - - WG Approval 10/01/2023rdf:PlainLiteral [0..*]epo-not:Notice8
epo:ProcedureTermepo:hasLotAwardCombinationThe 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 + epo-not:Notice9
epo-not:PIN-CFCSocial-D25
epo-not:PIN-CFCSocialNotice
epo-not:PIN-CFCSocialNotice-D25Additional information: + Social and other specific services – utilities rdf:PlainLiteral [0..1]
org:Organizationepo:hasMainActivityDescriptionSelf-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 + epo-not:PIN-CFCStandard-D24
epo-not:PIN-CFCStandardNotice
epo-not:PINDefence-D81
epo-not:PINOnly-D24
epo-not:PINOnly-D25
epo-not:PINOnlyNoticePriorInformationNotice
epo-not:PINProfile-D24
epo-not:PINProfile-D25
epo-not:PINProfile-D81
epo-not:PINProfileNotice
epo-not:PIN-RTL-D24
epo-not:PIN-RTL-D25
epo-not:PINTimeLimitNotice
epo-not:PlanningNoticeNotice which sets out the Contracting Authority's purchasing intentions. It is used + by Contracting Authorities to provide Suppliers with information about a Procurement + Process. rdf:PlainLiteral [0..1]
epo:Procedureepo:hasMainFeatureMain features of the procedure and information about where the full rules for the - procedure can be found. + epo-not:PreMarketConsultationNotice
epo-not:QS-D25
epo-not:QSNotice
epo-not:QSNotice-D25Additional information: + Social and other specific services – utilities +
epo-not:ResultNoticeAn announcement of the award or non-award of a Contract by a Buyer. - 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.rdf:PlainLiteral [0..*]
epo:ProcedureTermepo:hasMaximumLotSubmissionAllowedThe total number of lots for which one Tenderer can submit Tenders. + epo-not:SocialAndOtherSpecificServices-D23
epo-not:SocialAndOtherSpecificServices-D24public contracts
epo-not:StandardFormsNotice
epo-not:Subcontract-D81
epo-not:SubcontractNotice
epo-not:VEAT-D23
epo-not:VEAT-D24
epo-not:VEAT-D25
epo-not:VEAT-D81
epo-not:VoluntaryEx-AnteTransparencyNoticeA Notice informing of the intention to award a Contract without prior publication + of a Contract Notice. - 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). + Additional Information: - WG approval 12/12/2018 + For European Notices above the threshold + + "A means of advertising the intention to award the Contract without opening it up + to formal Competition. A Contracting Authority may decide that a Contract does not + require prior publication through a Contract Notice in the O.J.E.U. A reason for this + decision may be that the Contract meets the exceptional conditions described in Article + 31 of Directive 2004/18/EC. In a recent V.E.A.T notice the reason was listed as “extreme + urgency brought about by events unforeseeable by the Contracting Entity and in accordance + with the strict conditions stated in the Directive” . + "Voluntary Ex-Ante Transparency Notice" (VEAT) where a Contracting Authority deems + that a Contract does not require prior publication of a Contract Notice in the European + Journal (OJEU). This may apply, for example, if the Contract meets the exceptional + conditions justifying direct award of contracts. + <b>This definition is still to be worked on.</b> xsd:integer [0..1]
epo:MultipleStageProcedureTermepo:hasMaximumNumberOfCandidatesMaximum number of candidates to be invited for the second stage of the procedure. + epo-ord:AllowanceChargeInformationInformation about discounts, taxes, duties and fees imposed. - WG Approval 22/08/2019xsd:integer [0..1]
epo:ProcedureTermepo:hasMaximumNumberOfLotsToBeAwardedThe 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). + epo-ord:AllowanceInformationInformation about the discounts imposed. - WG Approval 22/08/2019xsd:integer [0..1]
epo:ContractTermepo:hasMaximumNumberOfRenewalsThe maximum number of times the contract can be renewed. + epo-ord:ConsigneeA Role of an Agent that receives the Shipment of the Procurement (service, goods or + works) and who is taking possession. - Additional Information + Additional information: + The Role is carried out by the Customer or on behalf of the Customer. + The possession of the goods does not necessary imply ownership. + The Consignee may be the end-user or the beneficiary. - 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. + (Consignee) Definition from PEPPOL Despatch: + The Consignee is the person or Organisation to which the products will be shipped + and who is taking possession. The Role is carried out by the Customer or on behalf + of the Customer. - PLEASE REVIEW THIS DEFINITION AGAIN WITH THE WORKING GROUP. It was originally taken - from eForms. + WG approval: 21/02/2023 xsd:integer [0..1]
epo:FrameworkAgreementTermepo:hasMaximumParticipantsNumberThe maximum number of participants in the framework agreement. + epo-ord:ContractInformationInformation about the Contract. - Additional Information: - Maximum number of tenderers who may be awarded a contract within the framework agreement. + WG approval 20/04/2023
epo-ord:DeliveryAgreementTerm applying to the delivery of goods, services and works. - The number is a positive integer. + Additional Information: + Delivery terms identifier can normally be Incoterms accompanied by the description + of specific conditions related to the delivery. - This corresponds in eForms to BT-113 Framework Maximum Participants Number. + WG approval 16/05/2023
epo-ord:DeliveryInformationInformation about the timing, the delivery destination, the delivery agreement and + the involved parties. - WG Approval 2019-02-05xsd:integer [0..1]
epo:SubcontractTermepo:hasMaximumShareThe maximum proportion of something to be distributed. + epo-ord:OrderA formal request of the Buyer to the Seller specifying the goods, services or works + to be delivered. Additional Information: - In the case of subcontracting the share may refer to the proportion of works, services - or supplies being subcontracted. + A Buyer submits an Order for delivery of goods, services or works to a Seller. - WG Approval 17/09/2019 + WG approval 23/04/2023 xsd:decimal [0..1]
epo:SubmissionStatisticalInformationepo:hasMediumTenderPerLotsTenders from medium-sized enterprise. + epo-ord:OrderLineDetails concerning a given unit of goods, services or works requested in the Order. - <u>Additional Information:</u> + Additional information: + In general, an Order Line contains the Quantity and Price of the goods, services and + goods requested in the Order. + However, in certain cases, the Price may not be known, as the Price may fluctuate + from one day to the other. - See Commission Recommendation 2003/361/EC. - xsd:integer [0..1]
epo:MultipleStageProcedureTermepo:hasMinimumNumberOfCandidatesMinimum number of candidates to be invited for the second stage of the procedure. + epo-ord:OrderResponseA formal reply from the Seller to the Buyer stating the Seller's ability to fulfil + the order. - WG Approval 22/08/2019 xsd:integer [0..1]
epo:SubcontractTermepo:hasMinimumShareThe minimum proportion of something to be distributed. + epo-ord:OrderResponseInformation
epo-ord:OrderResponseLineDetails concerning the Seller's ability to fulfil a given Order Line. Additional Information: - In the case of subcontracting the share may refer to the proportion of works, services - or supplies being subcontracted. + The Order Response Line is used to inform on the acceptance or rejection of an Order + Line or to make a counter-offer. - WG Approval 17/09/2019xsd:decimal [0..1]
epo:SubcontractTermepo:hasMinimumSubcontractorsProposedObligationThe minimum percentage of the contract value that the contractor must subcontract. + epo-ord:OriginatorA Role of an Agent that expresses the needs to trigger the Procurement. - Additional information: - This is used for the competitive procedure described in Title III of Directive 2009/81/EC. + Additional Information: + The Originator is often the end-user or the Beneficiary. + WG approval: 20/10/2022 - WG Approval 09/11/2021xsd:decimal [0..1]
epo:ProcedureTermepo:hasNationalProcedureRulesxsd:anyURI [0..*]epo-ord:OriginatorInformationInformation about the Originator of the Order. + + WG approval 20/03/2023
epo:StrategicProcurementepo:hasNonAccessibilityCriterionJustificationReason for not applying accessibility criteria. + epo-ord:SellerA Role of an Agent who transfers the ownership of the Procurement results (goods, + services or works) to the Buyer. Additional information: - This corresponds in eForma to BT-755 Accessibility Justification. + A Role of an Agent that sells a Procurement Result (goods, services or work) to a + Buyer. + The Seller is bound by a Contract i.e. it has legal responsibility. + The Seller may or may not be the same as the Supplier. + The Seller may or may not issue the Invoice. + The Seller may or may not be the owner of the credit owed by the Buyer. - WG Approval 05/03/2019rdf:PlainLiteral [0..*]
epo:LotAwardOutcomeepo:hasNonAwardedContractNumberThe 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. + epo-ord:TaxInformationInformation about the imposition of mandatory levies required by law. - WG agreement: 06/09/2022 + WG approval 25/04/2023 rdf:PlainLiteral [0..1]
epo:LotAwardOutcomeepo:hasNonAwardedContractTitleThe title the contract would have had if it had been awarded. + epo-sub:CertificateInformationInformation about a Certificate. - Additional information: + WG approval 12/03/2024
epo-sub:ESPDResponseA document conveying the fulfilment or not by the economic operator of the Exclusion + Grounds and the Selection Criteria set out by the Buyer for a specific Procurement + using an European Single Procurement Document (ESPD) Request. - This field is provided to support the data provided in the TED Standard Forms, and - it should be discontinued in the future. + WG Approval 05/03/2024
epo-sub:LegalRepresentativeThe Role of an Agent that can represent an Organization. - WG agreement: 06/09/2022rdf:PlainLiteral [0..1]
epo:SubmissionStatisticalInformationepo:hasNonEEAReceivedTendersThe amount of tenders received from economic operators in non-EEA countries. + epo-sub:MandateAn authorization to act as a representative of an Organization. - WG Approval 12/12/2019 15:20:36xsd:integer [0..1]
epo:MultipleStageProcedureTermepo:hasNoNegotiationNecessaryThe buyer reserves the right to award the contract on the basis of the initial tenders - without any further negotiations. + epo-sub:NationalPreQualificationDataData that describe the distinctive features or characteristics that qualify an economic + operator to take part in a tendering process. - Additional information: - See Article 29(4) of Directive 2014/24/EU. - xsd:boolean [0..1]
epo:SubmissionTermepo:hasNonElectronicSubmissionDescriptionTextual explanation of how non-electronic information is to be presented. + epo-sub:PowerOfAttorneyA legal document that grants someone the authority to make decisions on behalf of + an Organization. - WG Approval 21/07/2020 - - rdf:PlainLiteral [0..*]
epo:SubmissionStatisticalInformationepo:hasNonEUReceivedTendersThe amount of tenders received from economic operators in non-EU countries. - xsd:integer [0..1]epo-sub:ResponseAn answer given to a question that is part of an ESPD Request. + + WG approval 12/03/2024
epo:Noticeepo:hasNoticePublicationNumberrdf:PlainLiteral [0..1]foaf:AgentA Person, an Organisation, or a System that acts in Procurement or have the power + to act in Procurement. + + WG Approval 28/04/2020
epo:ReviewRequestepo:hasNumberOfReviewRequestsThe number of requests the buyer received to review any of its decisions.xsd:integer [1..1]foaf:PersonThe Person class represents people. Something is a Person if it is a Person. We don't + nitpick 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.
epo:SubmissionStatisticalInformationepo:hasNumberOfTenderersInvitedNumber of economic operators invited to tender. + locn:AddressThe particulars of the place where a Person or an Organisation is located. - 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 28/04/2020 - WG Approval 01/12/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.". - xsd:integer [0..1]
epo:Noticeepo:hasOJSIssueNumberxsd:integer [0..1]
epo:Noticeepo:hasOJSTyperdf:PlainLiteral [0..1]locn:GeometryThe 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.
epo:OpeningTermepo:hasOpeningDateTimeDate and time for the opening of tenders. - - WG Approval 12/03/2019 + org:OrganizationA 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). xsd:dateTime [1..1]
epo:OpeningTermepo:hasOpeningDescriptionFurther 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/2019rdf:PlainLiteral [0..*]person:PersonA individual human being who may be dead or alive, but not imaginary. +
epo:OpeningTermepo:hasOpeningURLThe identifier of the address of the Opening of Tenders. - WG Approval 09/11/2021xsd:anyURI [0..1]time:DurationDuration of a temporal extent expressed as a number scaled by a temporal unit.
+

Attributes (datatype properties) names and definitions

+ + - - - - + + + + + + - - - + + + - - - - - - - - - + + + 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. - - - - + + + + - - - + + + The weight must be between 0 and 1. Usually, all Criteria can be integrated within + a weighted sum equal to 1. - - - + + + - - - + + + - - - - + + + + - - - + + + + + + + + + - - - + + + - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
epo:ContractTermepo:hasOptionsThe buyer reserves the right (not an obligation) for additional purchases from the - contractor (while the contract is valid).xsd:boolean [0..1]Class nameAttribute nameDefinitionData type / cardinality
epo:ContractTermepo:hasOptionsDescriptionThe motivation and details about additional purchases that the buyer may undertake - while the contract is valid. - - WG Approval 09/04/2019 adms:Identifieradms:schemaAgencyThe name of the agency that issued the identifier. rdf:PlainLiteral [0..*]
epo:SubmissionStatisticalInformationepo:hasOtherCountriesReceivedTendersxsd:integer [0..1]
epo:AwardEvaluationTermepo:hasOverallCostAwardCriteriaPonderationThe weighting given to cost. + cccev:Criterioncccev:biasParameter used to adjust the evaluation of the Criterion. Additional Information: - This weighting covers usually all cost criteria against price or quality criteria. xsd:decimal [0..1]
epo:AwardEvaluationTermepo:hasOverallPriceAwardCriteriaPonderationThe weighting given to price. - - Additional Information: - This weighting covers usually all price criteria against cost or quality criteria.xsd:decimal [0..1]cccev:SupportedValuecccev:valueValue for the Information Concept that the Evidence supports.rdf:PlainLiteral [0..*]
epo:AwardEvaluationTermepo:hasOverallQualityAwardCriteriaPonderationThe weighting given to quality. + cccev:Criterioncccev:weightRelative importance of the Criterion. Additional Information: - This weighting covers usually all quality criteria against price or cost criteria. xsd:decimal [0..1]
epo:DesignContestRegimeTermepo:hasParticipationPaymentDetails on payments to participants - WG Approval 09/11/2021cccev:Criterioncccev:weightingConsiderationDescriptionExplanation 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. rdf:PlainLiteral [0..1]
epo:ContractTermepo:hasPaymentArrangementInformation 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. + cpov:ContactPointcpov:emailThe email of the Organisation. - WG Pending of discussion with eForms rdf:PlainLiteral [0..*]
epo:ContractLotCompletionInformationepo:hasPaymentValueDiscrepancyJustificationrdf:PlainLiteral [0..1]cpov:ContactPointcpov:telephoneA telephone number through which the Contact Point can be contacted. + rdf:PlainLiteral [0..*]
epo:ContractTermepo:hasPerformanceConditionsThe 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-2019person:Personcv:birthDateThe point in time on which the Person was born.xsd:date [0..1]
locn:Geometrycv:coordinatesThe coordinate list. rdf:PlainLiteral [0..*]
epo:ContractTermepo:hasPlaceOfPerformanceAdditionalInformationFurther details on the location of the execution of the contract. - - WG Approval 30/07/2019locn:Geometrycv:latitudeThe latitude. rdf:PlainLiteral [0..*]
epo:Prizeepo:hasPrizeRankThe position of the prize (e.g. first place, second place) in a design contest list - of prizes. + locn:Geometrycv:longitudeThe longitude.rdf:PlainLiteral [0..*]
person:Persondct:alternativeAny name by which an individual is known other than their full name. + WG 09/11/2021rdf:PlainLiteral [0..*]
cccev:Evidence
cccev:InformationConcept
cccev:Requirement
cpov:ContactPoint
cv:Channel
epo:AgentInRole
epo:Document
epo:ElectronicSignature
epo:Fund
epo:NonDisclosureAgreementTerm
epo:SecurityClearanceTerm
epo:SubcontractingEstimate
epo:SubcontractTerm
epo:System
epo:Technique
epo:LotGroup
epo:ProcurementElement
epo:TenderGroup
epo-cat:Line
epo-cat:Item
epo-ord:DeliveryAgreement
epo-ord:TaxInformation
epo-ful:ShipmentInformation
epo-ful:TemperatureSpecification
epo-ful:TransportEquipment
cccev:EvidenceTypeList
eli:LegalExpression
eli:LegalResource
epo-sub:CertificateInformation
dct:descriptionAn account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + An account of the resource. + + Additional Information: + Description may include but is not limited to: an abstract, a table of contents, a + graphical representation, or a free-text account of the resource. + + WG Approval 30/05/2023 + rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [1..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [1..1]
rdfs:Literal [0..*]
rdfs:Literal [1..1]
rdf:PlainLiteral [0..1]
eli:LegalExpression
eli:LegalResource
dct:identifierAn unambiguous reference to the resource within a given context. + An unambiguous reference to the resource within a given context. + xsd:anyURI [0..*]
xsd:anyURI [0..*]
epo:Documentdct:issuedDate of formal issuance of the resource. + + Additional information: + This is generally used for modules other than eNotice. + The xsd:dateTime here means that we can provide either xsd:date, xsd:dateTime, or + xsd:timeStamp or any other variant of time expression. This extension needs to be + encoded/automated in the ontology and in the application profile. + Why is it like this? Because UML cannot handle such expressions of disjunctive property + ranges. + + WG approval 26/01/2023xsd:dateTime [0..1]
epo:AgentInRole
epo:Document
epo:Fund
foaf:Agent
epo:LotGroup
epo:ProcurementElement
epo:TenderGroup
epo-cat:Brand
epo-cat:ItemModel
epo-cat:Item
eli:LegalExpression
dct:titleA name given to the resource. + + WG approval 30/05/2023 + A name given to the resource. + + WG approval 30/05/2023 + + A name given to the resource. + + WG approval 30/05/2023 + A name given to the resource. + + WG approval 30/05/2023 A name given to the resource. + + WG approval 30/05/2023 + A name given to the resource. + + WG approval 30/05/2023 A name given to the resource. + + WG approval 30/05/2023 + A name given to the resource. + + WG approval 30/05/2023 + A name given to the resource. + + WG approval 30/05/2023 A name given to the resource. + + WG approval 30/05/2023 A name given to the resource.rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
rdf:PlainLiteral [1..1]
rdf:PlainLiteral [1..1]
rdf:PlainLiteral [1..1]
rdfs:Literal [1..*]
eli:LegalExpression
eli:LegalResource
eli:numberAn identifier or other disambiguating feature for a legal resource or legal expression. + This can be the number of a legislation, the number of an article, or the issue number + of an official journal. An identifier or other disambiguating feature for a legal resource or legal expression. + This can be the number of a legislation, the number of an article, or the issue number + of an official journal.xsd:string [0..*]
xsd:string [0..*]
epo:SelectionCriteriaSummaryepo:describesMinimumLevelOfStandardsrdf:PlainLiteral [0..1]
epo:ParticipationConditionsSummaryepo:describesObjectiveParticipationRulesrdf:PlainLiteral [0..1]
epo:ProfessionalSuitabilitySummaryepo:describesProfessionrdf:PlainLiteral [0..1]
epo:ProfessionalSuitabilitySummaryepo:describesProfessionRelevantLawrdf:PlainLiteral [0..1]
epo:ParticipationConditionsSummaryepo:describesVerificationMethodrdf:PlainLiteral [0..1]
epo:SubmissionStatisticalInformationepo:hasAbnormallyLowTendersTenders 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:Procedureepo:hasAcceleratedProcedureJustificationThe 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 + + rdf:PlainLiteral [0..*]
epo:NonPublishedInformationepo:hasAccessibilityDateThe date at which unpublished data shall be published. + + WG Approval 11/06/2020xsd:date [0..1]
epo:Documentepo:hasAccessURLLocation where the resource can be accessed. + + WG approval 07/04/2022xsd:anyURI [0..*]
epo:Buyerepo:hasActivityDescriptionIn 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. + rdf:PlainLiteral [0..*]
epo:ChangeInformation
epo:Notice
epo:ProcurementCriterion
epo:ProcurementObject
epo:hasAdditionalInformationSupplementary data about the instance of the concept. + + WG Approval 15/10/2019 + Supplementary data about the instance of the concept. + + WG Approval 15/10/2019 Supplementary data about the instance of the concept. + + WG Approval 15/10/2019 Supplementary data about the instance of the concept. + + WG Approval 15/10/2019rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
epo:AccessTermepo:hasAdditionalInformationDeadlineThe 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:AwardDecisionepo:hasAdditionalNonAwardJustificationFurther justification for the non award . + + Additional information: + This is generally used when the non award reason code is set to "Other". + + WG: 18/01/2022rdf:PlainLiteral [0..1]
cv:Channelepo:hasAddressURLxsd:anyURI [0..1]
foaf:Agentepo:hasAliasAcronym or alternative name of the Agent. + WG Approval 25/03/2021rdf:PlainLiteral [0..*]
epo:MonetaryValueepo:hasAmountValueThe numeric value of the amount, including decimals.xsd:decimal [1..1]
epo:AwardEvaluationTermepo:hasAwardCriteriaEvaluationFormulaThe 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.rdf:PlainLiteral [0..*]
epo:AwardEvaluationTermepo:hasAwardCriteriaOrderJustificationThe 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.rdf:PlainLiteral [0..1]
epo:AwardCriterionepo:hasAwardCriteriaStatedInProcurementDocumentsxsd:boolean [1..1]
epo:ProcessPlanningTermepo:hasAwardDateScheduledPlanned date for the award decision. + WG Approval 09/11/2021xsd:date [0..1]
epo:AwardDecisionepo:hasAwardDecisionDateThe official date of the award decision. + + Additional Information: + This corresponds in eForms to BT-1451 Winner Decision Date. + + WG Approval 09/01/2020 + xsd:dateTime [0..1]
epo:TenderAwardOutcomeepo:hasAwardRankThe 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:Periodepo:hasBeginningThe date and time on which this period begins.xsd:dateTime [0..1]
epo:FrameworkAgreementTermepo:hasBuyerCategoryDescriptionA 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-06rdf:PlainLiteral [0..*]
org:Organizationepo:hasBuyerLegalTypeDescriptionSelf-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/2022rdf:PlainLiteral [0..1]
epo:Buyerepo:hasBuyerProfileWebsite 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:ConcessionEstimateepo:hasCalculationMethodFormula for obtaining values. + + Additional Information: + The possible values are monetary values, ranking scores, criterion weighting. + + WG Approval 25/05/2018rdf:PlainLiteral [0..1]
epo:Certificateepo:hasCertificationNumberThe unique identifier of the certificate. + + WG approval 26/07/2022rdf:PlainLiteral [0..1]
epo:ChangeInformationepo:hasChangeDescriptionExplanatory text about the instance of the concept. + + WG Approval 30/09/2019rdf:PlainLiteral [0..*]
epo:ChangeInformationepo:hasChangeReasonDescriptionExplanatory text about why the element is altered. + + Additional information: + This corresponds in eForms to BT-762 Change Reason Description.rdf:PlainLiteral [0..*]
epo:VehicleInformationepo:hasCleanVehiclesThe 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:QualificationCriteriaSummaryepo:hasConditionVerificationMethodrdf:PlainLiteral [0..*]
epo:NonPublishedInformationepo:hasConfidentialityJustificationA 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 + rdf:PlainLiteral [0..1]
cpov:ContactPointepo:hasContactNameA short text by which a contact is known or referred to. + + WG Approval: 27/01/2022rdf:PlainLiteral [0..1]
epo:Contractepo:hasContractConclusionDateThe 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/2020xsd:date [0..1]
epo:ProcedureTermepo:hasCrossBorderLawThe 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.rdf:PlainLiteral [0..*]
epo:MonetaryValueepo:hasCurrencyCodeListAgencyIDIdentifier of the agency that maintains the currency code list used. + WG approval 13/04/2021rdf:PlainLiteral [0..*]
epo:MonetaryValueepo:hasCurrencyCodeListAgencyNameName of the agency that maintains the currency code list used. + WG approval 13/04/2021rdf:PlainLiteral [0..*]
epo:MonetaryValueepo:hasCurrencyCodeListIDConcept scheme URI used for the currency code list. + WG approval 13/04/2021rdf:PlainLiteral [0..*]
epo:SecurityClearanceTermepo:hasDeadlineThe deadline by which the security clearance must be submitted to the buyer. + + WG Approval 12/09/2019 + + xsd:dateTime [0..1]
epo:ReviewDecisionepo:hasDecisionDateThe date of the review decision. + + Additional information: + This attribute corresponds to the BT-787 Review Date in eForms. + xsd:date [0..1]
epo:DesignContestRegimeTermepo:hasDescriptionOfPrizesrdf:PlainLiteral [0..1]
epo:Documentepo:hasDispatchDateDate and time of transmission of a record to an Organization. + + WG Approval 31/08/2023xsd:dateTime [0..1]
epo:FrameworkAgreementTermepo:hasDurationExtensionJustificationThe 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/2019rdf:PlainLiteral [0..1]
epo:SubmissionTermepo:hasEAuctionURLThe internet address of the electronic auction. + + Additional Information: + + This corresponds in eForms to BT-123 Electronic Auction URL.xsd:anyURI [0..1]
epo:SubmissionStatisticalInformationepo:hasEEAReceivedTendersThe amount of tenders received from economic operators in other EEA countries other + than the country of the buyer. + + WG Approval 12/12/2019xsd:integer [0..1]
epo:Noticeepo:hasEFormsSubtypexsd:integer [0..1]
epo:ContractTermepo:hasEInvoicingElectronic means will be used for invoicing in the post-award process. + + Additional Information: + This attribute is used for standard form mappings. + + WG Approval 12/09/2019 + xsd:boolean [0..1]
epo:Tenderepo:hasElectronicSubmissionTransmission of tenders is possible by electronic means of communication. xsd:boolean [0..1]
epo:SubmissionStatisticalInformationepo:hasElectronicTendersElectronic Tender Lots received. + + WG Approval 28/07/2020 + xsd:integer [0..1]
epo:ReviewObjectepo:hasElementReferenceReference 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 [0..*]
epo:Periodepo:hasEndThe date and time at which this period ends.xsd:dateTime [0..1]
epo:Contractepo:hasEntryIntoForceDateThe date on which the contract enters into force. + + Additional information: + + This is generally the date on which the fulfillment of the contract begins. + + This corresponds in eForms to + + WG approval 05/11/2019xsd:date [0..1]
epo:ContractTermepo:hasEOrderingElectronic means will be used for requesting and purchasing in the post-award process. + + WG Approval 12/09/2019 + + xsd:boolean [0..1]
epo:ContractTermepo:hasEPaymentElectronic means must be used for paying. + WG Approval 09/11/2021 + xsd:boolean [0..1]
epo:Noticeepo:hasESenderDispatchDateThe date and time the notice was transmitted electronically by the eSender to the + Publications Office of the European Union. + + Additional Information: + Typically, eSenders include national Official Journals, Buyers sending a large number + of electronic Notices, public or private bodies acting on behalf of Buyers and eProcurement + software developers. + + WG approval 20/06/2023xsd:dateTime [0..1]
epo:ProcessPlanningTermepo:hasEstimatedContractNoticePublicationDateForeseen date for publication of Contract Notice. + + Additional information: + This corresponds in eForms BT-127 Future Notice. + + xsd:date [0..1]
epo:MultipleStageProcedureTermepo:hasEstimatedInvitationToExpressInterestDateThe 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:MultipleStageProcedureTermepo:hasEstimatedInvitationToTenderDateThe 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/2019xsd:date [0..1]
epo:SubcontractingEstimateepo:hasEstimatedPercentageThe estimated proportion foreseen to be subcontracted. + + WG Approval 07/01/2020xsd:decimal [0..1]
epo:ProcessPlanningTermepo:hasEstimatedTenderInvitationDateThe planned date for the dispatch of the invitations to submit tenders. + WG Approval 09/11/2021xsd:date [0..1]
epo:SubmissionStatisticalInformationepo:hasEstimatedTotalSubcontractsThe estimated amount of work to be subcontracted in the contract resulting from the + lot. + WG Approval 09/11/2021xsd:integer [0..1]
epo:SubmissionStatisticalInformationepo:hasEUReceivedTendersThe amount of tenders received from economic operators in other EU countries other + than the country of the buyer.xsd:integer [0..1]
cpov:ContactPointepo:hasFaxThe fax number used to reach a person or an organisation.rdf:PlainLiteral [0..*]
epo:AwardCriterionepo:hasFixedValueThis corresponds in the eForms to BT-541 Award Criterion Number in association with + BT-5422 Award Criterion Number Fixed.xsd:decimal [0..1]
epo:DesignContestRegimeTermepo:hasFollowupContractAny 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:DesignContestRegimeTermepo:hasFollowupContractInformationFurther information about follow-up contracts, prizes and payments (for example non-monetary + prizes, payments given for participation). + + WG Approval 03/09/2019rdf:PlainLiteral [0..*]
epo:Noticeepo:hasFormNumberrdf:PlainLiteral [0..1]
epo:ProcurementCriterionepo:hasFormulaThe 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.rdf:PlainLiteral [0..1]
epo:ProcedureTermepo:hasGroupLotEvaluationMethodDescription of how lots and groups of lots are evaluated against one another in the + procedure. + + + + rdf:PlainLiteral [0..*]
epo:OrganisationGroupepo:hasGroupTypeForm of collaboration agreement between organisations. + + Additional Information: + This is not a legal type; not to be mistaken with epo:hasLegalFormType which may also + be used for Organisation Groups. + + WG Approval 09/11/2021rdf:PlainLiteral [0..*]
epo:SubmissionTermepo:hasGuaranteeDescriptionInformation 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 + rdf:PlainLiteral [0..*]
epo:SubmissionStatisticalInformationepo:hasInadmissibleTendersTenders 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/2019xsd:integer [0..1]
cpov:ContactPoint
org:Organization
epo:hasInternetAddressThe main web page used by the instance of the concept. + + WG Approval 01/06/2023 + + The main web page used by the instance of the concept. + + WG Approval 01/06/2023 + xsd:anyURI [0..1]
xsd:anyURI [0..*]
epo:DirectAwardTermepo:hasJustificationAn explanation about the reasons for using the concept. + WG Approval 5/11/2019 + rdf:PlainLiteral [0..*]
epo:SubmissionTermepo:hasLateSubmissionInformationDescriptionA 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. + rdf:PlainLiteral [0..*]
epo:ProcurementObjectepo:hasLegalBasisDescriptionrdf:PlainLiteral [0..*]
epo:ContractTermepo:hasLegalFormRequirementThe legal form to be taken by a Contractor. + + Additional Information: + Generally, this is defined to cover the case where an Organisation Group is involved. + Note that the codelist provided at national level should be used.rdf:PlainLiteral [0..1]
org:Organizationepo:hasLegalFormTypeThe classification of an Organisation according to legislation. + + Additional Information: + Generally, this is defined for Tenderers who want to submit as an Organisation Group. + Note that the codelist provided at national level should be used. + rdf:PlainLiteral [0..1]
org:Organizationepo:hasLegalNameThe officially registered name of an organisation. + + WG Approval 10/01/2023rdf:PlainLiteral [0..*]
epo:ProcedureTermepo:hasLotAwardCombinationThe 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 + rdf:PlainLiteral [0..1]
org:Organizationepo:hasMainActivityDescriptionSelf-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 + rdf:PlainLiteral [0..1]
epo:Procedureepo:hasMainFeatureMain 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.rdf:PlainLiteral [0..*]
epo:ProcedureTermepo:hasMaximumLotSubmissionAllowedThe 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:MultipleStageProcedureTermepo:hasMaximumNumberOfCandidatesMaximum number of candidates to be invited for the second stage of the procedure. + + WG Approval 22/08/2019xsd:integer [0..1]
epo:ProcedureTermepo:hasMaximumNumberOfLotsToBeAwardedThe 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/2019xsd:integer [0..1]
epo:ContractTermepo:hasMaximumNumberOfRenewalsThe 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:FrameworkAgreementTermepo:hasMaximumParticipantsNumberThe 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-05xsd:integer [0..1]
epo:SubcontractTermepo:hasMaximumShareThe 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:SubmissionStatisticalInformationepo:hasMediumTenderPerLotsTenders from medium-sized enterprise. + + <u>Additional Information:</u> + + See Commission Recommendation 2003/361/EC. + xsd:integer [0..1]
epo:MultipleStageProcedureTermepo:hasMinimumNumberOfCandidatesMinimum number of candidates to be invited for the second stage of the procedure. + + WG Approval 22/08/2019 xsd:integer [0..1]
epo:SubcontractTermepo:hasMinimumShareThe 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/2019xsd:decimal [0..1]
epo:SubcontractTermepo:hasMinimumSubcontractorsProposedObligationThe 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/2021xsd:decimal [0..1]
epo-con:ContractModificationInformationepo:hasModificationDescriptionAn 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 + rdf:PlainLiteral [0..1]
epo-con:ContractModificationInformationepo:hasModificationReasonDescriptionAn 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 + rdf:PlainLiteral [0..1]
epo:ProcedureTermepo:hasNationalProcedureRulesxsd:anyURI [0..*]
epo:StrategicProcurementepo:hasNonAccessibilityCriterionJustificationReason for not applying accessibility criteria. + + Additional information: + This corresponds in eForma to BT-755 Accessibility Justification. + + WG Approval 05/03/2019rdf:PlainLiteral [0..*]
epo:LotAwardOutcomeepo:hasNonAwardedContractNumberThe 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 + rdf:PlainLiteral [0..1]
epo:LotAwardOutcomeepo:hasNonAwardedContractTitleThe 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/2022rdf:PlainLiteral [0..1]
epo:SubmissionStatisticalInformationepo:hasNonEEAReceivedTendersThe amount of tenders received from economic operators in non-EEA countries. + + WG Approval 12/12/2019 15:20:36xsd:integer [0..1]
epo:MultipleStageProcedureTermepo:hasNoNegotiationNecessaryThe 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:SubmissionTermepo:hasNonElectronicSubmissionDescriptionTextual explanation of how non-electronic information is to be presented. + + WG Approval 21/07/2020 + + rdf:PlainLiteral [0..*]
epo:SubmissionStatisticalInformationepo:hasNonEUReceivedTendersThe amount of tenders received from economic operators in non-EU countries. + xsd:integer [0..1]
epo:Noticeepo:hasNoticePublicationNumberrdf:PlainLiteral [0..1]
epo:ReviewRequestepo:hasNumberOfReviewRequestsThe number of requests the buyer received to review any of its decisions.xsd:integer [1..1]
epo:SubmissionStatisticalInformationepo:hasNumberOfTenderersInvitedNumber 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:Noticeepo:hasOJSIssueNumberxsd:integer [0..1]
epo:Noticeepo:hasOJSTyperdf:PlainLiteral [0..1]
epo:OpeningTermepo:hasOpeningDateTimeDate and time for the opening of tenders. + + WG Approval 12/03/2019 + + xsd:dateTime [1..1]
epo:OpeningTermepo:hasOpeningDescriptionFurther 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/2019rdf:PlainLiteral [0..*]
epo:OpeningTermepo:hasOpeningURLThe identifier of the address of the Opening of Tenders. + WG Approval 09/11/2021xsd:anyURI [0..1]
epo:ContractTermepo:hasOptionsThe buyer reserves the right (not an obligation) for additional purchases from the + contractor (while the contract is valid).xsd:boolean [0..1]
epo:ContractTermepo:hasOptionsDescriptionThe motivation and details about additional purchases that the buyer may undertake + while the contract is valid. + + WG Approval 09/04/2019 rdf:PlainLiteral [0..*]
epo:SubmissionStatisticalInformationepo:hasOtherCountriesReceivedTendersxsd:integer [0..1]
epo:AwardEvaluationTermepo:hasOverallCostAwardCriteriaPonderationThe weighting given to cost. + + Additional Information: + This weighting covers usually all cost criteria against price or quality criteria.xsd:decimal [0..1]
epo:AwardEvaluationTermepo:hasOverallPriceAwardCriteriaPonderationThe weighting given to price. + + Additional Information: + This weighting covers usually all price criteria against cost or quality criteria.xsd:decimal [0..1]
epo:AwardEvaluationTermepo:hasOverallQualityAwardCriteriaPonderationThe weighting given to quality. + + Additional Information: + This weighting covers usually all quality criteria against price or cost criteria.xsd:decimal [0..1]
epo:DesignContestRegimeTermepo:hasParticipationPaymentDetails on payments to participants + WG Approval 09/11/2021rdf:PlainLiteral [0..1]
epo:ContractTermepo:hasPaymentArrangementInformation 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 eFormsrdf:PlainLiteral [0..*]
epo:ContractLotCompletionInformationepo:hasPaymentValueDiscrepancyJustificationrdf:PlainLiteral [0..1]
epo:ContractTermepo:hasPerformanceConditionsThe 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-2019rdf:PlainLiteral [0..*]
epo:ContractTermepo:hasPlaceOfPerformanceAdditionalInformationFurther details on the location of the execution of the contract. + + WG Approval 30/07/2019rdf:PlainLiteral [0..*]
epo:Prizeepo:hasPrizeRankThe 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:ChangeInformationepo:hasProcurementDocumentChangeDateThe 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:dateTime [0..1]
epo:AccessTermepo:hasPublicAccessURLWeb 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:Documentepo:hasPublicationDateDate of formal public issuance of the document. + + WG approval 20/06/2023xsd:date [0..1]
epo:QualificationCriteriaSummaryepo:hasQualificationConditionrdf:PlainLiteral [0..*]
epo:MultipleStageProcedureTermepo:hasQualificationSystemRenewalDescriptionrdf:PlainLiteral [0..1]
epo:Quantityepo:hasQuantityValueThe numeric value of the quantity, including decimals.xsd:decimal [1..1]
epo:SubmissionTermepo:hasReceiptDeadlineThe 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. + This attribute should be used for standard forms mappings. + + WG Approval 21/07/2020 + xsd:dateTime [0..1]
epo:SubmissionTermepo:hasReceiptExpressionDeadlineTime limit for receipt of expressions of interest. + + Pending of review by the WG + + xsd:dateTime [0..1]
epo:SubmissionTermepo:hasReceiptParticipationRequestDeadlinexsd:dateTime [0..1]
epo:SubmissionTermepo:hasReceiptPreliminaryMarketConsultationDeadlinexsd:dateTime [0..1]
epo:SubmissionTermepo:hasReceiptTenderDeadlinexsd:dateTime [0..1]
epo:SubmissionStatisticalInformationepo:hasReceivedMicroTendersThe amount of tenders received from a micro enterprise. + + <u>Additional Information:</u> + + See Commission Recommendation 2003/361/EC.xsd:integer [0..1]
epo:SubmissionStatisticalInformationepo:hasReceivedParticipationRequestsThe amount of applications to participate from economic operators. + + WG Approval 12/12/2019xsd:integer [0..1]
epo:SubmissionStatisticalInformationepo:hasReceivedSmallTendersTenders from small enterprise. + + <u>Additional Information:</u> + + See Commission Recommendation 2003/361/EC. + + xsd:integer [0..1]
epo:SubmissionStatisticalInformationepo:hasReceivedTendersThe total amount of tenders received. + + WG Approval 12/12/2019xsd:integer [0..1]
epo:Documentepo:hasReceptionDateNotes: Date when a record is acknowledged by an organisation. + + WG Approval 12/05/2020xsd:date [0..1]
epo:ProcurementObjectepo:hasRecurrenceDescriptionAny 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) + rdf:PlainLiteral [0..1]
epo:CertificationLabelepo:hasReferenceURIA reference to where the label specification (norms, expectations, standards and policies) + can be found. + + WG approval 26/07/2022xsd:anyURI [0..1]
epo:ContractTermepo:hasRenewalDescriptionAny other information about the renewal(s). + + WG approval 16/04/2019 rdf:PlainLiteral [0..*]
epo:ReviewRequestepo:hasRequestDateThe 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:AccessTermepo:hasRestrictedAccessURLThe 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:ReviewTermepo:hasReviewDeadlineThe time limit for review procedures. + + WG Approval 09/11/2021xsd:dateTime [0..1]
epo:ReviewTermepo:hasReviewDeadlineInformationThe description of the time limits for review procedures. + + WG Approval 01/10/2019rdf:PlainLiteral [0..*]
epo:ReviewIrregularitySummaryepo:hasReviewIrregularityCountThe 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:ReviewTermepo:hasReviewProcedureThe description of the method used to request the verification that the procedure + has been carried out correctly. + + WG Approval 09/11/2021rdf:PlainLiteral [0..*]
epo:ReviewObjectepo:hasReviewURLThe 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]
adms:Identifierepo:hasSchemeThe name of the identification scheme.rdf:PlainLiteral [0..*]
adms:Identifierepo:hasSchemeVersionThe version of the identification scheme.rdf:PlainLiteral [0..*]
epo:SelectionCriteriaSummaryepo:hasSelectionCriteriaStatedInProcurementDocumentsxsd:boolean [0..1]
epo:ProfessionalSuitabilitySummaryepo:hasServiceReservedToParticularProfessionxsd:boolean [0..1]
epo:SubmissionStatisticalInformationepo:hasSMEReceivedTendersThe 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:SubmissionStatisticalInformationepo:hasSMEReceivedTendersExcludingSubcontractorsxsd:integer [0..1]
epo:StrategicProcurementepo:hasStrategicProcurementDescriptionSelf-explanatory text about a concept. + rdf:PlainLiteral [0..*]
epo:SubcontractTermepo:hasSubcontractingInvolvedList 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/2019xsd:boolean [0..1]
epo:SubcontractTermepo:hasSubcontractorsProposedAboveObligationThe 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/2021xsd:decimal [0..1]
epo:SubcontractingEstimateepo:hasSubjectMatterDescription 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/2021rdf:PlainLiteral [0..*]
epo:SubmissionTermepo:hasSubmissionURL + Additional Information: + This corresponds to the eForms BT-18 Submission URL. + + This corresponds in eForms to BT-509 Organisation eDelivery Gateway.xsd:anyURI [0..*]
epo:MultipleStageProcedureTermepo:hasSuccessiveReductionThe 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:Constraintepo:hasThresholdValueThe 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:ReviewRequestSummaryepo:hasTotalNumberOfComplainantsThe 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/2019xsd:integer [0..1]
epo:VehicleInformationepo:hasTotalVehiclesThe 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:Quantityepo:hasUnitDescriptionA 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/2021rdf:PlainLiteral [0..*]
epo:SubmissionStatisticalInformationepo:hasUnverifiedTendersOffers 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]
cccev:Evidence
epo:Fund
epo:hasURLThe 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/2019xsd:anyURI [0..1]
xsd:anyURI [0..1]
epo:Documentepo:hasVersionA number that identifies a specific state of a document. + + WG approval: 18/11/2021 + rdf:PlainLiteral [0..1]
epo:ReviewRequestepo:hasWithdrawalDateThe 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:ReviewRequestepo:hasWithdrawalReasonThe explanation for withdrawing the request for review. + + Additional information: + This attribute corresponds in eForms to BT-798 Review Request Withdrawn Reasonsrdf:PlainLiteral [0..1]
epo:VehicleInformationepo:hasZeroEmissionVehiclesThe 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:ProcurementCriteriaSummaryepo:indicatesPerformingStaffInformationRequirementxsd:boolean [0..1]
epo:Procedureepo:isAcceleratedStatement 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]
epo:SubmissionTermepo:isAdvancedElectronicSignatureRequiredAdvanced 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:ProcedureTermepo:isAwardedByCPBProcedure is awarded by a Central Purchasing Body. + + xsd:boolean [0..1]
epo:ProcurementProcessInformationepo:isCompetitionTerminatedNo 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:Buyerepo:isContractingEntityRole 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:ProcurementObjectepo:isCoveredByGPASpecifies 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:Procedureepo:isDesignContestA 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:ProcurementProcessInformationepo:isDPSTerminatedEnd 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:SubmissionTermepo:isGuaranteeRequiredThe 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:Procedureepo:isJointProcurementMultiple 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:DesignContestRegimeTermepo:isJuryDecisionBindingIndicates whether the procuring entity is bound to apply the decision of the jury.xsd:boolean [0..1]
epo:Businessepo:isListedCompanyPublic 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/2019xsd:boolean [0..1]
epo:SubmissionTermepo:isMultipleTenderSubmissionAllowedTenderers may submit more than one competing tenders. + + WG Approval 10/10/2019 + + xsd:boolean [0..1]
epo:NonDisclosureAgreementTermepo:isNonDisclosureAgreementRequiredxsd:boolean [0..1]
epo:ProcedureTermepo:isOneLotOnlyAllowedIndicates 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:ChangeInformationepo:isProcurementDocumentChangedOne or more procurement documents have been changed. + + Additional information: + This corresponds in eForms to BT-718 Change Procurement Documents + + WG Approval 05/11/2019xsd:boolean [0..1]
epo:AccessTermepo:isProcurementDocumentRestrictedThe access to certain procurement documents is restricted. + + Additional Information: + This corresponds in eForms to BT-14 Documents Restricted. + + WG Approval 10/10/2019xsd:boolean [0..1]
epo:ProcurementObjectepo:isRecurrentThe 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:ContractTermepo:isRenewalIndicatorIndicates whether the contract is subject to a renewal clause. + WG Approval 09/11/2021xsd:boolean [0..1]
epo:SecurityClearanceTermepo:isSecurityClearanceRequiredxsd:boolean [0..1]
epo:ProcurementObjectepo:isSMESuitableThe 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:ProcedureTermepo:isSubmissionForAllLotsRequiredIndicates whether tenders must be submitted for all Lots. + xsd:boolean [0..1]
epo:ProcurementProcessInformationepo:isToBeRelaunchedIndicator 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:SelectionCriterionepo:isUsedForCandidateRestrictionThe 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 Invitexsd:boolean [0..1]
epo:ProcurementObjectepo:isUsingEUFundsThe procurement foresees funding by the Union. + + Additional Information: + The funding may cover the whole procurement or part of the procurement. + + For example the European Structural and Investment Funds or grants awarded by the + European Union. + + xsd:boolean [0..1]
epo:Tenderepo:isVariantAlternative 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:ReviewRequestepo:isWithdrawnThe review request was withdrawn. + + Additional information: + This attribute corresponds in eForms to BT-796 Review Request Withdrawn.xsd:boolean [0..1]
epo:GreenProcurementepo:usesCleanVehicleDirectiveThe procurement falls within the scope of the European Parliament and Council 2009/33/EC + (Clean Vehicles Directive – CVD).xsd:boolean [0..1]
epo-cat:ItemPropertyepo-cat:hasAttributeTypeThe property defined in a classification scheme. + + Additional Information: + For example, the following two properties are defined in the ECLASS classification + of goods and services: (0173-1#02-AAA026#007) drilling diameter: drilling diameter, + (0173-1#02-AAA030#007) flange diameter: flange diameter . + + + WG approval 28/07/2022rdf:PlainLiteral [1..1]
epo-cat:Batchepo-cat:hasBestBeforeDateThe day until which the quality of the item will remain optimal. + + WG approval 10/03/2021xsd:date [0..1]
epo-cat:ItemPropertyepo-cat:hasClassificationSchemeThe classification scheme where a property is defined. + + Additional Information: + For example, the following two properties are defined in the ECLASS classification + of goods and services: (0173-1#02-AAA026#007) drilling diameter: drilling diameter, + (0173-1#02-AAA030#007) flange diameter: flange diameter . + + WG approval 28/07/2022 + rdf:PlainLiteral [1..1]
epo-cat:Itemepo-cat:hasDimensionDescriptionTextual description of the item's dimensions.rdf:PlainLiteral [0..*]
epo-cat:Batchepo-cat:hasExpiryDateThe last day until which the item can be used. + + WG approval 10/03/2021 + xsd:date [0..1]
epo-cat:ItemRelationepo-cat:hasFactorThe number or the fraction of a related item. xsd:decimal [0..1]
epo-cat:Itemepo-cat:hasHazardousClassSpecification of the hazardous nature of an item according to a classification schema. + Provides detail of the classification and nature of a hazardous item.rdf:PlainLiteral [0..*]
epo-cat:Itemepo-cat:hasKeywordList of words (e.g, synonyms) to make the item searchable. + + WG Approval 7/04/2022 + rdf:PlainLiteral [0..*]
epo-cat:ItemPropertyepo-cat:hasLiteralValueSimple value of the property, which is defined in a classification scheme. + + Additional Information: + For example, the (0173-1#02-AAV139#001) coating 1 of an optical material has value + of "silver". + + This simple literal value is for the cases when the property value does not have units, + in which case the qualifiedValue shall be used. + + WG approval 28/07/2022 + + + rdf:PlainLiteral [0..1]
epo-cat:Batchepo-cat:hasManufactureDateThe day of production. + xsd:dateTime [0..1]
epo-cat:CatalogueLineepo-cat:hasOrderableQuantityIncrementOrderable quantity increment: The increment of Orderable units that can be ordered.xsd:integer [0..1]
epo-cat:CatalogueLineepo-cat:hasOrderableUnitFactorRateThe factor by which the Item net price of an unit of an item can be converted to the + orderable unit.xsd:decimal [0..1]
epo-ord:AllowanceChargeInformation
epo-ord:TaxInformation
epo-cat:hasPercentageThe factor relative to the price charged in addition. + + WG approval 26/07/2022 The factor relative to the price charged in addition. + + WG approval 26/07/2022 + xsd:decimal [0..1]
xsd:decimal [0..1]
epo-cat:Catalogueepo-cat:hasSpecificPaymentArrangementInformation about payment conditions applied to all items in the catalogue. + + Additional information: + This property may need to be used together with the payment arrangements provided + in the ContractTerms, where such terms exists. + + WG approval 30/06/2022 + + rdf:PlainLiteral [0..1]
epo-cat:CatalogueLineepo-cat:hasTransactionConditionsTextual description of the specific transaction conditions (purchasing, sales, payment) + for an item.rdf:PlainLiteral [0..1]
epo-cat:CatalogueLineepo-cat:hasWarrantyInformationWarranty information that applies to the catalogue line item.rdf:PlainLiteral [0..1]
epo-cat:CatalogueLineepo-cat:isContractedItemIndicator if the item is offered in accordance to an existing contract.xsd:boolean [0..1]
epo-cat:Itemepo-cat:isInStockIndicator whether an item is in the supplier's stock. If not in stock the supplier + has to order the item.xsd:boolean [0..1]
epo-cat:CatalogueLineepo-cat:isOrderableIndicator, if the item is orderable or not, e.g. because it is temporarily out of + stock.xsd:boolean [0..1]
epo-ful:ShipmentInformationepo-ful:despatchDatexsd:dateTime [0..1]
epo-ord:AllowanceChargeInformationepo-ful:hasAllowanceChargeReasonDescriptionrdf:PlainLiteral [0..*]
epo-ful:Consignmentepo-ful:hasCarrierServiceInstructionrdf:PlainLiteral [0..*]
epo-ful:Consignmentepo-ful:hasDeliveryInstructionrdf:PlainLiteral [0..*]
epo-ful:Consignment
epo-ful:TransportHandlingUnit
epo-ful:hasHandlingInstruction rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..*]
epo-ful:DespatchLineepo-ful:hasOutstandingQuantityReasonrdf:PlainLiteral [0..1]
epo-ful:Packageepo-ful:hasPackagingTypeDescriptionrdf:PlainLiteral [0..1]
epo-ful:TransportHandlingUnitepo-ful:hasShippingMarkrdf:PlainLiteral [0..*]
epo-ful:Consignmentepo-ful:hasSpecialInstructionrdf:PlainLiteral [0..*]
epo-ful:Consignmentepo-ful:hasSpecialServiceInstructionrdf:PlainLiteral [0..*]
epo-ful:Consignmentepo-ful:hasVehicleDescriptionrdf:PlainLiteral [0..1]
epo-ful:AbstractContainer
epo-ful:Consignment
epo-ful:ShipmentStage
epo-ful:isHazardousRisk xsd:boolean [0..1]
xsd:boolean [0..1]
xsd:boolean [0..1]
epo-ful:TransportEquipmentepo-ful:isPowerIndicatedxsd:boolean [0..1]
epo-ful:TransportEquipmentepo-ful:isRefrigeratedxsd:boolean [0..1]
epo-ful:TransportEquipmentepo-ful:isReturnablexsd:boolean [0..1]
epo-ful:AbstractContainerepo-ful:isReturnableMaterialxsd:boolean [0..1]
epo-ord:Orderepo-ord:hasAccountingCostThe accounting reference used by the Buyer to specify the account to which the order + and the corresponding invoice are booked. + + WG approval 2023-01-26rdf:PlainLiteral [0..1]
epo-ord:Orderepo-ord:hasCustomerReferenceA supplementary reference for the order. + + Additional information: + This information can be used for the buyer's internal processes. + This reference can also be used in the invoice. + + WG approval 2023-01-26xsd:boolean [0..1]
epo-ord:DeliveryInformationepo-ord:hasDeliveryDeadlinexsd:dateTime [0..1]
epo-ord:Orderepo-ord:hasPaymentTermrdf:PlainLiteral [0..1]
epo-ord:OrderResponseepo-ord:hasResponseDescriptionResponse clarification of the Supplier decision. rdf:PlainLiteral [0..1]
epo-ord:DeliveryInformationepo-ord:hasShippingMarkrdf:PlainLiteral [0..*]
epo-sub:CertificateInformationepo-sub:coversAllSelectionCriteriaIndicator that the Certificate proves whether the Organization fulfils all Selection + Criteria. + + WG approval 12/03/2024xsd:boolean [0..1]
epo-sub:NationalPreQualificationDataepo-sub:providesOrganisationCompletedTaskDescriptionText describing the works, supplies or services executed, delivered or performed in + a procurement project that can be used as an evidence for the classification of the + Organization. + + WG approval 05/03/2024rdf:PlainLiteral [0..1]
person:Personfoaf:familyNameThe hereditary surname of a family. + rdf:PlainLiteral [0..*]
person:Personfoaf:givenNameThe name(s) that identify the Person within a family with a common surname. + rdf:PlainLiteral [0..*]
person:Personfoaf:nameThe complete name of the Person as one string.rdf:PlainLiteral [0..*]
locn:Addresslocn:addressAreaThe 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.rdf:PlainLiteral [0..1]
locn:Addresslocn:adminUnitL1The 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.rdf:PlainLiteral [0..1]
locn:Addresslocn:adminUnitL2The 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. + rdf:PlainLiteral [0..1]
locn:Addresslocn:fullAddressThe 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".rdf:PlainLiteral [0..1]
dct:Locationlocn:geographicNameA 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. + rdf:PlainLiteral [0..1]
locn:Addresslocn:locatorDesignatorA 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".rdf:PlainLiteral [0..1]
locn:Addresslocn:locatorNameProper 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.rdf:PlainLiteral [0..1]
locn:Addresslocn:postCodeThe 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".rdf:PlainLiteral [0..1]
locn:Addresslocn:postNameThe 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".rdf:PlainLiteral [0..1]
locn:Addresslocn:thoroughfareAn 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".rdf:PlainLiteral [0..1]
person:Personperson:birthNameFamily name of the Person given upon their birth. + WG Approval 09/11/2021rdf:PlainLiteral [0..*]
person:Personperson:patronymicNameName based on the given name of the Person's father. + WG Approval 09/11/2021rdf:PlainLiteral [0..*]
adms:Identifierskos:notationThe literal identifying an entity, like a person or an object.rdf:PlainLiteral [1..1]
cccev:InformationConcept
cccev:Requirement
cccev:EvidenceTypeList
skos:prefLabelThe preferred lexical label for a resource, in a given language. + + WG approval 30/05/2023 + + The preferred lexical label for a resource, in a given language. + + WG approval 30/05/2023 The preferred lexical label for a resource, in a given language. + + WG approval 30/05/2023 + rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
rdf:PlainLiteral [0..*]
epo:SpecificDurationtime:numericDurationValue of a temporal extent expressed as a number.xsd:decimal [1..1]
+

Predicates (object properties) and definitions

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - + - - - + + + + + + + + + + + + + + + + - + - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - + - - - + - + WG approval 30/05/2023 Relation to the proof of conformance. + + WG approval 30/05/2023 Relation to the proof of conformance. + + WG approval 30/05/2023 + - - + + + + + + - + - - + + + + + + + + + + + - + - - - - + + + - - - + + + + + + + + + + + + + + + + + + + + + - + - - - + - + - - + + + + + + + + + + + - + + + + + + + + + + + + + + + + - - + - + - - + - + - - - + - - - - - - - + WG Approval 07/01/2020 + - - - + - + - - - + - - - - - - - + This corresponds to BT-162 in eForms. + + - - - + - - - - - - - - - - - - - - - - - - - - - - - - - + - - - + - - - - - - - + + - - - + - - - - - - - + This corresponds to BT-720 in eForms. + - - - + - - - - - - - - - - - - - + - - - - + + + - - + - + - - - + - + - - + - + - - - - + + + - - - + - - - - - - - + + + - - - - + + + - - - - + + + - - - - + + + - - - + - - - - - - - + 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 + - - - + - + WG approval 16/05/2023 + - - - - + + + - - - + - + - - - + + + + + + + + + + + - + The codelist to be used is at-voc:legal-basis which is available at http://publications.europa.eu/resource/dataset/legal-basis + + - - - - + + + - - - - + + + - - - + - + 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 + + + - - - + - + - - + - + - - - + + + + + + + + + + + - + 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 + + + + + + - - - + - + - - - + - + - - - + - + + - - - + + + + + + + + + + + + + + + + + + + + + - + - - - + - + - - - + + + + + + + + + + + + + + + + + + + + + - + + - - - + - + - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - + - - - - + + + + + + + + + + + + + + + + + + + + + + + - - - - + + + - - - + - - - - - - - + - - - - + + + - - - + - + - - - - + + + - - - - + + + - - - + + + + + + - + - - - - + + + - - + - + - - - + - + - - - + + + + + + - + - - - + - + - - - + - + + - - - + - + - - - + - + - - - - + + + - - - - + + + - - - + - + - - - + - - - - - - - - - - - - - + - - - + - - - - - - - + - - - + - + WG approval 30/05/2023 The relation indicating until when a given instance of a concept is applicable. + + WG approval 30/05/2023 + The relation indicating until when a given instance of a concept is applicable. + + WG approval 30/05/2023 + - - - + - + - - - + - + + + - - - + - + + - - - + - + In the ESPD, a Subcriterion is used to define national sub-criteria; maps to a UBL-2.3 + cac:SubTenderingCriterion class. It is currently used only for purely national criteria, + to be able to establish the mapping from eCertis. + + WG approval 07/11/2023 + + + - - - - + + + - - - - + + + - - - - + + + - - - - + + + - - - - + + + - - - + - + WG Acceptance 06/09/2022 + - - - - + + + - -
Predicate nameDefinitionDomain, Range and Cardinality
adms:identifierLinks a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. 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 + + Links a resource to an adms:Identifier class. 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 + Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class.cccev:Evidence -> adms:Identifier [1]
cccev:InformationConcept -> adms:Identifier [0..1]
cccev:Requirement -> adms:Identifier [0..1]
dct:Location -> adms:Identifier [0..1]
epo:Document -> adms:Identifier [0..*]
epo:Fund -> adms:Identifier [0..1]
epo:Project -> adms:Identifier [0..1]
foaf:Agent -> adms:Identifier [0..*]
epo:LotGroup -> adms:Identifier [0..1]
epo:ProcurementElement -> adms:Identifier [1]
epo:TenderGroup -> adms:Identifier [0..1]
cccev:EvidenceType -> adms:Identifier [0..1]
epo-ful:Consignment -> adms:Identifier [0..1]
epo-ful:TransportEquipment -> adms:Identifier [0..1]
epo-ful:ShipmentStage -> adms:Identifier [0..1]
epo-ful:TransportEquipmentSeal -> adms:Identifier [0..1]
cccev:EvidenceTypeList -> adms:Identifier [0..1]
epo-ful:ShipmentInformation -> adms:Identifier [0..1]
epo-cat:Line -> adms:Identifier [0..1]
epo-ful:AbstractContainer -> adms:Identifier [0..1]
cccev:confidentialityLevelTypeSecurity 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. + 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:access-rights [0..1]
epo-sub:Response -> at-voc:access-rights []
cccev:constrainsInformation 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:hasConceptInformation Concept for which a value is expected by the Requirement. + + Additional Information: + Information Concepts defined for specific Requirements also represent the basis for + specifying the Supported Value an Evidence should provide. cccev:Requirement -> cccev:InformationConcept [0..*]
cccev:hasEvidenceTypeListEvidence Type List that specifies the Evidence Types that are needed to meet the Requirement. + + Additional Information: + One or several Lists of Evidence Types can support a Requirement. At least one of + them must be satisfied by the response to the Requirement.cccev:Requirement -> cccev:EvidenceTypeList [0..*]
cccev:hasRequirementA more specific Requirement that is part of the Requirement.cccev:Requirement -> cccev:Requirement [0..*]
cccev:isDerivedFromReference Framework on which the Requirement is based, such as a law or regulation. + + Additional Information: + The relation between a parent Requirement and a sub-Requirement can be complex. Therefore, + qualified relations (see hasQualifiedRelation) can be used to represent this relationship + on its own and qualify it with additional information such as a date, a place. This + is left to implementers. In the case where the purpose is to link the two Requirements + without additional information, the simple relationship as proposed here can be directly + used.cccev:Requirement -> eli:LegalResource []
cccev:providesValueForInformation Concept for which the Supported Value provides a value.cccev:SupportedValue -> cccev:InformationConcept [0..*]
cccev:specifiesEvidenceTypeEvidence Type included in this Evidence Type List.cccev:EvidenceTypeList -> cccev:EvidenceType [0..*]
cccev:supportsConceptInformation Concept providing facts found/inferred from the Evidence. + + Additional Information: + Examples of Information Concepts are values found explicitly 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 Fair Trade product".cccev:Evidence -> cccev:InformationConcept [0..*]
cccev:supportsRequirementRequirement for which the Evidence provides proof.cccev:Evidence -> cccev:Requirement [0..*]
cccev:supportsValueSupported Value that the Evidence contains. Supported Value that the Evidence contains.cccev:Evidence -> cccev:SupportedValue [0..*]
epo-sub:Response -> cccev:SupportedValue [0..*]
cccev:validityPeriodConstraintTemporal condition on the validity period of the Evidence Type. + + Additional Information: + E.g. A Belgian birth evidence is valid for X months after emission. To express constraints + on the validity period that must hold when assessing the evidence (e.g. the certificate + of good conduct cannot be issued more than 3 months ago), we refer to the Constraint + class.cccev:EvidenceType -> epo:Period [0..*]
cv:registeredAddressThe 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. 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. + person:Person -> locn:Address [0..1]
org:Organization -> locn:Address [0..1]
dct:conformsToAn established standard to which the described resource conforms. + + Additional Information: + Examples of characteristics could be the layout or the configuration of the Evidence.cccev:Evidence -> cccev:EvidenceType [0..*]
dct:hasPartA related resource that is included either physically or logically in the described + resource. + + Additional Information: + In the eCatalogue context, when this relation is used between two items, the resource + in the definition refers to Items, i.e. one item is part of another item. + + WG Approval: 30/06/2022 + epo-cat:Item -> epo-cat:Item [0..*]
dct:isPartOfA related resource in which the described resource is physically or logically included.eli:Work -> eli:Work [0..*]
dct:isReplacedByA related resource that is supplanted, displaced, or superseded by the described resource. + + Additional Information: + In the eCatalogue context, when this relation is used between two items, the resource + in the definition refers to Items, i.e. one item replaces another item. + + WG Approval: 30/06/2022 + A related resource that is supplanted, displaced, or superseded by the described resource. + epo-cat:Item -> epo-cat:Item [0..*]
dct:languageA language of the resource.eli:LegalExpression -> at-voc:language [1..*]
dct:replacesA related resource that is supplanted, displaced, or superseded by the described resource. + + Additional Information: + In the eCatalogue context, when this relation is used between two items, the resource + in the definition refers to Items, i.e. one item replaces another item. + + WG Approval: 30/06/2022 + A related resource that is supplanted, displaced, or superseded by the described resource. + epo-cat:Item [,0..*] <- epo-cat:Item
dct:requiresA related resource that is required by the described resource to support its function, + delivery, or coherence. + + Additional Information: + In the eCatalogue context, when this relation is used between two items, the resource + in the definition refers to Items, i.e. one Item requires another Item. + + WG Approval: 30/06/2022 + epo-cat:Item -> epo-cat:Item [0..*]
dct:typeCategory to which the Requirement belongs.cccev:Criterion -> at-voc:criterion [0..1]
eli:is_realized_byRelates a work to an expression of this work in the form of a "sequence of signs" + (typically alpha-numeric characters in a legal context). Inverse of "realizes".eli:LegalExpression -> eli:Work [1]
eli:jurisdictionThe jurisdiction from which the legal resource originates. + + The place identifier can be taken from the Administrative Territorial Unit table published + of the EU Publications Office at https://op.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/atu. + Member States don't have to recreate their own list of values. + The jurisdiction from which the legal resource originates. + + The place identifier can be taken from the Administrative Territorial Unit table published + of the EU Publications Office at https://op.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/atu. + Member States don't have to recreate their own list of values. + eli:LegalExpression -> at-voc:atu [0..*]
eli:LegalResource -> at-voc:atu [0..*]
eli:uri_schemaSchema describing the URI of an ELI instance. ELI uses URI template specifications + (IETF RFC 6570). Schemes should be associated with member states and will be published + in a registry. + Schema describing the URI of an ELI instance. ELI uses URI template specifications + (IETF RFC 6570). Schemes should be associated with member states and will be published + in a registry. + eli:LegalResourceSubdivision -> adms:Identifier [0..*]
eli:LegalExpression -> adms:Identifier [0..*]
epo:actsOnBehalfOfRepresents. epo:ProcurementServiceProvider -> epo:Buyer [1..*]
epo-sub:LegalRepresentative -> epo:OfferingParty [0..1]
epo:amendsContractepo-con:ContractAmendment -> epo:Contract [1]
epo:announcesAwardDecision epo-not:ResultNotice -> epo:AwardDecision [0..*]
epo-not:DirectAwardPrenotificationNotice -> epo:AwardDecision [0..*]
epo:announcesCompletionOfContractepo-not:CompletionNotice -> epo:Contract [1]
epo:announcesContract epo-not:DirectAwardPrenotificationNotice -> epo:Contract [0..*]
epo-not:ResultNotice -> epo:Contract [0..*]
epo:announcesContractAmendmentepo-not:ContractModificationNotice -> epo-con:ContractAmendment [1]
epo:announcesLot epo-not:DirectAwardPrenotificationNotice -> epo:Lot [1..*]
epo-not:CompetitionNotice -> epo:Lot [1..*]
epo:announcesLotGroup epo-not:CompetitionNotice -> epo:LotGroup [0..*]
epo-not:DirectAwardPrenotificationNotice -> epo:LotGroup [0..*]
epo:announcesLotGroupAwardInformation epo-not:DirectAwardPrenotificationNotice -> epo:LotGroupAwardInformation [0..*]
epo-not:ResultNotice -> epo:LotGroupAwardInformation [0..*]
epo:announcesNoticeAwardInformation epo-not:DirectAwardPrenotificationNotice -> epo:NoticeAwardInformation [0..1]
epo-not:ResultNotice -> epo:NoticeAwardInformation [0..1]
epo:announcesPlannedProcurementPartepo-not:PlanningNotice -> epo:PlannedProcurementPart [0..*]
epo:announcesProcedure epo-not:DirectAwardPrenotificationNotice -> epo:Procedure [1]
epo-not:CompetitionNotice -> epo:Procedure [1]
epo:announcesReviewObjectepo-not:CompletionNotice -> epo:ReviewObject [1..*]
epo:announcesRole epo-not:DirectAwardPrenotificationNotice -> epo:AgentInRole [1..*]
epo-not:ContractModificationNotice -> epo:AgentInRole [0..*]
epo-not:PlanningNotice -> epo:AgentInRole [1..*]
epo-not:CompetitionNotice -> epo:AgentInRole [1..*]
epo-not:CompletionNotice -> epo:AgentInRole [0..*]
epo:answersExclusionGroundepo-sub:ESPDResponse -> epo:ExclusionGround [1]
epo:answersSelectionCriteriaepo-sub:ESPDResponse -> epo:SelectionCriterion [1]
epo:associatedWithThe document to which a document is associated. + + WGM 01/03/2022 + epo:Document -> epo:Document [0..*]
epo:attestedByLabelRelation indicating which label the certificate is about. + + WG approval 28/07/2022epo:Certificate -> epo:CertificationLabel [0..1]
epo:bindsBuyerProvides legal constraint on the Buyer.epo:Contract -> epo:Buyer [0..*]
epo:bindsContractorProvides legal constraint on the Contractor.epo:Contract -> epo:Contractor [0..*]
epo:canProvideNonDiscriminatoryEvidenceRelation showing that an Organization can supply an Evidence with regard to the fulfilment + of non-discriminatory criteria or the rules applied in order to reduce the number + of participants. + + WG approval 12/03/2024org:Organization -> cccev:Evidence [0..*]
epo:canProvideTaxAndSocialSecuritiesEvidenceRelation showing that an Organization can supply an Evidence with regard to the payment + of social security contributions and taxes. + + WG approval 12/03/2024org:Organization -> cccev:Evidence [0..*]
epo:comprisesAwardOutcomeIncorporates AwardOutcome.epo:AwardDecision -> epo:AwardOutcome [0..*]
epo:comprisesTenderIncorporates Tender.epo:TenderGroup -> epo:Tender [1..*]
epo:comprisesTenderAwardOutcomeIncorporates TenderAwardOutcome.epo:AwardOutcome -> epo:TenderAwardOutcome [0..*]
epo:concernsContractAmendmentepo-con:ContractModificationInformation -> epo-con:ContractAmendment [1]
epo:concernsGreenProcurementepo:VehicleInformation -> epo:GreenProcurement [1]
epo:concernsLotRelates to Lot. Relates to Lot.epo:LotAwardOutcome -> epo:Lot [1]
epo:ProcurementProcessInformation -> epo:Lot [0..1]
epo:concernsNotice epo:ChangeInformation -> epo:Notice [1]
epo:NonPublishedInformation -> epo:Notice [1]
epo:concernsProcedureRelates to Procedure. Relates to Procedure. + + WG approval 05/03/2024 + epo:ProcurementProcessInformation -> epo:Procedure [0..1]
epo-acc:ESPDRequest -> epo:Procedure [1]
epo:concernsReviewSummaryForLotRelates to Lot review summary. + + Additional information: + This relation corresponds in eForms to BT-13722 Buyer Review Lot Identifier.epo:ReviewRequestSummary -> epo:Lot [1]
epo:concernsTenderepo:TenderAwardOutcome -> epo:Tender [1]
epo:conformsToLegalBasisThe Notice was designed in accordance with the given legal basis. + + Additional Information: + This Notice can be used for Procedures which do not have the same legal basis. + This holds for standard forms.epo:Notice -> at-voc:legal-basis [0..*]
epo:containsCandidateepo:SelectedCandidateList -> epo:Candidate [0..*]
epo:contextualisedByThe place of the AgentInRole in the procurement is expressed by a ProcurementObject.epo:AgentInRole -> epo:ProcurementObject [0..*]
epo:definesBudgetProviderRelation indicating a ProcedureTerm has a BudgetProvider.epo:ProcedureTerm -> epo:BudgetProvider [0..1]
epo:definesCatalogueProviderRelation indicating an AccessTerm has a CatalogueProvider.epo:AccessTerm -> epo:CatalogueProvider [0..*]
epo:definesCatalogueReceiverRelation indicating an AccessTerm has a CatalogueReceiver.epo:AccessTerm -> epo:CatalogueReceiver [0..*]
epo:definesContractDurationRelation indicating a ContractTerm has a Duration.epo:ContractTerm -> epo:Duration [0..1]
epo:definesContractPeriodRelation indicating a ContractTerm has a Period.epo:ContractTerm -> epo:Period [0..1]
epo:definesInformationProviderRelation indicating a ProcedureTerm has an information provider.epo:ProcedureTerm -> epo:AuxiliaryParty [0..*]
epo:definesLotGroupRelation indicating a ProcedureTerm has a LotGroup.epo:ProcedureTerm -> epo:LotGroup [0..*]
epo:definesMediatorRelation indicating a ProcedureTerm has a Mediator.epo:ProcedureTerm -> epo:Mediator [0..1]
epo:definesOfflineAccessProviderRelation indicating an AccessTerm has an OfflineAccessProvider.epo:AccessTerm -> epo:OfflineAccessProvider [0..1]
epo:definesOpeningPlaceThe place where the tenders will be publicly opened. + + WG Approval 10-10-2019epo:OpeningTerm -> locn:Address [0..1]
epo:definesParticipationRequestProcessorRelation indicating a ParticipationRequestTerm has a ParticipationRequestProcessor.epo:ParticipationRequestTerm -> epo:ParticipationRequestProcessor [0..1]
epo:definesParticipationRequestReceiverRelation indicating a ParticipationRequestTerm has a ParticipationRequestReceiver.epo:ParticipationRequestTerm -> epo:ParticipationRequestReceiver [0..1]
epo:definesPaymentExecutorRelation indicating a ContractTerm has a PaymentExecutor.epo:ContractTerm -> epo:PaymentExecutor [0..1]
epo:definesPrizeRelation indicating a DesignContestRegimeTerm has a Prize.epo:DesignContestRegimeTerm -> epo:Prize [0..*]
epo:definesProcurementProcedureInformationProviderRelation indicating an AccessTerm has a ProcurementProcedureInformationProvider.epo:AccessTerm -> epo:ProcurementProcedureInformationProvider [0..1]
epo:definesReviewerRelation indicating a ReviewTerm has a Reviewer.epo:ReviewTerm -> epo:Reviewer [0..*]
epo:definesReviewProcedureInformationProviderRelation indicating a ReviewTerm has a ReviewProcedureInformationProvider.epo:ReviewTerm -> epo:ReviewProcedureInformationProvider [0..1]
epo:definesSpecificPlaceOfPerformanceRelation indicating a ContractTerm has a specific place of performance.epo:ContractTerm -> dct:Location [0..*]
epo:definesSubcontractingTermRelation indicating a ContractTerm has a SubcontractingTerm.Relation indicating a + term has a subterm.epo:ContractTerm -> epo:SubcontractTerm [0..1]
epo:definesTenderProcessorRelation indicating a SubmissionTerm has a TenderProcessor.epo:SubmissionTerm -> epo:TenderProcessor [0..1]
epo:definesTenderReceiverRelation indicating a SubmissionTerm has a TenderReceiver.epo:SubmissionTerm -> epo:TenderReceiver [0..1]
epo:delegatesAncillaryActivitiesToEntrusts 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:describesDirectAwardPrenotificationNoticeepo:NoticeAwardInformation -> epo-not:DirectAwardPrenotificationNotice [0..1]
epo:describesLotCompletionepo:ContractLotCompletionInformation -> epo:Lot [1]
epo:describesLotGroupepo:LotGroupAwardInformation -> epo:LotGroup [1]
epo:describesResultNoticeepo:NoticeAwardInformation -> epo-not:ResultNotice [0..1]
epo:distributesOfferepo:OfferIssuer -> epo:Offer [0..*]
epo:exposesChannelepo:AgentInRole -> cv:Channel [0..*]
epo:exposesInvoiceeChannelepo:Buyer -> cv:Channel [0..*]
epo:followsRulesSetByepo:PurchaseContract -> epo:FrameworkAgreement [0..1]
epo:foreseesConcession epo:Tender -> epo:ConcessionEstimate [0..1]
epo:ProcurementObject -> epo:ConcessionEstimate [0..1]
epo:foreseesContractSpecificTermepo:ProcurementObject -> epo:ContractSpecificTerm [0..*]
epo:foreseesProcurementObjectRelation indicating the instance of a Procurement Object that is planned. + + Additional Information: + The properties of the Procurement Object that is foreseen should be read as foreseen + properties. + For example, Procedure isSMESuitable should be read as Procedure foreseesToBeSMESuitable. + For example, Procedure isFundedBy should be read as Procedure foreseesToBeFundedBy.epo:PlannedProcurementPart -> epo:ProcurementObject [0..1]
epo:foreseesSubcontractingepo:Tender -> epo:SubcontractingEstimate [0..*]
epo:foreseesTechniqueepo:PlannedProcurementPart -> epo:Technique [0..*]
epo:fulfillsRequirementThe requirement to which the concept meets. + WG Approval 09/11/2021 + The requirement to which the concept meets. + WG Approval 09/11/2021 + + The requirement to which the concept meets. + WG Approval 09/11/2021 + + The requirement to which the concept meets. + WG Approval 09/11/2021 + + epo:GreenProcurement -> at-voc:green-public-procurement-criteria [0..*]
epo:GreenProcurement -> at-voc:environmental-impact [0..*]
epo:InnovativeProcurement -> at-voc:innovative-acquisition [0..*]
epo:SocialProcurement -> at-voc:social-objective [0..*]
epo:fulfillsStrategicProcurementepo:ProcurementObject -> epo:StrategicProcurement [0..*]
epo:hasAdditionalClassificationepo:Purpose -> at-voc:cpv [0..*]
epo:hasAdditionalContractNatureAdditional type of acquisition taken into consideration in the contract. + + WG Approval 11/06/2020 + + epo:ContractTerm -> at-voc:contract-nature [0..*]
epo:hasAllegedIrregularityTypeAdditional information: + This relation corresponds in eForms to BT-791 Review Irregularity Type + epo:ReviewRequest -> at-voc:irregularity-type [1..*]
epo:hasApproximateFrameworkAgreementValueThe estimated value to be spent within the Framework Agreement(s). - WG Approval 29/08/2019 + Additional information: + In the case of an Award Decision for a Lot, this relation represents the estimated + value for the awarded Framework Agreement. + In the case of a Notice, this relation represents the estimated value for all Framework + Agreements covered by the Notice. + The estimated value to be spent within the Framework Agreement(s). + + Additional information: + In the case of an Award Decision for a Lot, this relation represents the estimated + value for the awarded Framework Agreement. + In the case of a Notice, this relation represents the estimated value for all Framework + Agreements covered by the Notice. xsd:integer [0..1]epo:LotAwardOutcome -> epo:MonetaryValue [0..1]
epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]
epo:ChangeInformationepo:hasProcurementDocumentChangeDateThe date and time of the change. + epo:hasArrivalShipmentInformationepo-ful:ShipmentStage -> epo-ful:ShipmentInformation [0..*]
epo:hasAwardCriterionTypeCategory of award criterion. - Additional information: - This corresponds in eForms to BT-719 Change Procurement Documents Date + epo:AwardCriterion -> at-voc:award-criterion-type [0..1]
epo:hasAwardedValueThe 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/2019epo:AwardOutcome -> epo:MonetaryValue [0..1]
epo:hasAwardStatusIndicates whether the lot is awarded, not awarded or still open. + WG Approval 03/12/2019 - WG Approval 5/11/2019 xsd:dateTime [0..1]epo:AwardOutcome -> at-voc:winner-selection-status [0..1]
epo:AccessTermepo:hasPublicAccessURLWeb page where the procurement documents can be downloaded. + epo:hasBargainPriceThe value of procured supplies that have used a particularly advantageous opportunity + available for a very short time at a value considerably lower than normal market prices. + + WG approval 23/05/2023epo:AwardOutcome -> epo:MonetaryValue [0..1]
epo:hasBatchIDThe identifier assigned to a specific batch of the produced Item. + WG Approval 16/05/2023 + epo-cat:Batch -> adms:Identifier [0..1]
epo:hasBeneficialOwnerA 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/2021epo:Business -> person:Person [0..*]
epo:hasBroadPlaceOfPerformanceGeopolitical 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). + epo:ContractTerm -> at-voc:other-place-service [0..1]
epo:hasBusinessSizeThe 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. + + WG Approval 28/05/2020 + + epo:Business -> at-voc:economic-operator-size [0..1]
epo:hasBuyerItemIDThe general identifier assigned to the concept as defined by the Buyer.​ + + WG approval 16/05/2023 + epo-cat:Item -> adms:Identifier [0..1]
epo:hasBuyerLegalTypeA category that indicates the right of an Organisation to play the role of a buyer. Additional Information: - This corresponds in the eForms to BT-15 Documents URL. + The category also effects the rules that the buyer has to abide to within the public + procurement procedure. + WG 07/09/2021 - WG Approval 09/03/2021 xsd:anyURI [0..1]org:Organization -> at-voc:buyer-legal-type [0..1]
epo:Documentepo:hasPublicationDateDate of formal public issuance of the document. + epo:hasCertificationRelation to the proof of conformance. - WG approval 20/06/2023xsd:date [0..1]foaf:Person -> epo:Certificate [0..*]
org:Organization -> epo:Certificate [0..*]
epo-cat:Item -> epo:Certificate [0..*]
epo:QualificationCriteriaSummaryepo:hasQualificationConditionepo:hasChangeJustificationCode explaining the change. + + 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-justificationepo:ChangeInformation -> at-voc:change-corrig-justification [1]
epo:hasConcessionEstimatedValue rdf:PlainLiteral [0..*]epo:ConcessionEstimate -> epo:MonetaryValue [0..1]
epo:MultipleStageProcedureTermepo:hasQualificationSystemRenewalDescriptionepo:hasConfirmedIrregularityTypeAdditional information: + This relation corresponds in eForms to BT-791 Review Irregularity Typeepo:ReviewDecision -> at-voc:irregularity-type [0..*]
epo:hasConstraint cccev:InformationRequirement -> cccev:Constraint [0..*]
epo:ProcurementCriterion -> cccev:Constraint [0..*]
epo:hasContactPointInRole rdf:PlainLiteral [0..1]epo:AgentInRole -> cpov:ContactPoint [0..*]
epo:Quantityepo:hasQuantityValueThe numeric value of the quantity, including decimals.xsd:decimal [1..1]epo:hasContractNatureTypeSubject of the acquisition. + + WG Approval 11/06/2020 + + epo:ContractTerm -> at-voc:contract-nature [0..1]
epo:SubmissionTermepo:hasReceiptDeadlineThe time limit for receiving submissions. + epo:hasContractValueepo:Contract -> epo:MonetaryValue [0..1]
epo:hasCountryCode + dct:Location -> at-voc:country [0..1]
locn:Address -> at-voc:country [0..1]
epo:hasCountryOfBirthThe country in which the Person was born. + person:Person -> at-voc:country [0..1]
epo:hasCurrencyThe identifier of the currency as in the standard code list used. - 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. - This attribute should be used for standard forms mappings. + epo:MonetaryValue -> at-voc:currency [0..1]
epo:hasDirectAwardJustificationList of reasons for using a procedure which allows awarding contracts directly without + publishing a notice. - WG Approval 21/07/2020 + WG Approval 28/05/2020 xsd:dateTime [0..1]epo:DirectAwardTerm -> at-voc:direct-award-justification [0..1]
epo:SubmissionTermepo:hasReceiptExpressionDeadlineTime limit for receipt of expressions of interest. + epo:hasDocumentRestrictionJustificationAn explanation about the reasons why some procurement documents are restricted. - Pending of review by the WG + Additional Information: + This corresponds in eForms to BT-707 Documents Restricted Justification. + WG Approval 09/03/2021 xsd:dateTime [0..1]epo:AccessTerm -> at-voc:communication-justification [0..1]
epo:SubmissionTermepo:hasReceiptParticipationRequestDeadlineepo:hasDocumentStatushttps://test-docs.peppol.eu/logistics/transport-execution/codelist/DocumentStatusCode/epo-cat:PostAwardDocument -> at-voc-new:document-status [0..1]
epo:hasDPSScopeExplanation as to whether a dps is used and by whom. + + Additional Information: + This corresponds in eForms to BT-766 Dynamic Purchasing System. + 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-usageepo:DynamicPurchaseSystemTechnique -> at-voc:dps-usage [0..1]
epo:hasDriverPerson xsd:dateTime [0..1]epo-ful:TransportMeans -> epo-ful:TransportMeansOperator [1..*]
epo:hasECataloguePermissionThe extent to which electronic catalogues may be used in tenders. + + WG Approval 03/10/2019 + epo:SubmissionTerm -> at-voc:permission [0..1]
epo:hasEInvoicingPermissionepo:ContractTerm -> at-voc:permission [0..1]
epo:hasElectronicDigestepo:Document -> epo:Document [0..*]
epo:SubmissionTermepo:hasReceiptPreliminaryMarketConsultationDeadlineepo:hasElectronicSignature xsd:dateTime [0..1]epo:Document -> epo:ElectronicSignature [0..*]
epo:SubmissionTermepo:hasReceiptTenderDeadlineepo:hasEndpointIdentifier xsd:dateTime [0..1]cv:Channel -> adms:Identifier [0..*]
epo:SubmissionStatisticalInformationepo:hasReceivedMicroTendersThe amount of tenders received from a micro enterprise. + epo:hasEstimatedBuyerConcessionRevenueThe 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. - See Commission Recommendation 2003/361/EC.xsd:integer [0..1]
epo:SubmissionStatisticalInformationepo:hasReceivedParticipationRequestsThe amount of applications to participate from economic operators. + This corresponds to BT-160 in eForms. - WG Approval 12/12/2019xsd:integer [0..1]epo:ConcessionEstimate -> epo:MonetaryValue [0..1]
epo:SubmissionStatisticalInformationepo:hasReceivedSmallTendersTenders from small enterprise. - - <u>Additional Information:</u> + epo:hasEstimatedDurationRelation indicating a Contract has an estimated Duration. - See Commission Recommendation 2003/361/EC. + Additional Information + When the Lot uses a Technique the contract estimated duration applies to the Technique. xsd:integer [0..1]epo:Contract -> epo:Duration [0..1]
epo:SubmissionStatisticalInformationepo:hasReceivedTendersThe total amount of tenders received. + epo:hasEstimatedUserConcessionRevenueThe estimated revenue coming from the use of the concession. - WG Approval 12/12/2019xsd:integer [0..1]
epo:Documentepo:hasReceptionDateNotes: Date when a record is acknowledged by an organisation. + Additional Information: + Revenues are for example fees and fines. For example, the fees and fines coming from + the cars using a motorway. - WG Approval 12/05/2020xsd:date [0..1]epo:ConcessionEstimate -> epo:MonetaryValue [0..1]
epo:ProcurementObjectepo:hasRecurrenceDescriptionAny additional information about the recurrence of the Procurement. + epo:hasEstimatedValueA forecast of the value of the procurement before competition. Additional Information: - For example estimated timing of the Procedure. + 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. - This corresponds in eForms to BT-95 Recurrence Description. + In the case of framework agreements and dynamic purchasing systems this refers to + the maximum estimated value. - (WG approval 2019-01-16) - rdf:PlainLiteral [0..1]
epo:CertificationLabelepo:hasReferenceURIA reference to where the label specification (norms, expectations, standards and policies) - can be found. + This property corresponds to BT-27 in eForms (for Lot and Procedure) and can be used + for BT-157 (for LotGroup). + <b> + </b>WG Approval 05/12/2019 + A forecast of the value of the procurement before competition. - WG approval 26/07/2022xsd:anyURI [0..1]
epo:ContractTermepo:hasRenewalDescriptionAny other information about the renewal(s). + 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. - WG approval 16/04/2019 rdf:PlainLiteral [0..*]
epo:ReviewRequestepo:hasRequestDateThe date when the review request was submitted. + In the case of framework agreements and dynamic purchasing systems this refers to + the maximum estimated value. - Additional information: - This attribute corresponds to the BT-787 Review Date in eForms. - xsd:date [0..1]
epo:AccessTermepo:hasRestrictedAccessURLThe internet address with information on accessing the restricted (part of the) procurement - document. + 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> - Additional Information: - This corresponds in eForms to BT-615 Documents Restricted URL. xsd:anyURI [0..1]epo:LotGroup -> epo:MonetaryValue [0..1]
epo:ProcurementElement -> epo:MonetaryValue [0..1]
epo:ReviewTermepo:hasReviewDeadlineThe time limit for review procedures. + epo:hasESubmissionPermissionThe requirements as to what extent electronic submission is allowed. - WG Approval 09/11/2021xsd:dateTime [0..1]
epo:ReviewTermepo:hasReviewDeadlineInformationThe description of the time limits for review procedures. + WG Approval 03/10/2019 - WG Approval 01/10/2019rdf:PlainLiteral [0..*]epo:SubmissionTerm -> at-voc:permission [0..1]
epo:ReviewIrregularitySummaryepo:hasReviewIrregularityCountThe number of requests for a given irregularity. + epo:hasFinancialOfferValueThe value offered by the Tenderer for a Lot. - Additional information: - This attribute corresponds in eForms to BT-635 Buyer Review Requests Count.xsd:integer [1..1]
epo:ReviewTermepo:hasReviewProcedureThe description of the method used to request the verification that the procedure - has been carried out correctly. + 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. - WG Approval 09/11/2021rdf:PlainLiteral [0..*]epo:Tender -> epo:MonetaryValue [0..1]
epo:ReviewObjectepo:hasReviewURLThe internet address of the documents concerning the review instance. + epo:hasFixedValueTypeThe method to interpret the fixed value as pertaining to a total or unit. + + WG Approval 17/09/2019 - Additional information: - This attribute corresponds in eForms to BT-794 Review URL. xsd:anyURI [0..1]
adms:Identifierepo:hasSchemeThe name of the identification scheme.rdf:PlainLiteral [0..*]
adms:Identifierepo:hasSchemeVersionThe version of the identification scheme.rdf:PlainLiteral [0..*]epo:AwardCriterion -> at-voc:number-fixed [0..1]
epo:SelectionCriteriaSummaryepo:hasSelectionCriteriaStatedInProcurementDocumentsxsd:boolean [0..1]epo:hasFormTypeA categorisation of the steps in which the Notice is used. + + WG Approval 12/05/2020 + + epo:Notice -> at-voc:form-type [0..1]
epo-not:Notice1 -> planning [0..1]
epo-not:Notice10 -> competition [0..1]
epo-not:Notice11 -> competition [0..1]
epo-not:Notice12 -> competition [0..1]
epo-not:Notice13 -> competition [0..1]
epo-not:Notice14 -> competition [0..1]
epo-not:Notice15 -> competition [0..1]
epo-not:Notice16 -> competition [0..1]
epo-not:Notice17 -> competition [0..1]
epo-not:Notice18 -> competition [0..1]
epo-not:Notice19 -> competition [0..1]
epo-not:Notice2 -> planning [0..1]
epo-not:Notice20 -> competition [0..1]
epo-not:Notice21 -> competition [0..1]
epo-not:Notice22 -> competition [0..1]
epo-not:Notice23 -> competition [0..1]
epo-not:Notice24 -> competition [0..1]
epo-not:Notice25 -> dir-awa-pre [0..1]
epo-not:Notice26 -> dir-awa-pre [0..1]
epo-not:Notice27 -> dir-awa-pre [0..1]
epo-not:Notice28 -> dir-awa-pre [0..1]
epo-not:Notice29 -> result [0..1]
epo-not:Notice3 -> planning [0..1]
epo-not:Notice30 -> result [0..1]
epo-not:Notice31 -> result [0..1]
epo-not:Notice32 -> result [0..1]
epo-not:Notice33 -> result [0..1]
epo-not:Notice34 -> result [0..1]
epo-not:Notice35 -> result [0..1]
epo-not:Notice36 -> result [0..1]
epo-not:Notice37 -> result [0..1]
epo-not:Notice38 -> cont-modif [0..1]
epo-not:Notice39 -> cont-modif [0..1]
epo-not:Notice4 -> planning [0..1]
epo-not:Notice40 -> cont-modif [0..1]
epo-not:Notice5 -> planning [0..1]
epo-not:Notice6 -> planning [0..1]
epo-not:Notice7 -> planning [0..1]
epo-not:Notice8 -> planning [0..1]
epo-not:Notice9 -> planning [0..1]
epo-not:CANDefence-D81 -> Form18 [0..1]
epo-not:CANSocial-D25 -> Form6 [0..1]
epo-not:CANSocialNotice-D25 -> Form22 [0..1]
epo-not:CANStandard-D24 -> Form3 [0..1]
epo-not:CNDefence-D81 -> Form17 [0..1]
epo-not:CNSocial-D25 -> Form5 [0..1]
epo-not:CNSocialNotice-D25 -> Form22 [0..1]
epo-not:CNStandard-D24 -> Form2 [0..1]
epo-not:ConcessionAwardNotice-D23 -> Form25 [0..1]
epo-not:ConcessionNotice-D23 -> Form24 [0..1]
epo-not:DesignContest-D24 -> Form12 [0..1]
epo-not:DesignContest-D25 -> Form12 [0..1]
epo-not:DesignContestResult-D24 -> Form13 [0..1]
epo-not:DesignContestResult-D25 -> Form13 [0..1]
epo-not:Modification-D23 -> Form20 [0..1]
epo-not:Modification-D24 -> Form20 [0..1]
epo-not:Modification-D25 -> Form20 [0..1]
epo-not:PIN-CFCSocial-D25 -> Form4 [0..1]
epo-not:PIN-CFCSocialNotice-D25 -> Form22 [0..1]
epo-not:PIN-CFCStandard-D24 -> Form1 [0..1]
epo-not:PIN-RTL-D24 -> Form1 [0..1]
epo-not:PIN-RTL-D25 -> Form4 [0..1]
epo-not:PINDefence-D81 -> Form16 [0..1]
epo-not:PINOnly-D24 -> Form1 [0..1]
epo-not:PINOnly-D25 -> Form4 [0..1]
epo-not:PINProfile-D24 -> Form8 [0..1]
epo-not:PINProfile-D25 -> Form8 [0..1]
epo-not:PINProfile-D81 -> Form8 [0..1]
epo-not:QS-D25 -> Form7 [0..1]
epo-not:QSNotice-D25 -> Form22 [0..1]
epo-not:SocialAndOtherSpecificServices-D23 -> Form23 [0..1]
epo-not:SocialAndOtherSpecificServices-D24 -> Form21 [0..1]
epo-not:Subcontract-D81 -> Form19 [0..1]
epo-not:VEAT-D23 -> Form15 [0..1]
epo-not:VEAT-D24 -> Form15 [0..1]
epo-not:VEAT-D25 -> Form15 [0..1]
epo-not:VEAT-D81 -> Form15 [0..1]
epo:ProfessionalSuitabilitySummaryepo:hasServiceReservedToParticularProfessionepo:hasFrameworkAgreementMaximumValue xsd:boolean [0..1]epo:LotAwardOutcome -> epo:MonetaryValue [0..1]
epo:SubmissionStatisticalInformationepo:hasSMEReceivedTendersThe amount of tenders received from micro, small and medium-sized enterprises. + epo:hasFrameworkAgreementTypeThe form of framework agreement used in a procurement procedure. - <u>Additional Information:</u> + Addition information: - See Commission Recommendation 2003/361/EC. - The ReceivedSMETenderLots is used when the size of the company is not exactly knokn. + 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 - WG Approval 05/03/2020 xsd:integer [0..1]epo:FrameworkAgreementTerm -> at-voc:framework-agreement [1]
epo:SubmissionStatisticalInformationepo:hasSMEReceivedTendersExcludingSubcontractorsepo:hasFundProgramme xsd:integer [0..1]epo:Fund -> at-voc:EU-programme [0..1]
epo:StrategicProcurementepo:hasStrategicProcurementDescriptionSelf-explanatory text about a concept. - rdf:PlainLiteral [0..*]epo:hasGroupFrameworkAgreementMaximumValueThis corresponds to BT-156 in the eForms.epo:LotGroupAwardInformation -> epo:MonetaryValue [0..1]
epo:SubcontractTermepo:hasSubcontractingInvolvedList of Subcontractors and the subject matter they cover are required. - - Additional Information: - The tenderer will ned to supply this information in the tender. + epo:hasHighestReceivedTenderValueAmount of the Tender with the highest value. - WG Approval 28/02/2019xsd:boolean [0..1]
epo:SubcontractTermepo:hasSubcontractorsProposedAboveObligationThe maximum percentage of the contract value that the contractor must subcontract. + 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. - Additional information: - This is used for the competitive procedure described in Title III of Directive 2009/81/EC. + WG Approval 12/12/2019 - WG Approval 09/11/2021xsd:decimal [0..1]epo:SubmissionStatisticalInformation -> epo:MonetaryValue [0..1]
epo:SubcontractingEstimateepo:hasSubjectMatterDescription 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/2021rdf:PlainLiteral [0..*]epo:hasImplementingRegulation epo-not:StandardFormsNotice -> (EU) 2015/1986 [0..1]
epo-not:eFormsNotice -> (EU) 2019/1780 [0..1]
epo:SubmissionTermepo:hasSubmissionURL - Additional Information: - This corresponds to the eForms BT-18 Submission URL. - - This corresponds in eForms to BT-509 Organisation eDelivery Gateway.xsd:anyURI [0..*]epo:hasInternalIdentifier epo:LotGroup -> adms:Identifier [0..*]
epo:ProcurementElement -> adms:Identifier [0..*]
epo:MultipleStageProcedureTermepo:hasSuccessiveReductionThe 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]epo:hasIrregularityTypeAdditional information: + This relation corresponds in eForms to BT-636 Buyer Review Requests Irregularity + Typeepo:ReviewIrregularitySummary -> at-voc:irregularity-type [1]
cccev:Constraintepo:hasThresholdValueThe cut-off level for a given concept. + epo:hasItemCountryOfOriginThe source country of the product or service. 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:ReviewRequestSummaryepo:hasTotalNumberOfComplainantsThe 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 + 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 11/04/2019xsd:integer [0..1]epo:Tender -> at-voc:country [0..*]
epo:VehicleInformationepo:hasTotalVehiclesThe 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. + epo:hasItemStandardIDThe general identifier assigned to the concept based on a standard scheme.​ - 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. + Additional information: + For example the GTIN scheme (Global Trade Item Number). - WG Approval 28/07/2020 - xsd:integer [0..1]epo-cat:Item -> adms:Identifier [0..*]
epo:Quantityepo:hasUnitDescriptionA 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/2021rdf:PlainLiteral [0..*]epo:hasLabelTypeThe label type such environmental, quality, social etc.epo:CertificationLabel -> at-voc-new:certification-label-type [0..1]
epo:SubmissionStatisticalInformationepo:hasUnverifiedTendersOffers 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). + epo:hasLanguageLanguage in which the submitted information is to be expressed. + + WG Approval 21/07/2020 - WG Approval 28/07/2020 xsd:integer [0..1]epo:SubmissionTerm -> at-voc:language [0..*]
cccev:Evidence
epo:Fund
epo:hasURLThe identifier of a resource. + epo:hasLateSubmissionPermissionWhether 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. - For example: + WG Approval 21/07/2020 + epo:SubmissionTerm -> at-voc:missing-info-submission [0..1]
epo:hasLaunchFrameworkAgreementMaximumValue epo:ProcurementObject -> epo:MonetaryValue [0..1]
epo:LotGroup -> epo:MonetaryValue [0..1]
epo:hasLegalBasisThe legal basis under which the procurement procedure takes place. - 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; + Additional Information: + For example European Directives or Regulations, national laws etc. + The recommended code list is the example for the legal basis at the European level. - WG Approval 30/09/2019 - The identifier of a resource. + WG 04/04/2023 - Additional Information + The legal basis under which the procurement procedure takes place. - For example: + Additional Information: + For example European Directives or Regulations, national law - 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 09/11/2021 - WG Approval 30/09/2019xsd:anyURI [0..1]
xsd:anyURI [0..1]
epo:ProcurementObject -> at-voc:legal-basis [0..*]
epo-not:VEAT-D23 -> Directive 23 [0..1]
epo-not:Notice35 -> Directive 23 [0..1]
epo-not:Modification-D23 -> Directive 23 [0..1]
epo-not:Notice32 -> Directive 23 [0..1]
epo-not:Notice19 -> Directive 23 [0..1]
epo-not:ConcessionNotice-D23 -> Directive 23 [0..1]
epo-not:ConcessionAwardNotice-D23 -> Directive 23 [0..1]
epo-not:Notice40 -> Directive 23 [0..1]
epo-not:Notice28 -> Directive 23 [0..1]
epo-not:SocialAndOtherSpecificServices-D23 -> Directive 23 [0..1]
epo-not:Notice14 -> Directive 23 [0..1]
epo-not:Notice10 -> Directive 24 [0..1]
epo-not:SocialAndOtherSpecificServices-D24 -> Directive 24 [0..1]
epo-not:VEAT-D24 -> Directive 24 [0..1]
epo-not:PINOnly-D24 -> Directive 24 [0..1]
epo-not:Notice25 -> Directive 24 [0..1]
epo-not:Notice23 -> Directive 24 [0..1]
epo-not:CNStandard-D24 -> Directive 24 [0..1]
epo-not:PIN-CFCStandard-D24 -> Directive 24 [0..1]
epo-not:Notice29 -> Directive 24 [0..1]
epo-not:Notice38 -> Directive 24 [0..1]
epo-not:Notice36 -> Directive 24 [0..1]
epo-not:Notice1 -> Directive 24 [0..1]
epo-not:DesignContestResult-D24 -> Directive 24 [0..1]
epo-not:Notice33 -> Directive 24 [0..1]
epo-not:CANStandard-D24 -> Directive 24 [0..1]
epo-not:DesignContest-D24 -> Directive 24 [0..1]
epo-not:PIN-RTL-D24 -> Directive 24 [0..1]
epo-not:Notice20 -> Directive 24 [0..1]
epo-not:PINProfile-D24 -> Directive 24 [0..1]
epo-not:Notice12 -> Directive 24 [0..1]
epo-not:Notice4 -> Directive 24 [0..1]
epo-not:Notice16 -> Directive 24 [0..1]
epo-not:Notice7 -> Directive 24 [0..1]
epo-not:Modification-D25 -> Directive 25 [0..1]
epo-not:Notice26 -> Directive 25 [0..1]
epo-not:CNSocial-D25 -> Directive 25 [0..1]
epo-not:PIN-CFCSocial-D25 -> Directive 25 [0..1]
epo-not:PINOnly-D25 -> Directive 25 [0..1]
epo-not:Notice2 -> Directive 25 [0..1]
epo-not:PINProfile-D25 -> Directive 25 [0..1]
epo-not:PIN-RTL-D25 -> Directive 25 [0..1]
epo-not:Notice37 -> Directive 25 [0..1]
epo-not:VEAT-D25 -> Directive 25 [0..1]
epo-not:CANSocialNotice-D25 -> Directive 25 [0..1]
epo-not:QSNotice-D25 -> Directive 25 [0..1]
epo-not:QS-D25 -> Directive 25 [0..1]
epo-not:DesignContestResult-D25 -> Directive 25 [0..1]
epo-not:CNSocialNotice-D25 -> Directive 25 [0..1]
epo-not:Notice34 -> Directive 25 [0..1]
epo-not:Notice24 -> Directive 25 [0..1]
epo-not:CANSocial-D25 -> Directive 25 [0..1]
epo-not:Notice30 -> Directive 25 [0..1]
epo-not:Notice8 -> Directive 25 [0..1]
epo-not:Notice13 -> Directive 25 [0..1]
epo-not:Notice5 -> Directive 25 [0..1]
epo-not:Notice39 -> Directive 25 [0..1]
epo-not:Notice21 -> Directive 25 [0..1]
epo-not:Notice15 -> Directive 25 [0..1]
epo-not:Notice17 -> Directive 25 [0..1]
epo-not:DesignContest-D25 -> Directive 25 [0..1]
epo-not:Notice11 -> Directive 25 [0..1]
epo-not:PIN-CFCSocialNotice-D25 -> Directive 25 [0..1]
epo-not:VEAT-D81 -> Directive 81 [0..1]
epo-not:PINProfile-D81 -> Directive 81 [0..1]
epo-not:Notice6 -> Directive 81 [0..1]
epo-not:PINDefence-D81 -> Directive 81 [0..1]
epo-not:Subcontract-D81 -> Directive 81 [0..1]
epo-not:Notice27 -> Directive 81 [0..1]
epo-not:Notice22 -> Directive 81 [0..1]
epo-not:CNDefence-D81 -> Directive 81 [0..1]
epo-not:Notice18 -> Directive 81 [0..1]
epo-not:CANDefence-D81 -> Directive 81 [0..1]
epo-not:Notice3 -> Directive 81 [0..1]
epo-not:Notice9 -> Directive 81 [0..1]
epo-not:Notice31 -> Directive 81 [0..1]
epo:Documentepo:hasVersionA number that identifies a specific state of a document. - - WG approval: 18/11/2021 - rdf:PlainLiteral [0..1]epo:hasLegalIdentifierorg:Organization -> adms:Identifier [0..*]
epo:ReviewRequestepo:hasWithdrawalDateThe 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:hasLotReferenceepo:Contract -> epo:Lot [1..*]
epo:ReviewRequestepo:hasWithdrawalReasonThe explanation for withdrawing the request for review. + epo:hasLowestReceivedTenderValueAmount of the Tender with the lowest value. - Additional information: - This attribute corresponds in eForms to BT-798 Review Request Withdrawn Reasonsrdf:PlainLiteral [0..1]epo:SubmissionStatisticalInformation -> epo:MonetaryValue [0..1]
epo:VehicleInformationepo:hasZeroEmissionVehiclesThe 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. + epo:hasMainActivityThe principal sectoral area in which an organisation operates. - Additional Information + 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. + 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 - WG Approval 28/07/2020 xsd:integer [0..1]org:Organization -> at-voc:main-activity [0..1]
epo:ProcurementCriteriaSummaryepo:indicatesPerformingStaffInformationRequirementepo:hasMainClassification xsd:boolean [0..1]epo:Purpose -> at-voc:cpv [1..*]
epo:Procedureepo:isAcceleratedStatement about the fact that the procedure will be reduced due to a state of urgency. + epo:hasManufacturerIDThe manufacturer's identifier for the item. + epo-cat:Manufacturer -> adms:Identifier [0..1]
epo:hasManufacturerItemIDThe general identifier assigned to the concept as defined by the Manufacturer. ​ - Additional Information + WG approval 16/05/2023 + epo-cat:Item -> adms:Identifier [0..1]
epo:hasMaximumFrameworkAgreementAwardedValueThe maximum value which can be spent through all the framework agreements announced + in this notice, including options and renewals of contracts. - This modifies the time limit for the receipt of requests to participate or the receipt - of tenders. + Additional information: - WG Approval 20/08/2019 - xsd:boolean [0..1]epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]
epo:hasMemberepo:OrganisationGroup -> org:Organization [1..*]
epo:SubmissionTermepo:isAdvancedElectronicSignatureRequiredAdvanced or qualified electronic signature or seal (as defined in Regulation (EU) - No 910/2014) is required. + epo:hasModificationJustificationExplanation 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 - The submitted information is required to be signed electronically. + Additional Information - 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. - 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-con:ContractModificationInformation -> at-voc:modification-justification [1]
epo:ProcedureTermepo:isAwardedByCPBProcedure is awarded by a Central Purchasing Body. - + epo:hasNationality xsd:boolean [0..1]person:Person -> at-voc:country [0..*]
epo:ProcurementProcessInformationepo:isCompetitionTerminatedNo further contracts will be awarded in this procedure. - - Additional Information: - This can be instantiated in the post award phase. + epo:hasNonAwardJustificationOn hold; Enumeration. - 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:AwardOutcome -> at-voc:non-award-justification [0..1]
epo:Buyerepo:isContractingEntityRole 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. + epo:hasNonElectronicSubmissionJustification + Reason for not accepting electronic information. - Additional Information + WG Approval 21/07/2020 + epo:SubmissionTerm -> at-voc:communication-justification [0..*]
epo:hasNonPublicationJustificationThe reason why data is not published. + WG Approval 11/06/2020 + epo:NonPublishedInformation -> at-voc:non-publication-justification [1]
epo:hasNoticeType epo:Notice -> at-voc:notice-type [1]
epo-not:CANSocialNotice -> can-social [1]
epo-not:CANStandardNotice -> can-standard [1]
epo-not:CNSocialNotice -> cn-social [1]
epo-not:CNStandardNotice -> cn-standard [1]
epo-not:CompletionNotice -> compl [1]
epo-not:ContractModificationNotice -> can-modif [1]
epo-not:DesignContestNotice -> cn-desg [1]
epo-not:DesignContestResultNotice -> can-desg [1]
epo-not:PIN-CFCSocialNotice -> pin-cfc-social [1]
epo-not:PIN-CFCStandardNotice -> pin-cfc-standard [1]
epo-not:PINOnlyNotice -> pin-only [1]
epo-not:PINProfileNotice -> pin-buyer [1]
epo-not:PINTimeLimitNotice -> pin-rtl [1]
epo-not:PreMarketConsultationNotice -> pmc [1]
epo-not:QSNotice -> qu-sy [1]
epo-not:SubcontractNotice -> subco [1]
epo-not:VoluntaryEx-AnteTransparencyNotice -> veat [1]
epo:hasNutsCode dct:Location -> at-voc:nuts [0..1]
locn:Address -> at-voc:nuts [0..1]
epo:hasOfficialLanguageThe language(s) in which the instances of the given concepts are officially available. + These linguistic versions are equally legally valid. - 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 03/10/2019 - WG Approval 28/04/2020 xsd:boolean [0..1]epo:Document -> at-voc:language [1..*]
epo:ProcurementObjectepo:isCoveredByGPASpecifies whether the Agreement on Government Procurement (GPA) applies. - + epo:hasPerformingStaffQualificationInformation 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 + This relation corresponds in eForms to BT-79.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 xsd:boolean [0..1]epo:ProcurementCriterion -> at-voc:requirement-stage [0..*]
epo:Procedureepo:isDesignContestA competition which enables the buyer to acquire a plan or design via a jury. + epo:hasPlannedDurationepo:PlannedProcurementPart -> epo:Duration [0..1]
epo:hasPlannedPeriodepo:PlannedProcurementPart -> epo:Period [0..1]
epo:hasPriceSurchargeInformationepo-cat:Price -> epo-cat:ChargeInformation [0..1]
epo:hasPrimaryContactPointorg:Organization -> cpov:ContactPoint [0..1]
epo:hasPrizeValueThe monetary value of a prize, if any, for the winner (or runners-up) of the design + contest. - 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 + Additional Information: + This corresponds to BT-644 in eForms. - The contest may include or not the award of prizes; + WG Approval 29/08/2019 - WG approval 04-02-2021 xsd:boolean [0..1]epo:Prize -> epo:MonetaryValue [0..1]
epo:ProcurementProcessInformationepo:isDPSTerminatedEnd of the Dynamic Purchase System (DPS). - - Additional Information: This property can be used in the contract award notice even - if no contracts are awarded. + epo:hasProcedureTypeIdentification of the Procedure used. - WG Approval 22/11/2019 + WG Approval 09/06/2020 xsd:boolean [0..1]epo:Procedure -> at-voc:procurement-procedure-type [1]
epo:SubmissionTermepo:isGuaranteeRequiredThe submitted information must include a financial commitment to be used in case of - default. + epo:hasProcurementHighestReceivedTenderValueThe highest received tender value for the procurement. Additional Information: - See the additional information provided in the definition of the 'Guarantee Description' - element. + This corresponds to section II.1.7.3. according to Regulation (EU) 2015/1986.epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]
epo:hasProcurementLowestReceivedTenderValueThe lowest received tender value for the procurement. - WG Approval 21/07/20 + Additional Information: + This corresponds to section II.1.7.2. according to Regulation (EU) 2015/1986.epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]
epo:hasProcurementScopeDividedIntoLotepo:Procedure -> epo:Lot [1..*]
epo:hasPurpose Relation indicating the Purpose of a concept.epo:Contract -> epo:Purpose [0..1]
epo:ProcurementObject -> epo:Purpose [0..1]
epo:hasQualificationSystemDurationepo:MultipleStageProcedureTerm -> epo:Duration [0..1]
epo:hasReceivedSubmissionTypeepo:SubmissionStatisticalInformation -> at-voc:received-submission-type [0..1]
epo:hasRegistrationCountryorg:Organization -> at-voc:country [0..1]
epo:hasRejectedQuantityepo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
epo:hasRemedyValueAdditional information: + This relation corresponds in eForms to BT-793 Review Remedy Value.epo:ReviewDecision -> epo:MonetaryValue [0..1]
epo:hasReservedExecutionepo:ContractTerm -> at-voc:applicability [0..1]
epo:hasReservedProcurementExplanation as to whether a procurement may be reserved for the participation of certain + types of organisation. + Additional information: + This property corresponds in eForms to the BT-71 + WG Approval 09/11/2021 + Explanation as to whether a procurement may be reserved for the participation of certain + types of organisation. + + Additional information: + This property corresponds in eForms to the BT-71 + WG Approval 09/11/2021 xsd:boolean [0..1]epo:ParticipationCondition -> at-voc:reserved-procurement [0..*]
epo:ParticipationConditionsSummary -> at-voc:reserved-procurement [0..*]
epo:Procedureepo:isJointProcurementMultiple 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:hasResourceTypeeli:LegalResource -> at-voc:resource-type [1..*]
epo:hasReviewBodyTypeepo:Reviewer -> at-voc:review-body-type [0..*]
epo:hasReviewDecisionTypeAdditional information: + This relation corresponds in eForms to BT-790 Review Decision Type.epo:ReviewDecision -> at-voc:review-decision-type [0..*]
epo:hasReviewIrregularitySummaryAdditional information: + This relation corresponds in eForms to BG-613 Buyer Review Requestsepo:ReviewRequestSummary -> epo:ReviewIrregularitySummary [0..*]
epo:hasReviewRequestFeeAdditional information: + This relation corresponds in eForms to BT-795 Review Request Fee.epo:ReviewRequest -> epo:MonetaryValue [0..1]
epo:DesignContestRegimeTermepo:isJuryDecisionBindingIndicates whether the procuring entity is bound to apply the decision of the jury.xsd:boolean [0..1]epo:hasSelectionCriteriaUsage + Additional Information: + This corresponds in eForms to BT-748 Selection Criteria Used.epo:SelectionCriterion -> at-voc:usage [0..1]
epo:Businessepo:isListedCompanyPublic 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> + epo:hasSelectionCriterionTypeThe classification of the selection criteria. - 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/2019xsd:boolean [0..1]
epo:SubmissionTermepo:isMultipleTenderSubmissionAllowedTenderers may submit more than one competing tenders. + Additional Information: - WG Approval 10/10/2019 + This corresponds in eForms to BT-747 Selection Criteria Type. + WG Approval 09/11/2021 xsd:boolean [0..1]epo:SelectionCriterion -> at-voc:selection-criterion [0..1]
epo:NonDisclosureAgreementTermepo:isNonDisclosureAgreementRequiredxsd:boolean [0..1]epo:hasSellerItemIDThe general identifier assigned to the concept as defined by the Seller.​ + + WG approval 16/05/2023 + epo-cat:Item -> adms:Identifier [0..1]
epo:ProcedureTermepo:isOneLotOnlyAllowedIndicates 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 - + epo:hasSerialIDThe identifier assigned to the specific instance of the produced concept. + WG Approval 16/05/2023 xsd:boolean [0..1]epo-cat:Item -> adms:Identifier [0..1]
epo:ChangeInformationepo:isProcurementDocumentChangedOne or more procurement documents have been changed. - - Additional information: - This corresponds in eForms to BT-718 Change Procurement Documents - - WG Approval 05/11/2019xsd:boolean [0..1]epo:hasStartDateepo:SelectedCandidateList -> epo:Period [0..1]
epo:AccessTermepo:isProcurementDocumentRestrictedThe access to certain procurement documents is restricted. - - Additional Information: - This corresponds in eForms to BT-14 Documents Restricted. - - WG Approval 10/10/2019xsd:boolean [0..1]epo:hasSubcontractingepo:Tender -> at-voc:applicability [0..1]
epo:ProcurementObjectepo:isRecurrentThe Procurement being notified is likely to be included in another procedure in the - foreseeable future. + epo:hasSubcontractingEstimatedValueThe estimated value of a single subcontract. - Additional Information: + This relates to BT-553 in eForms. - 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. + WG Approval 01/09/2020 - This corresponds in eForms to BT-94 Recurrence. + epo:SubcontractingEstimate -> epo:MonetaryValue [0..1]
epo:hasSubcontractingObligationThe requirement the tender must meet with regard to subcontracting parts of the contract. + WG Approval 09/11/2021 - WG Approval 12/05/2020 xsd:boolean [0..1]epo:SubcontractTerm -> at-voc:subcontracting-obligation [0..*]
epo:ContractTermepo:isRenewalIndicatorIndicates whether the contract is subject to a renewal clause. - WG Approval 09/11/2021xsd:boolean [0..1]epo:hasSubdivisioneli:LegalResourceSubdivision -> at-voc:subdivision [0..1]
epo:SecurityClearanceTermepo:isSecurityClearanceRequiredepo:hasTaxIdentifier xsd:boolean [0..1]org:Organization -> adms:Identifier [0..*]
epo:ProcurementObjectepo:isSMESuitableThe 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. + epo:hasTenderSubcontractingInformationThe information about subcontracting that must be indicated in the tender. - For example, number of employees and turnover are applicable to the definition of - an SME. + WG Approval 10/10/2019 - WG Approval 15/10/2019 xsd:boolean [0..1]epo:SubmissionTerm -> at-voc:subcontracting-indication [0..*]
epo:ProcedureTermepo:isSubmissionForAllLotsRequiredIndicates whether tenders must be submitted for all Lots. + epo:hasTenderValidityDurationepo:SubmissionTerm -> epo:Duration [0..1]
epo:hasTenderValidityPeriodThe relation indicating until when a tender instance is applicable. xsd:boolean [0..1]epo:SubmissionTerm -> epo:Period [0..1]
epo:ProcurementProcessInformationepo:isToBeRelaunchedIndicator 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. + epo:hasThresholdTypeThe method to interpret the threshold value as minimum or a maximum. - WG Approval: 18/01/2022 + WG Approval 17/09/2019 xsd:boolean [0..1]cccev:Constraint -> at-voc:number-threshold [0..*]
epo:SelectionCriterionepo:isUsedForCandidateRestrictionThe criterion will be used to select the candidates to be invited for the second stage - of a multistage procedure. + epo:hasTimePeriod - 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 Invitexsd:boolean [0..1]epo:Period -> at-voc:timeperiod [1..*]
epo:ProcurementObjectepo:isUsingEUFundsThe procurement foresees funding by the Union. + epo:hasTotalAwardedValueThe awarded value of all lots announced in this notice, including options and renewals. - Additional Information: - The funding may cover the whole procurement or part of the procurement. - For example the European Structural and Investment Funds or grants awarded by the - European Union. + 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 xsd:boolean [0..1]epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]
epo:Tenderepo:isVariantAlternative solution to fulfil the buyer's needs as opposed to solutions indicated - in the procurement documents. + epo:hasTotalQuantityThe number of units required. Additional Information: + The quantity needs to go along with the unit. - 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:Purpose -> epo:Quantity [0..1]
epo:ReviewRequestepo:isWithdrawnThe review request was withdrawn. - - Additional information: - This attribute corresponds in eForms to BT-796 Review Request Withdrawn.xsd:boolean [0..1]epo:hasTotalValue epo:TenderGroup -> epo:MonetaryValue [0..1]
epo-con:Deliverable -> epo:MonetaryValue [0..1]
epo:GreenProcurementepo:usesCleanVehicleDirectiveThe procurement falls within the scope of the European Parliament and Council 2009/33/EC - (Clean Vehicles Directive – CVD).xsd:boolean [0..1]epo:hasUnitCodeepo:Quantity -> at-voc:measurement-unit [1]
person:Personfoaf:familyNameThe hereditary surname of a family. + epo:hasUnofficialLanguageThe 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 rdf:PlainLiteral [0..*]epo:Document -> at-voc:language [0..*]
person:Personfoaf:givenNameThe name(s) that identify the Person within a family with a common surname. + epo:hasUsageThe codelist to be used is at-voc:usage which is available at http://publications.europa.eu/resource/dataset/usage rdf:PlainLiteral [0..*]
person:Personfoaf:nameThe complete name of the Person as one string.rdf:PlainLiteral [0..*]
locn:Addresslocn:addressAreaThe 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.rdf:PlainLiteral [0..1]epo:Technique -> at-voc:usage [0..1]
locn:Addresslocn:adminUnitL1The 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. + epo:hasUUIDA universally unique identifier for an instance of this document. - 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.rdf:PlainLiteral [0..1]
locn:Addresslocn:adminUnitL2The 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. + WG Approval 12/05/2020 A universally unique identifier for an instance of this document. - 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. + WG Approval 12/05/2020 rdf:PlainLiteral [0..1]epo:Document -> adms:Identifier [0..1]
epo-cat:CatalogueResponseLine -> adms:Identifier [1]
locn:Addresslocn:fullAddressThe complete address written as a formatted string. + epo:hasValidityPeriodThe relation indicating until when a given instance of a concept is applicable. - 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".rdf:PlainLiteral [0..1]cccev:Evidence -> epo:Period [0..1]
epo:Technique -> epo:Period [0..1]
epo-cat:Catalogue -> epo:Period [0..1]
dct:Locationlocn:geographicNameA textual description for a Location. + epo:hasVariantPermissionThe obligation or possibility for tenderers to submit variants or not. 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: + Variants are alternative ways to fulfil the buyer's needs as opposed to solutions + indicated in the procurement documents. - - "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. + 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. - 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. + Additional Information: + + Further conditions for submitting variant tenders are in the procurement documents. rdf:PlainLiteral [0..1]epo:SubmissionTerm -> at-voc:permission [0..1]
locn:Addresslocn:locatorDesignatorA 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. + epo:hasWeightValueTypeNo definition. Waiting on CCCEV alignment. - 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".rdf:PlainLiteral [0..1]epo:ProcurementCriterion -> at-voc:number-weight [0..1]
locn:Addresslocn:locatorNameProper 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. + epo:includesAccessibilityCriterionExplanation as to whether accessibility Criterion are used or not. + WG Approval 09/11/2021 - 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.rdf:PlainLiteral [0..1]epo:StrategicProcurement -> at-voc:accessibility [0..*]
locn:Addresslocn:postCodeThe 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.") + epo:includesNationalCriterionRelation indicating that a Criterion contains a Criterion that is specific to a given + Member State. 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".rdf:PlainLiteral [0..1]epo:QualificationCriterion -> epo:QualificationCriterion [0..*]
locn:Addresslocn:postNameThe 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".rdf:PlainLiteral [0..1]epo:includesTenderAdditional information: + This corresponds in eForms to BT-3202 Contract Tender Identifier. + epo:Contract -> epo:Tender [0..*]
locn:Addresslocn:thoroughfareAn 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".rdf:PlainLiteral [0..1]epo:indicatesAwardToWinnerReveals the winner to whom the tender award outcome is attributed.epo:TenderAwardOutcome -> epo:Winner [0..1]
person:Personperson:birthNameFamily name of the Person given upon their birth. - WG Approval 09/11/2021rdf:PlainLiteral [0..*]epo:indicatesInvoiceeContactPointepo:Buyer -> cpov:ContactPoint []
person:Personperson:patronymicNameName based on the given name of the Person's father. - WG Approval 09/11/2021rdf:PlainLiteral [0..*]epo:involvesBuyerepo:Procedure -> epo:Buyer [0..*]
adms:Identifierskos:notationThe literal identifying an entity, like a person or an object.rdf:PlainLiteral [1..1]epo:involvesProcurementDocumentepo:AccessTerm -> epo:ProcurementDocument [0..1]
cccev:InformationConcept
cccev:Requirement
skos:prefLabelThe preferred lexical label for a resource, in a given language. - - WG approval 30/05/2023 - - The preferred lexical label for a resource, in a given language. + epo:isBasedOnImplementingRegulationIndicates under which regulation a notice is created. - WG approval 30/05/2023rdf:PlainLiteral [0..*]
rdf:PlainLiteral [0..1]
epo:Notice -> at-voc:legal-basis [0..1]
epo:SpecificDurationtime:numericDurationValue of a temporal extent expressed as a number.xsd:decimal [1..1]epo:isBeneficialOwnerOfA 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/2021epo:Business [,0..*] <- person:Person
-

Predicates (object properties) and definitions

- - - - - + + + - - - - - + + + - - + - + + - - - + + + - - + - + In case there are multiple buyers, it may be the case that one or more buyers are + in charge of the procedure. + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - + + + + + + - + Additional Information: + Certifier is a role played by an organisation. + + WG approval 26/07/2022 + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - + - + - - - + + + - - - + + + - + + + + + + + + + + + + + + + + - + - - - + + + - + - + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - + - + - + - + - + - + - + - + - + - + - + - + - + + + + + + - + - + - + - - + + + + + + - + WG approval 30/05/2023 + - + - + - + - + - - + + + + + + - + WG approval 12/03/2024 + - + - + - + - + - - - + + + - - - + + + - - + - - - - - - + - - - + + + - - + - + - - - + + + - - - + + + - - + - + WG approval 21/09/2023 + - - + + + + + + - + - - + - + - - - + + + - - - + + + - + - + - - - + + + - - - + + + - - - + + + - - + - + WG acceptance 10/03/2022 + - - - + + + - - + - + - - + - + - - - + + + - - + - + - - + - + - - + - + + - - - + + + - - - + + + - + - + - - - + + + - + - + - - + - + WG approval 28/07/2022 + - - - + + + - - - + + + - - + + + + + + - + The unit must be indicated in the Quantity, with a quantity value of 1. + - - - + + + - - - + + + - - + - + + + + + + + + + + + - - - + + + - + - + - - - + + + - + - + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - + + + + + + + + + + + - + https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL7161/ + - + + + + + + - + - + - + - - - + + + - - - + + + - + - + - - + - + This is a logistics information needed for logistics, security measures, customs check, + etc. + - + - + - - - + + + - - + - + - - - + + + - - - + + + - + - + - + + + + + + - + - - - + + + - - - + + + - + - + - + - + - + - + - - - + + + - - - + + + - - - - + + + + - - - + + + - + + + + + + - + - - - + + + - + - + - + - + - + - + - - - + + + - + - + - - - + + + - + - + - - - + + + - - - + + + - - - + + + - - - + + + - - + - + - + - + - + - + - - - + + + - - - + + + - + - + - - - + + + - + - + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - + - + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + + + + + + + + + + + - + - + - + - + - + - + - - - + + + - - - + + + - + - + - - - + + + - + - + - - - + + + - + - + - + - + - + - + - + - + - + - + - - - + + + - + - + - + + + + + + - + - - - + + + - - - + + + - - - + + + - - - + + + - + - + - - - + + + - - - + + + - - - + + + - - - + + + - + - + - - - + + + - + - + - + - + - + - + - + - + Additional information: + If an order refers to multiple catalogues then all these catalogues ideally are subordinated + to the same contract. + Some countries however may allow multiple contracts per order (i.e Italy). + - - + - + The reference to the catalogue line is for information only, to trace the source of + the information provided in the order line. + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - + - + - - - + + + - + - + - + - + - + - + - + - + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - - + + + - - + - + WG approval 05/03/2024 + - - - + + + - - - + + + + + + + + + + + + + + + + + + diff --git a/implementation/ePO_core/conventions_report/ePO_core_convention_report.html b/implementation/ePO_core/conventions_report/ePO_core_convention_report.html index 058e15f5..0133ab62 100644 --- a/implementation/ePO_core/conventions_report/ePO_core_convention_report.html +++ b/implementation/ePO_core/conventions_report/ePO_core_convention_report.html @@ -19,7 +19,7 @@

UML Conventions Comformance Report

-

[ 21/03/2024 ]

+

[ 24/06/2024 ]

Publications Office of the European Union
@@ -56,7 +56,7 @@

Abstract

Generalisations. Each major section lists model items that need correction of errors or consideration of warnings.

The UML model in file ePO_core.xml - was tested at 11:52 on March 21, 2024.

+ was tested at 13:32 on June 24, 2024.

Nomenclature

Class names

@@ -65,13 +65,20 @@

Clas
  • cccev:Constraint
  • cccev:Criterion
  • cccev:Evidence
    • +
  • cccev:EvidenceType
    • +
  • cccev:EvidenceTypeList
  • cccev:InformationConcept
  • cccev:InformationRequirement
  • cccev:Requirement
    • +
  • cccev:SupportedValue
  • cpov:ContactPoint
  • cpov:PublicOrganisation
  • cv:Channel
  • dct:Location
    • +
  • eli:LegalExpression
    • +
  • eli:LegalResource
    • +
  • eli:LegalResourceSubdivision
    • +
  • eli:Work
  • epo:AccessTerm
  • epo:AcquiringCentralPurchasingBody
  • epo:AcquiringParty
    • @@ -218,6 +225,176 @@

    Clas
  • epo:Term
  • epo:VehicleInformation
  • epo:Winner
    • +
  • epo-acc:ESPDRequest
    • +
  • epo-cat:Batch
    • +
  • epo-cat:Brand
    • +
  • epo-cat:Catalogue
    • +
  • epo-cat:CatalogueLine
    • +
  • epo-cat:CatalogueResponse
    • +
  • epo-cat:CatalogueResponseInformation
    • +
  • epo-cat:CatalogueResponseLine
    • +
  • epo-cat:ChargeInformation
    • +
  • epo-cat:InformationHub
    • +
  • epo-cat:Item
    • +
  • epo-cat:ItemAccessoryRelation
    • +
  • epo-cat:ItemComplementaryRelation
    • +
  • epo-cat:ItemComposition
    • +
  • epo-cat:ItemModel
    • +
  • epo-cat:ItemProperty
    • +
  • epo-cat:ItemRelation
    • +
  • epo-cat:ItemReplacement
    • +
  • epo-cat:ItemRequirement
    • +
  • epo-cat:Line
    • +
  • epo-cat:Manufacturer
    • +
  • epo-cat:PostAwardDocument
    • +
  • epo-cat:Price
    • +
  • epo-cat:ProductSpecification
    • +
  • epo-con:ContractAmendment
    • +
  • epo-con:ContractModificationInformation
    • +
  • epo-con:Deliverable
    • +
  • epo-ful:AbstractContainer
    • +
  • epo-ful:Carrier
    • +
  • epo-ful:Consignment
    • +
  • epo-ful:DespatchAdvice
    • +
  • epo-ful:Despatcher
    • +
  • epo-ful:DespatchLine
    • +
  • epo-ful:FreightForwarder
    • +
  • epo-ful:GoodsItem
    • +
  • epo-ful:Notifier
    • +
  • epo-ful:Package
    • +
  • epo-ful:ReceiptAdvice
    • +
  • epo-ful:ReceiptAdviceLine
    • +
  • epo-ful:ShipmentAgreement
    • +
  • epo-ful:ShipmentInformation
    • +
  • epo-ful:ShipmentStage
    • +
  • epo-ful:TemperatureSpecification
    • +
  • epo-ful:TransportEquipment
    • +
  • epo-ful:TransportEquipmentSeal
    • +
  • epo-ful:TransportHandlingUnit
    • +
  • epo-ful:TransportMeans
    • +
  • epo-ful:TransportMeansOperator
    • +
  • epo-not:CANDefence-D81
    • +
  • epo-not:CANSocial-D25
    • +
  • epo-not:CANSocialNotice
    • +
  • epo-not:CANSocialNotice-D25
    • +
  • epo-not:CANStandard-D24
    • +
  • epo-not:CANStandardNotice
    • +
  • epo-not:CNDefence-D81
    • +
  • epo-not:CNSocial-D25
    • +
  • epo-not:CNSocialNotice
    • +
  • epo-not:CNSocialNotice-D25
    • +
  • epo-not:CNStandard-D24
    • +
  • epo-not:CNStandardNotice
    • +
  • epo-not:CompetitionNotice
    • +
  • epo-not:CompletionNotice
    • +
  • epo-not:ConcessionAwardNotice-D23
    • +
  • epo-not:ConcessionNotice-D23
    • +
  • epo-not:ContractModificationNotice
    • +
  • epo-not:DesignContest-D24
    • +
  • epo-not:DesignContest-D25
    • +
  • epo-not:DesignContestNotice
    • +
  • epo-not:DesignContestResult-D24
    • +
  • epo-not:DesignContestResult-D25
    • +
  • epo-not:DesignContestResultNotice
    • +
  • epo-not:DirectAwardPrenotificationNotice
    • +
  • epo-not:eFormsNotice
    • +
  • epo-not:Modification-D23
    • +
  • epo-not:Modification-D24
    • +
  • epo-not:Modification-D25
    • +
  • epo-not:Notice1
    • +
  • epo-not:Notice10
    • +
  • epo-not:Notice11
    • +
  • epo-not:Notice12
    • +
  • epo-not:Notice13
    • +
  • epo-not:Notice14
    • +
  • epo-not:Notice15
    • +
  • epo-not:Notice16
    • +
  • epo-not:Notice17
    • +
  • epo-not:Notice18
    • +
  • epo-not:Notice19
    • +
  • epo-not:Notice2
    • +
  • epo-not:Notice20
    • +
  • epo-not:Notice21
    • +
  • epo-not:Notice22
    • +
  • epo-not:Notice23
    • +
  • epo-not:Notice24
    • +
  • epo-not:Notice25
    • +
  • epo-not:Notice26
    • +
  • epo-not:Notice27
    • +
  • epo-not:Notice28
    • +
  • epo-not:Notice29
    • +
  • epo-not:Notice3
    • +
  • epo-not:Notice30
    • +
  • epo-not:Notice31
    • +
  • epo-not:Notice32
    • +
  • epo-not:Notice33
    • +
  • epo-not:Notice34
    • +
  • epo-not:Notice35
    • +
  • epo-not:Notice36
    • +
  • epo-not:Notice37
    • +
  • epo-not:Notice38
    • +
  • epo-not:Notice39
    • +
  • epo-not:Notice4
    • +
  • epo-not:Notice40
    • +
  • epo-not:Notice5
    • +
  • epo-not:Notice6
    • +
  • epo-not:Notice7
    • +
  • epo-not:Notice8
    • +
  • epo-not:Notice9
    • +
  • epo-not:PIN-CFCSocial-D25
    • +
  • epo-not:PIN-CFCSocialNotice
    • +
  • epo-not:PIN-CFCSocialNotice-D25
    • +
  • epo-not:PIN-CFCStandard-D24
    • +
  • epo-not:PIN-CFCStandardNotice
    • +
  • epo-not:PINDefence-D81
    • +
  • epo-not:PINOnly-D24
    • +
  • epo-not:PINOnly-D25
    • +
  • epo-not:PINOnlyNotice
    • +
  • epo-not:PINProfile-D24
    • +
  • epo-not:PINProfile-D25
    • +
  • epo-not:PINProfile-D81
    • +
  • epo-not:PINProfileNotice
    • +
  • epo-not:PIN-RTL-D24
    • +
  • epo-not:PIN-RTL-D25
    • +
  • epo-not:PINTimeLimitNotice
    • +
  • epo-not:PlanningNotice
    • +
  • epo-not:PreMarketConsultationNotice
    • +
  • epo-not:QS-D25
    • +
  • epo-not:QSNotice
    • +
  • epo-not:QSNotice-D25
    • +
  • epo-not:ResultNotice
    • +
  • epo-not:SocialAndOtherSpecificServices-D23
    • +
  • epo-not:SocialAndOtherSpecificServices-D24
    • +
  • epo-not:StandardFormsNotice
    • +
  • epo-not:Subcontract-D81
    • +
  • epo-not:SubcontractNotice
    • +
  • epo-not:VEAT-D23
    • +
  • epo-not:VEAT-D24
    • +
  • epo-not:VEAT-D25
    • +
  • epo-not:VEAT-D81
    • +
  • epo-not:VoluntaryEx-AnteTransparencyNotice
    • +
  • epo-ord:AllowanceChargeInformation
    • +
  • epo-ord:AllowanceInformation
    • +
  • epo-ord:Consignee
    • +
  • epo-ord:ContractInformation
    • +
  • epo-ord:DeliveryAgreement
    • +
  • epo-ord:DeliveryInformation
    • +
  • epo-ord:Order
    • +
  • epo-ord:OrderLine
    • +
  • epo-ord:OrderResponse
    • +
  • epo-ord:OrderResponseInformation
    • +
  • epo-ord:OrderResponseLine
    • +
  • epo-ord:Originator
    • +
  • epo-ord:OriginatorInformation
    • +
  • epo-ord:Seller
    • +
  • epo-ord:TaxInformation
    • +
  • epo-sub:CertificateInformation
    • +
  • epo-sub:ESPDResponse
    • +
  • epo-sub:LegalRepresentative
    • +
  • epo-sub:Mandate
    • +
  • epo-sub:NationalPreQualificationData
    • +
  • epo-sub:PowerOfAttorney
    • +
  • epo-sub:Response
  • foaf:Agent
  • foaf:Person
  • locn:Address
    • @@ -230,6 +407,7 @@

  • adms:schemaAgency
  • cccev:bias
    • +
  • cccev:value
  • cccev:weight
  • cccev:weightingConsiderationDescription
  • cpov:email
    • @@ -239,7 +417,7 @@

    cv:latitude
  • cv:longitude
  • dct:alternative
    • -
  • dct:description (18) +
  • cccev:EvidenceType -> adms:Identifier [0..1]
    • +
  • epo-ful:Consignment -> adms:Identifier [0..1]
    • +
  • epo-ful:TransportEquipment -> adms:Identifier [0..1]
    • +
  • epo-ful:ShipmentStage -> adms:Identifier [0..1]
    • +
  • epo-ful:TransportEquipmentSeal -> adms:Identifier [0..1]
    • +
  • cccev:EvidenceTypeList -> adms:Identifier [0..1]
    • +
  • epo-ful:ShipmentInformation -> adms:Identifier [0..1]
    • +
  • epo-cat:Line -> adms:Identifier [0..1]
    • +
  • epo-ful:AbstractContainer -> adms:Identifier [0..1]
  • cccev:confidentialityLevelType (2)
    • cccev:Evidence -> at-voc:access-rights [0..1]
      • -
    • -> at-voc:access-rights []
    +
  • epo-sub:Response -> at-voc:access-rights []
  • cccev:constrains
  • cccev:hasConcept
    • @@ -534,63 +791,78 @@

  • cccev:hasRequirement
  • cccev:isDerivedFrom
  • cccev:providesValueFor
    • +
  • cccev:specifiesEvidenceType
  • cccev:supportsConcept
  • cccev:supportsRequirement
    • -
  • cccev:supportsValue
    • +
  • cccev:supportsValue (2)
      +
    • cccev:Evidence -> cccev:SupportedValue [0..*]
      • +
    • epo-sub:Response -> cccev:SupportedValue [0..*]
    +
  • cccev:validityPeriodConstraint
  • cv:registeredAddress (2)
    • person:Person -> locn:Address [0..1]
    • org:Organization -> locn:Address [0..1]
  • dct:conformsTo
    • +
  • dct:hasPart
    • +
  • dct:isPartOf
    • +
  • dct:isReplacedBy
  • dct:language
    • +
  • dct:replaces
    • +
  • dct:requires
  • dct:type
    • +
  • eli:is_realized_by
    • +
  • eli:jurisdiction (2)
      +
    • eli:LegalExpression -> at-voc:atu [0..*]
      • +
    • eli:LegalResource -> at-voc:atu [0..*]
    +
  • eli:uri_schema (2)
      -
    • -> adms:Identifier [0..*]
      • -
    • -> adms:Identifier [0..*]
    +
  • eli:LegalResourceSubdivision -> adms:Identifier [0..*]
    • +
  • eli:LegalExpression -> adms:Identifier [0..*]
  • epo:actsOnBehalfOf (2)
    • epo:ProcurementServiceProvider -> epo:Buyer [1..*]
      • -
    • -> epo:OfferingParty [0..1]
    +
  • epo-sub:LegalRepresentative -> epo:OfferingParty [0..1]
  • epo:amendsContract
  • epo:announcesAwardDecision (2)
      -
    • -> epo:AwardDecision [0..*]
      • -
    • -> epo:AwardDecision [0..*]
    +
  • epo-not:ResultNotice -> epo:AwardDecision [0..*]
    • +
  • epo-not:DirectAwardPrenotificationNotice -> epo:AwardDecision [0..*]
  • epo:announcesCompletionOfContract
  • epo:announcesContract (2)
      -
    • -> epo:Contract [0..*]
      • -
    • -> epo:Contract [0..*]
    +
  • epo-not:DirectAwardPrenotificationNotice -> epo:Contract [0..*]
    • +
  • epo-not:ResultNotice -> epo:Contract [0..*]
    • +
  • epo:announcesContractAmendment
  • epo:announcesLot (2)
      -
    • -> epo:Lot [1..*]
      • -
    • -> epo:Lot [1..*]
    +
  • epo-not:DirectAwardPrenotificationNotice -> epo:Lot [1..*]
    • +
  • epo-not:CompetitionNotice -> epo:Lot [1..*]
  • epo:announcesLotGroup (2)
      -
    • -> epo:LotGroup [0..*]
      • -
    • -> epo:LotGroup [0..*]
    +
  • epo-not:CompetitionNotice -> epo:LotGroup [0..*]
    • +
  • epo-not:DirectAwardPrenotificationNotice -> epo:LotGroup [0..*]
  • epo:announcesLotGroupAwardInformation (2)
      -
    • -> epo:LotGroupAwardInformation [0..*]
      • -
    • -> epo:LotGroupAwardInformation [0..*]
    +
  • epo-not:DirectAwardPrenotificationNotice -> epo:LotGroupAwardInformation [0..*]
    • +
  • epo-not:ResultNotice -> epo:LotGroupAwardInformation [0..*]
  • epo:announcesNoticeAwardInformation (2)
      -
    • -> epo:NoticeAwardInformation [0..1]
      • -
    • -> epo:NoticeAwardInformation [0..1]
    +
  • epo-not:DirectAwardPrenotificationNotice -> epo:NoticeAwardInformation [0..1]
    • +
  • epo-not:ResultNotice -> epo:NoticeAwardInformation [0..1]
  • epo:announcesPlannedProcurementPart
  • epo:announcesProcedure (2)
      -
    • -> epo:Procedure [1]
      • -
    • -> epo:Procedure [1]
    +
  • epo-not:DirectAwardPrenotificationNotice -> epo:Procedure [1]
    • +
  • epo-not:CompetitionNotice -> epo:Procedure [1]
  • epo:announcesReviewObject
  • epo:announcesRole (5)
      -
    • -> epo:AgentInRole [1..*]
      • -
    • -> epo:AgentInRole [0..*]
      • -
    • -> epo:AgentInRole [1..*]
      • -
    • -> epo:AgentInRole [1..*]
      • -
    • -> epo:AgentInRole [0..*]
    +
  • epo-not:DirectAwardPrenotificationNotice -> epo:AgentInRole [1..*]
    • +
  • epo-not:ContractModificationNotice -> epo:AgentInRole [0..*]
    • +
  • epo-not:PlanningNotice -> epo:AgentInRole [1..*]
    • +
  • epo-not:CompetitionNotice -> epo:AgentInRole [1..*]
    • +
  • epo-not:CompletionNotice -> epo:AgentInRole [0..*]
  • epo:answersExclusionGround
  • epo:answersSelectionCriteria
    • @@ -603,6 +875,7 @@

  • epo:comprisesAwardOutcome
  • epo:comprisesTender
  • epo:comprisesTenderAwardOutcome
    • +
  • epo:concernsContractAmendment
  • epo:concernsGreenProcurement
  • epo:concernsLot (2)
    • epo:LotAwardOutcome -> epo:Lot [1]
      • @@ -614,7 +887,7 @@

    • epo:concernsProcedure (2)
      • epo:ProcurementProcessInformation -> epo:Procedure [0..1]
        • -
      • -> epo:Procedure [1]
      +
    • epo-acc:ESPDRequest -> epo:Procedure [1]

  • epo:concernsReviewSummaryForLot
  • epo:concernsTender
    • @@ -673,6 +946,7 @@

  • epo:LotAwardOutcome -> epo:MonetaryValue [0..1]
  • epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]
    • +
  • epo:hasArrivalShipmentInformation
  • epo:hasAwardCriterionType
  • epo:hasAwardedValue
  • epo:hasAwardStatus
    • @@ -686,7 +960,7 @@

  • epo:hasCertification (3)
    • foaf:Person -> epo:Certificate [0..*]
    • org:Organization -> epo:Certificate [0..*]
      • -
    • -> epo:Certificate [0..*]
    +
  • epo-cat:Item -> epo:Certificate [0..*]
  • epo:hasChangeJustification
  • epo:hasConcessionEstimatedValue
    • @@ -706,7 +980,9 @@

  • epo:hasCurrency
  • epo:hasDirectAwardJustification
  • epo:hasDocumentRestrictionJustification
    • +
  • epo:hasDocumentStatus
  • epo:hasDPSScope
    • +
  • epo:hasDriverPerson
  • epo:hasECataloguePermission
  • epo:hasEInvoicingPermission
  • epo:hasElectronicDigest
    • @@ -722,12 +998,95 @@

  • epo:hasESubmissionPermission
  • epo:hasFinancialOfferValue
  • epo:hasFixedValueType
    • -
  • epo:hasFormType
    • +
  • epo:hasFormType (78)
      +
    • epo:Notice -> at-voc:form-type [0..1]
      • +
    • epo-not:Notice1 -> planning [0..1]
      • +
    • epo-not:Notice10 -> competition [0..1]
      • +
    • epo-not:Notice11 -> competition [0..1]
      • +
    • epo-not:Notice12 -> competition [0..1]
      • +
    • epo-not:Notice13 -> competition [0..1]
      • +
    • epo-not:Notice14 -> competition [0..1]
      • +
    • epo-not:Notice15 -> competition [0..1]
      • +
    • epo-not:Notice16 -> competition [0..1]
      • +
    • epo-not:Notice17 -> competition [0..1]
      • +
    • epo-not:Notice18 -> competition [0..1]
      • +
    • epo-not:Notice19 -> competition [0..1]
      • +
    • epo-not:Notice2 -> planning [0..1]
      • +
    • epo-not:Notice20 -> competition [0..1]
      • +
    • epo-not:Notice21 -> competition [0..1]
      • +
    • epo-not:Notice22 -> competition [0..1]
      • +
    • epo-not:Notice23 -> competition [0..1]
      • +
    • epo-not:Notice24 -> competition [0..1]
      • +
    • epo-not:Notice25 -> dir-awa-pre [0..1]
      • +
    • epo-not:Notice26 -> dir-awa-pre [0..1]
      • +
    • epo-not:Notice27 -> dir-awa-pre [0..1]
      • +
    • epo-not:Notice28 -> dir-awa-pre [0..1]
      • +
    • epo-not:Notice29 -> result [0..1]
      • +
    • epo-not:Notice3 -> planning [0..1]
      • +
    • epo-not:Notice30 -> result [0..1]
      • +
    • epo-not:Notice31 -> result [0..1]
      • +
    • epo-not:Notice32 -> result [0..1]
      • +
    • epo-not:Notice33 -> result [0..1]
      • +
    • epo-not:Notice34 -> result [0..1]
      • +
    • epo-not:Notice35 -> result [0..1]
      • +
    • epo-not:Notice36 -> result [0..1]
      • +
    • epo-not:Notice37 -> result [0..1]
      • +
    • epo-not:Notice38 -> cont-modif [0..1]
      • +
    • epo-not:Notice39 -> cont-modif [0..1]
      • +
    • epo-not:Notice4 -> planning [0..1]
      • +
    • epo-not:Notice40 -> cont-modif [0..1]
      • +
    • epo-not:Notice5 -> planning [0..1]
      • +
    • epo-not:Notice6 -> planning [0..1]
      • +
    • epo-not:Notice7 -> planning [0..1]
      • +
    • epo-not:Notice8 -> planning [0..1]
      • +
    • epo-not:Notice9 -> planning [0..1]
      • +
    • epo-not:CANDefence-D81 -> Form18 [0..1]
      • +
    • epo-not:CANSocial-D25 -> Form6 [0..1]
      • +
    • epo-not:CANSocialNotice-D25 -> Form22 [0..1]
      • +
    • epo-not:CANStandard-D24 -> Form3 [0..1]
      • +
    • epo-not:CNDefence-D81 -> Form17 [0..1]
      • +
    • epo-not:CNSocial-D25 -> Form5 [0..1]
      • +
    • epo-not:CNSocialNotice-D25 -> Form22 [0..1]
      • +
    • epo-not:CNStandard-D24 -> Form2 [0..1]
      • +
    • epo-not:ConcessionAwardNotice-D23 -> Form25 [0..1]
      • +
    • epo-not:ConcessionNotice-D23 -> Form24 [0..1]
      • +
    • epo-not:DesignContest-D24 -> Form12 [0..1]
      • +
    • epo-not:DesignContest-D25 -> Form12 [0..1]
      • +
    • epo-not:DesignContestResult-D24 -> Form13 [0..1]
      • +
    • epo-not:DesignContestResult-D25 -> Form13 [0..1]
      • +
    • epo-not:Modification-D23 -> Form20 [0..1]
      • +
    • epo-not:Modification-D24 -> Form20 [0..1]
      • +
    • epo-not:Modification-D25 -> Form20 [0..1]
      • +
    • epo-not:PIN-CFCSocial-D25 -> Form4 [0..1]
      • +
    • epo-not:PIN-CFCSocialNotice-D25 -> Form22 [0..1]
      • +
    • epo-not:PIN-CFCStandard-D24 -> Form1 [0..1]
      • +
    • epo-not:PIN-RTL-D24 -> Form1 [0..1]
      • +
    • epo-not:PIN-RTL-D25 -> Form4 [0..1]
      • +
    • epo-not:PINDefence-D81 -> Form16 [0..1]
      • +
    • epo-not:PINOnly-D24 -> Form1 [0..1]
      • +
    • epo-not:PINOnly-D25 -> Form4 [0..1]
      • +
    • epo-not:PINProfile-D24 -> Form8 [0..1]
      • +
    • epo-not:PINProfile-D25 -> Form8 [0..1]
      • +
    • epo-not:PINProfile-D81 -> Form8 [0..1]
      • +
    • epo-not:QS-D25 -> Form7 [0..1]
      • +
    • epo-not:QSNotice-D25 -> Form22 [0..1]
      • +
    • epo-not:SocialAndOtherSpecificServices-D23 -> Form23 [0..1]
      • +
    • epo-not:SocialAndOtherSpecificServices-D24 -> Form21 [0..1]
      • +
    • epo-not:Subcontract-D81 -> Form19 [0..1]
      • +
    • epo-not:VEAT-D23 -> Form15 [0..1]
      • +
    • epo-not:VEAT-D24 -> Form15 [0..1]
      • +
    • epo-not:VEAT-D25 -> Form15 [0..1]
      • +
    • epo-not:VEAT-D81 -> Form15 [0..1]
    +
  • epo:hasFrameworkAgreementMaximumValue
  • epo:hasFrameworkAgreementType
  • epo:hasFundProgramme
  • epo:hasGroupFrameworkAgreementMaximumValue
  • epo:hasHighestReceivedTenderValue
    • +
  • epo:hasImplementingRegulation (2)
      +
    • epo-not:StandardFormsNotice -> (EU) 2015/1986 [0..1]
      • +
    • epo-not:eFormsNotice -> (EU) 2019/1780 [0..1]
    +
  • epo:hasInternalIdentifier (2)
    • epo:LotGroup -> adms:Identifier [0..*]
    • epo:ProcurementElement -> adms:Identifier [0..*]
    @@ -742,7 +1101,85 @@

  • epo:ProcurementObject -> epo:MonetaryValue [0..1]
  • epo:LotGroup -> epo:MonetaryValue [0..1]

    • -
  • epo:hasLegalBasis
    • +
  • epo:hasLegalBasis (77)
      +
    • epo:ProcurementObject -> at-voc:legal-basis [0..*]
      • +
    • epo-not:VEAT-D23 -> Directive 23 [0..1]
      • +
    • epo-not:Notice35 -> Directive 23 [0..1]
      • +
    • epo-not:Modification-D23 -> Directive 23 [0..1]
      • +
    • epo-not:Notice32 -> Directive 23 [0..1]
      • +
    • epo-not:Notice19 -> Directive 23 [0..1]
      • +
    • epo-not:ConcessionNotice-D23 -> Directive 23 [0..1]
      • +
    • epo-not:ConcessionAwardNotice-D23 -> Directive 23 [0..1]
      • +
    • epo-not:Notice40 -> Directive 23 [0..1]
      • +
    • epo-not:Notice28 -> Directive 23 [0..1]
      • +
    • epo-not:SocialAndOtherSpecificServices-D23 -> Directive 23 [0..1]
      • +
    • epo-not:Notice14 -> Directive 23 [0..1]
      • +
    • epo-not:Notice10 -> Directive 24 [0..1]
      • +
    • epo-not:SocialAndOtherSpecificServices-D24 -> Directive 24 [0..1]
      • +
    • epo-not:VEAT-D24 -> Directive 24 [0..1]
      • +
    • epo-not:PINOnly-D24 -> Directive 24 [0..1]
      • +
    • epo-not:Notice25 -> Directive 24 [0..1]
      • +
    • epo-not:Notice23 -> Directive 24 [0..1]
      • +
    • epo-not:CNStandard-D24 -> Directive 24 [0..1]
      • +
    • epo-not:PIN-CFCStandard-D24 -> Directive 24 [0..1]
      • +
    • epo-not:Notice29 -> Directive 24 [0..1]
      • +
    • epo-not:Notice38 -> Directive 24 [0..1]
      • +
    • epo-not:Notice36 -> Directive 24 [0..1]
      • +
    • epo-not:Notice1 -> Directive 24 [0..1]
      • +
    • epo-not:DesignContestResult-D24 -> Directive 24 [0..1]
      • +
    • epo-not:Notice33 -> Directive 24 [0..1]
      • +
    • epo-not:CANStandard-D24 -> Directive 24 [0..1]
      • +
    • epo-not:DesignContest-D24 -> Directive 24 [0..1]
      • +
    • epo-not:PIN-RTL-D24 -> Directive 24 [0..1]
      • +
    • epo-not:Notice20 -> Directive 24 [0..1]
      • +
    • epo-not:PINProfile-D24 -> Directive 24 [0..1]
      • +
    • epo-not:Notice12 -> Directive 24 [0..1]
      • +
    • epo-not:Notice4 -> Directive 24 [0..1]
      • +
    • epo-not:Notice16 -> Directive 24 [0..1]
      • +
    • epo-not:Notice7 -> Directive 24 [0..1]
      • +
    • epo-not:Modification-D25 -> Directive 25 [0..1]
      • +
    • epo-not:Notice26 -> Directive 25 [0..1]
      • +
    • epo-not:CNSocial-D25 -> Directive 25 [0..1]
      • +
    • epo-not:PIN-CFCSocial-D25 -> Directive 25 [0..1]
      • +
    • epo-not:PINOnly-D25 -> Directive 25 [0..1]
      • +
    • epo-not:Notice2 -> Directive 25 [0..1]
      • +
    • epo-not:PINProfile-D25 -> Directive 25 [0..1]
      • +
    • epo-not:PIN-RTL-D25 -> Directive 25 [0..1]
      • +
    • epo-not:Notice37 -> Directive 25 [0..1]
      • +
    • epo-not:VEAT-D25 -> Directive 25 [0..1]
      • +
    • epo-not:CANSocialNotice-D25 -> Directive 25 [0..1]
      • +
    • epo-not:QSNotice-D25 -> Directive 25 [0..1]
      • +
    • epo-not:QS-D25 -> Directive 25 [0..1]
      • +
    • epo-not:DesignContestResult-D25 -> Directive 25 [0..1]
      • +
    • epo-not:CNSocialNotice-D25 -> Directive 25 [0..1]
      • +
    • epo-not:Notice34 -> Directive 25 [0..1]
      • +
    • epo-not:Notice24 -> Directive 25 [0..1]
      • +
    • epo-not:CANSocial-D25 -> Directive 25 [0..1]
      • +
    • epo-not:Notice30 -> Directive 25 [0..1]
      • +
    • epo-not:Notice8 -> Directive 25 [0..1]
      • +
    • epo-not:Notice13 -> Directive 25 [0..1]
      • +
    • epo-not:Notice5 -> Directive 25 [0..1]
      • +
    • epo-not:Notice39 -> Directive 25 [0..1]
      • +
    • epo-not:Notice21 -> Directive 25 [0..1]
      • +
    • epo-not:Notice15 -> Directive 25 [0..1]
      • +
    • epo-not:Notice17 -> Directive 25 [0..1]
      • +
    • epo-not:DesignContest-D25 -> Directive 25 [0..1]
      • +
    • epo-not:Notice11 -> Directive 25 [0..1]
      • +
    • epo-not:PIN-CFCSocialNotice-D25 -> Directive 25 [0..1]
      • +
    • epo-not:VEAT-D81 -> Directive 81 [0..1]
      • +
    • epo-not:PINProfile-D81 -> Directive 81 [0..1]
      • +
    • epo-not:Notice6 -> Directive 81 [0..1]
      • +
    • epo-not:PINDefence-D81 -> Directive 81 [0..1]
      • +
    • epo-not:Subcontract-D81 -> Directive 81 [0..1]
      • +
    • epo-not:Notice27 -> Directive 81 [0..1]
      • +
    • epo-not:Notice22 -> Directive 81 [0..1]
      • +
    • epo-not:CNDefence-D81 -> Directive 81 [0..1]
      • +
    • epo-not:Notice18 -> Directive 81 [0..1]
      • +
    • epo-not:CANDefence-D81 -> Directive 81 [0..1]
      • +
    • epo-not:Notice3 -> Directive 81 [0..1]
      • +
    • epo-not:Notice9 -> Directive 81 [0..1]
      • +
    • epo-not:Notice31 -> Directive 81 [0..1]
    +
  • epo:hasLegalIdentifier
  • epo:hasLotReference
  • epo:hasLowestReceivedTenderValue
    • @@ -757,7 +1194,26 @@

  • epo:hasNonAwardJustification
  • epo:hasNonElectronicSubmissionJustification
  • epo:hasNonPublicationJustification
    • -
  • epo:hasNoticeType
    • +
  • epo:hasNoticeType (18)
      +
    • epo:Notice -> at-voc:notice-type [1]
      • +
    • epo-not:CANSocialNotice -> can-social [1]
      • +
    • epo-not:CANStandardNotice -> can-standard [1]
      • +
    • epo-not:CNSocialNotice -> cn-social [1]
      • +
    • epo-not:CNStandardNotice -> cn-standard [1]
      • +
    • epo-not:CompletionNotice -> compl [1]
      • +
    • epo-not:ContractModificationNotice -> can-modif [1]
      • +
    • epo-not:DesignContestNotice -> cn-desg [1]
      • +
    • epo-not:DesignContestResultNotice -> can-desg [1]
      • +
    • epo-not:PIN-CFCSocialNotice -> pin-cfc-social [1]
      • +
    • epo-not:PIN-CFCStandardNotice -> pin-cfc-standard [1]
      • +
    • epo-not:PINOnlyNotice -> pin-only [1]
      • +
    • epo-not:PINProfileNotice -> pin-buyer [1]
      • +
    • epo-not:PINTimeLimitNotice -> pin-rtl [1]
      • +
    • epo-not:PreMarketConsultationNotice -> pmc [1]
      • +
    • epo-not:QSNotice -> qu-sy [1]
      • +
    • epo-not:SubcontractNotice -> subco [1]
      • +
    • epo-not:VoluntaryEx-AnteTransparencyNotice -> veat [1]
    +
  • epo:hasNutsCode (2)
    • dct:Location -> at-voc:nuts [0..1]
    • locn:Address -> at-voc:nuts [0..1]
    @@ -766,6 +1222,7 @@

  • epo:hasPerformingStaffQualificationInformation
  • epo:hasPlannedDuration
  • epo:hasPlannedPeriod
    • +
  • epo:hasPriceSurchargeInformation
  • epo:hasPrimaryContactPoint
  • epo:hasPrizeValue
  • epo:hasProcedureType
    • @@ -786,6 +1243,7 @@

  • epo:ParticipationCondition -> at-voc:reserved-procurement [0..*]
  • epo:ParticipationConditionsSummary -> at-voc:reserved-procurement [0..*]

    • +
  • epo:hasResourceType
  • epo:hasReviewBodyType
  • epo:hasReviewDecisionType
  • epo:hasReviewIrregularitySummary
    • @@ -798,6 +1256,7 @@

  • epo:hasSubcontracting
  • epo:hasSubcontractingEstimatedValue
  • epo:hasSubcontractingObligation
    • +
  • epo:hasSubdivision
  • epo:hasTaxIdentifier
  • epo:hasTenderSubcontractingInformation
  • epo:hasTenderValidityDuration
    • @@ -808,19 +1267,19 @@

  • epo:hasTotalQuantity
  • epo:hasTotalValue (2)
    • epo:TenderGroup -> epo:MonetaryValue [0..1]
      • -
    • -> epo:MonetaryValue [0..1]
    +
  • epo-con:Deliverable -> epo:MonetaryValue [0..1]
  • epo:hasUnitCode
  • epo:hasUnofficialLanguage
  • epo:hasUsage
  • epo:hasUUID (2)
    • epo:Document -> adms:Identifier [0..1]
      • -
    • -> adms:Identifier [1]
    +
  • epo-cat:CatalogueResponseLine -> adms:Identifier [1]
  • epo:hasValidityPeriod (3)
    • cccev:Evidence -> epo:Period [0..1]
    • epo:Technique -> epo:Period [0..1]
      • -
    • -> epo:Period [0..1]
    +
  • epo-cat:Catalogue -> epo:Period [0..1]
  • epo:hasVariantPermission
  • epo:hasWeightValueType
    • @@ -834,8 +1293,8 @@

  • epo:isBasedOnImplementingRegulation
  • epo:isBeneficialOwnerOf
  • epo:isCalculatedOn (2)
      -
    • -> epo:MonetaryValue [0..1]
      • -
    • -> epo:MonetaryValue [0..1]
    +
  • epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [0..1]
    • +
  • epo-ord:TaxInformation -> epo:MonetaryValue [0..1]
  • epo:isExecutedByProcurementServiceProvider
  • epo:isFundedBy (2)
      @@ -861,36 +1320,36 @@

    • epo:playedBy (3)
      • epo:AgentInRole -> foaf:Agent [1]
      • epo:JuryMember -> person:Person [0..1]
        • -
      • -> foaf:Person [0..1]
      +
    • epo-ful:TransportMeansOperator -> foaf:Person [0..1]

  • epo:providesContractTotalPaymentValue
  • epo:providesContractTotalPenaltyValue
  • epo:providesRulingOnRemedy
  • epo:refersToAwardDecision (2)
      -
    • -> epo:AwardDecision [0..*]
      • -
    • -> epo:AwardDecision [0..*]
    +
  • epo-not:CompletionNotice -> epo:AwardDecision [0..*]
    • +
  • epo-not:ContractModificationNotice -> epo:AwardDecision [0..*]
  • epo:refersToContract
  • epo:refersToContractToBeModified
  • epo:refersToLot (4)
    • epo:Notice -> epo:Lot [1..*]
      • -
    • -> epo:Lot [1..*]
      • -
    • -> epo:Lot [1..*]
      • -
    • -> epo:Lot [1..*]
    +
  • epo-not:CompletionNotice -> epo:Lot [1..*]
    • +
  • epo-not:ContractModificationNotice -> epo:Lot [1..*]
    • +
  • epo-not:ResultNotice -> epo:Lot [1..*]
  • epo:refersToLotGroup (3)
      -
    • -> epo:LotGroup [0..*]
      • -
    • -> epo:LotGroup [0..*]
      • -
    • -> epo:LotGroup [0..*]
    +
  • epo-not:ContractModificationNotice -> epo:LotGroup [0..*]
    • +
  • epo-not:ResultNotice -> epo:LotGroup [0..*]
    • +
  • epo-not:CompletionNotice -> epo:LotGroup [0..*]
  • epo:refersToLotGroupAwardInformation (2)
      -
    • -> epo:LotGroupAwardInformation [0..*]
      • -
    • -> epo:LotGroupAwardInformation [0..*]
    +
  • epo-not:CompletionNotice -> epo:LotGroupAwardInformation [0..*]
    • +
  • epo-not:ContractModificationNotice -> epo:LotGroupAwardInformation [0..*]
  • epo:refersToNotice
  • epo:refersToNoticeAwardInformation (2)
      -
    • -> epo:NoticeAwardInformation [0..1]
      • -
    • -> epo:NoticeAwardInformation [0..1]
    +
  • epo-not:ContractModificationNotice -> epo:NoticeAwardInformation [0..1]
    • +
  • epo-not:CompletionNotice -> epo:NoticeAwardInformation [0..1]
  • epo:refersToPlannedPart
  • epo:refersToPrevious
    • @@ -900,16 +1359,16 @@

  • epo:refersToPreviousReview
  • epo:refersToProcedure (4)
    • epo:Notice -> epo:Procedure [1]
      • -
    • -> epo:Procedure [1]
      • -
    • -> epo:Procedure [1]
      • -
    • -> epo:Procedure [1]
    +
  • epo-not:ResultNotice -> epo:Procedure [1]
    • +
  • epo-not:ContractModificationNotice -> epo:Procedure [1]
    • +
  • epo-not:CompletionNotice -> epo:Procedure [1]
  • epo:refersToProject
  • epo:refersToRole
  • epo:relatesToEFormSectionIdentifier (3)
    • epo:ChangeInformation -> adms:Identifier [1..*]
    • epo:NonPublishedInformation -> adms:Identifier [1..*]
      • -
    • -> adms:Identifier [0..1]
    +
  • epo-con:ContractModificationInformation -> adms:Identifier [0..1]
  • epo:requestsRemedyType
  • epo:resolvesReviewRequest
    • @@ -924,26 +1383,34 @@

  • epo:signedByContractor
  • epo:signsAwardDecision
  • epo:specifiesBuyer (2)
      -
    • -> epo:Buyer [0..*]
      • -
    • -> epo:Buyer [1]
    +
  • epo-cat:Catalogue -> epo:Buyer [0..*]
    • +
  • epo-ord:Order -> epo:Buyer [1]
    • +
  • epo:specifiesCarrier
  • epo:specifiesCatalogueProvider (2)
      -
    • -> epo:CatalogueProvider [0..1]
      • -
    • -> epo:CatalogueProvider [1]
    +
  • epo-cat:Catalogue -> epo:CatalogueProvider [0..1]
    • +
  • epo-cat:CatalogueResponse -> epo:CatalogueProvider [1]
  • epo:specifiesCatalogueReceiver (2)
      -
    • -> epo:CatalogueReceiver [0..1]
      • -
    • -> epo:CatalogueReceiver [1]
    +
  • epo-cat:Catalogue -> epo:CatalogueReceiver [0..1]
    • +
  • epo-cat:CatalogueResponse -> epo:CatalogueReceiver [1]
  • epo:specifiesCleanVehicleDirectiveContractType
  • epo:specifiesCleanVehicleDirectiveVehicleCategory
  • epo:specifiesDeliverable
    • +
  • epo:specifiesDespatcher
    • +
  • epo:specifiesFreightForwarder
    • +
  • epo:specifiesNotifier
  • epo:specifiesProcurementCriteriaSummary
  • epo:specifiesProcurementCriterion (3)
      -
    • -> epo:ProcurementCriterion [1..*]
      • +
    • epo-acc:ESPDRequest -> epo:ProcurementCriterion [1..*]
    • epo:Lot -> epo:ProcurementCriterion [0..*]
    • epo:LotGroup -> epo:ProcurementCriterion [0..*]
    • +
  • epo:specifiesSeller (2)
      +
    • epo-cat:Catalogue -> epo-ord:Seller [0..*]
      • +
    • epo-ord:Order -> epo-ord:Seller [1]
    +
  • epo:specifiesSubcontractors
  • epo:substantiatesExclusionGround
  • epo:summarisesInformationForAwardOutcome
    • @@ -951,34 +1418,80 @@

  • epo:usesChannel
  • epo:usesTechnique
  • epo-acc:refersToNotice
    • +
  • epo-cat:comprisesCatalogueLine
    • +
  • epo-cat:comprisesCatalogueResponseLine
    • +
  • epo-cat:describesItem
    • +
  • epo-cat:foreseesPackage
    • +
  • epo-cat:hasAccessoryItem
    • +
  • epo-cat:hasActivityCode (2)
      +
    • epo-cat:Catalogue -> at-voc-new:activity-code [0..1]
      • +
    • epo-cat:CatalogueLine -> at-voc-new:activity-code [0..1]
    +
  • epo-cat:hasAmount (2)
      -
    • -> epo:MonetaryValue [1]
      • -
    • -> epo:MonetaryValue [0..1]
    +
  • epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [1]
    • +
  • epo-ord:TaxInformation -> epo:MonetaryValue [0..1]
  • epo-cat:hasBaseQuantity
    • +
  • epo-cat:hasBrand
  • epo-cat:hasCatalogueLineValidity
    • +
  • epo-cat:hasChargeInformation
    • +
  • epo-cat:hasComplementaryItem
  • epo-cat:hasCountryOfOrigin
    • +
  • epo-cat:hasDeliveryClassification
  • epo-cat:hasDeliveryLocation
    • +
  • epo-cat:hasDocumentType
  • epo-cat:hasExpectedDeliveryTime
  • epo-cat:hasExternalSpecification
    • +
  • epo-cat:hasHazardousItemUNDGCode
    • +
  • epo-cat:hasItemClassification
    • +
  • epo-cat:hasManufacturer
  • epo-cat:hasMaximumOrderQuantity
  • epo-cat:hasMinimumQuantityGuaranteedForDelivery
    • +
  • epo-cat:hasModel
  • epo-cat:hasNetMonetaryValue
  • epo-cat:hasNetQuantity
  • epo-cat:hasOrderabableUnitFactorRate
    • +
  • epo-cat:hasOrderableUnit
    • +
  • epo-cat:hasPrice (2)
      +
    • epo-ord:OrderLine -> epo-cat:Price [0..1]
      • +
    • epo-cat:CatalogueLine -> epo-cat:Price [1..*]
    +
    • +
  • epo-cat:hasPriceType
  • epo-cat:hasPriceValidity
    • +
  • epo-cat:hasQualifiedItemRelation
  • epo-cat:hasQualifiedValue
  • epo-cat:hasQuantity (2)
      -
    • -> epo:Quantity [1]
      • -
    • -> epo:Quantity [0..1]
    +
  • epo-ord:OrderLine -> epo:Quantity [1]
    • +
  • epo-con:Deliverable -> epo:Quantity [0..1]
  • epo-cat:hasQuantityThreshold
    • +
  • epo-cat:hasSpecification
    • +
  • epo-cat:hasStandardisedUnitPrice
    • +
  • epo-cat:hasTaxCategory
    • +
  • epo-cat:hasTaxScheme
    • +
  • epo-cat:hasTransactionConditionsCode
    • +
  • epo-cat:isProductionOf
    • +
  • epo-cat:isRelatedToItem
    • +
  • epo-cat:isSpecificToCatalogueResponseLine
    • +
  • epo-cat:isSpecificToLine
  • epo-cat:isSubordinatedToContract
    • +
  • epo-cat:refersToCatalogue
    • +
  • epo-cat:refersToCatalogueLine
    • +
  • epo-cat:specifiesCatalogueResponseInformation
    • +
  • epo-cat:specifiesChargeInformation
    • +
  • epo-cat:specifiesItem
  • epo-ful:agreedByBuyer
    • +
  • epo-ful:agreedBySeller
    • +
  • epo-ful:comprisesDespatchLine
    • +
  • epo-ful:comprisesReceiptAdviceLine
    • +
  • epo-ful:containsGoodsItem
    • +
  • epo-ful:containsPackage
    • +
  • epo-ful:containsTransportHandlingUnit
    • +
  • epo-ful:hasAllowanceChargeReason
  • epo-ful:hasAssociatedDocument (3)
      -
    • -> epo:Document [0..1]
      • -
    • -> epo:Document [0..1]
      • -
    • -> epo:Document [0..1]
    +
  • epo-ful:ReceiptAdvice -> epo:Document [0..1]
    • +
  • epo-ful:DespatchAdvice -> epo:Document [0..1]
    • +
  • epo-ful:DespatchLine -> epo:Document [0..1]
  • epo-ful:hasCarrierConsignmentID
  • epo-ful:hasChargeableWeight
    • @@ -987,73 +1500,158 @@

  • epo-ful:hasConsignmentFreeOnBoardValue
  • epo-ful:hasConsignmentInvoiceValue
  • epo-ful:hasDeclaredStatisticalValue
    • +
  • epo-ful:hasDepartureShipmentInformation
    • +
  • epo-ful:hasDespatchAdviceType
  • epo-ful:hasDespatchedQuantity
  • epo-ful:hasEstimatedDeliveryPeriod
    • +
  • epo-ful:hasFreightAllowanceCharge
  • epo-ful:hasFreightForwarderConsignmentID
  • epo-ful:hasGrossVolume (2)
      -
    • -> epo:Quantity [0..1]
      • -
    • -> epo:Quantity [0..1]
    +
  • epo-ful:AbstractContainer -> epo:Quantity [0..1]
    • +
  • epo-ful:Consignment -> epo:Quantity [0..1]
  • epo-ful:hasGrossWeight (2)
      -
    • -> epo:Quantity [0..1]
      • -
    • -> epo:Quantity [0..1]
    +
  • epo-ful:AbstractContainer -> epo:Quantity [0..1]
    • +
  • epo-ful:Consignment -> epo:Quantity [0..1]
    • + +
  • epo-ful:hasHandlingInstructionCode (2)
      +
    • epo-ful:Consignment -> at-voc-new:handling-instruction [0..1]
      • +
    • epo-ful:TransportHandlingUnit -> at-voc-new:handling-instruction [0..1]
  • epo-ful:hasHeight
  • epo-ful:hasLength
  • epo-ful:hasLoadingLength
    • +
  • epo-ful:hasMainCarriageShipmentStage
  • epo-ful:hasMaximumTemperature
  • epo-ful:hasMinimumTemperature
  • epo-ful:hasNetVolume
  • epo-ful:hasNetWeight (2)
      -
    • -> epo:Quantity [0..1]
      • -
    • -> epo:Quantity [0..1]
    +
  • epo-ful:AbstractContainer -> epo:Quantity [0..1]
    • +
  • epo-ful:Consignment -> epo:Quantity [0..1]
    • +
  • epo-ful:hasOnCarriageShipmentStage
  • epo-ful:hasOutstandingQuantity
  • epo-ful:hasOversupplyQuantity
    • +
  • epo-ful:hasPackagingType
    • +
  • epo-ful:hasPreCarriageShipmentStage
  • epo-ful:hasReceivedQuantity
    • +
  • epo-ful:hasRejectReason
    • +
  • epo-ful:hasRequestedPickUpInformation
    • +
  • epo-ful:hasShortageAction
  • epo-ful:hasShortQuantity
    • +
  • epo-ful:hasSizeType
    • +
  • epo-ful:hasTemperatureSpecification
  • epo-ful:hasTotalGoodsItemQuantity (2)
      -
    • -> epo:Quantity [0..1]
      • -
    • -> epo:Quantity [0..1]
    +
  • epo-ful:AbstractContainer -> epo:Quantity [0..1]
    • +
  • epo-ful:Consignment -> epo:Quantity [0..1]
  • epo-ful:hasTraceID
  • epo-ful:hasTrackingID
    • +
  • epo-ful:hasTransportEquipmentSeal
    • +
  • epo-ful:hasTransportEquipmentType
  • epo-ful:hasTransportHandlingUnitQuantity
    • +
  • epo-ful:hasTransportMeansType
    • +
  • epo-ful:hasTransportMode
  • epo-ful:hasVehicleID
  • epo-ful:hasVehicleSegmentID
  • epo-ful:hasWidth
    • +
  • epo-ful:isSpecificToDespatchLine
    • +
  • epo-ful:isSubmittedForDespatchAdvice
    • +
  • epo-ful:isSubmittedForDespatchLine
    • +
  • epo-ful:isSubmittedForShipment
    • +
  • epo-ful:refersToConsignment
    • +
  • epo-ful:refersToDeliveryInformation
    • +
  • epo-ful:refersToDespatchLine
    • +
  • epo-ful:refersToOrder
    • +
  • epo-ful:refersToOrderLine
    • +
  • epo-ful:refersToShipmentAgreement
    • +
  • epo-ful:RejectionAction
  • epo-ful:specifiesBuyer
    • +
  • epo-ful:specifiesConsignee (2)
      +
    • epo-ful:DespatchAdvice -> epo-ord:Consignee [1..*]
      • +
    • epo-ful:ReceiptAdvice -> epo-ord:Consignee [1..*]
    +
    • +
  • epo-ful:specifiesDespatcher (2)
      +
    • epo-ful:DespatchAdvice -> epo-ful:Despatcher [1..*]
      • +
    • epo-ful:ReceiptAdvice -> epo-ful:Despatcher [1]
    +
    • +
  • epo-ful:specifiesOriginator
  • epo-ful:specifiesPlaceOfDespatch
    • +
  • epo-ful:specifiesSeller
    • +
  • epo-ful:specifiesShipment
    • +
  • epo-ful:specifiesTransportHandlingUnits
    • +
  • epo-ful:transportsItemFrom
    • +
  • epo-ful:usesTransportEquipment
    • +
  • epo-ful:usesTransportMeans
  • epo-not:announcesRole
    • +
  • epo-not:hasLegalBasis
  • epo-not:refersToRole
    • +
  • epo-ord:comprisesOrderLine
    • +
  • epo-ord:comprisesOrderResponseLine
    • +
  • epo-ord:concernsConsignee
  • epo-ord:concernsContract
    • +
  • epo-ord:concernsOriginator
  • epo-ord:concernsOriginatorRequest
    • +
  • epo-ord:hasAcceptanceStatus (2)
      +
    • epo-cat:CatalogueResponseInformation -> at-voc-new:ResponseStatus [1]
      • +
    • epo-ord:OrderResponseInformation -> at-voc-new:ResponseStatus [1]
    +
  • epo-ord:hasAmountDueForPayment
  • epo-ord:hasDeliveryPeriod (2)
      -
    • -> epo:Period [0..1]
      • -
    • -> epo:Period [0..1]
    +
  • epo-ord:OrderResponseInformation -> epo:Period [0..1]
    • +
  • epo-ord:DeliveryInformation -> epo:Period [0..1]
  • epo-ord:hasPrepaidAmount
    • +
  • epo-ord:hasPriceDiscountInformation
  • epo-ord:hasRoundingAmount
  • epo-ord:hasSellerOrderID
    • -
  • epo-ord:hasTaxInformation
    • +
  • epo-ord:hasTaxInformation (3)
      +
    • epo:Contract -> epo-ord:TaxInformation [0..1]
      • +
    • epo-cat:Item -> epo-ord:TaxInformation [0..*]
      • +
    • epo-ord:AllowanceChargeInformation -> epo-ord:TaxInformation [0..1]
    +
  • epo-ord:hasTotalAllowanceAmount
  • epo-ord:hasTotalChargeAmount
  • epo-ord:hasTotalLineAmount
  • epo-ord:hasTotalTaxExclusiveAmount
  • epo-ord:hasTotalTaxInclusiveAmount
  • epo-ord:implementsContract
    • +
  • epo-ord:isSpecificToOrderLine (5)
      +
    • epo-cat:ChargeInformation -> epo-ord:OrderLine [0..*]
      • +
    • epo-ord:AllowanceInformation -> epo-ord:OrderLine [0..*]
      • +
    • epo-ord:ContractInformation -> epo-ord:OrderLine [0..*]
      • +
    • epo-ord:DeliveryInformation -> epo-ord:OrderLine [0..*]
      • +
    • epo-ord:OriginatorInformation -> epo-ord:OrderLine [0..*]
    +
    • +
  • epo-ord:isSpecificToOrderResponseLine
    • +
  • epo-ord:isSubmittedForOrder
    • +
  • epo-ord:isSubmittedForOrderLine
    • +
  • epo-ord:refersToCatalogue
    • +
  • epo-ord:refersToCatalogueLine
    • +
  • epo-ord:specifiesAllowanceInformation
  • epo-ord:specifiesBuyer
    • +
  • epo-ord:specifiesContractInformation
  • epo-ord:specifiesDeliveryAgreementLocation
    • +
  • epo-ord:specifiesDeliveryInformation
    • +
  • epo-ord:specifiesGeneralDeliveryAgreement
    • +
  • epo-ord:specifiesOrderResponseInformation
    • +
  • epo-ord:specifiesOriginatorInformation
  • epo-ord:specifiesPlaceOfDelivery
    • +
  • epo-ord:specifiesSeller
    • +
  • epo-ord:specifiesSpecificDeliveryAgreement
  • epo-sub:answersQuestion
  • epo-sub:concernsOrganisation
    • +
  • epo-sub:hasMandate
    • +
  • epo-sub:hasPowerOfAttorney
  • epo-sub:isReinforcedBy
  • epo-sub:providesInformationOn
  • epo-sub:providesOrganisationEmployeeQuantity
  • epo-sub:providesOrganisationFinancialCapability
  • epo-sub:providesOrganisationPreQualificationListingIdentifier
  • epo-sub:refersToApplicablePeriod
    • +
  • epo-sub:refersToOtherESPDResponse
    • +
  • epo-sub:relatesToESPDRequest
    • +
  • epo-sub:specifiesResponse
  • epo-sub:summarisesInformationAboutCertificate
  • locn:address (3)
    • cpov:ContactPoint -> locn:Address [0..1]
      • @@ -1075,6 +1673,14 @@

      +

      cccev:EvidenceType

      +
      +
      +
      Unmet class conventions
      +
      The class cccev:EvidenceType has no attributes provided. A class should define some + attributes.
      +
      +

      cccev:InformationRequirement

      @@ -1106,6 +1712,21 @@

      cv:C
      epo:hasAddressURL is missing a description. All concepts should be defined or described.

      +

      eli:LegalResourceSubdivision

      +
      +
      +
      Unmet class conventions
      +
      The class eli:LegalResourceSubdivision has no attributes provided. A class should + define some attributes.
      +
      +
      +

      eli:Work

      +
      +
      +
      Unmet class conventions
      +
      The class eli:Work has no attributes provided. A class should define some attributes.
      +
      +

      epo:AcquiringCentralPurchasingBody

      @@ -2147,1299 +2768,6666 @@

      epo:
      The class epo:Winner has no attributes provided. A class should define some attributes.

      -

      foaf:Agent

      +

      epo-acc:ESPDRequest

      -
      -
      epo:hasAlias
      +
      +
      Unmet class conventions
      +
      The class epo-acc:ESPDRequest has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-cat:CatalogueLine

      +
      +
      +
      epo-cat:hasTransactionConditions
      The name is possibly in plural grammatical number. Names shall be usually provided in singular number.
      -

      foaf:Person

      +

      epo-cat:CatalogueResponse

      Unmet class conventions
      -
      The class foaf:Person has no attributes provided. A class should define some attributes.
      +
      epo-cat:CatalogueResponse is missing a description. All concepts should be defined + or described.
      +
      The class epo-cat:CatalogueResponse has no attributes provided. A class should define + some attributes.
      -

      locn:Address

      +

      epo-cat:CatalogueResponseInformation

      Unmet class conventions
      -
      The name is possibly in plural grammatical number. Names shall be usually provided - in singular number.
      +
      epo-cat:CatalogueResponseInformation is missing a description. All concepts should + be defined or described.
      +
      The class epo-cat:CatalogueResponseInformation has no attributes provided. A class + should define some attributes.
      -
      -
      locn:fullAddress
      -
      The name is possibly in plural grammatical number. Names shall be usually provided - in singular number.
      +
      +

      epo-cat:CatalogueResponseLine

      +
      +
      +
      Unmet class conventions
      +
      epo-cat:CatalogueResponseLine is missing a description. All concepts should be defined + or described.
      +
      The class epo-cat:CatalogueResponseLine has no attributes provided. A class should + define some attributes.
      -

      locn:Geometry

      +

      epo-cat:ChargeInformation

      -
      -
      cv:coordinates
      -
      The name is possibly in plural grammatical number. Names shall be usually provided - in singular number.
      +
      +
      Unmet class conventions
      +
      The class epo-cat:ChargeInformation has no attributes provided. A class should define + some attributes.
      -

      org:Organization

      +

      epo-cat:InformationHub

      -
      -
      epo:hasInternetAddress
      +
      +
      Unmet class conventions
      +
      The class epo-cat:InformationHub has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-cat:Item

      +
      +
      +
      epo-cat:hasHazardousClass
      The name is possibly in plural grammatical number. Names shall be usually provided in singular number.
      -

      time:Duration

      +

      epo-cat:ItemAccessoryRelation

      Unmet class conventions
      -
      The class time:Duration has no attributes provided. A class should define some attributes.
      +
      The class epo-cat:ItemAccessoryRelation has no attributes provided. A class should + define some attributes.
      -

      Enumerations

      -

      at-voc:access-rights

      +

      epo-cat:ItemComplementaryRelation

      -
      Unmet enumeration conventions
      -
      The name is possibly in plural grammatical number. Names shall be usually provided - in singular number.
      +
      Unmet class conventions
      +
      The class epo-cat:ItemComplementaryRelation has no attributes provided. A class should + define some attributes.
      -

      at-voc:cvd-contract-type

      +

      epo-cat:ItemComposition

      -
      Unmet enumeration conventions
      -
      at-voc:cvd-contract-type is missing a description. All concepts should be defined +
      Unmet class conventions
      +
      The class epo-cat:ItemComposition has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-cat:ItemReplacement

      +
      +
      +
      Unmet class conventions
      +
      The class epo-cat:ItemReplacement has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-cat:ItemRequirement

      +
      +
      +
      Unmet class conventions
      +
      The class epo-cat:ItemRequirement has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-cat:Line

      +
      +
      +
      Unmet class conventions
      +
      epo-cat:Line is missing a description. All concepts should be defined or described.
      +
      +
      +

      epo-cat:Manufacturer

      +
      +
      +
      Unmet class conventions
      +
      The class epo-cat:Manufacturer has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-cat:PostAwardDocument

      +
      +
      +
      Unmet class conventions
      +
      epo-cat:PostAwardDocument is missing a description. All concepts should be defined or described.
      +
      The class epo-cat:PostAwardDocument has no attributes provided. A class should define + some attributes.
      -

      at-voc:green-public-procurement-criteria

      +

      epo-cat:Price

      -
      Unmet enumeration conventions
      -
      at-voc:green-public-procurement-criteria is missing a description. All concepts should +
      Unmet class conventions
      +
      The class epo-cat:Price has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-cat:ProductSpecification

      +
      +
      +
      Unmet class conventions
      +
      The class epo-cat:ProductSpecification has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-con:ContractAmendment

      +
      +
      +
      Unmet class conventions
      +
      The class epo-con:ContractAmendment has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-con:ContractModificationInformation

      +
      +
      +
      Unmet class conventions
      +
      epo-con:ContractModificationInformation is missing a description. All concepts should be defined or described.
      -

      at-voc:legal-basis

      +

      epo-con:Deliverable

      -
      Unmet enumeration conventions
      -
      The name is possibly in plural grammatical number. Names shall be usually provided - in singular number.
      +
      Unmet class conventions
      +
      epo-con:Deliverable is missing a description. All concepts should be defined or described.
      +
      The class epo-con:Deliverable has no attributes provided. A class should define some + attributes.
      -

      at-voc:nuts

      +

      epo-ful:AbstractContainer

      -
      Unmet enumeration conventions
      -
      The name is possibly in plural grammatical number. Names shall be usually provided - in singular number.
      +
      Unmet class conventions
      +
      epo-ful:AbstractContainer is missing a description. All concepts should be defined + or described.
      +
      +
      +
      epo-ful:isReturnableMaterial
      +
      epo-ful:isReturnableMaterial is missing a description. All concepts should be defined + or described.
      +
      +
      +
      epo-ful:isHazardousRisk
      +
      epo-ful:isHazardousRisk is missing a description. All concepts should be defined or + described.
      -

      at-voc:vehicle-category

      +

      epo-ful:Carrier

      -
      Unmet enumeration conventions
      -
      at-voc:vehicle-category is missing a description. All concepts should be defined or +
      Unmet class conventions
      +
      The class epo-ful:Carrier has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-ful:Consignment

      +
      +
      +
      epo-ful:hasVehicleDescription
      +
      epo-ful:hasVehicleDescription is missing a description. All concepts should be defined + or described.
      +
      +
      +
      epo-ful:isHazardousRisk
      +
      epo-ful:isHazardousRisk is missing a description. All concepts should be defined or described.
      +
      +
      epo-ful:hasHandlingInstruction
      +
      epo-ful:hasHandlingInstruction is missing a description. All concepts should be defined + or described.
      +
      +
      +
      epo-ful:hasCarrierServiceInstruction
      +
      epo-ful:hasCarrierServiceInstruction is missing a description. All concepts should + be defined or described.
      +
      +
      +
      epo-ful:hasSpecialInstruction
      +
      epo-ful:hasSpecialInstruction is missing a description. All concepts should be defined + or described.
      +
      +
      +
      epo-ful:hasDeliveryInstruction
      +
      epo-ful:hasDeliveryInstruction is missing a description. All concepts should be defined + or described.
      +
      +
      +
      epo-ful:hasSpecialServiceInstruction
      +
      epo-ful:hasSpecialServiceInstruction is missing a description. All concepts should + be defined or described.
      +
      -

      at-voc:winner-selection-status

      +

      epo-ful:DespatchAdvice

      -
      Unmet enumeration conventions
      -
      The name is possibly in plural grammatical number. Names shall be usually provided - in singular number.
      +
      Unmet class conventions
      +
      epo-ful:DespatchAdvice is missing a description. All concepts should be defined or + described.
      +
      The class epo-ful:DespatchAdvice has no attributes provided. A class should define + some attributes.
      -

      Data-types

      -

      rdf:PlainLiteral

      -
      -
      - Unmet data-type conventions -
      -
      rdf:PlainLiteral is missing a description. All concepts should be defined or described.
      -
      -

      xsd:anyURI

      -
      -
      - Unmet data-type conventions -
      -
      xsd:anyURI is missing a description. All concepts should be defined or described.
      -
      -

      xsd:boolean

      -
      -
      - Unmet data-type conventions -
      -
      xsd:boolean is missing a description. All concepts should be defined or described.
      -
      -

      xsd:date

      -
      -
      - Unmet data-type conventions -
      -
      xsd:date is missing a description. All concepts should be defined or described.
      -
      -

      xsd:dateTime

      -
      -
      - Unmet data-type conventions -
      -
      xsd:dateTime is missing a description. All concepts should be defined or described.
      -
      -

      xsd:decimal

      -
      -
      - Unmet data-type conventions -
      -
      xsd:decimal is missing a description. All concepts should be defined or described.
      -
      -

      xsd:integer

      -
      -
      - Unmet data-type conventions -
      -
      xsd:integer is missing a description. All concepts should be defined or described.
      -
      -

      Packages

      -

      access term

      -
      -
      - Unmet package conventions -
      -
      The package access term is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      -
      -

      agent

      -
      -
      - Unmet package conventions -
      -
      The package agent is empty. Packages must contain child classes and conenctors (i.e. - owned elements).
      +

      epo-ful:Despatcher

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ful:Despatcher has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-ful:DespatchLine

      +
      +
      +
      Unmet class conventions
      +
      epo-ful:DespatchLine is missing a description. All concepts should be defined or described.
      +
      +
      +
      epo-ful:hasOutstandingQuantityReason
      +
      epo-ful:hasOutstandingQuantityReason is missing a description. All concepts should + be defined or described.
      +
      +
      +

      epo-ful:FreightForwarder

      +
      +
      +
      Unmet class conventions
      +
      epo-ful:FreightForwarder is missing a description. All concepts should be defined + or described.
      +
      The class epo-ful:FreightForwarder has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-ful:GoodsItem

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ful:GoodsItem has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-ful:Notifier

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ful:Notifier has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-ful:Package

      +
      +
      +
      Unmet class conventions
      +
      epo-ful:Package is missing a description. All concepts should be defined or described.
      +
      +
      +
      epo-ful:hasPackagingTypeDescription
      +
      epo-ful:hasPackagingTypeDescription is missing a description. All concepts should + be defined or described.
      +
      +
      +

      epo-ful:ReceiptAdvice

      +
      +
      +
      Unmet class conventions
      +
      epo-ful:ReceiptAdvice is missing a description. All concepts should be defined or + described.
      +
      The class epo-ful:ReceiptAdvice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-ful:ReceiptAdviceLine

      +
      +
      +
      Unmet class conventions
      +
      epo-ful:ReceiptAdviceLine is missing a description. All concepts should be defined + or described.
      +
      The class epo-ful:ReceiptAdviceLine has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-ful:ShipmentAgreement

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ful:ShipmentAgreement has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-ful:ShipmentInformation

      +
      +
      +
      epo-ful:despatchDate
      +
      epo-ful:despatchDate is missing a description. All concepts should be defined or described.
      +
      +
      +

      epo-ful:ShipmentStage

      +
      +
      +
      Unmet class conventions
      +
      epo-ful:ShipmentStage is missing a description. All concepts should be defined or + described.
      +
      +
      +
      epo-ful:isHazardousRisk
      +
      epo-ful:isHazardousRisk is missing a description. All concepts should be defined or + described.
      +
      +
      +

      epo-ful:TemperatureSpecification

      +
      +
      +
      Unmet class conventions
      +
      epo-ful:TemperatureSpecification is missing a description. All concepts should be + defined or described.
      +
      +
      +

      epo-ful:TransportEquipment

      +
      +
      +
      Unmet class conventions
      +
      epo-ful:TransportEquipment is missing a description. All concepts should be defined + or described.
      +
      +
      +
      epo-ful:isReturnable
      +
      epo-ful:isReturnable is missing a description. All concepts should be defined or described.
      +
      +
      +
      epo-ful:isRefrigerated
      +
      epo-ful:isRefrigerated is missing a description. All concepts should be defined or + described.
      +
      +
      +
      epo-ful:isPowerIndicated
      +
      epo-ful:isPowerIndicated is missing a description. All concepts should be defined + or described.
      +
      +
      +

      epo-ful:TransportEquipmentSeal

      +
      +
      +
      Unmet class conventions
      +
      epo-ful:TransportEquipmentSeal is missing a description. All concepts should be defined + or described.
      +
      The class epo-ful:TransportEquipmentSeal has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-ful:TransportHandlingUnit

      +
      +
      +
      epo-ful:hasShippingMark
      +
      epo-ful:hasShippingMark is missing a description. All concepts should be defined or + described.
      +
      +
      +
      epo-ful:hasHandlingInstruction
      +
      epo-ful:hasHandlingInstruction is missing a description. All concepts should be defined + or described.
      +
      +
      +

      epo-ful:TransportMeans

      +
      +
      +
      Unmet class conventions
      +
      epo-ful:TransportMeans is missing a description. All concepts should be defined or + described.
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      The class epo-ful:TransportMeans has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-ful:TransportMeansOperator

      +
      +
      +
      Unmet class conventions
      +
      epo-ful:TransportMeansOperator is missing a description. All concepts should be defined + or described.
      +
      The class epo-ful:TransportMeansOperator has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-not:CANDefence-D81

      +
      +
      +
      Unmet class conventions
      +
      epo-not:CANDefence-D81 is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:CANDefence-D81 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CANSocial-D25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:CANSocial-D25 is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:CANSocial-D25 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CANSocialNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:CANSocialNotice is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:CANSocialNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CANSocialNotice-D25

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:CANSocialNotice-D25 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CANStandard-D24

      +
      +
      +
      Unmet class conventions
      +
      epo-not:CANStandard-D24 is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:CANStandard-D24 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CANStandardNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:CANStandardNotice is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:CANStandardNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CNDefence-D81

      +
      +
      +
      Unmet class conventions
      +
      epo-not:CNDefence-D81 is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:CNDefence-D81 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CNSocial-D25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:CNSocial-D25 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:CNSocial-D25 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:CNSocialNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:CNSocialNotice is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:CNSocialNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CNSocialNotice-D25

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:CNSocialNotice-D25 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CNStandard-D24

      +
      +
      +
      Unmet class conventions
      +
      epo-not:CNStandard-D24 is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:CNStandard-D24 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CNStandardNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:CNStandardNotice is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:CNStandardNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CompetitionNotice

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:CompetitionNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:CompletionNotice

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:CompletionNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:ConcessionAwardNotice-D23

      +
      +
      +
      Unmet class conventions
      +
      epo-not:ConcessionAwardNotice-D23 is missing a description. All concepts should be + defined or described.
      +
      The class epo-not:ConcessionAwardNotice-D23 has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-not:ConcessionNotice-D23

      +
      +
      +
      Unmet class conventions
      +
      epo-not:ConcessionNotice-D23 is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:ConcessionNotice-D23 has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-not:ContractModificationNotice

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:ContractModificationNotice has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-not:DesignContest-D24

      +
      +
      +
      Unmet class conventions
      +
      epo-not:DesignContest-D24 is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:DesignContest-D24 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:DesignContest-D25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:DesignContest-D25 is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:DesignContest-D25 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:DesignContestNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:DesignContestNotice is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:DesignContestNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:DesignContestResult-D24

      +
      +
      +
      Unmet class conventions
      +
      epo-not:DesignContestResult-D24 is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:DesignContestResult-D24 has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-not:DesignContestResult-D25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:DesignContestResult-D25 is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:DesignContestResult-D25 has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-not:DesignContestResultNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:DesignContestResultNotice is missing a description. All concepts should be + defined or described.
      +
      The class epo-not:DesignContestResultNotice has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-not:DirectAwardPrenotificationNotice

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:DirectAwardPrenotificationNotice has no attributes provided. A class + should define some attributes.
      +
      +
      +

      epo-not:eFormsNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:eFormsNotice is missing a description. All concepts should be defined or described.
      +
      The class name epo-not:eFormsNotice is invalid. The class name must start with a capital + case.
      +
      The class epo-not:eFormsNotice has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Modification-D23

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Modification-D23 is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:Modification-D23 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:Modification-D24

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Modification-D24 is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:Modification-D24 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:Modification-D25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Modification-D25 is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:Modification-D25 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:Notice1

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice1 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice1 has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-not:Notice10

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice10 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice10 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice11

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice11 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice11 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice12

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice12 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice12 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice13

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice13 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice13 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice14

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice14 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice14 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice15

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice15 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice15 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice16

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice16 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice16 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice17

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice17 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice17 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice18

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice18 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice18 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice19

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice19 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice19 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice2

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice2 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice2 has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-not:Notice20

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice20 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice20 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice21

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice21 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice21 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice22

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice22 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice22 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice23

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice23 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice23 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice24

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice24 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice24 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice25 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice25 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice26

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice26 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice26 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice27

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice27 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice27 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice28

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice28 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice28 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice29

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice29 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice29 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice3

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice3 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice3 has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-not:Notice30

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice30 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice30 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice31

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice31 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice31 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice32

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice32 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice32 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice33

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice33 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice33 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice34

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice34 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice34 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice35

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice35 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice35 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice36

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice36 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice36 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice37

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice37 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice37 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice38

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice38 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice38 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice39

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice39 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice39 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice4

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice4 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice4 has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-not:Notice40

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice40 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice40 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:Notice5

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice5 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice5 has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-not:Notice6

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice6 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice6 has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-not:Notice7

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice7 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice7 has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-not:Notice8

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice8 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice8 has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-not:Notice9

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Notice9 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:Notice9 has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-not:PIN-CFCSocial-D25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PIN-CFCSocial-D25 is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:PIN-CFCSocial-D25 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:PIN-CFCSocialNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PIN-CFCSocialNotice is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:PIN-CFCSocialNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:PIN-CFCSocialNotice-D25

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:PIN-CFCSocialNotice-D25 has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-not:PIN-CFCStandard-D24

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PIN-CFCStandard-D24 is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:PIN-CFCStandard-D24 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:PIN-CFCStandardNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PIN-CFCStandardNotice is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:PIN-CFCStandardNotice has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-not:PINDefence-D81

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PINDefence-D81 is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:PINDefence-D81 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:PINOnly-D24

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PINOnly-D24 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:PINOnly-D24 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:PINOnly-D25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PINOnly-D25 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:PINOnly-D25 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:PINOnlyNotice

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:PINOnlyNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:PINProfile-D24

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PINProfile-D24 is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:PINProfile-D24 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:PINProfile-D25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PINProfile-D25 is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:PINProfile-D25 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:PINProfile-D81

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PINProfile-D81 is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:PINProfile-D81 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:PINProfileNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PINProfileNotice is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:PINProfileNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:PIN-RTL-D24

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PIN-RTL-D24 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:PIN-RTL-D24 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:PIN-RTL-D25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PIN-RTL-D25 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:PIN-RTL-D25 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:PINTimeLimitNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PINTimeLimitNotice is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:PINTimeLimitNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:PlanningNotice

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:PlanningNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:PreMarketConsultationNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:PreMarketConsultationNotice is missing a description. All concepts should + be defined or described.
      +
      The class epo-not:PreMarketConsultationNotice has no attributes provided. A class + should define some attributes.
      +
      +
      +

      epo-not:QS-D25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:QS-D25 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:QS-D25 has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-not:QSNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:QSNotice is missing a description. All concepts should be defined or described.
      +
      The class epo-not:QSNotice has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:QSNotice-D25

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:QSNotice-D25 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:ResultNotice

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:ResultNotice has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:SocialAndOtherSpecificServices-D23

      +
      +
      +
      Unmet class conventions
      +
      epo-not:SocialAndOtherSpecificServices-D23 is missing a description. All concepts + should be defined or described.
      +
      The class epo-not:SocialAndOtherSpecificServices-D23 has no attributes provided. A + class should define some attributes.
      +
      +
      +

      epo-not:SocialAndOtherSpecificServices-D24

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:SocialAndOtherSpecificServices-D24 has no attributes provided. A + class should define some attributes.
      +
      +
      +

      epo-not:StandardFormsNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:StandardFormsNotice is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:StandardFormsNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:Subcontract-D81

      +
      +
      +
      Unmet class conventions
      +
      epo-not:Subcontract-D81 is missing a description. All concepts should be defined or + described.
      +
      The class epo-not:Subcontract-D81 has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:SubcontractNotice

      +
      +
      +
      Unmet class conventions
      +
      epo-not:SubcontractNotice is missing a description. All concepts should be defined + or described.
      +
      The class epo-not:SubcontractNotice has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-not:VEAT-D23

      +
      +
      +
      Unmet class conventions
      +
      epo-not:VEAT-D23 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:VEAT-D23 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:VEAT-D24

      +
      +
      +
      Unmet class conventions
      +
      epo-not:VEAT-D24 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:VEAT-D24 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:VEAT-D25

      +
      +
      +
      Unmet class conventions
      +
      epo-not:VEAT-D25 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:VEAT-D25 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:VEAT-D81

      +
      +
      +
      Unmet class conventions
      +
      epo-not:VEAT-D81 is missing a description. All concepts should be defined or described.
      +
      The class epo-not:VEAT-D81 has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-not:VoluntaryEx-AnteTransparencyNotice

      +
      +
      +
      Unmet class conventions
      +
      The class epo-not:VoluntaryEx-AnteTransparencyNotice has no attributes provided. A + class should define some attributes.
      +
      +
      +

      epo-ord:AllowanceChargeInformation

      +
      +
      +
      epo-ful:hasAllowanceChargeReasonDescription
      +
      epo-ful:hasAllowanceChargeReasonDescription is missing a description. All concepts + should be defined or described.
      +
      +
      +

      epo-ord:AllowanceInformation

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ord:AllowanceInformation has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-ord:Consignee

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ord:Consignee has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-ord:ContractInformation

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ord:ContractInformation has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-ord:DeliveryInformation

      +
      +
      +
      epo-ord:hasShippingMark
      +
      epo-ord:hasShippingMark is missing a description. All concepts should be defined or + described.
      +
      +
      +
      epo-ord:hasDeliveryDeadline
      +
      epo-ord:hasDeliveryDeadline is missing a description. All concepts should be defined + or described.
      +
      +
      +

      epo-ord:Order

      +
      +
      +
      epo-ord:hasPaymentTerm
      +
      epo-ord:hasPaymentTerm is missing a description. All concepts should be defined or + described.
      +
      +
      +

      epo-ord:OrderLine

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ord:OrderLine has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-ord:OrderResponseInformation

      +
      +
      +
      Unmet class conventions
      +
      epo-ord:OrderResponseInformation is missing a description. All concepts should be + defined or described.
      +
      The class epo-ord:OrderResponseInformation has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-ord:OrderResponseLine

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ord:OrderResponseLine has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-ord:Originator

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ord:Originator has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-ord:OriginatorInformation

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ord:OriginatorInformation has no attributes provided. A class should + define some attributes.
      +
      +
      +

      epo-ord:Seller

      +
      +
      +
      Unmet class conventions
      +
      The class epo-ord:Seller has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-sub:ESPDResponse

      +
      +
      +
      Unmet class conventions
      +
      The class epo-sub:ESPDResponse has no attributes provided. A class should define some + attributes.
      +
      +
      +

      epo-sub:LegalRepresentative

      +
      +
      +
      Unmet class conventions
      +
      The class epo-sub:LegalRepresentative has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-sub:Mandate

      +
      +
      +
      Unmet class conventions
      +
      The class epo-sub:Mandate has no attributes provided. A class should define some attributes.
      +
      +
      +

      epo-sub:PowerOfAttorney

      +
      +
      +
      Unmet class conventions
      +
      The class epo-sub:PowerOfAttorney has no attributes provided. A class should define + some attributes.
      +
      +
      +

      epo-sub:Response

      +
      +
      +
      Unmet class conventions
      +
      The class epo-sub:Response has no attributes provided. A class should define some + attributes.
      +
      +
      +

      foaf:Agent

      +
      +
      +
      epo:hasAlias
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +

      foaf:Person

      +
      +
      +
      Unmet class conventions
      +
      The class foaf:Person has no attributes provided. A class should define some attributes.
      +
      +
      +

      locn:Address

      +
      +
      +
      Unmet class conventions
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +
      locn:fullAddress
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +

      locn:Geometry

      +
      +
      +
      cv:coordinates
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +

      org:Organization

      +
      +
      +
      epo:hasInternetAddress
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +

      time:Duration

      +
      +
      +
      Unmet class conventions
      +
      The class time:Duration has no attributes provided. A class should define some attributes.
      +
      +
      +

      Enumerations

      +

      at-voc:access-rights

      +
      +
      +
      Unmet enumeration conventions
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +

      at-voc:cvd-contract-type

      +
      +
      +
      Unmet enumeration conventions
      +
      at-voc:cvd-contract-type is missing a description. All concepts should be defined + or described.
      +
      +
      +

      at-voc:green-public-procurement-criteria

      +
      +
      +
      Unmet enumeration conventions
      +
      at-voc:green-public-procurement-criteria is missing a description. All concepts should + be defined or described.
      +
      +
      +

      at-voc:legal-basis

      +
      +
      +
      Unmet enumeration conventions
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +

      at-voc:nuts

      +
      +
      +
      Unmet enumeration conventions
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +

      at-voc:vehicle-category

      +
      +
      +
      Unmet enumeration conventions
      +
      at-voc:vehicle-category is missing a description. All concepts should be defined or + described.
      +
      +
      +

      at-voc:winner-selection-status

      +
      +
      +
      Unmet enumeration conventions
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +

      at-voc-new:allowance-charge-reason

      +
      +
      +
      Unmet enumeration conventions
      +
      at-voc-new:allowance-charge-reason is missing a description. All concepts should be + defined or described.
      +
      +
      +

      at-voc-new:dangerous-goods-list

      +
      +
      +
      Unmet enumeration conventions
      +
      at-voc-new:dangerous-goods-list is missing a description. All concepts should be defined + or described.
      +
      +
      +

      at-voc-new:despatch-advice-type

      +
      +
      +
      Unmet enumeration conventions
      +
      at-voc-new:despatch-advice-type is missing a description. All concepts should be defined + or described.
      +
      +
      +

      at-voc-new:document-status

      +
      +
      +
      Unmet enumeration conventions
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +

      at-voc-new:ResponseStatus

      +
      +
      +
      Unmet enumeration conventions
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      The enumeration at-voc-new:ResponseStatus shall have no values/attributes defined. + An Enumeration stands for a controlled list and its management is out of model scope. +
      +
      +
      +

      at-voc-new:transaction-conditions

      +
      +
      +
      Unmet enumeration conventions
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +

      epo-not:StandardForm

      +
      +
      +
      Unmet enumeration conventions
      +
      epo-not:StandardForm is missing a description. All concepts should be defined or described.
      +
      +
      +

      Data-types

      +

      rdf:PlainLiteral

      +
      +
      + Unmet data-type conventions +
      +
      rdf:PlainLiteral is missing a description. All concepts should be defined or described.
      +
      +

      xsd:anyURI

      +
      +
      + Unmet data-type conventions +
      +
      xsd:anyURI is missing a description. All concepts should be defined or described.
      +
      +

      xsd:boolean

      +
      +
      + Unmet data-type conventions +
      +
      xsd:boolean is missing a description. All concepts should be defined or described.
      +
      +

      xsd:date

      +
      +
      + Unmet data-type conventions +
      +
      xsd:date is missing a description. All concepts should be defined or described.
      +
      +

      xsd:dateTime

      +
      +
      + Unmet data-type conventions +
      +
      xsd:dateTime is missing a description. All concepts should be defined or described.
      +
      +

      xsd:decimal

      +
      +
      + Unmet data-type conventions +
      +
      xsd:decimal is missing a description. All concepts should be defined or described.
      +
      +

      xsd:integer

      +
      +
      + Unmet data-type conventions +
      +
      xsd:integer is missing a description. All concepts should be defined or described.
      +
      +

      Packages

      +

      access term

      +
      +
      + Unmet package conventions +
      +
      The package access term is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      agent

      +
      +
      + Unmet package conventions +
      +
      The package agent is empty. Packages must contain child classes and conenctors (i.e. + owned elements).
      +
      +

      award

      +
      +
      + Unmet package conventions +
      +
      The package award is empty. Packages must contain child classes and conenctors (i.e. + owned elements).
      +
      +

      competition notices

      +
      +
      + Unmet package conventions +
      +
      The package competition notices is empty. Packages must contain child classes and + conenctors (i.e. owned elements).
      +
      +

      competition subtype notices

      +
      +
      + Unmet package conventions +
      +
      The package competition subtype notices is empty. Packages must contain child classes + and conenctors (i.e. owned elements).
      +
      +

      completion notices

      +
      +
      + Unmet package conventions +
      +
      The package completion notices is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      completion subtype notices

      +
      +
      + Unmet package conventions +
      +
      The package completion subtype notices is empty. Packages must contain child classes + and conenctors (i.e. owned elements).
      +
      +

      contextual description

      +
      +
      + Unmet package conventions +
      +
      The package contextual description is empty. Packages must contain child classes and + conenctors (i.e. owned elements).
      +
      +

      contract

      +
      +
      + Unmet package conventions +
      +
      The package contract is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      contract modification notices

      +
      +
      + Unmet package conventions +
      +
      The package contract modification notices is empty. Packages must contain child classes + and conenctors (i.e. owned elements).
      +
      +

      contract modification subtype notices

      +
      +
      + Unmet package conventions +
      +
      The package contract modification subtype notices is empty. Packages must contain + child classes and conenctors (i.e. owned elements).
      +
      +

      contract term

      +
      +
      + Unmet package conventions +
      +
      The package contract term is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      criterion

      +
      +
      + Unmet package conventions +
      +
      The package criterion is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      DAP notices

      +
      +
      + Unmet package conventions +
      +
      The package DAP notices is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      DAP subtype notices

      +
      +
      + Unmet package conventions +
      +
      The package DAP subtype notices is empty. Packages must contain child classes and + conenctors (i.e. owned elements).
      +
      +

      diagrams

      +
      +
      + Unmet package conventions +
      +
      The package diagrams is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      diagrams

      +
      +
      + Unmet package conventions +
      +
      The package diagrams is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      evaluation term

      +
      +
      + Unmet package conventions +
      +
      The package evaluation term is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      location

      +
      +
      + Unmet package conventions +
      +
      The package location is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      participation request term

      +
      +
      + Unmet package conventions +
      +
      The package participation request term is empty. Packages must contain child classes + and conenctors (i.e. owned elements).
      +
      +

      phase oriented

      +
      +
      + Unmet package conventions +
      +
      The package phase oriented is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      planning notices

      +
      +
      + Unmet package conventions +
      +
      The package planning notices is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      planning subtype notices

      +
      +
      + Unmet package conventions +
      +
      The package planning subtype notices is empty. Packages must contain child classes + and conenctors (i.e. owned elements).
      +
      +

      premarket consultation notice

      +
      +
      + Unmet package conventions +
      +
      The package premarket consultation notice is empty. Packages must contain child classes + and conenctors (i.e. owned elements).
      +
      +

      procedure term

      +
      +
      + Unmet package conventions +
      +
      The package procedure term is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      procurement object

      +
      +
      + Unmet package conventions +
      +
      The package procurement object is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      result notices

      +
      +
      + Unmet package conventions +
      +
      The package result notices is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      result subtype notices

      +
      +
      + Unmet package conventions +
      +
      The package result subtype notices is empty. Packages must contain child classes and + conenctors (i.e. owned elements).
      +
      +

      review

      +
      +
      + Unmet package conventions +
      +
      The package review is empty. Packages must contain child classes and conenctors (i.e. + owned elements).
      +
      +

      review term

      +
      +
      + Unmet package conventions +
      +
      The package review term is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      role playing sides

      +
      +
      + Unmet package conventions +
      +
      The package role playing sides is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      role predecessor dependecies

      +
      +
      + Unmet package conventions +
      +
      The package role predecessor dependecies is empty. Packages must contain child classes + and conenctors (i.e. owned elements).
      +
      +

      standardFormsD25

      +
      +
      + Unmet package conventions +
      +
      The package standardFormsD25 is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      strategic procurement

      +
      +
      + Unmet package conventions +
      +
      The package strategic procurement is empty. Packages must contain child classes and + conenctors (i.e. owned elements).
      +
      +

      submission term

      +
      +
      + Unmet package conventions +
      +
      The package submission term is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      technique

      +
      +
      + Unmet package conventions +
      +
      The package technique is empty. Packages must contain child classes and conenctors + (i.e. owned elements).
      +
      +

      Object

      +

      (EU) 2015/1986

      +
      +
      +
      Unmet object conventions
      +
      The name (EU) 2015/1986 does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element (EU) 2015/1986 is missing a prefix. The name should comprise a + prefix respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      The local name segment , is invalid. Please provide a concise label using alphanumeric + characters [a-zA-Z0-9_\-\s]+, preferably in CamelCase, or possibly with tokens delimited + by single spaces.
      +
      The local name segment (EU) 2015/1986 starts with an invalid character. The local + segment must start with a letter or underscore.
      +
      The local name segment (EU) 2015/1986 contains token delimiters. It is best if the + names are camel cased and delimiters removed.
      +
      (EU) 2015/1986 is missing a description. All concepts should be defined or described.
      +
      +
      +

      (EU) 2019/1780

      +
      +
      +
      Unmet object conventions
      +
      The name (EU) 2019/1780 does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element (EU) 2019/1780 is missing a prefix. The name should comprise a + prefix respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      The local name segment , is invalid. Please provide a concise label using alphanumeric + characters [a-zA-Z0-9_\-\s]+, preferably in CamelCase, or possibly with tokens delimited + by single spaces.
      +
      The local name segment (EU) 2019/1780 starts with an invalid character. The local + segment must start with a letter or underscore.
      +
      The local name segment (EU) 2019/1780 contains token delimiters. It is best if the + names are camel cased and delimiters removed.
      +
      (EU) 2019/1780 is missing a description. All concepts should be defined or described.
      +
      +
      +

      bri

      +
      +
      +
      Unmet object conventions
      +
      The name bri does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element bri is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      bri is missing a description. All concepts should be defined or described.
      +
      +
      +

      brin-ecs

      +
      +
      +
      Unmet object conventions
      +
      The name brin-ecs does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element brin-ecs is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      The name is possibly in plural grammatical number. Names shall be usually provided + in singular number.
      +
      +
      +

      can-desg

      +
      +
      +
      Unmet object conventions
      +
      The name can-desg does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element can-desg is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      can-modif

      +
      +
      +
      Unmet object conventions
      +
      The name can-modif does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element can-modif is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      can-social

      +
      +
      +
      Unmet object conventions
      +
      The name can-social does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element can-social is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      can-standard

      +
      +
      +
      Unmet object conventions
      +
      The name can-standard does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element can-standard is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      change

      +
      +
      +
      Unmet object conventions
      +
      The name change does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element change is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      change is missing a description. All concepts should be defined or described.
      +
      +
      +

      cn-desg

      +
      +
      +
      Unmet object conventions
      +
      The name cn-desg does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element cn-desg is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      cn-social

      +
      +
      +
      Unmet object conventions
      +
      The name cn-social does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element cn-social is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      cn-standard

      +
      +
      +
      Unmet object conventions
      +
      The name cn-standard does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element cn-standard is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      competition

      +
      +
      +
      Unmet object conventions
      +
      The name competition does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element competition is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      competition is missing a description. All concepts should be defined or described.
      +
      +
      +

      compl

      +
      +
      +
      Unmet object conventions
      +
      The name compl does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element compl is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      cont-modif

      +
      +
      +
      Unmet object conventions
      +
      The name cont-modif does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element cont-modif is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      cont-modif is missing a description. All concepts should be defined or described.
      +
      +
      +

      dir-awa-pre

      +
      +
      +
      Unmet object conventions
      +
      The name dir-awa-pre does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element dir-awa-pre is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      dir-awa-pre is missing a description. All concepts should be defined or described.
      +
      +
      +

      Directive 23

      +
      +
      +
      Unmet object conventions
      +
      The name Directive 23 does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element Directive 23 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      The local name segment Directive 23 contains token delimiters. It is best if the names + are camel cased and delimiters removed.
      +
      Directive 23 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Directive 24

      +
      +
      +
      Unmet object conventions
      +
      The name Directive 24 does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element Directive 24 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      The local name segment Directive 24 contains token delimiters. It is best if the names + are camel cased and delimiters removed.
      +
      Directive 24 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Directive 25

      +
      +
      +
      Unmet object conventions
      +
      The name Directive 25 does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element Directive 25 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      The local name segment Directive 25 contains token delimiters. It is best if the names + are camel cased and delimiters removed.
      +
      Directive 25 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Directive 81

      +
      +
      +
      Unmet object conventions
      +
      The name Directive 81 does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element Directive 81 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      The local name segment Directive 81 contains token delimiters. It is best if the names + are camel cased and delimiters removed.
      +
      Directive 81 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form1

      +
      +
      +
      Unmet object conventions
      +
      The name Form1 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form1 is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form1 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form12

      +
      +
      +
      Unmet object conventions
      +
      The name Form12 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form12 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form12 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form13

      +
      +
      +
      Unmet object conventions
      +
      The name Form13 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form13 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form13 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form14

      +
      +
      +
      Unmet object conventions
      +
      The name Form14 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form14 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form14 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form15

      +
      +
      +
      Unmet object conventions
      +
      The name Form15 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form15 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form15 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form16

      +
      +
      +
      Unmet object conventions
      +
      The name Form16 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form16 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form16 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form17

      +
      +
      +
      Unmet object conventions
      +
      The name Form17 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form17 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form17 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form18

      +
      +
      +
      Unmet object conventions
      +
      The name Form18 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form18 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form18 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form19

      +
      +
      +
      Unmet object conventions
      +
      The name Form19 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form19 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form19 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form2

      +
      +
      +
      Unmet object conventions
      +
      The name Form2 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form2 is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form2 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form20

      +
      +
      +
      Unmet object conventions
      +
      The name Form20 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form20 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form20 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form21

      +
      +
      +
      Unmet object conventions
      +
      The name Form21 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form21 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form21 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form22

      +
      +
      +
      Unmet object conventions
      +
      The name Form22 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form22 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form22 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form23

      +
      +
      +
      Unmet object conventions
      +
      The name Form23 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form23 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form23 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form24

      +
      +
      +
      Unmet object conventions
      +
      The name Form24 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form24 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form24 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form25

      +
      +
      +
      Unmet object conventions
      +
      The name Form25 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form25 is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form25 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form3

      +
      +
      +
      Unmet object conventions
      +
      The name Form3 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form3 is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form3 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form4

      +
      +
      +
      Unmet object conventions
      +
      The name Form4 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form4 is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form4 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form5

      +
      +
      +
      Unmet object conventions
      +
      The name Form5 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form5 is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form5 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form6

      +
      +
      +
      Unmet object conventions
      +
      The name Form6 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form6 is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form6 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form7

      +
      +
      +
      Unmet object conventions
      +
      The name Form7 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form7 is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form7 is missing a description. All concepts should be defined or described.
      +
      +
      +

      Form8

      +
      +
      +
      Unmet object conventions
      +
      The name Form8 does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element Form8 is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      Form8 is missing a description. All concepts should be defined or described.
      +
      +
      +

      pin-buyer

      +
      +
      +
      Unmet object conventions
      +
      The name pin-buyer does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element pin-buyer is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      pin-cfc-social

      +
      +
      +
      Unmet object conventions
      +
      The name pin-cfc-social does not match the pattern. The name should respect the syntax + prefix:localSegment (similar to the XML QName).
      +
      The name of element pin-cfc-social is missing a prefix. The name should comprise a + prefix respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      pin-cfc-standard

      +
      +
      +
      Unmet object conventions
      +
      The name pin-cfc-standard does not match the pattern. The name should respect the + syntax prefix:localSegment (similar to the XML QName).
      +
      The name of element pin-cfc-standard is missing a prefix. The name should comprise + a prefix respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      pin-only

      +
      +
      +
      Unmet object conventions
      +
      The name pin-only does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element pin-only is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      pin-rtl

      +
      +
      +
      Unmet object conventions
      +
      The name pin-rtl does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element pin-rtl is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      planning

      +
      +
      +
      Unmet object conventions
      +
      The name planning does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element planning is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      planning is missing a description. All concepts should be defined or described.
      +
      +
      +

      pmc

      +
      +
      +
      Unmet object conventions
      +
      The name pmc does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element pmc is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      qu-sy

      +
      +
      +
      Unmet object conventions
      +
      The name qu-sy does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element qu-sy is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      result

      +
      +
      +
      Unmet object conventions
      +
      The name result does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element result is missing a prefix. The name should comprise a prefix + respecing the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      result is missing a description. All concepts should be defined or described.
      +
      +
      +

      subco

      +
      +
      +
      Unmet object conventions
      +
      The name subco does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element subco is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      veat

      +
      +
      +
      Unmet object conventions
      +
      The name veat does not match the pattern. The name should respect the syntax prefix:localSegment + (similar to the XML QName).
      +
      The name of element veat is missing a prefix. The name should comprise a prefix respecing + the syntax prefix:localSegment.
      +
      The name prefix , is invalid. Please provide a short prefix name containing only + alphanumeric characters [a-zA-Z0-9]+.
      +
      The prefix is not defined. A prefix must be associated to a namespace URI.
      +
      +
      +

      Generalizations

      +

      eli:LegalResource -> eli:Work (+)

      +
      +
      Unmet generalisation conventions
      +
      The class eli:Work has only one sub-class eli:LegalResource. Class inheritance should + be built employing at least two subclasses for each class or not at all.
      +
      +

      eli:LegalResourceSubdivision -> eli:LegalResource (+)

      +
      +
      Unmet generalisation conventions
      +
      The class eli:LegalResource has only one sub-class eli:LegalResourceSubdivision. Class + inheritance should be built employing at least two subclasses for each class or not + at all.
      +
      +

      epo:AcquiringCentralPurchasingBody -> epo:CentralPurchasingBody (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:CentralPurchasingBody has only one sub-class epo:AcquiringCentralPurchasingBody. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo:AdHocChannel -> cv:Channel (+)

      +
      +
      Unmet generalisation conventions
      +
      The class cv:Channel has only one sub-class epo:AdHocChannel. Class inheritance should + be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:AwardEvaluationTerm -> epo:EvaluationTerm (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:EvaluationTerm has only one sub-class epo:AwardEvaluationTerm. Class + inheritance should be built employing at least two subclasses for each class or not + at all.
      +
      +

      epo:AwardingCentralPurchasingBody -> epo:CentralPurchasingBody (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:CentralPurchasingBody has only one sub-class epo:AwardingCentralPurchasingBody. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo:AwardOutcome -> epo:ContextualProjection (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:ContextualProjection has only one sub-class epo:AwardOutcome. Class + inheritance should be built employing at least two subclasses for each class or not + at all.
      +
      +

      epo:CentralPurchasingBody -> epo:Buyer (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:Buyer has only one sub-class epo:CentralPurchasingBody. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:Certificate -> cccev:Evidence (+)

      +
      +
      Unmet generalisation conventions
      +
      The class cccev:Evidence has only one sub-class epo:Certificate. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:CertificationLabel -> cccev:InformationConcept (+)

      +
      +
      Unmet generalisation conventions
      +
      The class cccev:InformationConcept has only one sub-class epo:CertificationLabel. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo:ConcessionEstimate -> epo:Estimate (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:Estimate has only one sub-class epo:ConcessionEstimate. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:Duration -> time:Duration (+)

      +
      +
      Unmet generalisation conventions
      +
      The class time:Duration has only one sub-class epo:Duration. Class inheritance should + be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:ExclusionGround -> epo:QualificationCriterion (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:QualificationCriterion has only one sub-class epo:ExclusionGround. Class + inheritance should be built employing at least two subclasses for each class or not + at all.
      +
      +

      epo:ExclusionGroundsSummary -> epo:QualificationCriteriaSummary (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:QualificationCriteriaSummary has only one sub-class epo:ExclusionGroundsSummary. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo:IndefiniteDuration -> epo:Duration (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:Duration has only one sub-class epo:IndefiniteDuration. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:LeadBuyer -> epo:Buyer (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:Buyer has only one sub-class epo:LeadBuyer. Class inheritance should + be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:Lot -> epo:ProcurementObject (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:ProcurementObject has only one sub-class epo:Lot. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:LotAwardOutcome -> epo:AwardOutcome (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:AwardOutcome has only one sub-class epo:LotAwardOutcome. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:MiniCompetitionAwardOutcome -> epo:AwardOutcome (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:AwardOutcome has only one sub-class epo:MiniCompetitionAwardOutcome. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo:PlannedProcurementPart -> epo:ProcurementElement (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:ProcurementElement has only one sub-class epo:PlannedProcurementPart. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo:Procedure -> epo:ProcurementObject (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:ProcurementObject has only one sub-class epo:Procedure. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:ProcurementCriterion -> cccev:Criterion (+)

      +
      +
      Unmet generalisation conventions
      +
      The class cccev:Criterion has only one sub-class epo:ProcurementCriterion. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:ProcurementObject -> epo:ProcurementElement (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:ProcurementElement has only one sub-class epo:ProcurementObject. Class + inheritance should be built employing at least two subclasses for each class or not + at all.
      +
      +

      epo:ReviewDecision -> epo:ReviewObject (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:ReviewObject has only one sub-class epo:ReviewDecision. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:ReviewRequest -> epo:ReviewObject (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:ReviewObject has only one sub-class epo:ReviewRequest. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:SelectionCriteriaSummary -> epo:QualificationCriteriaSummary (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:QualificationCriteriaSummary has only one sub-class epo:SelectionCriteriaSummary. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo:SelectionCriterion -> epo:QualificationCriterion (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:QualificationCriterion has only one sub-class epo:SelectionCriterion. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo:SelectionEvaluationTerm -> epo:EvaluationTerm (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:EvaluationTerm has only one sub-class epo:SelectionEvaluationTerm. Class + inheritance should be built employing at least two subclasses for each class or not + at all.
      +
      +

      epo:SpecificDuration -> epo:Duration (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:Duration has only one sub-class epo:SpecificDuration. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:SubcontractingEstimate -> epo:Estimate (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:Estimate has only one sub-class epo:SubcontractingEstimate. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo:TechnicalSpecification -> epo:ProcurementDocument (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:ProcurementDocument has only one sub-class epo:TechnicalSpecification. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo:TenderAwardOutcome -> epo:ContextualProjection (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo:ContextualProjection has only one sub-class epo:TenderAwardOutcome. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo-cat:ChargeInformation -> epo-ord:AllowanceChargeInformation (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo-ord:AllowanceChargeInformation has only one sub-class epo-cat:ChargeInformation. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo-con:Deliverable -> epo-cat:Item (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo-cat:Item has only one sub-class epo-con:Deliverable. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      epo-ful:Package -> epo-ful:AbstractContainer (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo-ful:AbstractContainer has only one sub-class epo-ful:Package. Class + inheritance should be built employing at least two subclasses for each class or not + at all.
      +
      +

      epo-ful:TransportHandlingUnit -> epo-ful:Package (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo-ful:Package has only one sub-class epo-ful:TransportHandlingUnit. Class + inheritance should be built employing at least two subclasses for each class or not + at all.
      +
      +

      epo-not:Notice22 -> epo-not:SubcontractNotice (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo-not:SubcontractNotice has only one sub-class epo-not:Notice22. Class + inheritance should be built employing at least two subclasses for each class or not + at all.
      +
      +

      epo-not:Subcontract-D81 -> epo-not:SubcontractNotice (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo-not:SubcontractNotice has only one sub-class epo-not:Subcontract-D81. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo-not:VoluntaryEx-AnteTransparencyNotice -> epo-not:DirectAwardPrenotificationNotice + (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo-not:DirectAwardPrenotificationNotice has only one sub-class epo-not:VoluntaryEx-AnteTransparencyNotice. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo-ord:AllowanceInformation -> epo-ord:AllowanceChargeInformation (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo-ord:AllowanceChargeInformation has only one sub-class epo-ord:AllowanceInformation. + Class inheritance should be built employing at least two subclasses for each class + or not at all.
      +
      +

      epo-ord:OrderResponseLine -> epo-ord:OrderLine (+)

      +
      +
      Unmet generalisation conventions
      +
      The class epo-ord:OrderLine has only one sub-class epo-ord:OrderResponseLine. Class + inheritance should be built employing at least two subclasses for each class or not + at all.
      +
      +

      person:Person -> foaf:Person (+)

      +
      +
      Unmet generalisation conventions
      +
      The class foaf:Person has only one sub-class person:Person. Class inheritance should + be built employing at least two subclasses for each class or not at all.
      +
      +

      (epo:Procedure - epo:ProcedureSpecificTerm) -> (epo:ProcurementObject - epo:Term) + (+)

      +
      +
      Unmet generalisation conventions
      +
      The class ProxyConnector has only one sub-class ProxyConnector. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      (epo:Lot - epo:LotSpecificTerm) -> (epo:ProcurementObject - epo:Term) (+)

      +
      +
      Unmet generalisation conventions
      +
      The class ProxyConnector has only one sub-class ProxyConnector. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      (epo:Certificate - epo:CertificationLabel) -> (cccev:Evidence - cccev:InformationConcept) + (+)

      +
      +
      Unmet generalisation conventions
      +
      The class ProxyConnector has only one sub-class ProxyConnector. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      (cccev:InformationRequirement - cccev:Constraint) -> (cccev:Requirement - cccev:Requirement) + (+)

      +
      +
      Unmet generalisation conventions
      +
      The class ProxyConnector has only one sub-class ProxyConnector. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      (epo:ProcurementCriterion - cccev:Constraint) -> (cccev:Requirement - cccev:Requirement) + (+)

      +
      +
      Unmet generalisation conventions
      +
      The class ProxyConnector has only one sub-class ProxyConnector. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      (epo:Procedure - epo:Buyer) -> (epo:Procedure - epo:Buyer) (+)

      +
      +
      Unmet generalisation conventions
      +
      The class ProxyConnector has only one sub-class ProxyConnector. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      (epo-not:CompetitionNotice - epo:Procedure) -> (epo-not:ResultNotice - epo:Procedure) + (+)

      +
      +
      Unmet generalisation conventions
      +
      The class ProxyConnector has only one sub-class ProxyConnector. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      (epo-not:DirectAwardPrenotificationNotice - epo:Procedure) -> (epo-not:ResultNotice + - epo:Procedure) (+)

      +
      +
      Unmet generalisation conventions
      +
      The class ProxyConnector has only one sub-class ProxyConnector. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      (epo:Notice - epo:Notice) -> (epo:Document - epo:Document) (+)

      +
      +
      Unmet generalisation conventions
      +
      The class ProxyConnector has only one sub-class ProxyConnector. Class inheritance + should be built employing at least two subclasses for each class or not at all.
      +
      +

      Associations

      +

      cccev:InformationRequirement -> cccev:Constraint (+epo:hasConstraint)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      cccev:Requirement -> eli:LegalResource (+cccev:isDerivedFrom)

      +
      +
      + Unmet association conventions +
      +
      The target role of cccev:Requirement -> eli:LegalResource (+cccev:isDerivedFrom) has + no multiplicity. Cardinality must be provided for each role.
      +
      +

      cv:Channel -> adms:Identifier (+epo:hasEndpointIdentifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      dct:Location -> locn:Address (+locn:address)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      dct:Location -> locn:Geometry (+locn:geometry)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:AccessTerm -> epo:ProcurementDocument (+epo:involvesProcurementDocument)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:AccessTerm -> epo:PlannedProcurementPart (+epo:refersToPlannedPart)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:AgentInRole -> cpov:ContactPoint (+epo:hasContactPointInRole)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:AgentInRole -> cv:Channel (+epo:exposesChannel)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:AgentInRole -> foaf:Agent (+epo:playedBy)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Buyer -> cpov:ContactPoint (+epo:indicatesInvoiceeContactPoint)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      The target role of epo:Buyer -> cpov:ContactPoint (+epo:indicatesInvoiceeContactPoint) + has no multiplicity. Cardinality must be provided for each role.
      +
      +

      epo:Buyer -> cv:Channel (+epo:exposesInvoiceeChannel)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Buyer -> epo:AwardDecision (+epo:signsAwardDecision)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ChangeInformation -> adms:Identifier (+epo:relatesToEFormSectionIdentifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ChangeInformation -> epo:Notice (+epo:concernsNotice)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ConcessionEstimate -> epo:MonetaryValue (+epo:hasConcessionEstimatedValue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Contract -> epo:Buyer (+epo:signedByBuyer)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Contract -> epo:Lot (+epo:hasLotReference)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Contract -> epo-con:Deliverable (+epo:specifiesDeliverable)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Contract -> epo:MonetaryValue (+epo:hasContractValue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Contract -> epo:ContractSpecificTerm (+epo:isSubjectToContractSpecificTerm)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Contract -> epo:Contractor (+epo:signedByContractor)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Contract -> epo:Purpose (+epo:hasPurpose)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Contract -> epo-ord:TaxInformation (+epo-ord:hasTaxInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ContractLotCompletionInformation -> epo:Contract (+epo:refersToContract)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ContractLotCompletionInformation -> epo:Lot (+epo:describesLotCompletion)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:DirectContract -> epo:LotAwardOutcome (+epo:resultsFromLotAwardOutcome)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Document -> epo:Document (+epo:hasElectronicDigest)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Document -> epo:ElectronicSignature (+epo:hasElectronicSignature)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Document -> epo:Document (+epo:refersToPrevious)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:FrameworkAgreement -> epo:LotAwardOutcome (+epo:resultsFromLotAwardOutcome)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:JuryMember -> person:Person (+epo:playedBy)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Lot -> epo:LotSpecificTerm (+epo:isSubjectToLotSpecificTerm)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Lot -> epo:ProcurementCriterion (+epo:specifiesProcurementCriterion)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:LotAwardOutcome -> epo:MonetaryValue (+epo:hasFrameworkAgreementMaximumValue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:LotGroup -> epo:ProcurementCriterion (+epo:specifiesProcurementCriterion)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:LotGroup -> epo:Lot (+epo:setsGroupingContextForLot)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:LotGroup -> adms:Identifier (+epo:hasInternalIdentifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:LotGroup -> epo:MonetaryValue (+epo:hasLaunchFrameworkAgreementMaximumValue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:LotGroupAwardInformation -> epo:LotGroup (+epo:describesLotGroup)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:MiniCompetitionAwardOutcome -> epo:SelectedCandidateList (+epo:resultsFromUsingCandidateList)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:MultipleStageProcedureTerm -> epo:Duration (+epo:hasQualificationSystemDuration)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:NonPublishedInformation -> epo:Notice (+epo:concernsNotice)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:NonPublishedInformation -> adms:Identifier (+epo:relatesToEFormSectionIdentifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Notice -> epo:Lot (+epo:refersToLot)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Notice -> epo:Notice (+epo:refersToNotice)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Notice -> epo:Procedure (+epo:refersToProcedure)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:NoticeAwardInformation -> epo-not:DirectAwardPrenotificationNotice (+epo:describesDirectAwardPrenotificationNotice)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:NoticeAwardInformation -> epo-not:ResultNotice (+epo:describesResultNotice)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:OfferIssuer -> epo:Offer (+epo:distributesOffer)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:OrganisationGroup -> org:Organization (+epo:hasMember)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:PlannedProcurementPart -> epo:Technique (+epo:foreseesTechnique)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:PlannedProcurementPart -> epo:Period (+epo:hasPlannedPeriod)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:PlannedProcurementPart -> epo:Duration (+epo:hasPlannedDuration)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Procedure -> epo:Buyer (+epo:involvesBuyer)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Procedure -> epo:ProcedureSpecificTerm (+epo:isSubjectToProcedureSpecificTerm)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Procedure -> epo:ProcurementCriteriaSummary (+epo:specifiesProcurementCriteriaSummary)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Procedure -> epo:ProcurementServiceProvider (+epo:isExecutedByProcurementServiceProvider)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Procedure -> epo:Lot (+epo:hasProcurementScopeDividedIntoLot)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ProcurementCriterion -> cccev:Constraint (+epo:hasConstraint)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ProcurementElement -> cv:Channel (+epo:usesChannel)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ProcurementElement -> adms:Identifier (+epo:hasInternalIdentifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ProcurementObject -> epo:ConcessionEstimate (+epo:foreseesConcession)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ProcurementObject -> epo:ContractSpecificTerm (+epo:foreseesContractSpecificTerm)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ProcurementObject -> epo:StrategicProcurement (+epo:fulfillsStrategicProcurement)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ProcurementObject -> epo:Technique (+epo:usesTechnique)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ProcurementObject -> epo:Term (+epo:isSubjectToTerm)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ProcurementObject -> epo:MonetaryValue (+epo:hasLaunchFrameworkAgreementMaximumValue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:PurchaseContract -> epo:FrameworkAgreement (+epo:followsRulesSetBy)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:PurchaseContract -> epo:MiniCompetitionAwardOutcome (+epo:resultsFromMiniCompetitionAwardOutcome)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ReviewDecision -> epo:ReviewRequest (+epo:resolvesReviewRequest)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:SelectedCandidateList -> epo:Candidate (+epo:containsCandidate)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:SelectedCandidateList -> epo:Period (+epo:hasStartDate)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:SubmissionTerm -> epo:Duration (+epo:hasTenderValidityDuration)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:System <-> foaf:Agent (+epo:isOwnedByAgent +epo:ownsSystem)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description.It is recommended to define + and describe all the relations.
      +
      +

      epo:Tender -> epo:ConcessionEstimate (+epo:foreseesConcession)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Tender -> epo:SubcontractingEstimate (+epo:foreseesSubcontracting)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Tender -> epo:Subcontractor (+epo:specifiesSubcontractors)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Tender -> epo:Lot (+epo:isSubmittedForLot)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Tender -> epo:LotGroup (+epo:isSubjectToGrouping)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Tender -> epo-sub:ESPDResponse (+epo:isSupportedBy)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:TenderAwardOutcome -> epo:Tender (+epo:concernsTender)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Tenderer -> epo:ExclusionGround (+epo:substantiatesExclusionGround)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:TenderGroup -> epo:LotGroup (+epo:isSubmittedForLotGroup)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:TenderGroup -> epo:MonetaryValue (+epo:hasTotalValue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:VehicleInformation -> epo:GreenProcurement (+epo:concernsGreenProcurement)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-acc:ESPDRequest -> epo:ProcurementCriterion (+epo:specifiesProcurementCriterion)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Batch -> epo-cat:Item (+epo-cat:isProductionOf)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Catalogue -> epo:Buyer (+epo:specifiesBuyer)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Catalogue -> epo:CatalogueProvider (+epo:specifiesCatalogueProvider)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Catalogue -> epo:CatalogueReceiver (+epo:specifiesCatalogueReceiver)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Catalogue -> epo:Contract (+epo-cat:isSubordinatedToContract)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Catalogue -> epo-ord:Seller (+epo:specifiesSeller)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Catalogue -> epo-cat:CatalogueLine (+epo-cat:comprisesCatalogueLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueLine -> epo-cat:ChargeInformation (+epo-cat:hasChargeInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueLine -> epo-cat:Price (+epo-cat:hasPrice)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueLine -> epo-ful:Package (+epo-cat:foreseesPackage)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueResponse -> epo:CatalogueProvider (+epo:specifiesCatalogueProvider)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueResponse -> epo:CatalogueReceiver (+epo:specifiesCatalogueReceiver)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueResponse -> epo-cat:Catalogue (+epo-cat:refersToCatalogue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueResponse -> epo-cat:CatalogueResponseInformation (+epo-cat:specifiesCatalogueResponseInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueResponse -> epo-cat:CatalogueResponseLine (+epo-cat:comprisesCatalogueResponseLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueResponseInformation -> epo-cat:CatalogueResponseLine (+epo-cat:isSpecificToCatalogueResponseLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueResponseLine -> epo-cat:CatalogueLine (+epo-cat:refersToCatalogueLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:InformationHub -> epo-cat:Line (+epo-cat:isSpecificToLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Item -> epo:Document (+epo-cat:hasExternalSpecification)

      +
      +
      + Unmet association conventions +
      +
      The target role of epo-cat:Item -> epo:Document (+epo-cat:hasExternalSpecification) + has no multiplicity. Cardinality must be provided for each role.
      +
      +

      epo-cat:Item -> epo-cat:Brand (+epo-cat:hasBrand)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Item -> epo-cat:ItemModel (+epo-cat:hasModel)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Item -> epo-cat:ItemRelation (+epo-cat:hasQualifiedItemRelation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Item -> epo-cat:ProductSpecification (+epo-cat:hasSpecification)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Item -> epo-ord:TaxInformation (+epo-ord:hasTaxInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:ItemProperty -> epo-cat:Item (+epo-cat:describesItem)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:ItemRelation -> epo-cat:Item (+epo-cat:isRelatedToItem)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Line -> epo-cat:Item (+epo-cat:specifiesItem)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Price -> epo-cat:ChargeInformation (+epo:hasPriceSurchargeInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Price -> epo-ord:AllowanceInformation (+epo-ord:hasPriceDiscountInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-con:ContractAmendment -> epo:Contract (+epo:amendsContract)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-con:ContractAmendment -> epo:MonetaryValue (+epo:updatesContractValue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-con:ContractModificationInformation -> adms:Identifier (+epo:relatesToEFormSectionIdentifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-con:ContractModificationInformation -> epo-con:ContractAmendment (+epo:concernsContractAmendment)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-con:Deliverable -> epo:MonetaryValue (+epo:hasTotalValue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-con:Deliverable -> epo:Quantity (+epo-cat:hasQuantity)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:AbstractContainer -> epo:Quantity (+epo-ful:hasGrossWeight)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:AbstractContainer -> epo:Quantity (+epo-ful:hasNetWeight)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:AbstractContainer -> epo:Quantity (+epo-ful:hasLength)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:AbstractContainer -> epo:Quantity (+epo-ful:hasGrossVolume)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:AbstractContainer -> epo:Quantity (+epo-ful:hasWidth)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:AbstractContainer -> epo:Quantity (+epo-ful:hasHeight)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:AbstractContainer -> epo:Quantity (+epo-ful:hasTotalGoodsItemQuantity)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:AbstractContainer -> epo:Quantity (+epo-ful:hasNetVolume)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:AbstractContainer -> epo-ful:TemperatureSpecification (+epo-ful:hasTemperatureSpecification)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> adms:Identifier (+epo-ful:hasFreightForwarderConsignmentID)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> adms:Identifier (+epo-ful:hasCarrierConsignmentID)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> adms:Identifier (+epo-ful:hasConsigneeConsignmentID)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo:MonetaryValue (+epo-ful:hasConsignmentFreeOnBoardValue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo:MonetaryValue (+epo-ful:hasConsignmentDeclaredStatisticsValue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo:Quantity (+epo-ful:hasNetWeight)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo:Quantity (+epo-ful:hasChargeableWeight)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo:Quantity (+epo-ful:hasTransportHandlingUnitQuantity)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo:Quantity (+epo-ful:hasLoadingLength)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo:Quantity (+epo-ful:hasGrossVolume)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo:Quantity (+epo-ful:hasTotalGoodsItemQuantity)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo:Quantity (+epo-ful:hasGrossWeight)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo-cat:ChargeInformation (+epo-ful:hasFreightAllowanceCharge)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo-ful:ShipmentStage (+epo-ful:hasPreCarriageShipmentStage)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo-ful:ShipmentStage (+epo-ful:hasOnCarriageShipmentStage)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo-ful:Notifier (+epo:specifiesNotifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo-ful:FreightForwarder (+epo:specifiesFreightForwarder)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo-ful:ShipmentStage (+epo-ful:hasMainCarriageShipmentStage)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo-ful:TransportHandlingUnit (+epo-ful:containsTransportHandlingUnit)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> epo-ful:ShipmentInformation (+epo-ful:hasRequestedPickUpInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchAdvice -> epo:Document (+epo-ful:hasAssociatedDocument)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchAdvice -> epo-ord:Consignee (+epo-ful:specifiesConsignee)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchAdvice -> epo-ord:Order (+epo-ful:refersToOrder)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchAdvice -> epo-ord:Originator (+epo-ful:specifiesOriginator)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchAdvice -> epo-ful:Consignment (+epo-ful:refersToConsignment)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchAdvice -> epo-ful:ShipmentAgreement (+epo-ful:refersToShipmentAgreement)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchAdvice -> epo-ful:DespatchLine (+epo-ful:comprisesDespatchLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchAdvice -> epo-ful:ShipmentInformation (+epo-ful:specifiesShipment)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchAdvice -> epo-ful:TransportHandlingUnit (+epo-ful:specifiesTransportHandlingUnits)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchAdvice -> epo-ful:Despatcher (+epo-ful:specifiesDespatcher)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchLine -> epo:Document (+epo-ful:hasAssociatedDocument)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchLine -> epo:Quantity (+epo-ful:hasOutstandingQuantity)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:DespatchLine -> epo-ord:OrderLine (+epo-ful:refersToOrderLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:GoodsItem -> epo:MonetaryValue (+epo-ful:hasDeclaredStatisticalValue)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:GoodsItem -> epo-ful:DespatchLine (+epo-ful:refersToDespatchLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Package -> epo-ful:GoodsItem (+epo-ful:containsGoodsItem)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Package -> epo-ful:Package (+epo-ful:containsPackage)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdvice -> epo:Buyer (+epo-ful:specifiesBuyer)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdvice -> epo:Document (+epo-ful:hasAssociatedDocument)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdvice -> epo-ord:Consignee (+epo-ful:specifiesConsignee)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdvice -> epo-ord:Seller (+epo-ful:specifiesSeller)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdvice -> epo-ful:Despatcher (+epo-ful:specifiesDespatcher)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdvice -> epo-ful:ShipmentInformation (+epo-ful:isSubmittedForShipment)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdvice -> epo-ful:ReceiptAdviceLine (+epo-ful:comprisesReceiptAdviceLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdviceLine -> epo:Quantity (+epo-ful:hasOversupplyQuantity)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdviceLine -> epo:Quantity (+epo-ful:hasReceivedQuantity)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdviceLine -> epo:Quantity (+epo-ful:hasShortQuantity)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdviceLine -> epo:Quantity (+epo:hasRejectedQuantity)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdviceLine -> epo-ful:DespatchLine (+epo-ful:isSubmittedForDespatchLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ShipmentAgreement -> epo:Buyer (+epo-ful:agreedByBuyer)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ShipmentAgreement -> epo-ord:Seller (+epo-ful:agreedBySeller)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ShipmentInformation -> dct:Location (+epo-ful:specifiesPlaceOfDespatch)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ShipmentInformation -> epo:Period (+epo-ful:hasEstimatedDeliveryPeriod)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ShipmentInformation -> epo-ord:DeliveryInformation (+epo-ful:refersToDeliveryInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ShipmentInformation -> epo-ful:DespatchLine (+epo-ful:isSpecificToDespatchLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ShipmentStage -> adms:Identifier (+adms:identifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ShipmentStage -> epo-ful:Carrier (+epo:specifiesCarrier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ShipmentStage -> epo-ful:ShipmentInformation (+epo-ful:hasDepartureShipmentInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ShipmentStage -> epo-ful:ShipmentInformation (+epo:hasArrivalShipmentInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ShipmentStage -> epo-ful:TransportMeans (+epo-ful:usesTransportMeans)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TemperatureSpecification -> epo:Quantity (+epo-ful:hasMaximumTemperature)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TemperatureSpecification -> epo:Quantity (+epo-ful:hasMinimumTemperature)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportEquipment -> adms:Identifier (+adms:identifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportEquipment -> epo-ful:TransportEquipmentSeal (+epo-ful:hasTransportEquipmentSeal)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportEquipmentSeal -> adms:Identifier (+adms:identifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportHandlingUnit -> epo-ful:DespatchLine (+epo-ful:transportsItemFrom)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportHandlingUnit -> epo-ful:TransportEquipment (+epo-ful:usesTransportEquipment)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportMeans -> adms:Identifier (+epo-ful:hasVehicleSegmentID)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportMeans -> adms:Identifier (+epo-ful:hasVehicleID)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportMeans -> epo-ful:TransportMeansOperator (+epo:hasDriverPerson)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportMeansOperator -> foaf:Person (+epo:playedBy)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompetitionNotice -> epo:AgentInRole (+epo:announcesRole)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompetitionNotice -> epo:Lot (+epo:announcesLot)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompetitionNotice -> epo:Procedure (+epo:announcesProcedure)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompetitionNotice -> epo:LotGroup (+epo:announcesLotGroup)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompletionNotice -> epo:AgentInRole (+epo:refersToRole)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompletionNotice -> epo:AgentInRole (+epo:announcesRole)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompletionNotice -> epo:Contract (+epo:announcesCompletionOfContract)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompletionNotice -> epo:LotGroupAwardInformation (+epo:refersToLotGroupAwardInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompletionNotice -> epo:NoticeAwardInformation (+epo:refersToNoticeAwardInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompletionNotice -> epo:ReviewObject (+epo:announcesReviewObject)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompletionNotice -> epo:AwardDecision (+epo:refersToAwardDecision)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompletionNotice -> epo:Lot (+epo:refersToLot)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompletionNotice -> epo:Procedure (+epo:refersToProcedure)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompletionNotice -> epo:LotGroup (+epo:refersToLotGroup)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ContractModificationNotice -> epo:AgentInRole (+epo:announcesRole)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ContractModificationNotice -> epo:Contract (+epo:refersToContractToBeModified)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ContractModificationNotice -> epo:LotGroupAwardInformation (+epo:refersToLotGroupAwardInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ContractModificationNotice -> epo:NoticeAwardInformation (+epo:refersToNoticeAwardInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ContractModificationNotice -> epo:AwardDecision (+epo:refersToAwardDecision)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ContractModificationNotice -> epo:Lot (+epo:refersToLot)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ContractModificationNotice -> epo:Procedure (+epo:refersToProcedure)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ContractModificationNotice -> epo:LotGroup (+epo:refersToLotGroup)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ContractModificationNotice -> epo-con:ContractAmendment (+epo:announcesContractAmendment)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:DirectAwardPrenotificationNotice -> epo:AgentInRole (+epo:announcesRole)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:DirectAwardPrenotificationNotice -> epo:Contract (+epo:announcesContract)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:DirectAwardPrenotificationNotice -> epo:LotGroupAwardInformation (+epo:announcesLotGroupAwardInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:DirectAwardPrenotificationNotice -> epo:NoticeAwardInformation (+epo:announcesNoticeAwardInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:DirectAwardPrenotificationNotice -> epo:AwardDecision (+epo:announcesAwardDecision)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:DirectAwardPrenotificationNotice -> epo:Lot (+epo:announcesLot)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:DirectAwardPrenotificationNotice -> epo:Procedure (+epo:announcesProcedure)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:DirectAwardPrenotificationNotice -> epo:LotGroup (+epo:announcesLotGroup)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:PlanningNotice -> epo:AgentInRole (+epo:announcesRole)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:PlanningNotice -> epo:PlannedProcurementPart (+epo:announcesPlannedProcurementPart)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ResultNotice -> epo:AgentInRole (+epo-not:refersToRole)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ResultNotice -> epo:AgentInRole (+epo-not:announcesRole)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ResultNotice -> epo:Contract (+epo:announcesContract)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ResultNotice -> epo:LotGroupAwardInformation (+epo:announcesLotGroupAwardInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ResultNotice -> epo:NoticeAwardInformation (+epo:announcesNoticeAwardInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ResultNotice -> epo:AwardDecision (+epo:announcesAwardDecision)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ResultNotice -> epo:Lot (+epo:refersToLot)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ResultNotice -> epo:Procedure (+epo:refersToProcedure)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ResultNotice -> epo:LotGroup (+epo:refersToLotGroup)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:AllowanceChargeInformation -> epo-ord:TaxInformation (+epo-ord:hasTaxInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:ContractInformation -> epo:Contract (+epo-ord:concernsContract)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:DeliveryAgreement -> dct:Location (+epo-ord:specifiesDeliveryAgreementLocation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:DeliveryInformation -> dct:Location (+epo-ord:specifiesPlaceOfDelivery)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:DeliveryInformation -> adms:Identifier (+epo-ful:hasTrackingID)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:DeliveryInformation -> epo:Period (+epo-ord:hasDeliveryPeriod)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:DeliveryInformation -> epo-ord:Consignee (+epo-ord:concernsConsignee)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:DeliveryInformation -> epo-ord:DeliveryAgreement (+epo-ord:specifiesGeneralDeliveryAgreement)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:DeliveryInformation -> epo-ord:DeliveryAgreement (+epo-ord:specifiesSpecificDeliveryAgreement)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo:Buyer (+epo:specifiesBuyer)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo:Project (+epo:refersToProject)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> adms:Identifier (+epo-ord:hasSellerOrderID)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo:MonetaryValue (+epo-ord:hasTotalTaxInclusiveAmount)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo:MonetaryValue (+epo-ord:hasTotalTaxExclusiveAmount)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo:MonetaryValue (+epo-ord:hasTotalLineAmount)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo:MonetaryValue (+epo-ord:hasTotalAllowanceAmount)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo:MonetaryValue (+epo-ord:hasRoundingAmount)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo:MonetaryValue (+epo-ord:hasPrepaidAmount)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo:MonetaryValue (+epo-ord:hasAmountDueForPayment)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo:MonetaryValue (+epo-ord:hasTotalChargeAmount)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo-cat:ChargeInformation (+epo-cat:specifiesChargeInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo-ord:AllowanceInformation (+epo-ord:specifiesAllowanceInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo-ord:DeliveryInformation (+epo-ord:specifiesDeliveryInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo-ord:OrderLine (+epo-ord:comprisesOrderLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo-ful:Despatcher (+epo:specifiesDespatcher)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo-ord:Seller (+epo:specifiesSeller)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:Order -> epo-ord:OriginatorInformation (+epo-ord:specifiesOriginatorInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OrderLine -> epo:Quantity (+epo-cat:hasQuantity)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OrderLine -> epo-cat:Price (+epo-cat:hasPrice)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OrderResponse -> epo:Buyer (+epo-ord:specifiesBuyer)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OrderResponse -> epo:Contract (+epo-ord:implementsContract)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OrderResponse -> epo-ord:Order (+epo-ord:isSubmittedForOrder)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OrderResponse -> epo-ord:Seller (+epo-ord:specifiesSeller)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OrderResponse -> epo-ord:OrderResponseLine (+epo-ord:comprisesOrderResponseLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OrderResponse -> epo-ord:OrderResponseInformation (+epo-ord:specifiesOrderResponseInformation)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OrderResponseInformation -> epo:Period (+epo-ord:hasDeliveryPeriod)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OrderResponseInformation -> epo-ord:OrderResponseLine (+epo-ord:isSpecificToOrderResponseLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OrderResponseLine -> epo-ord:OrderLine (+epo-ord:isSubmittedForOrderLine)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OriginatorInformation -> epo:OriginatorRequest (+epo-ord:concernsOriginatorRequest)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ord:OriginatorInformation -> epo-ord:Originator (+epo-ord:concernsOriginator)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-sub:ESPDResponse -> epo:ExclusionGround (+epo:answersExclusionGround)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-sub:ESPDResponse -> epo:SelectionCriterion (+epo:answersSelectionCriteria)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-sub:LegalRepresentative -> epo:OfferingParty (+epo:actsOnBehalfOf)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      org:Organization -> cpov:ContactPoint (+epo:hasPrimaryContactPoint)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      org:Organization -> adms:Identifier (+epo:hasLegalIdentifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      org:Organization -> adms:Identifier (+epo:hasTaxIdentifier)

      +
      +
      + Unmet association conventions +
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      Dependencies

      +

      dct:Location -> at-voc:country (+epo:hasCountryCode)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      dct:Location -> at-voc:nuts (+epo:hasNutsCode)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      eli:LegalResource -> at-voc:resource-type (+epo:hasResourceType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      eli:LegalResourceSubdivision -> at-voc:subdivision (+epo:hasSubdivision)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ContractTerm -> at-voc:permission (+epo:hasEInvoicingPermission)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:ContractTerm -> at-voc:applicability (+epo:hasReservedExecution)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Fund -> at-voc:EU-programme (+epo:hasFundProgramme)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Notice -> at-voc:notice-type (+epo:hasNoticeType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Purpose -> at-voc:cpv (+epo:hasMainClassification)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Purpose -> at-voc:cpv (+epo:hasAdditionalClassification)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Quantity -> at-voc:measurement-unit (+epo:hasUnitCode)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Reviewer -> at-voc:review-body-type (+epo:hasReviewBodyType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:SpecificDuration -> time:TemporalUnit (+time:unitType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:SubmissionStatisticalInformation -> at-voc:received-submission-type (+epo:hasReceivedSubmissionType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:Tender -> at-voc:applicability (+epo:hasSubcontracting)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:VehicleInformation -> at-voc:vehicle-category (+epo:specifiesCleanVehicleDirectiveVehicleCategory)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo:VehicleInformation -> at-voc:cvd-contract-type (+epo:specifiesCleanVehicleDirectiveContractType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Catalogue -> at-voc-new:activity-code (+epo-cat:hasActivityCode)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueLine -> at-voc-new:activity-code (+epo-cat:hasActivityCode)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:CatalogueResponseInformation -> at-voc-new:ResponseStatus (+epo-ord:hasAcceptanceStatus)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Item -> at-voc-new:delivery-item-type (+epo-cat:hasDeliveryClassification)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:PostAwardDocument -> at-voc-new:document-type (+epo-cat:hasDocumentType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-cat:Price -> at-voc-new:price-type (+epo-cat:hasPriceType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Consignment -> at-voc-new:handling-instruction (+epo-ful:hasHandlingInstructionCode)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:Package -> at-voc-new:packaging-type (+epo-ful:hasPackagingType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdviceLine -> at-voc-new:action-code (+epo-ful:hasShortageAction)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdviceLine -> at-voc-new:reject-reason (+epo-ful:hasRejectReason)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:ReceiptAdviceLine -> at-voc-new:action-code (+epo-ful:RejectionAction)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportEquipment -> at-voc-new:transport-equipment-type (+epo-ful:hasTransportEquipmentType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportEquipment -> at-voc-new:size-type (+epo-ful:hasSizeType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportHandlingUnit -> at-voc-new:handling-instruction (+epo-ful:hasHandlingInstructionCode)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportMeans -> at-voc-new:transport-means-type (+epo-ful:hasTransportMeansType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-ful:TransportMeans -> at-voc-new:transport-mode (+epo-ful:hasTransportMode)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CANDefence-D81 -> Directive 81 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CANDefence-D81 -> Form18 (+epo:hasFormType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CANSocial-D25 -> Directive 25 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CANSocial-D25 -> Form6 (+epo:hasFormType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CANSocialNotice -> can-social (+epo:hasNoticeType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CANSocialNotice-D25 -> Directive 25 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CANSocialNotice-D25 -> Form22 (+epo:hasFormType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CANStandard-D24 -> Directive 24 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CANStandard-D24 -> Form3 (+epo:hasFormType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CANStandardNotice -> can-standard (+epo:hasNoticeType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CNDefence-D81 -> Directive 81 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CNDefence-D81 -> Form17 (+epo:hasFormType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CNSocial-D25 -> Directive 25 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CNSocial-D25 -> Form5 (+epo:hasFormType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CNSocialNotice -> cn-social (+epo:hasNoticeType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CNSocialNotice-D25 -> Directive 25 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CNSocialNotice-D25 -> Form22 (+epo:hasFormType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CNStandard-D24 -> Directive 24 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CNStandard-D24 -> Form2 (+epo:hasFormType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CNStandardNotice -> cn-standard (+epo:hasNoticeType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:CompletionNotice -> compl (+epo:hasNoticeType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ConcessionAwardNotice-D23 -> Directive 23 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ConcessionAwardNotice-D23 -> Form25 (+epo:hasFormType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:ConcessionNotice-D23 -> Directive 23 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      award

      +

      epo-not:ConcessionNotice-D23 -> Form24 (+epo:hasFormType)

      -
      - Unmet package conventions -
      -
      The package award is empty. Packages must contain child classes and conenctors (i.e. - owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      contextual description

      +

      epo-not:ContractModificationNotice -> can-modif (+epo:hasNoticeType)

      -
      - Unmet package conventions -
      -
      The package contextual description is empty. Packages must contain child classes and - conenctors (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      contract

      +

      epo-not:DesignContest-D24 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet package conventions -
      -
      The package contract is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      contract term

      +

      epo-not:DesignContest-D24 -> Form12 (+epo:hasFormType)

      -
      - Unmet package conventions -
      -
      The package contract term is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      criterion

      +

      epo-not:DesignContest-D25 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet package conventions -
      -
      The package criterion is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      evaluation term

      +

      epo-not:DesignContest-D25 -> Form12 (+epo:hasFormType)

      -
      - Unmet package conventions -
      -
      The package evaluation term is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      location

      +

      epo-not:DesignContestNotice -> cn-desg (+epo:hasNoticeType)

      -
      - Unmet package conventions -
      -
      The package location is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      participation request term

      +

      epo-not:DesignContestResult-D24 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet package conventions -
      -
      The package participation request term is empty. Packages must contain child classes - and conenctors (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      phase oriented

      +

      epo-not:DesignContestResult-D24 -> Form13 (+epo:hasFormType)

      -
      - Unmet package conventions -
      -
      The package phase oriented is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      procedure term

      +

      epo-not:DesignContestResult-D25 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet package conventions -
      -
      The package procedure term is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      procurement object

      +

      epo-not:DesignContestResult-D25 -> Form13 (+epo:hasFormType)

      -
      - Unmet package conventions -
      -
      The package procurement object is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      review

      +

      epo-not:DesignContestResultNotice -> can-desg (+epo:hasNoticeType)

      -
      - Unmet package conventions -
      -
      The package review is empty. Packages must contain child classes and conenctors (i.e. - owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      review term

      +

      epo-not:eFormsNotice -> (EU) 2019/1780 (+epo:hasImplementingRegulation)

      -
      - Unmet package conventions -
      -
      The package review term is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      role playing sides

      +

      epo-not:Modification-D23 -> Directive 23 (+epo:hasLegalBasis)

      -
      - Unmet package conventions -
      -
      The package role playing sides is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      role predecessor dependecies

      +

      epo-not:Modification-D23 -> Form20 (+epo:hasFormType)

      -
      - Unmet package conventions -
      -
      The package role predecessor dependecies is empty. Packages must contain child classes - and conenctors (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      strategic procurement

      +

      epo-not:Modification-D24 -> Directive 24 (+epo-not:hasLegalBasis)

      -
      - Unmet package conventions -
      -
      The package strategic procurement is empty. Packages must contain child classes and - conenctors (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      submission term

      +

      epo-not:Modification-D24 -> Form20 (+epo:hasFormType)

      -
      - Unmet package conventions -
      -
      The package submission term is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      technique

      +

      epo-not:Modification-D25 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet package conventions -
      -
      The package technique is empty. Packages must contain child classes and conenctors - (i.e. owned elements).
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      Object

      -

      Generalizations

      -

      epo:AcquiringCentralPurchasingBody -> epo:CentralPurchasingBody (+)

      +

      epo-not:Modification-D25 -> Form20 (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:CentralPurchasingBody has only one sub-class epo:AcquiringCentralPurchasingBody. - Class inheritance should be built employing at least two subclasses for each class - or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:AdHocChannel -> cv:Channel (+)

      +

      epo-not:Notice1 -> Directive 24 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class cv:Channel has only one sub-class epo:AdHocChannel. Class inheritance should - be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:AwardEvaluationTerm -> epo:EvaluationTerm (+)

      +

      epo-not:Notice1 -> planning (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:EvaluationTerm has only one sub-class epo:AwardEvaluationTerm. Class - inheritance should be built employing at least two subclasses for each class or not - at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:AwardingCentralPurchasingBody -> epo:CentralPurchasingBody (+)

      +

      epo-not:Notice10 -> Directive 24 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:CentralPurchasingBody has only one sub-class epo:AwardingCentralPurchasingBody. - Class inheritance should be built employing at least two subclasses for each class - or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:AwardOutcome -> epo:ContextualProjection (+)

      +

      epo-not:Notice10 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:ContextualProjection has only one sub-class epo:AwardOutcome. Class - inheritance should be built employing at least two subclasses for each class or not - at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:CentralPurchasingBody -> epo:Buyer (+)

      +

      epo-not:Notice11 -> Directive 25 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:Buyer has only one sub-class epo:CentralPurchasingBody. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:Certificate -> cccev:Evidence (+)

      +

      epo-not:Notice11 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class cccev:Evidence has only one sub-class epo:Certificate. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:CertificationLabel -> cccev:InformationConcept (+)

      +

      epo-not:Notice12 -> Directive 24 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class cccev:InformationConcept has only one sub-class epo:CertificationLabel. - Class inheritance should be built employing at least two subclasses for each class - or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:ConcessionEstimate -> epo:Estimate (+)

      +

      epo-not:Notice12 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:Estimate has only one sub-class epo:ConcessionEstimate. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:Duration -> time:Duration (+)

      +

      epo-not:Notice13 -> Directive 25 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class time:Duration has only one sub-class epo:Duration. Class inheritance should - be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:Notice13 -> competition (+epo:hasFormType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:Notice14 -> Directive 23 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      +
      +

      epo-not:Notice14 -> competition (+epo:hasFormType)

      +
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:ExclusionGround -> epo:QualificationCriterion (+)

      +

      epo-not:Notice15 -> Directive 25 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:QualificationCriterion has only one sub-class epo:ExclusionGround. Class - inheritance should be built employing at least two subclasses for each class or not - at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:ExclusionGroundsSummary -> epo:QualificationCriteriaSummary (+)

      +

      epo-not:Notice15 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:QualificationCriteriaSummary has only one sub-class epo:ExclusionGroundsSummary. - Class inheritance should be built employing at least two subclasses for each class - or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:IndefiniteDuration -> epo:Duration (+)

      +

      epo-not:Notice16 -> Directive 24 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:Duration has only one sub-class epo:IndefiniteDuration. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:LeadBuyer -> epo:Buyer (+)

      +

      epo-not:Notice16 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:Buyer has only one sub-class epo:LeadBuyer. Class inheritance should - be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:Lot -> epo:ProcurementObject (+)

      +

      epo-not:Notice17 -> Directive 25 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:ProcurementObject has only one sub-class epo:Lot. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:LotAwardOutcome -> epo:AwardOutcome (+)

      +

      epo-not:Notice17 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:AwardOutcome has only one sub-class epo:LotAwardOutcome. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:MiniCompetitionAwardOutcome -> epo:AwardOutcome (+)

      +

      epo-not:Notice18 -> Directive 81 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:AwardOutcome has only one sub-class epo:MiniCompetitionAwardOutcome. - Class inheritance should be built employing at least two subclasses for each class - or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:PlannedProcurementPart -> epo:ProcurementElement (+)

      +

      epo-not:Notice18 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:ProcurementElement has only one sub-class epo:PlannedProcurementPart. - Class inheritance should be built employing at least two subclasses for each class - or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:Procedure -> epo:ProcurementObject (+)

      +

      epo-not:Notice19 -> Directive 23 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:ProcurementObject has only one sub-class epo:Procedure. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:ProcurementCriterion -> cccev:Criterion (+)

      +

      epo-not:Notice19 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class cccev:Criterion has only one sub-class epo:ProcurementCriterion. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:ProcurementObject -> epo:ProcurementElement (+)

      +

      epo-not:Notice2 -> Directive 25 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:ProcurementElement has only one sub-class epo:ProcurementObject. Class - inheritance should be built employing at least two subclasses for each class or not - at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:ReviewDecision -> epo:ReviewObject (+)

      +

      epo-not:Notice2 -> planning (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:ReviewObject has only one sub-class epo:ReviewDecision. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:ReviewRequest -> epo:ReviewObject (+)

      +

      epo-not:Notice20 -> Directive 24 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:ReviewObject has only one sub-class epo:ReviewRequest. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:SelectionCriteriaSummary -> epo:QualificationCriteriaSummary (+)

      +

      epo-not:Notice20 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:QualificationCriteriaSummary has only one sub-class epo:SelectionCriteriaSummary. - Class inheritance should be built employing at least two subclasses for each class - or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:SelectionCriterion -> epo:QualificationCriterion (+)

      +

      epo-not:Notice21 -> Directive 25 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:QualificationCriterion has only one sub-class epo:SelectionCriterion. - Class inheritance should be built employing at least two subclasses for each class - or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:SelectionEvaluationTerm -> epo:EvaluationTerm (+)

      +

      epo-not:Notice21 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:EvaluationTerm has only one sub-class epo:SelectionEvaluationTerm. Class - inheritance should be built employing at least two subclasses for each class or not - at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:SpecificDuration -> epo:Duration (+)

      +

      epo-not:Notice22 -> Directive 81 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:Duration has only one sub-class epo:SpecificDuration. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:SubcontractingEstimate -> epo:Estimate (+)

      +

      epo-not:Notice22 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:Estimate has only one sub-class epo:SubcontractingEstimate. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:TechnicalSpecification -> epo:ProcurementDocument (+)

      +

      epo-not:Notice23 -> Directive 24 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class epo:ProcurementDocument has only one sub-class epo:TechnicalSpecification. - Class inheritance should be built employing at least two subclasses for each class - or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:TenderAwardOutcome -> epo:ContextualProjection (+)

      +

      epo-not:Notice23 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class epo:ContextualProjection has only one sub-class epo:TenderAwardOutcome. - Class inheritance should be built employing at least two subclasses for each class - or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      person:Person -> foaf:Person (+)

      +

      epo-not:Notice24 -> Directive 25 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class foaf:Person has only one sub-class person:Person. Class inheritance should - be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      (epo:Procedure - epo:ProcedureSpecificTerm) -> (epo:ProcurementObject - epo:Term) - (+)

      +

      epo-not:Notice24 -> competition (+epo:hasFormType)

      -
      Unmet generalisation conventions
      -
      The class ProxyConnector has only one sub-class ProxyConnector. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      (epo:Lot - epo:LotSpecificTerm) -> (epo:ProcurementObject - epo:Term) (+)

      +

      epo-not:Notice25 -> Directive 24 (+epo:hasLegalBasis)

      -
      Unmet generalisation conventions
      -
      The class ProxyConnector has only one sub-class ProxyConnector. Class inheritance - should be built employing at least two subclasses for each class or not at all.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      Associations

      -

      cccev:InformationRequirement -> cccev:Constraint (+epo:hasConstraint)

      +

      epo-not:Notice25 -> dir-awa-pre (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      cv:Channel -> adms:Identifier (+epo:hasEndpointIdentifier)

      +

      epo-not:Notice26 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      dct:Location -> locn:Address (+locn:address)

      +

      epo-not:Notice26 -> dir-awa-pre (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      dct:Location -> locn:Geometry (+locn:geometry)

      +

      epo-not:Notice27 -> Directive 81 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:AccessTerm -> epo:ProcurementDocument (+epo:involvesProcurementDocument)

      +

      epo-not:Notice27 -> dir-awa-pre (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:AccessTerm -> epo:PlannedProcurementPart (+epo:refersToPlannedPart)

      +

      epo-not:Notice28 -> Directive 23 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:AgentInRole -> cpov:ContactPoint (+epo:hasContactPointInRole)

      +

      epo-not:Notice28 -> dir-awa-pre (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:AgentInRole -> cv:Channel (+epo:exposesChannel)

      +

      epo-not:Notice29 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:AgentInRole -> foaf:Agent (+epo:playedBy)

      +

      epo-not:Notice29 -> result (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Buyer -> cpov:ContactPoint (+epo:indicatesInvoiceeContactPoint)

      +

      epo-not:Notice3 -> Directive 81 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -
      The target role of epo:Buyer -> cpov:ContactPoint (+epo:indicatesInvoiceeContactPoint) - has no multiplicity. Cardinality must be provided for each role.
      -

      epo:Buyer -> cv:Channel (+epo:exposesInvoiceeChannel)

      +

      epo-not:Notice3 -> planning (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Buyer -> epo:AwardDecision (+epo:signsAwardDecision)

      +

      epo-not:Notice30 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ChangeInformation -> adms:Identifier (+epo:relatesToEFormSectionIdentifier)

      +

      epo-not:Notice30 -> result (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ChangeInformation -> epo:Notice (+epo:concernsNotice)

      +

      epo-not:Notice31 -> Directive 81 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ConcessionEstimate -> epo:MonetaryValue (+epo:hasConcessionEstimatedValue)

      +

      epo-not:Notice31 -> result (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Contract -> epo:Buyer (+epo:signedByBuyer)

      -
      -
      - Unmet association conventions -
      +

      epo-not:Notice32 -> Directive 23 (+epo:hasLegalBasis)

      +
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Contract -> epo:Lot (+epo:hasLotReference)

      +

      epo-not:Notice32 -> result (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Contract -> epo:MonetaryValue (+epo:hasContractValue)

      +

      epo-not:Notice33 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Contract -> epo:ContractSpecificTerm (+epo:isSubjectToContractSpecificTerm)

      +

      epo-not:Notice33 -> result (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Contract -> epo:Contractor (+epo:signedByContractor)

      +

      epo-not:Notice34 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Contract -> epo:Purpose (+epo:hasPurpose)

      +

      epo-not:Notice34 -> result (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ContractLotCompletionInformation -> epo:Contract (+epo:refersToContract)

      +

      epo-not:Notice35 -> Directive 23 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ContractLotCompletionInformation -> epo:Lot (+epo:describesLotCompletion)

      +

      epo-not:Notice35 -> result (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:DirectContract -> epo:LotAwardOutcome (+epo:resultsFromLotAwardOutcome)

      +

      epo-not:Notice36 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Document -> epo:Document (+epo:hasElectronicDigest)

      +

      epo-not:Notice36 -> result (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Document -> epo:ElectronicSignature (+epo:hasElectronicSignature)

      +

      epo-not:Notice37 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Document -> epo:Document (+epo:refersToPrevious)

      +

      epo-not:Notice37 -> result (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:FrameworkAgreement -> epo:LotAwardOutcome (+epo:resultsFromLotAwardOutcome)

      +

      epo-not:Notice38 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:JuryMember -> person:Person (+epo:playedBy)

      +

      epo-not:Notice38 -> cont-modif (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Lot -> epo:LotSpecificTerm (+epo:isSubjectToLotSpecificTerm)

      +

      epo-not:Notice39 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Lot -> epo:ProcurementCriterion (+epo:specifiesProcurementCriterion)

      +

      epo-not:Notice39 -> cont-modif (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:LotAwardOutcome -> epo:MonetaryValue (+epo:hasFrameworkAgreementMaximumValue)

      +

      epo-not:Notice4 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:LotGroup -> epo:ProcurementCriterion (+epo:specifiesProcurementCriterion)

      +

      epo-not:Notice4 -> planning (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:LotGroup -> epo:Lot (+epo:setsGroupingContextForLot)

      +

      epo-not:Notice40 -> Directive 23 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:LotGroup -> adms:Identifier (+epo:hasInternalIdentifier)

      +

      epo-not:Notice40 -> cont-modif (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:LotGroup -> epo:MonetaryValue (+epo:hasLaunchFrameworkAgreementMaximumValue)

      +

      epo-not:Notice5 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:LotGroupAwardInformation -> epo:LotGroup (+epo:describesLotGroup)

      +

      epo-not:Notice5 -> planning (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:MiniCompetitionAwardOutcome -> epo:SelectedCandidateList (+epo:resultsFromUsingCandidateList)

      +

      epo-not:Notice6 -> Directive 81 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:MultipleStageProcedureTerm -> epo:Duration (+epo:hasQualificationSystemDuration)

      +

      epo-not:Notice6 -> planning (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:NonPublishedInformation -> epo:Notice (+epo:concernsNotice)

      +

      epo-not:Notice7 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:NonPublishedInformation -> adms:Identifier (+epo:relatesToEFormSectionIdentifier)

      +

      epo-not:Notice7 -> planning (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Notice -> epo:Lot (+epo:refersToLot)

      +

      epo-not:Notice8 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Notice -> epo:Notice (+epo:refersToNotice)

      +

      epo-not:Notice8 -> planning (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Notice -> epo:Procedure (+epo:refersToProcedure)

      +

      epo-not:Notice9 -> Directive 81 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:OfferIssuer -> epo:Offer (+epo:distributesOffer)

      +

      epo-not:Notice9 -> planning (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:OrganisationGroup -> org:Organization (+epo:hasMember)

      +

      epo-not:PIN-CFCSocial-D25 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:PlannedProcurementPart -> epo:Technique (+epo:foreseesTechnique)

      +

      epo-not:PIN-CFCSocial-D25 -> Form4 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:PlannedProcurementPart -> epo:Period (+epo:hasPlannedPeriod)

      +

      epo-not:PIN-CFCSocialNotice -> pin-cfc-social (+epo:hasNoticeType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:PlannedProcurementPart -> epo:Duration (+epo:hasPlannedDuration)

      +

      epo-not:PIN-CFCSocialNotice-D25 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Procedure -> epo:Buyer (+epo:involvesBuyer)

      +

      epo-not:PIN-CFCSocialNotice-D25 -> Form22 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Procedure -> epo:ProcedureSpecificTerm (+epo:isSubjectToProcedureSpecificTerm)

      +

      epo-not:PIN-CFCStandard-D24 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Procedure -> epo:ProcurementCriteriaSummary (+epo:specifiesProcurementCriteriaSummary)

      +

      epo-not:PIN-CFCStandard-D24 -> Form1 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Procedure -> epo:ProcurementServiceProvider (+epo:isExecutedByProcurementServiceProvider)

      +

      epo-not:PIN-CFCStandardNotice -> pin-cfc-standard (+epo:hasNoticeType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Procedure -> epo:Lot (+epo:hasProcurementScopeDividedIntoLot)

      +

      epo-not:PINDefence-D81 -> Directive 81 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ProcurementCriterion -> cccev:Constraint (+epo:hasConstraint)

      +

      epo-not:PINDefence-D81 -> Form16 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ProcurementElement -> cv:Channel (+epo:usesChannel)

      +

      epo-not:PINOnly-D24 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ProcurementElement -> adms:Identifier (+epo:hasInternalIdentifier)

      +

      epo-not:PINOnly-D24 -> Form1 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ProcurementObject -> epo:ConcessionEstimate (+epo:foreseesConcession)

      +

      epo-not:PINOnly-D25 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ProcurementObject -> epo:ContractSpecificTerm (+epo:foreseesContractSpecificTerm)

      +

      epo-not:PINOnly-D25 -> Form4 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ProcurementObject -> epo:StrategicProcurement (+epo:fulfillsStrategicProcurement)

      +

      epo-not:PINOnlyNotice -> pin-only (+epo:hasNoticeType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ProcurementObject -> epo:Technique (+epo:usesTechnique)

      +

      epo-not:PINProfile-D24 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ProcurementObject -> epo:Term (+epo:isSubjectToTerm)

      +

      epo-not:PINProfile-D24 -> Form8 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ProcurementObject -> epo:MonetaryValue (+epo:hasLaunchFrameworkAgreementMaximumValue)

      +

      epo-not:PINProfile-D25 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:PurchaseContract -> epo:FrameworkAgreement (+epo:followsRulesSetBy)

      +

      epo-not:PINProfile-D25 -> Form8 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:PurchaseContract -> epo:MiniCompetitionAwardOutcome (+epo:resultsFromMiniCompetitionAwardOutcome)

      +

      epo-not:PINProfile-D81 -> Directive 81 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ReviewDecision -> epo:ReviewRequest (+epo:resolvesReviewRequest)

      +

      epo-not:PINProfile-D81 -> Form8 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:SelectedCandidateList -> epo:Candidate (+epo:containsCandidate)

      +

      epo-not:PINProfileNotice -> pin-buyer (+epo:hasNoticeType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:SelectedCandidateList -> epo:Period (+epo:hasStartDate)

      +

      epo-not:PIN-RTL-D24 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:SubmissionTerm -> epo:Duration (+epo:hasTenderValidityDuration)

      +

      epo-not:PIN-RTL-D24 -> Form1 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:System <-> foaf:Agent (+epo:isOwnedByAgent +epo:ownsSystem)

      +

      epo-not:PIN-RTL-D25 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      -
      The connector is missing a description.It is recommended to define - and describe all the relations.
      +
      Unmet dependency conventions
      +
      The connector is missing a description. It is recommended to + define and describe all the relations.
      -

      epo:Tender -> epo:ConcessionEstimate (+epo:foreseesConcession)

      +

      epo-not:PIN-RTL-D25 -> Form4 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Tender -> epo:SubcontractingEstimate (+epo:foreseesSubcontracting)

      +

      epo-not:PINTimeLimitNotice -> pin-rtl (+epo:hasNoticeType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Tender -> epo:Subcontractor (+epo:specifiesSubcontractors)

      +

      epo-not:PreMarketConsultationNotice -> pmc (+epo:hasNoticeType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Tender -> epo:Lot (+epo:isSubmittedForLot)

      +

      epo-not:QS-D25 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Tender -> epo:LotGroup (+epo:isSubjectToGrouping)

      +

      epo-not:QS-D25 -> Form7 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:TenderAwardOutcome -> epo:Tender (+epo:concernsTender)

      +

      epo-not:QSNotice -> qu-sy (+epo:hasNoticeType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Tenderer -> epo:ExclusionGround (+epo:substantiatesExclusionGround)

      +

      epo-not:QSNotice-D25 -> Directive 25 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:TenderGroup -> epo:LotGroup (+epo:isSubmittedForLotGroup)

      +

      epo-not:QSNotice-D25 -> Form22 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:TenderGroup -> epo:MonetaryValue (+epo:hasTotalValue)

      +

      epo-not:SocialAndOtherSpecificServices-D23 -> Directive 23 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:VehicleInformation -> epo:GreenProcurement (+epo:concernsGreenProcurement)

      +

      epo-not:SocialAndOtherSpecificServices-D23 -> Form23 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      org:Organization -> cpov:ContactPoint (+epo:hasPrimaryContactPoint)

      +

      epo-not:SocialAndOtherSpecificServices-D24 -> Directive 24 (+epo:hasLegalBasis)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      org:Organization -> adms:Identifier (+epo:hasLegalIdentifier)

      +

      epo-not:SocialAndOtherSpecificServices-D24 -> Form21 (+epo:hasFormType)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      org:Organization -> adms:Identifier (+epo:hasTaxIdentifier)

      +

      epo-not:StandardFormsNotice -> (EU) 2015/1986 (+epo:hasImplementingRegulation)

      -
      - Unmet association conventions -
      +
      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      Dependencies

      -

      dct:Location -> at-voc:country (+epo:hasCountryCode)

      +

      epo-not:Subcontract-D81 -> Directive 81 (+epo:hasLegalBasis)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      dct:Location -> at-voc:nuts (+epo:hasNutsCode)

      +

      epo-not:Subcontract-D81 -> Form19 (+epo:hasFormType)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ContractTerm -> at-voc:permission (+epo:hasEInvoicingPermission)

      +

      epo-not:SubcontractNotice -> subco (+epo:hasNoticeType)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:ContractTerm -> at-voc:applicability (+epo:hasReservedExecution)

      +

      epo-not:VEAT-D23 -> Directive 23 (+epo:hasLegalBasis)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Fund -> at-voc:EU-programme (+epo:hasFundProgramme)

      +

      epo-not:VEAT-D23 -> Form15 (+epo:hasFormType)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Notice -> at-voc:notice-type (+epo:hasNoticeType)

      +

      epo-not:VEAT-D24 -> Directive 24 (+epo:hasLegalBasis)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Purpose -> at-voc:cpv (+epo:hasMainClassification)

      +

      epo-not:VEAT-D24 -> Form15 (+epo:hasFormType)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Purpose -> at-voc:cpv (+epo:hasAdditionalClassification)

      +

      epo-not:VEAT-D25 -> Directive 25 (+epo:hasLegalBasis)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Quantity -> at-voc:measurement-unit (+epo:hasUnitCode)

      +

      epo-not:VEAT-D25 -> Form15 (+epo:hasFormType)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Reviewer -> at-voc:review-body-type (+epo:hasReviewBodyType)

      +

      epo-not:VEAT-D81 -> Directive 81 (+epo:hasLegalBasis)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:SpecificDuration -> time:TemporalUnit (+time:unitType)

      +

      epo-not:VEAT-D81 -> Form15 (+epo:hasFormType)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:SubmissionStatisticalInformation -> at-voc:received-submission-type (+epo:hasReceivedSubmissionType)

      +

      epo-not:VoluntaryEx-AnteTransparencyNotice -> veat (+epo:hasNoticeType)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:Tender -> at-voc:applicability (+epo:hasSubcontracting)

      +

      epo-ord:OrderResponseInformation -> at-voc-new:ResponseStatus (+epo-ord:hasAcceptanceStatus)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:VehicleInformation -> at-voc:vehicle-category (+epo:specifiesCleanVehicleDirectiveVehicleCategory)

      +

      epo-ord:TaxInformation -> at-voc-new:tax-category (+epo-cat:hasTaxCategory)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      -

      epo:VehicleInformation -> at-voc:cvd-contract-type (+epo:specifiesCleanVehicleDirectiveContractType)

      +

      epo-ord:TaxInformation -> at-voc-new:tax-scheme (+epo-cat:hasTaxScheme)

      Unmet dependency conventions
      The connector is missing a description. It is recommended to define and describe all the relations.
      +

      epo-sub:Response -> at-voc:access-rights (+cccev:confidentialityLevelType)

      +
      +
      Unmet dependency conventions
      +
      The target role of epo-sub:Response -> at-voc:access-rights (+cccev:confidentialityLevelType) + has no multiplicity. Cardinality must be provided for each role.
      +

      locn:Address -> at-voc:nuts (+epo:hasNutsCode)

      Unmet dependency conventions
      @@ -3557,6 +9545,18 @@

    +
    +
    cccev:supportsValue
    +
    +
    The property is reused in multiple contexts, the meaning given by the definition is + the same. Here is the property usage: +
      +
    • Supported Value that the Evidence contains. (cccev:Evidence -> cccev:SupportedValue + (+cccev:supportsValue))
      • +
    • Supported Value that the Evidence contains. (epo-sub:Response -> cccev:SupportedValue + (+cccev:supportsValue))
      • +
    +
    cv:registeredAddress
    @@ -3575,6 +9575,26 @@

    +
    +
    eli:jurisdiction
    +
    +
    The property is reused in multiple contexts, the meaning given by the definition is + the same. Here is the property usage: +
      +
    • The jurisdiction from which the legal resource originates. + + The place identifier can be taken from the Administrative Territorial Unit table published + of the EU Publications Office at https://op.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/atu. + Member States don't have to recreate their own list of values. + (eli:LegalExpression -> at-voc:atu (+eli:jurisdiction))
      • +
    • The jurisdiction from which the legal resource originates. + + The place identifier can be taken from the Administrative Territorial Unit table published + of the EU Publications Office at https://op.europa.eu/en/web/eu-vocabularies/at-dataset/-/resource/dataset/atu. + Member States don't have to recreate their own list of values. + (eli:LegalResource -> at-voc:atu (+eli:jurisdiction))
      • +
    +
    eli:uri_schema
    @@ -3762,6 +9782,193 @@

    +
    +
    epo:hasFormType
    +
    +
    When a property is reused in multiple contexts, the meaning given by the definition + is expected to be the same. In this case, multiple definitions are found: +
      +
    • A categorisation of the steps in which the Notice is used. + + WG Approval 12/05/2020 + + (epo:Notice -> at-voc:form-type (+epo:hasFormType))
      • +
    • ... (epo-not:Notice1 -> planning (+epo:hasFormType))
      • +
    • ... (epo-not:Notice10 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice11 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice12 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice13 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice14 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice15 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice16 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice17 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice18 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice19 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice2 -> planning (+epo:hasFormType))
      • +
    • ... (epo-not:Notice20 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice21 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice22 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice23 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice24 -> competition (+epo:hasFormType))
      • +
    • ... (epo-not:Notice25 -> dir-awa-pre (+epo:hasFormType))
      • +
    • ... (epo-not:Notice26 -> dir-awa-pre (+epo:hasFormType))
      • +
    • ... (epo-not:Notice27 -> dir-awa-pre (+epo:hasFormType))
      • +
    • ... (epo-not:Notice28 -> dir-awa-pre (+epo:hasFormType))
      • +
    • ... (epo-not:Notice29 -> result (+epo:hasFormType))
      • +
    • ... (epo-not:Notice3 -> planning (+epo:hasFormType))
      • +
    • ... (epo-not:Notice30 -> result (+epo:hasFormType))
      • +
    • ... (epo-not:Notice31 -> result (+epo:hasFormType))
      • +
    • ... (epo-not:Notice32 -> result (+epo:hasFormType))
      • +
    • ... (epo-not:Notice33 -> result (+epo:hasFormType))
      • +
    • ... (epo-not:Notice34 -> result (+epo:hasFormType))
      • +
    • ... (epo-not:Notice35 -> result (+epo:hasFormType))
      • +
    • ... (epo-not:Notice36 -> result (+epo:hasFormType))
      • +
    • ... (epo-not:Notice37 -> result (+epo:hasFormType))
      • +
    • ... (epo-not:Notice38 -> cont-modif (+epo:hasFormType))
      • +
    • ... (epo-not:Notice39 -> cont-modif (+epo:hasFormType))
      • +
    • ... (epo-not:Notice4 -> planning (+epo:hasFormType))
      • +
    • ... (epo-not:Notice40 -> cont-modif (+epo:hasFormType))
      • +
    • ... (epo-not:Notice5 -> planning (+epo:hasFormType))
      • +
    • ... (epo-not:Notice6 -> planning (+epo:hasFormType))
      • +
    • ... (epo-not:Notice7 -> planning (+epo:hasFormType))
      • +
    • ... (epo-not:Notice8 -> planning (+epo:hasFormType))
      • +
    • ... (epo-not:Notice9 -> planning (+epo:hasFormType))
      • +
    • ... (epo-not:CANDefence-D81 -> Form18 (+epo:hasFormType))
      • +
    • ... (epo-not:CANSocial-D25 -> Form6 (+epo:hasFormType))
      • +
    • ... (epo-not:CANSocialNotice-D25 -> Form22 (+epo:hasFormType))
      • +
    • ... (epo-not:CANStandard-D24 -> Form3 (+epo:hasFormType))
      • +
    • ... (epo-not:CNDefence-D81 -> Form17 (+epo:hasFormType))
      • +
    • ... (epo-not:CNSocial-D25 -> Form5 (+epo:hasFormType))
      • +
    • ... (epo-not:CNSocialNotice-D25 -> Form22 (+epo:hasFormType))
      • +
    • ... (epo-not:CNStandard-D24 -> Form2 (+epo:hasFormType))
      • +
    • ... (epo-not:ConcessionAwardNotice-D23 -> Form25 (+epo:hasFormType))
      • +
    • ... (epo-not:ConcessionNotice-D23 -> Form24 (+epo:hasFormType))
      • +
    • ... (epo-not:DesignContest-D24 -> Form12 (+epo:hasFormType))
      • +
    • ... (epo-not:DesignContest-D25 -> Form12 (+epo:hasFormType))
      • +
    • ... (epo-not:DesignContestResult-D24 -> Form13 (+epo:hasFormType))
      • +
    • ... (epo-not:DesignContestResult-D25 -> Form13 (+epo:hasFormType))
      • +
    • ... (epo-not:Modification-D23 -> Form20 (+epo:hasFormType))
      • +
    • ... (epo-not:Modification-D24 -> Form20 (+epo:hasFormType))
      • +
    • ... (epo-not:Modification-D25 -> Form20 (+epo:hasFormType))
      • +
    • ... (epo-not:PIN-CFCSocial-D25 -> Form4 (+epo:hasFormType))
      • +
    • ... (epo-not:PIN-CFCSocialNotice-D25 -> Form22 (+epo:hasFormType))
      • +
    • ... (epo-not:PIN-CFCStandard-D24 -> Form1 (+epo:hasFormType))
      • +
    • ... (epo-not:PIN-RTL-D24 -> Form1 (+epo:hasFormType))
      • +
    • ... (epo-not:PIN-RTL-D25 -> Form4 (+epo:hasFormType))
      • +
    • ... (epo-not:PINDefence-D81 -> Form16 (+epo:hasFormType))
      • +
    • ... (epo-not:PINOnly-D24 -> Form1 (+epo:hasFormType))
      • +
    • ... (epo-not:PINOnly-D25 -> Form4 (+epo:hasFormType))
      • +
    • ... (epo-not:PINProfile-D24 -> Form8 (+epo:hasFormType))
      • +
    • ... (epo-not:PINProfile-D25 -> Form8 (+epo:hasFormType))
      • +
    • ... (epo-not:PINProfile-D81 -> Form8 (+epo:hasFormType))
      • +
    • ... (epo-not:QS-D25 -> Form7 (+epo:hasFormType))
      • +
    • ... (epo-not:QSNotice-D25 -> Form22 (+epo:hasFormType))
      • +
    • ... (epo-not:SocialAndOtherSpecificServices-D23 -> Form23 (+epo:hasFormType))
      • +
    • ... (epo-not:SocialAndOtherSpecificServices-D24 -> Form21 (+epo:hasFormType))
      • +
    • ... (epo-not:Subcontract-D81 -> Form19 (+epo:hasFormType))
      • +
    • ... (epo-not:VEAT-D23 -> Form15 (+epo:hasFormType))
      • +
    • ... (epo-not:VEAT-D24 -> Form15 (+epo:hasFormType))
      • +
    • ... (epo-not:VEAT-D25 -> Form15 (+epo:hasFormType))
      • +
    • ... (epo-not:VEAT-D81 -> Form15 (+epo:hasFormType))
      • +
    +
    +
    +
    epo:hasLegalBasis
    +
    +
    When a property is reused in multiple contexts, the multiplicity is expected to be + the same. Please check the nomenclature above for a summary.
    +
    When a property is reused in multiple contexts, the meaning given by the definition + is expected to be the same. In this case, multiple definitions are found: +
      +
    • The legal basis under which the procurement procedure takes place. + + Additional Information: + For example European Directives or Regulations, national laws etc. + The recommended code list is the example for the legal basis at the European level. + + WG 04/04/2023 + + (epo:ProcurementObject -> at-voc:legal-basis (+epo:hasLegalBasis))
      • +
    • ... (epo-not:VEAT-D23 -> Directive 23 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice35 -> Directive 23 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Modification-D23 -> Directive 23 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice32 -> Directive 23 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice19 -> Directive 23 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:ConcessionNotice-D23 -> Directive 23 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:ConcessionAwardNotice-D23 -> Directive 23 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice40 -> Directive 23 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice28 -> Directive 23 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:SocialAndOtherSpecificServices-D23 -> Directive 23 (+epo:hasLegalBasis)) +
      • +
    • ... (epo-not:Notice14 -> Directive 23 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice10 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:SocialAndOtherSpecificServices-D24 -> Directive 24 (+epo:hasLegalBasis)) +
      • +
    • ... (epo-not:VEAT-D24 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:PINOnly-D24 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice25 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice23 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:CNStandard-D24 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:PIN-CFCStandard-D24 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice29 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice38 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice36 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice1 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:DesignContestResult-D24 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice33 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:CANStandard-D24 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:DesignContest-D24 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:PIN-RTL-D24 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice20 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:PINProfile-D24 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice12 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice4 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice16 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice7 -> Directive 24 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Modification-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice26 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:CNSocial-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:PIN-CFCSocial-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:PINOnly-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice2 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:PINProfile-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:PIN-RTL-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice37 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:VEAT-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:CANSocialNotice-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:QSNotice-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:QS-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:DesignContestResult-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:CNSocialNotice-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice34 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice24 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:CANSocial-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice30 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice8 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice13 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice5 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice39 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice21 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice15 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice17 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:DesignContest-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice11 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:PIN-CFCSocialNotice-D25 -> Directive 25 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:VEAT-D81 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:PINProfile-D81 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice6 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:PINDefence-D81 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Subcontract-D81 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice27 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice22 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:CNDefence-D81 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice18 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:CANDefence-D81 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice3 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice9 -> Directive 81 (+epo:hasLegalBasis))
      • +
    • ... (epo-not:Notice31 -> Directive 81 (+epo:hasLegalBasis))
      • +
    +
    epo:hasPurpose
    @@ -3902,6 +10109,11 @@

    epo:specifiesProcurementCriterion
    +
    When a property is reused in multiple contexts, the multiplicity is expected to be + the same. Please check the nomenclature above for a summary.
    +
    +
    epo:specifiesSeller
    +
    When a property is reused in multiple contexts, the multiplicity is expected to be the same. Please check the nomenclature above for a summary.
    @@ -3923,11 +10135,47 @@

    +
    +
    epo-cat:hasPrice
    +
    +
    When a property is reused in multiple contexts, the multiplicity is expected to be + the same. Please check the nomenclature above for a summary.
    epo-cat:hasQuantity
    When a property is reused in multiple contexts, the multiplicity is expected to be the same. Please check the nomenclature above for a summary.
    +
    +
    epo-ful:specifiesDespatcher
    +
    +
    When a property is reused in multiple contexts, the multiplicity is expected to be + the same. Please check the nomenclature above for a summary.
    +
    +
    epo-ord:hasTaxInformation
    +
    +
    When a property is reused in multiple contexts, the multiplicity is expected to be + the same. Please check the nomenclature above for a summary.
    +
    +
    epo-ord:isSpecificToOrderLine
    +
    +
    When a property is reused in multiple contexts, the meaning given by the definition + is expected to be the same. In this case, multiple definitions are found: +
      +
    • Information that is particular to one or multiple Order Lines. + (epo-cat:ChargeInformation -> epo-ord:OrderLine (+epo-ord:isSpecificToOrderLine)) +
      • +
    • Information that is particular to one or multiple Order Lines. + (epo-ord:AllowanceInformation -> epo-ord:OrderLine (+epo-ord:isSpecificToOrderLine)) +
      • +
    • Information that is particular to one or multiple Order Lines. (epo-ord:ContractInformation + -> epo-ord:OrderLine (+epo-ord:isSpecificToOrderLine))
      • +
    • Information that is particular to one or multiple Order Lines. (epo-ord:DeliveryInformation + -> epo-ord:OrderLine (+epo-ord:isSpecificToOrderLine))
      • +
    • Information that is particular to one or multiple Order Lines. + (epo-ord:OriginatorInformation -> epo-ord:OrderLine (+epo-ord:isSpecificToOrderLine)) +
      • +
    +
    locn:address
    @@ -3974,6 +10222,17 @@

    The attribute dct:description is defined differently in reuse contexts. When a property @@ -4110,6 +10369,122 @@

    The attribute dct:description is has different datatypes in reuse contexts.When a + property is reused in multiple contexts, the data-type is expected to be the same.In + this case, multiple data-types are found: +
      +
    • rdf:PlainLiteral (cccev:Evidence)
      • +
    • rdf:PlainLiteral (cccev:InformationConcept)
      • +
    • rdf:PlainLiteral (cccev:Requirement)
      • +
    • rdf:PlainLiteral (cpov:ContactPoint)
      • +
    • rdf:PlainLiteral (cv:Channel)
      • +
    • rdf:PlainLiteral (epo:AgentInRole)
      • +
    • rdf:PlainLiteral (epo:Document)
      • +
    • rdf:PlainLiteral (epo:ElectronicSignature)
      • +
    • rdf:PlainLiteral (epo:Fund)
      • +
    • rdf:PlainLiteral (epo:NonDisclosureAgreementTerm)
      • +
    • rdf:PlainLiteral (epo:SecurityClearanceTerm)
      • +
    • rdf:PlainLiteral (epo:SubcontractingEstimate)
      • +
    • rdf:PlainLiteral (epo:SubcontractTerm)
      • +
    • rdf:PlainLiteral (epo:System)
      • +
    • rdf:PlainLiteral (epo:Technique)
      • +
    • rdf:PlainLiteral (epo:LotGroup)
      • +
    • rdf:PlainLiteral (epo:ProcurementElement)
      • +
    • rdf:PlainLiteral (epo:TenderGroup)
      • +
    • rdf:PlainLiteral (epo-cat:Line)
      • +
    • rdf:PlainLiteral (epo-cat:Item)
      • +
    • rdf:PlainLiteral (epo-ord:DeliveryAgreement)
      • +
    • rdf:PlainLiteral (epo-ord:TaxInformation)
      • +
    • rdf:PlainLiteral (epo-ful:ShipmentInformation)
      • +
    • rdf:PlainLiteral (epo-ful:TemperatureSpecification)
      • +
    • rdf:PlainLiteral (epo-ful:TransportEquipment)
      • +
    • rdf:PlainLiteral (cccev:EvidenceTypeList)
      • +
    • rdfs:Literal (eli:LegalExpression)
      • +
    • rdfs:Literal (eli:LegalResource)
      • +
    • rdf:PlainLiteral (epo-sub:CertificateInformation)

    @@ -4126,6 +10501,10 @@

    The attribute dct:title is defined differently in reuse contexts. When a property @@ -4159,6 +10538,34 @@

    The attribute dct:title is has different datatypes in reuse contexts.When a property + is reused in multiple contexts, the data-type is expected to be the same.In this case, + multiple data-types are found: +
      +
    • rdf:PlainLiteral (epo:AgentInRole)
      • +
    • rdf:PlainLiteral (epo:Document)
      • +
    • rdf:PlainLiteral (epo:Fund)
      • +
    • rdf:PlainLiteral (foaf:Agent)
      • +
    • rdf:PlainLiteral (epo:LotGroup)
      • +
    • rdf:PlainLiteral (epo:ProcurementElement)
      • +
    • rdf:PlainLiteral (epo:TenderGroup)
      • +
    • rdf:PlainLiteral (epo-cat:Brand)
      • +
    • rdf:PlainLiteral (epo-cat:ItemModel)
      • +
    • rdf:PlainLiteral (epo-cat:Item)
      • +
    • rdfs:Literal (eli:LegalExpression)
    @@ -4260,6 +10667,22 @@

    +
    epo-cat:hasPercentage
    +
    The attribute epo-cat:hasPercentage is defined differently in reuse contexts. When + a property is reused in multiple contexts, the meaning given by the definition is + expected to be the same.In this case, multiple definitions are found: +
      +
    • The factor relative to the price charged in addition. + + WG approval 26/07/2022 (epo-ord:AllowanceChargeInformation)
      • +
    • The factor relative to the price charged in addition. + + WG approval 26/07/2022 + (epo-ord:TaxInformation)
      • +
    +
    +
    skos:prefLabel
    The attribute skos:prefLabel has different multiplicities in reuse contexts. @@ -4268,6 +10691,7 @@

    The attribute skos:prefLabel is defined differently in reuse contexts. When a property @@ -4282,6 +10706,10 @@

    • Predicate nameDefinitionDomain, Range and Cardinalityepo:isCalculatedOnThe monetary amount to which the multiplier factor is applied in calculating the amount + of this allowance or charge. + + The monetary amount to which the multiplier factor is applied in calculating the amount + of this allowance or charge.epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [0..1]
    epo-ord:TaxInformation -> epo:MonetaryValue [0..1]
    adms:identifierLinks a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. 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 - - Links a resource to an adms:Identifier class. 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 - Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class.cccev:Evidence -> adms:Identifier [1]
    cccev:InformationConcept -> adms:Identifier [0..1]
    cccev:Requirement -> adms:Identifier [0..1]
    dct:Location -> adms:Identifier [0..1]
    epo:Document -> adms:Identifier [0..*]
    epo:Fund -> adms:Identifier [0..1]
    epo:Project -> adms:Identifier [0..1]
    foaf:Agent -> adms:Identifier [0..*]
    epo:LotGroup -> adms:Identifier [0..1]
    epo:ProcurementElement -> adms:Identifier [1]
    epo:TenderGroup -> adms:Identifier [0..1]









    		epo:isExecutedByProcurementServiceProviderepo:Procedure -> epo:ProcurementServiceProvider [0..1]
    cccev:confidentialityLevelTypeSecurity classification assigned to an Evidence e.g. classified, sensitive, public. + epo:isFundedByFunding is provided either completely or partially by a Fund. - Additional Information: + 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. - Classifications should be defined by an organisation/country as an outcome of a security - assessment. - Security classification assigned to an Evidence e.g. classified, sensitive, public. + Funding is provided either completely or partially by a Fund. - Additional Information: + 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. - Classifications should be defined by an organisation/country as an outcome of a security - assessment.cccev:Evidence -> at-voc:access-rights [0..1]

    		epo:Contract -> epo:Fund [0..*]
    epo:ProcurementObject -> epo:Fund [0..*]
    cccev:constrainsInformation 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..*]epo:isOwnedByAgentepo:System -> foaf:Agent [0..1]
    cccev:hasConceptInformation Concept for which a value is expected by the Requirement. + epo:isResponsibilityOfBuyerThe buyer in charge of the procedure. Additional Information: - Information Concepts defined for specific Requirements also represent the basis for - specifying the Supported Value an Evidence should provide. cccev:Requirement -> cccev:InformationConcept [0..*]epo:Procedure -> epo:Buyer [0..*]
    cccev:hasRequirementA more specific Requirement that is part of the Requirement.cccev:Requirement -> cccev:Requirement [0..*]epo:isSubjectToContractSpecificTermepo:Contract -> epo:ContractSpecificTerm [0..*]
    cccev:supportsConceptInformation Concept providing facts found/inferred from the Evidence. - - Additional Information: - Examples of Information Concepts are values found explicitly 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 Fair Trade product".cccev:Evidence -> cccev:InformationConcept [0..*]epo:isSubjectToGroupingepo:Tender -> epo:LotGroup [0..1]
    cccev:supportsRequirementRequirement for which the Evidence provides proof.cccev:Evidence -> cccev:Requirement [0..*]epo:isSubjectToLotSpecificTermepo:Lot -> epo:LotSpecificTerm [0..*]
    cv:registeredAddressThe 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. 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. - person:Person -> locn:Address [0..1]
    org:Organization -> locn:Address [0..1]
    		epo:isSubjectToProcedureSpecificTermepo:Procedure -> epo:ProcedureSpecificTerm [1..*]
    dct:typeCategory to which the Requirement belongs.cccev:Criterion -> at-voc:criterion [0..1]epo:isSubjectToTermepo:ProcurementObject -> epo:Term [0..*]
    epo:actsOnBehalfOfRepresents. epo:ProcurementServiceProvider -> epo:Buyer [1..*]

    		epo:isSubmitedByRelation indicating the submission of a tender by an economic operator. + WG approval 18/05/2021epo:Tender -> epo:Tenderer [0..1]
    epo:associatedWithThe document to which a document is associated. - - WGM 01/03/2022 - epo:Document -> epo:Document [0..*]epo:isSubmittedForLotepo:Tender -> epo:Lot [1]
    epo:attestedByLabelRelation indicating which label the certificate is about. + epo:isSubmittedForLotGroupepo:TenderGroup -> epo:LotGroup [1]
    epo:issuedByCertifierRelation indicating the Certifier responsible for providing the ItemCertificate. - WG approval 28/07/2022epo:Certificate -> epo:CertificationLabel [0..1]epo:Certificate -> epo:Certifier [0..1]
    epo:bindsBuyerProvides legal constraint on the Buyer.epo:Contract -> epo:Buyer [0..*]epo:isSupportedByepo:Tender -> epo-sub:ESPDResponse [1]
    epo:bindsContractorProvides legal constraint on the Contractor.epo:Contract -> epo:Contractor [0..*]epo:leadByThe epo:OrganisationGroup epo:leadBy org:Organization was implemented to be used in + case of an Economic Operator Group.epo:OrganisationGroup -> org:Organization [0..1]
    epo:canProvideNonDiscriminatoryEvidenceRelation showing that an Organization can supply an Evidence with regard to the fulfilment - of non-discriminatory criteria or the rules applied in order to reduce the number - of participants. - - WG approval 12/03/2024org:Organization -> cccev:Evidence [0..*]epo:needsToBeATendererThe Winner must be a Tenderer.epo:Winner -> epo:Tenderer [0..1]
    epo:canProvideTaxAndSocialSecuritiesEvidenceRelation showing that an Organization can supply an Evidence with regard to the payment - of social security contributions and taxes. - - WG approval 12/03/2024org:Organization -> cccev:Evidence [0..*]epo:needsToBeAWinnerThe Contractor must be a Winner. + epo:Contractor -> epo:Winner [0..1]
    epo:comprisesAwardOutcomeIncorporates AwardOutcome.epo:AwardDecision -> epo:AwardOutcome [0..*]epo:ownsSystemepo:System [,0..*] <- foaf:Agent
    epo:comprisesTenderIncorporates Tender.epo:TenderGroup -> epo:Tender [1..*]epo:playedBy epo:AgentInRole -> foaf:Agent [1]
    epo:JuryMember -> person:Person [0..1]
    epo-ful:TransportMeansOperator -> foaf:Person [0..1]
    epo:comprisesTenderAwardOutcomeIncorporates TenderAwardOutcome.epo:AwardOutcome -> epo:TenderAwardOutcome [0..*]epo:providesContractTotalPaymentValueAdditional Information: + This corresponds to BT-779 in eForms. epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1]
    epo:concernsGreenProcurementepo:VehicleInformation -> epo:GreenProcurement [1]epo:providesContractTotalPenaltyValue + Additional Information: + This corresponds to BT-782 in eForms. + epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1]
    epo:concernsLotRelates to Lot. Relates to Lot.epo:LotAwardOutcome -> epo:Lot [1]
    epo:ProcurementProcessInformation -> epo:Lot [0..1]
    		epo:providesRulingOnRemedyStates the measures to be taken after a review procedure.epo:ReviewDecision -> at-voc:remedy-type [0..*]
    epo:concernsNoticeepo:refersToAwardDecision epo:ChangeInformation -> epo:Notice [1]
    epo:NonPublishedInformation -> epo:Notice [1]
    		epo-not:CompletionNotice -> epo:AwardDecision [0..*]
    epo-not:ContractModificationNotice -> epo:AwardDecision [0..*]
    epo:concernsProcedureRelates to Procedure. Relates to Procedure. - - WG approval 05/03/2024 - epo:ProcurementProcessInformation -> epo:Procedure [0..1]

    		epo:refersToContractepo:ContractLotCompletionInformation -> epo:Contract [1]
    epo:concernsReviewSummaryForLotRelates to Lot review summary. - - Additional information: - This relation corresponds in eForms to BT-13722 Buyer Review Lot Identifier.epo:ReviewRequestSummary -> epo:Lot [1]epo:refersToContractToBeModifiedepo-not:ContractModificationNotice -> epo:Contract [1]
    epo:concernsTenderepo:refersToLot epo:Notice -> epo:Lot [1..*]
    epo-not:CompletionNotice -> epo:Lot [1..*]
    epo-not:ContractModificationNotice -> epo:Lot [1..*]
    epo-not:ResultNotice -> epo:Lot [1..*]
    epo:refersToLotGroup epo-not:ContractModificationNotice -> epo:LotGroup [0..*]
    epo-not:ResultNotice -> epo:LotGroup [0..*]
    epo-not:CompletionNotice -> epo:LotGroup [0..*]
    epo:refersToLotGroupAwardInformation epo-not:CompletionNotice -> epo:LotGroupAwardInformation [0..*]
    epo-not:ContractModificationNotice -> epo:LotGroupAwardInformation [0..*]
    epo:refersToNotice epo:TenderAwardOutcome -> epo:Tender [1]epo:Notice -> epo:Notice [0..1]
    epo:conformsToLegalBasisThe Notice was designed in accordance with the given legal basis. - - Additional Information: - This Notice can be used for Procedures which do not have the same legal basis. - This holds for standard forms.epo:Notice -> at-voc:legal-basis [0..*]epo:refersToNoticeAwardInformation epo-not:ContractModificationNotice -> epo:NoticeAwardInformation [0..1]
    epo-not:CompletionNotice -> epo:NoticeAwardInformation [0..1]
    epo:containsCandidateepo:refersToPlannedPart epo:SelectedCandidateList -> epo:Candidate [0..*]epo:AccessTerm -> epo:PlannedProcurementPart [0..*]
    epo:contextualisedByThe place of the AgentInRole in the procurement is expressed by a ProcurementObject.epo:AgentInRole -> epo:ProcurementObject [0..*]epo:refersToPreviousepo:Document -> epo:Document [0..*]
    epo:definesBudgetProviderRelation indicating a ProcedureTerm has a BudgetProvider.epo:ProcedureTerm -> epo:BudgetProvider [0..1]epo:refersToPreviousNotice + Additional information: + This corresponds in eForms to BT-758 Change Notice Version Identifier.epo:ChangeInformation -> epo:Notice [1]
    epo:definesCatalogueProviderRelation indicating an AccessTerm has a CatalogueProvider.epo:AccessTerm -> epo:CatalogueProvider [0..*]epo:refersToPreviousProcedureReference 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 Identifierepo:DirectAwardTerm -> epo:Procedure [0..1]
    epo:definesCatalogueReceiverRelation indicating an AccessTerm has a CatalogueReceiver.epo:AccessTerm -> epo:CatalogueReceiver [0..*]epo:refersToPreviousProcedureLotReference 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:55epo:DirectAwardTerm -> epo:Lot [0..*]
    epo:definesContractDurationRelation indicating a ContractTerm has a Duration.epo:ContractTerm -> epo:Duration [0..1]epo:refersToPreviousReviewAdditional information: + This relation corresponds in eForms to BT-785 "Review Previous Identifier".epo:ReviewObject -> epo:ReviewObject [0..1]
    epo:definesContractPeriodRelation indicating a ContractTerm has a Period.epo:ContractTerm -> epo:Period [0..1]epo:refersToProcedure epo:Notice -> epo:Procedure [1]
    epo-not:ResultNotice -> epo:Procedure [1]
    epo-not:ContractModificationNotice -> epo:Procedure [1]
    epo-not:CompletionNotice -> epo:Procedure [1]
    epo:definesInformationProviderRelation indicating a ProcedureTerm has an information provider.epo:ProcedureTerm -> epo:AuxiliaryParty [0..*]epo:refersToProjectepo-ord:Order -> epo:Project [0..1]
    epo:definesLotGroupRelation indicating a ProcedureTerm has a LotGroup.epo:ProcedureTerm -> epo:LotGroup [0..*]epo:refersToRoleepo-not:CompletionNotice -> epo:AgentInRole [0..*]
    epo:definesMediatorRelation indicating a ProcedureTerm has a Mediator.epo:ProcedureTerm -> epo:Mediator [0..1]epo:relatesToEFormSectionIdentifier epo:ChangeInformation -> adms:Identifier [1..*]
    epo:NonPublishedInformation -> adms:Identifier [1..*]
    epo-con:ContractModificationInformation -> adms:Identifier [0..1]
    epo:definesOfflineAccessProviderRelation indicating an AccessTerm has an OfflineAccessProvider.epo:AccessTerm -> epo:OfflineAccessProvider [0..1]epo:requestsRemedyTypeAdditional information: + This relation corresponds in eForms to BT-792 Review Remedy Typeepo:ReviewRequest -> at-voc:remedy-type [0..*]
    epo:definesOpeningPlaceThe place where the tenders will be publicly opened. - - WG Approval 10-10-2019epo:OpeningTerm -> locn:Address [0..1]epo:resolvesReviewRequestepo:ReviewDecision -> epo:ReviewRequest [1]
    epo:definesParticipationRequestProcessorRelation indicating a ParticipationRequestTerm has a ParticipationRequestProcessor.epo:ParticipationRequestTerm -> epo:ParticipationRequestProcessor [0..1]epo:resultsFromLotAwardOutcome epo:DirectContract -> epo:LotAwardOutcome [0..*]
    epo:FrameworkAgreement -> epo:LotAwardOutcome [0..*]
    epo:definesParticipationRequestReceiverRelation indicating a ParticipationRequestTerm has a ParticipationRequestReceiver.epo:ParticipationRequestTerm -> epo:ParticipationRequestReceiver [0..1]epo:resultsFromMiniCompetitionAwardOutcomeepo:PurchaseContract -> epo:MiniCompetitionAwardOutcome [0..1]
    epo:definesPaymentExecutorRelation indicating a ContractTerm has a PaymentExecutor.epo:ContractTerm -> epo:PaymentExecutor [0..1]epo:resultsFromUsingCandidateListepo:MiniCompetitionAwardOutcome -> epo:SelectedCandidateList [0..1]
    epo:definesPrizeRelation indicating a DesignContestRegimeTerm has a Prize.epo:DesignContestRegimeTerm -> epo:Prize [0..*]epo:setsGroupingContextForLotepo:LotGroup -> epo:Lot [1..*]
    epo:definesProcurementProcedureInformationProviderRelation indicating an AccessTerm has a ProcurementProcedureInformationProvider.epo:AccessTerm -> epo:ProcurementProcedureInformationProvider [0..1]epo:signedByBuyerepo:Contract -> epo:Buyer [0..*]
    epo:definesReviewerRelation indicating a ReviewTerm has a Reviewer.epo:ReviewTerm -> epo:Reviewer [0..*]epo:signedByContractorepo:Contract -> epo:Contractor [0..*]
    epo:definesReviewProcedureInformationProviderRelation indicating a ReviewTerm has a ReviewProcedureInformationProvider.epo:ReviewTerm -> epo:ReviewProcedureInformationProvider [0..1]epo:signsAwardDecisionepo:Buyer -> epo:AwardDecision [0..*]
    epo:definesSpecificPlaceOfPerformanceRelation indicating a ContractTerm has a specific place of performance.epo:ContractTerm -> dct:Location [0..*]epo:specifiesBuyer epo-cat:Catalogue -> epo:Buyer [0..*]
    epo-ord:Order -> epo:Buyer [1]
    epo:definesSubcontractingTermRelation indicating a ContractTerm has a SubcontractingTerm.Relation indicating a - term has a subterm.epo:ContractTerm -> epo:SubcontractTerm [0..1]epo:specifiesCarrierepo-ful:ShipmentStage -> epo-ful:Carrier [0..1]
    epo:definesTenderProcessorRelation indicating a SubmissionTerm has a TenderProcessor.epo:SubmissionTerm -> epo:TenderProcessor [0..1]epo:specifiesCatalogueProvider epo-cat:Catalogue -> epo:CatalogueProvider [0..1]
    epo-cat:CatalogueResponse -> epo:CatalogueProvider [1]
    epo:definesTenderReceiverRelation indicating a SubmissionTerm has a TenderReceiver.epo:SubmissionTerm -> epo:TenderReceiver [0..1]epo:specifiesCatalogueReceiver epo-cat:Catalogue -> epo:CatalogueReceiver [0..1]
    epo-cat:CatalogueResponse -> epo:CatalogueReceiver [1]
    epo:delegatesAncillaryActivitiesToEntrusts 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:specifiesCleanVehicleDirectiveContractTypeepo:VehicleInformation -> at-voc:cvd-contract-type [0..1]
    epo:describesLotCompletionepo:specifiesCleanVehicleDirectiveVehicleCategory epo:ContractLotCompletionInformation -> epo:Lot [1]epo:VehicleInformation -> at-voc:vehicle-category [0..1]
    epo:describesLotGroupepo:specifiesDeliverable epo:LotGroupAwardInformation -> epo:LotGroup [1]epo:Contract -> epo-con:Deliverable [0..*]
    epo:distributesOfferepo:specifiesDespatcher epo:OfferIssuer -> epo:Offer [0..*]epo-ord:Order -> epo-ful:Despatcher [0..1]
    epo:exposesChannelepo:specifiesFreightForwarder epo:AgentInRole -> cv:Channel [0..*]epo-ful:Consignment -> epo-ful:FreightForwarder [0..*]
    epo:exposesInvoiceeChannelepo:specifiesNotifier epo:Buyer -> cv:Channel [0..*]epo-ful:Consignment -> epo-ful:Notifier [0..*]
    epo:followsRulesSetByepo:specifiesProcurementCriteriaSummary epo:PurchaseContract -> epo:FrameworkAgreement [0..1]epo:Procedure -> epo:ProcurementCriteriaSummary [0..*]
    epo:foreseesConcessionepo:specifiesProcurementCriterion epo-acc:ESPDRequest -> epo:ProcurementCriterion [1..*]
    epo:Lot -> epo:ProcurementCriterion [0..*]
    epo:LotGroup -> epo:ProcurementCriterion [0..*]
    epo:specifiesSeller epo:Tender -> epo:ConcessionEstimate [0..1]
    epo:ProcurementObject -> epo:ConcessionEstimate [0..1]
    		epo-cat:Catalogue -> epo-ord:Seller [0..*]
    epo-ord:Order -> epo-ord:Seller [1]
    epo:foreseesContractSpecificTermepo:specifiesSubcontractors epo:ProcurementObject -> epo:ContractSpecificTerm [0..*]epo:Tender -> epo:Subcontractor [0..*]
    epo:foreseesProcurementObjectRelation indicating the instance of a Procurement Object that is planned. + epo:substantiatesExclusionGroundepo:Tenderer -> epo:ExclusionGround [0..1]
    epo:summarisesInformationForAwardOutcomeRelates to submission for the given competition, either at Lot level or Mini-Competition + level. - Additional Information: - The properties of the Procurement Object that is foreseen should be read as foreseen - properties. - For example, Procedure isSMESuitable should be read as Procedure foreseesToBeSMESuitable. - For example, Procedure isFundedBy should be read as Procedure foreseesToBeFundedBy.epo:PlannedProcurementPart -> epo:ProcurementObject [0..1]epo:SubmissionStatisticalInformation -> epo:AwardOutcome [1]
    epo:foreseesSubcontractingepo:updatesContractValue epo:Tender -> epo:SubcontractingEstimate [0..*]epo-con:ContractAmendment -> epo:MonetaryValue [0..1]
    epo:foreseesTechniqueepo:usesChannel epo:PlannedProcurementPart -> epo:Technique [0..*]epo:ProcurementElement -> cv:Channel [0..*]
    epo:fulfillsRequirementThe requirement to which the concept meets. - WG Approval 09/11/2021 - The requirement to which the concept meets. - WG Approval 09/11/2021 - - The requirement to which the concept meets. - WG Approval 09/11/2021 - - The requirement to which the concept meets. - WG Approval 09/11/2021 + epo:usesTechniqueepo:ProcurementObject -> epo:Technique [0..*]
    epo-acc:refersToNoticeReference to a Notice. - epo:GreenProcurement -> at-voc:green-public-procurement-criteria [0..*]
    epo:GreenProcurement -> at-voc:environmental-impact [0..*]
    epo:InnovativeProcurement -> at-voc:innovative-acquisition [0..*]
    epo:SocialProcurement -> at-voc:social-objective [0..*]
    		epo-acc:ESPDRequest -> epo:Notice [0..*]
    epo:fulfillsStrategicProcurementepo-cat:comprisesCatalogueLine epo:ProcurementObject -> epo:StrategicProcurement [0..*]epo-cat:Catalogue -> epo-cat:CatalogueLine [1..*]
    epo:hasAdditionalClassificationepo-cat:comprisesCatalogueResponseLine epo:Purpose -> at-voc:cpv [0..*]epo-cat:CatalogueResponse -> epo-cat:CatalogueResponseLine [0..*]
    epo:hasAdditionalContractNatureAdditional type of acquisition taken into consideration in the contract. - - WG Approval 11/06/2020 - - epo:ContractTerm -> at-voc:contract-nature [0..*]epo-cat:describesItemepo-cat:ItemProperty -> epo-cat:Item [1]
    epo:hasAllegedIrregularityTypeAdditional information: - This relation corresponds in eForms to BT-791 Review Irregularity Type - epo:ReviewRequest -> at-voc:irregularity-type [1..*]epo-cat:foreseesPackageepo-cat:CatalogueLine -> epo-ful:Package [0..1]
    epo:hasApproximateFrameworkAgreementValueThe estimated value to be spent within the Framework Agreement(s). + epo-cat:hasAccessoryItemAn item that can be added to another item to enhance it. - Additional information: - In the case of an Award Decision for a Lot, this relation represents the estimated - value for the awarded Framework Agreement. - In the case of a Notice, this relation represents the estimated value for all Framework - Agreements covered by the Notice. - The estimated value to be spent within the Framework Agreement(s). - - Additional information: - In the case of an Award Decision for a Lot, this relation represents the estimated - value for the awarded Framework Agreement. - In the case of a Notice, this relation represents the estimated value for all Framework - Agreements covered by the Notice. - epo:LotAwardOutcome -> epo:MonetaryValue [0..1]
    epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]
    epo:hasAwardCriterionTypeCategory of award criterion. + WG Approval: 30/06/2022An additional item that can enhance the original item. + WG Approval: 19/05/2022 epo:AwardCriterion -> at-voc:award-criterion-type [0..1]epo-cat:Item -> epo-cat:Item [0..*]
    epo:hasAwardedValueThe 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/2019epo:AwardOutcome -> epo:MonetaryValue [0..1]epo-cat:hasActivityCode epo-cat:Catalogue -> at-voc-new:activity-code [0..1]
    epo-cat:CatalogueLine -> at-voc-new:activity-code [0..1]
    epo:hasAwardStatusIndicates whether the lot is awarded, not awarded or still open. - WG Approval 03/12/2019 + epo-cat:hasAmountThe predetermined monetary value charged in addition to the price. + + WG approval 26/07/2022 The predetermined monetary value charged in addition to the price. + + WG approval 26/07/2022 epo:AwardOutcome -> at-voc:winner-selection-status [0..1]epo-ord:AllowanceChargeInformation -> epo:MonetaryValue [1]
    epo-ord:TaxInformation -> epo:MonetaryValue [0..1]
    epo:hasBargainPriceThe value of procured supplies that have used a particularly advantageous opportunity - available for a very short time at a value considerably lower than normal market prices. - - WG approval 23/05/2023epo:AwardOutcome -> epo:MonetaryValue [0..1]epo-cat:hasBaseQuantityThe quantity at which the net monetary value applies.epo-cat:Price -> epo:Quantity [0..1]
    epo:hasBeneficialOwnerA 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/2021epo:Business -> person:Person [0..*]epo-cat:hasBrandepo-cat:Item -> epo-cat:Brand [0..1]
    epo:hasBroadPlaceOfPerformanceGeopolitical zone where the contract can be executed. + epo-cat:hasCatalogueLineValidityThe relation indicating until when a Catalogue Line instance is applicable. - 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). - epo:ContractTerm -> at-voc:other-place-service [0..1]epo-cat:CatalogueLine -> epo:Period [0..1]
    epo:hasBusinessSizeThe category of the business depending on number of employees and turnover. + epo-cat:hasChargeInformationepo-cat:CatalogueLine -> epo-cat:ChargeInformation [0..*]
    epo-cat:hasComplementaryItemAn item that if used with another item provides mutual enhancements to both of them. Additional information: + For example, gin and tonic; or smart-phone and smart-watch. - See Commission Recommendation of 6 May 2003 concerning the definition of micro, small - and medium-sized enterprises. - - WG Approval 28/05/2020 + WG Approval: 19/05/2022 epo:Business -> at-voc:economic-operator-size [0..1]epo-cat:Item -> epo-cat:Item [0..*]
    epo:hasBuyerLegalTypeA category that indicates the right of an Organisation to play the role of a buyer. + epo-cat:hasCountryOfOriginThe source country of the product or service. 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 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 org:Organization -> at-voc:buyer-legal-type [0..1]epo-cat:Item -> at-voc:country [0..1]
    epo:hasCertificationRelation to the proof of conformance. - - WG approval 30/05/2023 Relation to the proof of conformance. - - WG approval 30/05/2023 Relation to the proof of conformance. - - WG approval 30/05/2023foaf:Person -> epo:Certificate [0..*]
    org:Organization -> epo:Certificate [0..*]

    		epo-cat:hasDeliveryClassificationepo-cat:Item -> at-voc-new:delivery-item-type [0..1]
    epo:hasChangeJustificationCode explaining the change. - - 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-justificationepo:ChangeInformation -> at-voc:change-corrig-justification [1]epo-cat:hasDeliveryLocationLocation delivery area where the Item can be ordered to the given price. + epo-cat:Price -> dct:Location [0..1]
    epo:hasConcessionEstimatedValueepo-cat:hasDocumentType epo:ConcessionEstimate -> epo:MonetaryValue [0..1]epo-cat:PostAwardDocument -> at-voc-new:document-type [0..1]
    epo:hasConfirmedIrregularityTypeAdditional information: - This relation corresponds in eForms to BT-791 Review Irregularity Typeepo:ReviewDecision -> at-voc:irregularity-type [0..*]epo-cat:hasExpectedDeliveryTimeThe expected amount of time between the order and delivery of an item. + + WG approval 26/07/2022 + epo-cat:Price -> epo:Duration [0..1]
    epo:hasConstraint cccev:InformationRequirement -> cccev:Constraint [0..*]
    epo:ProcurementCriterion -> cccev:Constraint [0..*]
    		epo-cat:hasExternalSpecificationURI reference to external item information or specifications, e.g. web address. + epo-cat:Item -> epo:Document []
    epo:hasContactPointInRoleepo:AgentInRole -> cpov:ContactPoint [0..*]epo-cat:hasHazardousItemUNDGCodeSpecification of the hazardous nature of an item according to the UNDG classification + schema. Provides detail of the classification and nature of a hazardous item. + epo-cat:Item -> at-voc-new:dangerous-goods-list [0..*]
    epo:hasContractNatureTypeSubject of the acquisition. + epo-cat:hasItemClassificationA classification of this item according to a specific system for classifying products + or services. - WG Approval 11/06/2020 + Additional information: + Examples of classification schemes are: CPV, UNSPC, eCl@ss, GPC, ... - epo:ContractTerm -> at-voc:contract-nature [0..1]epo-cat:Item -> at-voc-new:item-classification [0..*]
    epo:hasContractValueepo:Contract -> epo:MonetaryValue [0..1]epo-cat:hasManufacturerThe product maker or service provider.epo-cat:Item -> epo-cat:Manufacturer [0..1]
    epo:hasCountryCode + epo-cat:hasMaximumOrderQuantityThe maximum number of orderable units that can be ordered according to details provided + in the catalogue line, such as price. dct:Location -> at-voc:country [0..1]
    locn:Address -> at-voc:country [0..1]
    		epo-cat:CatalogueLine -> epo:Quantity [0..1]
    epo:hasCountryOfBirthThe country in which the Person was born. + epo-cat:hasMinimumQuantityGuaranteedForDeliveryThe minimum quantity of an item that is guaranteed by the seller to be delivered. + person:Person -> at-voc:country [0..1]epo-cat:CatalogueLine -> epo:Quantity [0..1]
    epo:hasCurrencyThe identifier of the currency as in the standard code list used. - - epo:MonetaryValue -> at-voc:currency [0..1]epo-cat:hasModelepo-cat:Item -> epo-cat:ItemModel [0..1]
    epo:hasDirectAwardJustificationList of reasons for using a procedure which allows awarding contracts directly without - publishing a notice. - - WG Approval 28/05/2020 + epo-cat:hasNetMonetaryValueThe price amount of an Item exclusive of taxes and after substracting price discounts. epo:DirectAwardTerm -> at-voc:direct-award-justification [0..1]epo-cat:Price -> epo:MonetaryValue [1]
    epo:hasDocumentRestrictionJustificationAn 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-cat:hasNetQuantityThe net quantity of the item that is contained in each consumable unit, excluding + any packaging materials. epo:AccessTerm -> at-voc:communication-justification [0..1]epo-cat:Item -> epo:Quantity [0..1]
    epo:hasDPSScopeExplanation as to whether a dps is used and by whom. + epo-cat:hasOrderabableUnitFactorRateThe factor by which the base unit of the price can be converted to orderable unit. - Additional Information: - This corresponds in eForms to BT-766 Dynamic Purchasing System. - WG Approval 09/11/2021 - Explanation as to whether a dps is used and by whom. - WG Approval 09/11/2021 + Additional information: + This is needed when the base price is provided different than the orderable unit. + For example, when selling paper, the price may be set per page, but the orderable + unit is a package of 500 pieces. Therefore the price needs to be converted to the + orderable unit. - The codelist to be used is at-voc:dps-usage which is available at http://publications.europa.eu/resource/dataset/dps-usageepo:DynamicPurchaseSystemTechnique -> at-voc:dps-usage [0..1]epo-cat:Price -> epo:Quantity [0..1]
    epo:hasECataloguePermissionThe extent to which electronic catalogues may be used in tenders. - - WG Approval 03/10/2019 - epo:SubmissionTerm -> at-voc:permission [0..1]epo-cat:hasOrderableUnitThe unit in which the item described in this catalogue line can be ordered.epo-cat:CatalogueLine -> at-voc-new:orderable-unit [0..1]
    epo:hasEInvoicingPermissionepo:ContractTerm -> at-voc:permission [0..1]epo-cat:hasPrice epo-ord:OrderLine -> epo-cat:Price [0..1]
    epo-cat:CatalogueLine -> epo-cat:Price [1..*]
    epo:hasElectronicDigestepo-cat:hasPriceType epo:Document -> epo:Document [0..*]epo-cat:Price -> at-voc-new:price-type [0..1]
    epo:hasElectronicSignatureepo:Document -> epo:ElectronicSignature [0..*]epo-cat:hasPriceValidityThe period of time when the Item can be ordered to the given price. + epo-cat:Price -> epo:Period [1]
    epo:hasEndpointIdentifierepo-cat:hasQualifiedItemRelation cv:Channel -> adms:Identifier [0..*]epo-cat:Item -> epo-cat:ItemRelation [0..*]
    epo:hasEstimatedBuyerConcessionRevenueThe 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. + epo-cat:hasQualifiedValueQualified value of the property, which is defined in a classification scheme. - This corresponds to BT-160 in eForms. + Additional Information: + For example, the (0173-1#02-AAA026#007) drilling diameter of an item has value of + 12 inches. - WG Approval 07/01/2020epo:ConcessionEstimate -> epo:MonetaryValue [0..1]epo-cat:ItemProperty -> epo:Quantity [0..1]
    epo:hasEstimatedDurationRelation 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-cat:hasQuantity epo-ord:OrderLine -> epo:Quantity [1]
    epo-con:Deliverable -> epo:Quantity [0..1]
    epo:hasEstimatedUserConcessionRevenueThe 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-cat:hasQuantityThresholdThe minimum quantity of the item that can be ordered to the given net monetary value.epo-cat:Price -> epo:Quantity [0..1]
    epo:hasEstimatedValueA 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>WG Approval 05/12/2019 - A forecast of the value of the procurement before competition. + epo-cat:hasSpecificationepo-cat:Item -> epo-cat:ProductSpecification [0..*]
    epo-cat:hasStandardisedUnitPriceThe item price based on a standardised unit. 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> - - epo:LotGroup -> epo:MonetaryValue [0..1]
    epo:ProcurementElement -> epo:MonetaryValue [0..1]
    		epo-cat:CatalogueLine -> epo-cat:Price [0..*]
    epo:hasESubmissionPermissionThe requirements as to what extent electronic submission is allowed. - - WG Approval 03/10/2019 - - epo:SubmissionTerm -> at-voc:permission [0..1]epo-cat:hasTaxCategoryepo-ord:TaxInformation -> at-voc-new:tax-category [0..1]
    epo:hasFinancialOfferValueThe 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-cat:hasTaxSchemeepo-ord:TaxInformation -> at-voc-new:tax-scheme [0..1]
    epo:hasFixedValueTypeThe method to interpret the fixed value as pertaining to a total or unit. - - WG Approval 17/09/2019 - + epo-cat:hasTransactionConditionsCodeCoded description of the specific transaction conditions (purchasing, sales, payment) + for an item. epo:AwardCriterion -> at-voc:number-fixed [0..1]epo-cat:CatalogueLine -> at-voc-new:transaction-conditions [0..1]
    epo-cat:isProductionOfepo-cat:Batch -> epo-cat:Item [1]
    epo-cat:isRelatedToItemepo-cat:ItemRelation -> epo-cat:Item [1]
    epo:hasFormTypeA categorisation of the steps in which the Notice is used. - - WG Approval 12/05/2020 - - epo:Notice -> at-voc:form-type [0..1]epo-cat:isSpecificToCatalogueResponseLineepo-cat:CatalogueResponseInformation -> epo-cat:CatalogueResponseLine [0..1]
    epo:hasFrameworkAgreementMaximumValueepo-cat:isSpecificToLine epo:LotAwardOutcome -> epo:MonetaryValue [0..1]epo-cat:InformationHub -> epo-cat:Line [0..*]
    epo:hasFrameworkAgreementTypeThe 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 - - epo:FrameworkAgreementTerm -> at-voc:framework-agreement [1]epo-cat:isSubordinatedToContractepo-cat:Catalogue -> epo:Contract [0..1]
    epo:hasFundProgrammeepo-cat:refersToCatalogue epo:Fund -> at-voc:EU-programme [0..1]epo-cat:CatalogueResponse -> epo-cat:Catalogue [1]
    epo:hasGroupFrameworkAgreementMaximumValueThis corresponds to BT-156 in the eForms.epo:LotGroupAwardInformation -> epo:MonetaryValue [0..1]epo-cat:refersToCatalogueLineepo-cat:CatalogueResponseLine -> epo-cat:CatalogueLine [1]
    epo:hasHighestReceivedTenderValueAmount 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-cat:specifiesCatalogueResponseInformationepo-cat:CatalogueResponse -> epo-cat:CatalogueResponseInformation [1]
    epo:hasInternalIdentifier epo:LotGroup -> adms:Identifier [0..*]
    epo:ProcurementElement -> adms:Identifier [0..*]
    		epo-cat:specifiesChargeInformationepo-ord:Order -> epo-cat:ChargeInformation [0..*]
    epo:hasIrregularityTypeAdditional information: - This relation corresponds in eForms to BT-636 Buyer Review Requests Irregularity - Typeepo:ReviewIrregularitySummary -> at-voc:irregularity-type [1]epo-cat:specifiesItemepo-cat:Line -> epo-cat:Item [1]
    epo:hasItemCountryOfOriginThe 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/countryepo:Tender -> at-voc:country [0..*]epo-ful:agreedByBuyerepo-ful:ShipmentAgreement -> epo:Buyer [1..*]
    epo:hasLabelTypeThe label type such environmental, quality, social etc.epo:CertificationLabel -> at-voc-new:certification-label-type [0..1]epo-ful:agreedBySellerepo-ful:ShipmentAgreement -> epo-ord:Seller [1..*]
    epo:hasLanguageLanguage in which the submitted information is to be expressed. - - WG Approval 21/07/2020 - - epo:SubmissionTerm -> at-voc:language [0..*]epo-ful:comprisesDespatchLineepo-ful:DespatchAdvice -> epo-ful:DespatchLine [1..*]
    epo:hasLateSubmissionPermissionWhether 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 - epo:SubmissionTerm -> at-voc:missing-info-submission [0..1]epo-ful:comprisesReceiptAdviceLineepo-ful:ReceiptAdvice -> epo-ful:ReceiptAdviceLine [0..*]
    epo:hasLaunchFrameworkAgreementMaximumValue epo:ProcurementObject -> epo:MonetaryValue [0..1]
    epo:LotGroup -> epo:MonetaryValue [0..1]
    		epo-ful:containsGoodsItemepo-ful:Package -> epo-ful:GoodsItem [1..*]
    epo:hasLegalBasisThe legal basis under which the procurement procedure takes place. - - Additional Information: - For example European Directives or Regulations, national laws etc. - The recommended code list is the example for the legal basis at the European level. - - WG 04/04/2023 - - The legal basis under which the procurement procedure takes place. - - Additional Information: - For example European Directives or Regulations, national law - - WG 09/11/2021 + epo-ful:containsPackageepo-ful:Package -> epo-ful:Package [0..*]
    epo-ful:containsTransportHandlingUnitepo-ful:Consignment -> epo-ful:TransportHandlingUnit [1..*]
    epo-ful:hasAllowanceChargeReasonhttps://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL5189/ - The codelist to be used is at-voc:legal-basis which is available at http://publications.europa.eu/resource/dataset/legal-basis - epo:ProcurementObject -> at-voc:legal-basis [0..*]epo-ord:AllowanceChargeInformation -> at-voc-new:allowance-charge-reason [0..1]
    epo:hasLegalIdentifierepo-ful:hasAssociatedDocument epo-ful:ReceiptAdvice -> epo:Document [0..1]
    epo-ful:DespatchAdvice -> epo:Document [0..1]
    epo-ful:DespatchLine -> epo:Document [0..1]
    epo-ful:hasCarrierConsignmentID org:Organization -> adms:Identifier [0..*]epo-ful:Consignment -> adms:Identifier [0..1]
    epo:hasLotReferenceepo-ful:hasChargeableWeight epo:Contract -> epo:Lot [1..*]epo-ful:Consignment -> epo:Quantity [0..1]
    epo:hasLowestReceivedTenderValueAmount 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-ful:hasConsigneeConsignmentIDepo-ful:Consignment -> adms:Identifier [0..1]
    epo:hasMainActivityThe 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 - - org:Organization -> at-voc:main-activity [0..1]epo-ful:hasConsignmentDeclaredStatisticsValueepo-ful:Consignment -> epo:MonetaryValue [0..1]
    epo:hasMainClassificationepo-ful:hasConsignmentFreeOnBoardValue epo:Purpose -> at-voc:cpv [1..*]epo-ful:Consignment -> epo:MonetaryValue [0..1]
    epo:hasMaximumFrameworkAgreementAwardedValueThe maximum value which can be spent through all the framework agreements announced - in this notice, including options and renewals of contracts. + epo-ful:hasConsignmentInvoiceValueDeclared amount of the Consignment. - 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. + Additional Information: - WG Approval 03/12/2019epo:NoticeAwardInformation -> epo:MonetaryValue [0..1]epo-ful:Consignment -> epo:MonetaryValue [0..1]
    epo:hasMemberepo-ful:hasDeclaredStatisticalValue epo:OrganisationGroup -> org:Organization [1..*]epo-ful:GoodsItem -> epo:MonetaryValue [0..*]
    epo:hasNationality - person:Person -> at-voc:country [0..*]epo-ful:hasDepartureShipmentInformationepo-ful:ShipmentStage -> epo-ful:ShipmentInformation [0..*]
    epo:hasNonAwardJustificationOn hold; Enumeration. - - + epo-ful:hasDespatchAdviceTypehttps://test-docs.peppol.eu/logistics/transport-execution/codelist/DespatchAdviceTypeCode/ epo:AwardOutcome -> at-voc:non-award-justification [0..1]epo-ful:DespatchAdvice -> at-voc-new:despatch-advice-type [0..1]
    epo:hasNonElectronicSubmissionJustification - Reason for not accepting electronic information. - - WG Approval 21/07/2020 - epo:SubmissionTerm -> at-voc:communication-justification [0..*]epo-ful:hasDespatchedQuantityQuantity despatched for delivered.epo-ful:DespatchLine -> epo:Quantity [1]
    epo:hasNonPublicationJustificationThe reason why data is not published. - WG Approval 11/06/2020 - epo:NonPublishedInformation -> at-voc:non-publication-justification [1]epo-ful:hasEstimatedDeliveryPeriodepo-ful:ShipmentInformation -> epo:Period [0..1]
    epo:hasNoticeTypeepo-ful:hasFreightAllowanceCharge epo:Notice -> at-voc:notice-type [1]epo-ful:Consignment -> epo-cat:ChargeInformation [0..*]
    epo:hasNutsCodeepo-ful:hasFreightForwarderConsignmentIDepo-ful:Consignment -> adms:Identifier [0..1]
    epo-ful:hasGrossVolume dct:Location -> at-voc:nuts [0..1]
    locn:Address -> at-voc:nuts [0..1]
    		epo-ful:AbstractContainer -> epo:Quantity [0..1]
    epo-ful:Consignment -> epo:Quantity [0..1]
    epo:hasOfficialLanguageThe 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 - - epo:Document -> at-voc:language [1..*]epo-ful:hasGrossWeight epo-ful:AbstractContainer -> epo:Quantity [0..1]
    epo-ful:Consignment -> epo:Quantity [0..1]
    epo:hasPerformingStaffQualificationInformation - Additional information: - - This relation corresponds in eForms to BT-79.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:ProcurementCriterion -> at-voc:requirement-stage [0..*]epo-ful:hasHandlingInstructionCode epo-ful:Consignment -> at-voc-new:handling-instruction [0..1]
    epo-ful:TransportHandlingUnit -> at-voc-new:handling-instruction [0..1]
    epo:hasPlannedDurationepo-ful:hasHeight epo:PlannedProcurementPart -> epo:Duration [0..1]epo-ful:AbstractContainer -> epo:Quantity [0..1]
    epo:hasPlannedPeriodepo-ful:hasLength epo:PlannedProcurementPart -> epo:Period [0..1]epo-ful:AbstractContainer -> epo:Quantity [0..1]
    epo:hasPrimaryContactPointepo-ful:hasLoadingLength org:Organization -> cpov:ContactPoint [0..1]epo-ful:Consignment -> epo:Quantity [0..1]
    epo:hasPrizeValueThe 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-ful:hasMainCarriageShipmentStageepo-ful:Consignment -> epo-ful:ShipmentStage [0..1]
    epo:hasProcedureTypeIdentification of the Procedure used. - - WG Approval 09/06/2020 - epo:Procedure -> at-voc:procurement-procedure-type [1]epo-ful:hasMaximumTemperatureepo-ful:TemperatureSpecification -> epo:Quantity [0..1]
    epo:hasProcurementHighestReceivedTenderValueThe 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-ful:hasMinimumTemperatureepo-ful:TemperatureSpecification -> epo:Quantity [0..1]
    epo:hasProcurementLowestReceivedTenderValueThe 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-ful:hasNetVolumeepo-ful:AbstractContainer -> epo:Quantity [0..1]
    epo:hasProcurementScopeDividedIntoLotepo-ful:hasNetWeight epo-ful:AbstractContainer -> epo:Quantity [0..1]
    epo-ful:Consignment -> epo:Quantity [0..1]
    epo-ful:hasOnCarriageShipmentStage epo:Procedure -> epo:Lot [1..*]epo-ful:Consignment -> epo-ful:ShipmentStage [0..*]
    epo:hasPurpose Relation indicating the Purpose of a concept.epo:Contract -> epo:Purpose [0..1]
    epo:ProcurementObject -> epo:Purpose [0..1]
    		epo-ful:hasOutstandingQuantityepo-ful:DespatchLine -> epo:Quantity [0..1]
    epo:hasQualificationSystemDurationepo-ful:hasOversupplyQuantity epo:MultipleStageProcedureTerm -> epo:Duration [0..1]epo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
    epo:hasReceivedSubmissionTypeepo-ful:hasPackagingType epo:SubmissionStatisticalInformation -> at-voc:received-submission-type [0..1]epo-ful:Package -> at-voc-new:packaging-type [0..1]
    epo:hasRegistrationCountryepo-ful:hasPreCarriageShipmentStage org:Organization -> at-voc:country [0..1]epo-ful:Consignment -> epo-ful:ShipmentStage [0..*]
    epo:hasRemedyValueAdditional information: - This relation corresponds in eForms to BT-793 Review Remedy Value.epo:ReviewDecision -> epo:MonetaryValue [0..1]epo-ful:hasReceivedQuantityepo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
    epo:hasReservedExecutionepo-ful:hasRejectReason epo:ContractTerm -> at-voc:applicability [0..1]epo-ful:ReceiptAdviceLine -> at-voc-new:reject-reason [0..1]
    epo:hasReservedProcurementExplanation as to whether a procurement may be reserved for the participation of certain - types of organisation. - - Additional information: - This property corresponds in eForms to the BT-71 - WG Approval 09/11/2021 - Explanation as to whether a procurement may be reserved for the participation of certain - types of organisation. - - Additional information: - This property corresponds in eForms to the BT-71 - WG Approval 09/11/2021 - epo:ParticipationCondition -> at-voc:reserved-procurement [0..*]
    epo:ParticipationConditionsSummary -> at-voc:reserved-procurement [0..*]
    		epo-ful:hasRequestedPickUpInformationepo-ful:Consignment -> epo-ful:ShipmentInformation [1]
    epo:hasReviewBodyTypeepo-ful:hasShortageAction epo:Reviewer -> at-voc:review-body-type [0..*]epo-ful:ReceiptAdviceLine -> at-voc-new:action-code [0..1]
    epo:hasReviewDecisionTypeAdditional information: - This relation corresponds in eForms to BT-790 Review Decision Type.epo:ReviewDecision -> at-voc:review-decision-type [0..*]epo-ful:hasShortQuantityepo-ful:ReceiptAdviceLine -> epo:Quantity [0..1]
    epo:hasReviewIrregularitySummaryAdditional information: - This relation corresponds in eForms to BG-613 Buyer Review Requestsepo:ReviewRequestSummary -> epo:ReviewIrregularitySummary [0..*]epo-ful:hasSizeTypeepo-ful:TransportEquipment -> at-voc-new:size-type [0..*]
    epo:hasReviewRequestFeeAdditional information: - This relation corresponds in eForms to BT-795 Review Request Fee.epo:ReviewRequest -> epo:MonetaryValue [0..1]epo-ful:hasTemperatureSpecificationepo-ful:AbstractContainer -> epo-ful:TemperatureSpecification [0..1]
    epo:hasSelectionCriteriaUsage - Additional Information: - This corresponds in eForms to BT-748 Selection Criteria Used.epo:SelectionCriterion -> at-voc:usage [0..1]epo-ful:hasTotalGoodsItemQuantity epo-ful:AbstractContainer -> epo:Quantity [0..1]
    epo-ful:Consignment -> epo:Quantity [0..1]
    epo:hasSelectionCriterionTypeThe classification of the selection criteria. + epo-ful:hasTraceIDThe identifier used for tracking the goods item + Additional information: + An example is the EPC number used in RFID. - Additional Information: - - This corresponds in eForms to BT-747 Selection Criteria Type. - - WG Approval 09/11/2021 + WG approval 21/09/2023 epo:SelectionCriterion -> at-voc:selection-criterion [0..1]epo-ful:GoodsItem -> adms:Identifier [0..1]
    epo:hasStartDateepo-ful:hasTrackingID epo:SelectedCandidateList -> epo:Period [0..1]epo-ord:DeliveryInformation -> adms:Identifier [0..1]
    epo:hasSubcontractingepo-ful:hasTransportEquipmentSeal epo:Tender -> at-voc:applicability [0..1]epo-ful:TransportEquipment -> epo-ful:TransportEquipmentSeal [0..*]
    epo:hasSubcontractingEstimatedValueThe 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-ful:hasTransportEquipmentTypeepo-ful:TransportEquipment -> at-voc-new:transport-equipment-type [0..*]
    epo:hasSubcontractingObligationThe requirement the tender must meet with regard to subcontracting parts of the contract. - WG Approval 09/11/2021 - - epo:SubcontractTerm -> at-voc:subcontracting-obligation [0..*]epo-ful:hasTransportHandlingUnitQuantityepo-ful:Consignment -> epo:Quantity [0..1]
    epo:hasTaxIdentifierepo-ful:hasTransportMeansType org:Organization -> adms:Identifier [0..*]epo-ful:TransportMeans -> at-voc-new:transport-means-type [0..1]
    epo:hasTenderSubcontractingInformationThe information about subcontracting that must be indicated in the tender. - - WG Approval 10/10/2019 - - epo:SubmissionTerm -> at-voc:subcontracting-indication [0..*]epo-ful:hasTransportModeepo-ful:TransportMeans -> at-voc-new:transport-mode [1]
    epo:hasTenderValidityDurationepo-ful:hasVehicleID epo:SubmissionTerm -> epo:Duration [0..1]epo-ful:TransportMeans -> adms:Identifier [1]
    epo:hasTenderValidityPeriodThe relation indicating until when a tender instance is applicable. - epo:SubmissionTerm -> epo:Period [0..1]epo-ful:hasVehicleSegmentIDepo-ful:TransportMeans -> adms:Identifier [0..1]
    epo:hasThresholdTypeThe method to interpret the threshold value as minimum or a maximum. - - WG Approval 17/09/2019 - cccev:Constraint -> at-voc:number-threshold [0..*]epo-ful:hasWidthepo-ful:AbstractContainer -> epo:Quantity [0..1]
    epo:hasTimePeriod - - epo:Period -> at-voc:timeperiod [1..*]epo-ful:isSpecificToDespatchLineepo-ful:ShipmentInformation -> epo-ful:DespatchLine [0..1]
    epo:hasTotalAwardedValueThe 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-ful:isSubmittedForDespatchAdviceAdditional information: + In PEPPOL (https://test-docs.peppol.eu/logistics/qa/codelist/ReceiptAdviceTypeCode/) + this predicate is used for option D - Response to the Advanced Despatch Advice document.epo-ful:ReceiptAdvice -> epo-ful:DespatchAdvice [0..1]
    epo:hasTotalQuantityThe number of units required. - - Additional Information: - The quantity needs to go along with the unit. - - - - epo:Purpose -> epo:Quantity [0..1]epo-ful:isSubmittedForDespatchLineepo-ful:ReceiptAdviceLine -> epo-ful:DespatchLine [1]
    epo:hasTotalValue epo:TenderGroup -> epo:MonetaryValue [0..1]

    		epo-ful:isSubmittedForShipmentepo-ful:ReceiptAdvice -> epo-ful:ShipmentInformation [0..1]
    epo:hasUnitCodeepo-ful:refersToConsignment epo:Quantity -> at-voc:measurement-unit [1]epo-ful:DespatchAdvice -> epo-ful:Consignment [1]
    epo:hasUnofficialLanguageThe 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 - epo:Document -> at-voc:language [0..*]epo-ful:refersToDeliveryInformationepo-ful:ShipmentInformation -> epo-ord:DeliveryInformation [1]
    epo:hasUsageThe codelist to be used is at-voc:usage which is available at http://publications.europa.eu/resource/dataset/usage - epo:Technique -> at-voc:usage [0..1]epo-ful:refersToDespatchLineepo-ful:GoodsItem -> epo-ful:DespatchLine [1]
    epo:hasUUIDA universally unique identifier for an instance of this document. - - WG Approval 12/05/2020 A universally unique identifier for an instance of this document. - - WG Approval 12/05/2020 - epo:Document -> adms:Identifier [0..1]

    		epo-ful:refersToOrderepo-ful:DespatchAdvice -> epo-ord:Order [0..1]
    epo:hasValidityPeriodThe relation indicating until when a given instance of a concept is applicable. - - WG approval 30/05/2023 The relation indicating until when a given instance of a concept is applicable. - - WG approval 30/05/2023 - The relation indicating until when a given instance of a concept is applicable. - - WG approval 30/05/2023cccev:Evidence -> epo:Period [0..1]
    epo:Technique -> epo:Period [0..1]

    		epo-ful:refersToOrderLineepo-ful:DespatchLine -> epo-ord:OrderLine [0..1]
    epo:hasVariantPermissionThe 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. - epo:SubmissionTerm -> at-voc:permission [0..1]epo-ful:refersToShipmentAgreementepo-ful:DespatchAdvice -> epo-ful:ShipmentAgreement [0..1]
    epo:hasWeightValueTypeNo definition. Waiting on CCCEV alignment. - - - epo:ProcurementCriterion -> at-voc:number-weight [0..1]epo-ful:RejectionActionepo-ful:ReceiptAdviceLine -> at-voc-new:action-code [0..1]
    epo:includesAccessibilityCriterionExplanation as to whether accessibility Criterion are used or not. - WG Approval 09/11/2021 - - epo:StrategicProcurement -> at-voc:accessibility [0..*]epo-ful:specifiesBuyerepo-ful:ReceiptAdvice -> epo:Buyer [0..1]
    epo:includesNationalCriterionRelation indicating that a Criterion contains a Criterion that is specific to a given - Member State. - - Additional Information: - In the ESPD, a Subcriterion is used to define national sub-criteria; maps to a UBL-2.3 - cac:SubTenderingCriterion class. It is currently used only for purely national criteria, - to be able to establish the mapping from eCertis. - - WG approval 07/11/2023 - - epo:QualificationCriterion -> epo:QualificationCriterion [0..*]epo-ful:specifiesConsignee epo-ful:DespatchAdvice -> epo-ord:Consignee [1..*]
    epo-ful:ReceiptAdvice -> epo-ord:Consignee [1..*]
    epo:includesTenderAdditional information: - This corresponds in eForms to BT-3202 Contract Tender Identifier. - epo:Contract -> epo:Tender [0..*]epo-ful:specifiesDespatcher epo-ful:DespatchAdvice -> epo-ful:Despatcher [1..*]
    epo-ful:ReceiptAdvice -> epo-ful:Despatcher [1]
    epo:indicatesAwardToWinnerReveals the winner to whom the tender award outcome is attributed.epo:TenderAwardOutcome -> epo:Winner [0..1]epo-ful:specifiesOriginatorepo-ful:DespatchAdvice -> epo-ord:Originator [0..*]
    epo-ful:specifiesPlaceOfDespatchepo-ful:ShipmentInformation -> dct:Location [0..1]
    epo-ful:specifiesSellerepo-ful:ReceiptAdvice -> epo-ord:Seller [0..1]
    epo:indicatesInvoiceeContactPointepo-ful:specifiesShipment epo:Buyer -> cpov:ContactPoint []epo-ful:DespatchAdvice -> epo-ful:ShipmentInformation [0..1]
    epo:involvesBuyerepo-ful:specifiesTransportHandlingUnits epo:Procedure -> epo:Buyer [0..*]epo-ful:DespatchAdvice -> epo-ful:TransportHandlingUnit [0..*]
    epo:involvesProcurementDocumentepo-ful:transportsItemFrom epo:AccessTerm -> epo:ProcurementDocument [0..1]epo-ful:TransportHandlingUnit -> epo-ful:DespatchLine [1..*]
    epo:isBasedOnImplementingRegulationIndicates under which regulation a notice is created. - - WG Acceptance 06/09/2022epo:Notice -> at-voc:legal-basis [0..1]epo-ful:usesTransportEquipmentepo-ful:TransportHandlingUnit -> epo-ful:TransportEquipment [0..*]
    epo:isBeneficialOwnerOfA 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/2021epo:Business [,0..*] <- person:Personepo-ful:usesTransportMeansepo-ful:ShipmentStage -> epo-ful:TransportMeans [1..*]
    epo:isExecutedByProcurementServiceProviderepo-not:announcesRole epo:Procedure -> epo:ProcurementServiceProvider [0..1]epo-not:ResultNotice -> epo:AgentInRole [0..*]
    epo:isFundedByFunding is provided either completely or partially by a Fund. - - 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. - - Funding is provided either completely or partially by a Fund. - - 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:Contract -> epo:Fund [0..*]
    epo:ProcurementObject -> epo:Fund [0..*]
    		epo-not:hasLegalBasisepo-not:Modification-D24 -> Directive 24 [0..1]
    epo:isOwnedByAgentepo-not:refersToRole epo:System -> foaf:Agent [0..1]epo-not:ResultNotice -> epo:AgentInRole [1..*]
    epo:isResponsibilityOfBuyerThe 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-ord:comprisesOrderLineepo-ord:Order -> epo-ord:OrderLine [1..*]
    epo:isSubjectToContractSpecificTermepo-ord:comprisesOrderResponseLine epo:Contract -> epo:ContractSpecificTerm [0..*]epo-ord:OrderResponse -> epo-ord:OrderResponseLine [0..*]
    epo:isSubjectToGroupingepo-ord:concernsConsignee epo:Tender -> epo:LotGroup [0..1]epo-ord:DeliveryInformation -> epo-ord:Consignee [0..1]
    epo:isSubjectToLotSpecificTermepo-ord:concernsContract epo:Lot -> epo:LotSpecificTerm [0..*]epo-ord:ContractInformation -> epo:Contract [1]
    epo:isSubjectToProcedureSpecificTermepo-ord:concernsOriginator epo:Procedure -> epo:ProcedureSpecificTerm [1..*]epo-ord:OriginatorInformation -> epo-ord:Originator [1]
    epo:isSubjectToTermepo-ord:concernsOriginatorRequest epo:ProcurementObject -> epo:Term [0..*]epo-ord:OriginatorInformation -> epo:OriginatorRequest [0..1]
    epo:isSubmitedByRelation indicating the submission of a tender by an economic operator. - WG approval 18/05/2021epo:Tender -> epo:Tenderer [0..1]epo-ord:hasAcceptanceStatus epo-cat:CatalogueResponseInformation -> at-voc-new:ResponseStatus [1]
    epo-ord:OrderResponseInformation -> at-voc-new:ResponseStatus [1]
    epo:isSubmittedForLotepo-ord:hasAmountDueForPayment epo:Tender -> epo:Lot [1]epo-ord:Order -> epo:MonetaryValue [1]
    epo:isSubmittedForLotGroupepo-ord:hasDeliveryPeriod epo-ord:OrderResponseInformation -> epo:Period [0..1]
    epo-ord:DeliveryInformation -> epo:Period [0..1]
    epo-ord:hasPrepaidAmount epo:TenderGroup -> epo:LotGroup [1]epo-ord:Order -> epo:MonetaryValue [0..1]
    epo:issuedByCertifierRelation indicating the Certifier responsible for providing the ItemCertificate. - - Additional Information: - Certifier is a role played by an organisation. - - WG approval 26/07/2022epo:Certificate -> epo:Certifier [0..1]epo-ord:hasPriceDiscountInformationepo-cat:Price -> epo-ord:AllowanceInformation [0..1]
    epo:leadByThe epo:OrganisationGroup epo:leadBy org:Organization was implemented to be used in - case of an Economic Operator Group.epo:OrganisationGroup -> org:Organization [0..1]epo-ord:hasRoundingAmountepo-ord:Order -> epo:MonetaryValue [0..1]
    epo:needsToBeATendererThe Winner must be a Tenderer.epo:Winner -> epo:Tenderer [0..1]epo-ord:hasSellerOrderIDepo-ord:Order -> adms:Identifier [0..1]
    epo:needsToBeAWinnerThe Contractor must be a Winner. - epo:Contractor -> epo:Winner [0..1]epo-ord:hasTaxInformation epo:Contract -> epo-ord:TaxInformation [0..1]
    epo-cat:Item -> epo-ord:TaxInformation [0..*]
    epo-ord:AllowanceChargeInformation -> epo-ord:TaxInformation [0..1]
    epo:ownsSystemepo-ord:hasTotalAllowanceAmount epo:System [,0..*] <- foaf:Agentepo-ord:Order -> epo:MonetaryValue [0..1]
    epo:playedBy epo:AgentInRole -> foaf:Agent [1]
    epo:JuryMember -> person:Person [0..1]

    		epo-ord:hasTotalChargeAmountepo-ord:Order -> epo:MonetaryValue [0..1]
    epo:providesContractTotalPaymentValueAdditional Information: - This corresponds to BT-779 in eForms. epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1]epo-ord:hasTotalLineAmountepo-ord:Order -> epo:MonetaryValue [1]
    epo:providesContractTotalPenaltyValue - Additional Information: - This corresponds to BT-782 in eForms. - epo:ContractLotCompletionInformation -> epo:MonetaryValue [0..1]epo-ord:hasTotalTaxExclusiveAmountepo-ord:Order -> epo:MonetaryValue [0..1]
    epo:providesRulingOnRemedyStates the measures to be taken after a review procedure.epo:ReviewDecision -> at-voc:remedy-type [0..*]epo-ord:hasTotalTaxInclusiveAmountepo-ord:Order -> epo:MonetaryValue [0..1]
    epo:refersToContractepo-ord:implementsContract epo:ContractLotCompletionInformation -> epo:Contract [1]epo-ord:OrderResponse -> epo:Contract [0..1]
    epo:refersToLot epo:Notice -> epo:Lot [1..*]



    		epo-ord:isSpecificToOrderLineInformation that is particular to one or multiple Order Lines. + Information that is particular to one or multiple Order Lines. + Information that is particular to one or multiple Order Lines. Information that is particular to one or multiple Order Lines. Information that is particular to one or multiple Order Lines. + epo-cat:ChargeInformation -> epo-ord:OrderLine [0..*]
    epo-ord:AllowanceInformation -> epo-ord:OrderLine [0..*]
    epo-ord:ContractInformation -> epo-ord:OrderLine [0..*]
    epo-ord:DeliveryInformation -> epo-ord:OrderLine [0..*]
    epo-ord:OriginatorInformation -> epo-ord:OrderLine [0..*]
    epo:refersToNoticeepo-ord:isSpecificToOrderResponseLine epo:Notice -> epo:Notice [0..1]epo-ord:OrderResponseInformation -> epo-ord:OrderResponseLine [0..*]
    epo:refersToPlannedPartepo-ord:isSubmittedForOrder epo:AccessTerm -> epo:PlannedProcurementPart [0..*]epo-ord:OrderResponse -> epo-ord:Order [1]
    epo:refersToPreviousepo-ord:isSubmittedForOrderLine epo:Document -> epo:Document [0..*]epo-ord:OrderResponseLine -> epo-ord:OrderLine [1..*]
    epo:refersToPreviousNoticeepo-ord:refersToCatalogue - Additional information: - This corresponds in eForms to BT-758 Change Notice Version Identifier.epo:ChangeInformation -> epo:Notice [1]epo-ord:Order -> epo-cat:Catalogue [0..*]
    epo:refersToPreviousProcedureReference to a previous procedure. - + epo-ord:refersToCatalogueLine 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 Identifierepo:DirectAwardTerm -> epo:Procedure [0..1]epo-ord:OrderLine -> epo-cat:CatalogueLine [0..1]
    epo:refersToPreviousProcedureLotReference 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:55epo:DirectAwardTerm -> epo:Lot [0..*]epo-ord:specifiesAllowanceInformationepo-ord:Order -> epo-ord:AllowanceInformation [0..*]
    epo:refersToPreviousReviewAdditional information: - This relation corresponds in eForms to BT-785 "Review Previous Identifier".epo:ReviewObject -> epo:ReviewObject [0..1]epo-ord:specifiesBuyerepo-ord:OrderResponse -> epo:Buyer [0..1]
    epo:refersToProcedure epo:Notice -> epo:Procedure [1]



    		epo-ord:specifiesContractInformation + epo-ord:Order -> epo-ord:ContractInformation [0..*]
    epo:relatesToEFormSectionIdentifier epo:ChangeInformation -> adms:Identifier [1..*]
    epo:NonPublishedInformation -> adms:Identifier [1..*]

    		epo-ord:specifiesDeliveryAgreementLocationepo-ord:DeliveryAgreement -> dct:Location [0..1]
    epo:requestsRemedyTypeAdditional information: - This relation corresponds in eForms to BT-792 Review Remedy Typeepo:ReviewRequest -> at-voc:remedy-type [0..*]epo-ord:specifiesDeliveryInformationepo-ord:Order -> epo-ord:DeliveryInformation [1..*]
    epo:resolvesReviewRequestepo-ord:specifiesGeneralDeliveryAgreement epo:ReviewDecision -> epo:ReviewRequest [1]epo-ord:DeliveryInformation -> epo-ord:DeliveryAgreement [0..1]
    epo:resultsFromLotAwardOutcome epo:DirectContract -> epo:LotAwardOutcome [0..*]
    epo:FrameworkAgreement -> epo:LotAwardOutcome [0..*]
    		epo-ord:specifiesOrderResponseInformationepo-ord:OrderResponse -> epo-ord:OrderResponseInformation [0..*]
    epo:resultsFromMiniCompetitionAwardOutcomeepo-ord:specifiesOriginatorInformation epo:PurchaseContract -> epo:MiniCompetitionAwardOutcome [0..1]epo-ord:Order -> epo-ord:OriginatorInformation [0..1]
    epo:resultsFromUsingCandidateListepo-ord:specifiesPlaceOfDelivery epo:MiniCompetitionAwardOutcome -> epo:SelectedCandidateList [0..1]epo-ord:DeliveryInformation -> dct:Location [0..1]
    epo:setsGroupingContextForLotepo-ord:specifiesSeller epo:LotGroup -> epo:Lot [1..*]epo-ord:OrderResponse -> epo-ord:Seller [0..1]
    epo:signedByBuyerepo-ord:specifiesSpecificDeliveryAgreement epo:Contract -> epo:Buyer [0..*]epo-ord:DeliveryInformation -> epo-ord:DeliveryAgreement [0..1]
    epo:signedByContractorepo:Contract -> epo:Contractor [0..*]epo-sub:answersQuestionRelation indicating that the Response replies to a question. + + WG approval 12/03/2024epo-sub:Response -> cccev:InformationRequirement [0..*]
    epo:signsAwardDecisionepo:Buyer -> epo:AwardDecision [0..*]epo-sub:concernsOrganisationRelates to Organization. + + WG approval 05/03/2024 + + epo-sub:NationalPreQualificationData -> org:Organization [1]
    epo:specifiesCleanVehicleDirectiveContractTypeepo:VehicleInformation -> at-voc:cvd-contract-type [0..1]epo-sub:hasMandateRelation indicating that a Legal Representative has a Mandate. + + WG approval 12/03/2024epo-sub:LegalRepresentative -> epo-sub:Mandate [0..*]
    epo:specifiesCleanVehicleDirectiveVehicleCategoryepo:VehicleInformation -> at-voc:vehicle-category [0..1]epo-sub:hasPowerOfAttorneyRelation indicating that a Legal Representative has a Power of Attorney. + + WG approval 12/03/2024epo-sub:LegalRepresentative -> epo-sub:PowerOfAttorney [0..1]
    epo:specifiesProcurementCriteriaSummaryepo:Procedure -> epo:ProcurementCriteriaSummary [0..*]epo-sub:isReinforcedByRelation indicating an Evidence that supports the Response. + + WG approval 12/03/2024epo-sub:Response -> cccev:Evidence [0..*]
    epo:specifiesProcurementCriterion
    epo:Lot -> epo:ProcurementCriterion [0..*]
    epo:LotGroup -> epo:ProcurementCriterion [0..*]
    		epo-sub:providesInformationOnOffers information about an instance of a concept. + + WG approval 05/03/2024epo-sub:ESPDResponse -> org:Organization [0..*]
    epo:specifiesSubcontractorsepo:Tender -> epo:Subcontractor [0..*]epo-sub:providesOrganisationEmployeeQuantityThe number of people hired by the Organization. + + WG approval 05/03/2024epo-sub:NationalPreQualificationData -> epo:Quantity [0..1]
    epo:substantiatesExclusionGroundepo:Tenderer -> epo:ExclusionGround [0..1]epo-sub:providesOrganisationFinancialCapabilityA monetary amount representing the financial capability of the Organization. + + Additional information: + Used to represent the general Turnover of the Organization (for statistical purposes). + + WG approval 05/03/2024epo-sub:NationalPreQualificationData -> epo:MonetaryValue [0..1]
    epo:summarisesInformationForAwardOutcomeRelates to submission for the given competition, either at Lot level or Mini-Competition - level. + epo-sub:providesOrganisationPreQualificationListingIdentifierThe identifier assigned to an economic operator in a national pre-qualification system + or official list. - WG approval 30/05/2023epo:SubmissionStatisticalInformation -> epo:AwardOutcome [1]epo-sub:NationalPreQualificationData -> adms:Identifier [0..*]
    epo:usesChannelepo:ProcurementElement -> cv:Channel [0..*]epo-sub:refersToApplicablePeriodRelation indicating the period to which the Response shall apply. + + WG approval 12/03/2024epo-sub:Response -> epo:Period [0..1]
    epo:usesTechniqueepo:ProcurementObject -> epo:Technique [0..*]epo-sub:refersToOtherESPDResponseReference to other European Single Procurement Document (ESPD) Response. + + WG approval 05/03/2024epo-sub:ESPDResponse -> epo-sub:ESPDResponse [0..*]
    epo-sub:relatesToESPDRequestIs about an European Single Procurement Document (ESPD) Request. + + WG approval 05/03/2024epo-sub:ESPDResponse -> epo-acc:ESPDRequest [1]
    epo-sub:specifiesResponseRelation indicating that an ESPD Response contains a Response. + + WG approval 12/03/2024epo-sub:ESPDResponse -> epo-sub:Response [1..*]
    epo-sub:summarisesInformationAboutCertificateRelation indicating the Certificate that the information refers to. + + WG approval 12/03/2024 epo-sub:CertificateInformation -> epo:Certificate [1]
    locn:address