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.
+
+
+
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-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 05/03/2024
+
+
+
+
Attributes (datatype properties) names and definitions
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 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..*]
+
+
+
eli:LegalExpression
+
dct:title
+
A name given to the resource.
+
rdfs:Literal [1..*]
+
+
+
eli:LegalExpression eli:LegalResource
+
eli:number
+
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. 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..*]
+
+
+
cccev:EvidenceTypeList
+
skos:prefLabel
+
The preferred lexical label for a resource, in a given language.
+
+ WG approval 30/05/2023
+
+
rdf:PlainLiteral [0..*]
+
+
+
+
Predicates (object properties) and definitions
+
+
+
+
Predicate name
+
Definition
+
Domain, Range and Cardinality
+
+
+
+
+
adms:identifier
+
Links a resource to an adms:Identifier class. Links a resource to an adms:Identifier class.
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.
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.
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.
An established standard to which the described resource conforms.
+
+ Additional Information:
+ Examples of characteristics could be the layout or the configuration of the Evidence.
Relates 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: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.
+ 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.
+
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.
+
+
+
+
\ No newline at end of file
diff --git a/glossary/eCatalogue_glossary.html b/glossary/eCatalogue_glossary.html
index 465b9f73..a71fc728 100644
--- a/glossary/eCatalogue_glossary.html
+++ b/glossary/eCatalogue_glossary.html
@@ -86,6 +86,18 @@
Class names and defi
+
+
epo-cat:CatalogueResponse
+
+
+
+
epo-cat:CatalogueResponseInformation
+
+
+
+
epo-cat:CatalogueResponseLine
+
+
epo-cat:ChargeInformation
Information about tax, fee or duty imposed.
@@ -523,8 +535,9 @@
Predicates (object p
epo:hasBuyerItemID
-
This refers to the identifier for the specific instance of the produced concept.
- 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 (external) [0..1]
@@ -542,13 +555,12 @@
Predicates (object p
epo:hasItemStandardID
-
The identifier for the instance of the concept based on a standard scheme.
+
The general identifier assigned to the concept based on a standard scheme.
Additional information:
- For example the GTIN scheme (Global Trade Item Number).
+ For example the GTIN scheme (Global Trade Item Number).
- WG Approval 24/02/2022
-
+ WG approval 16/05/2023
epo-cat:Item -> adms:Identifier (external) [0..*]
@@ -559,11 +571,9 @@
Predicates (object p
epo:hasManufacturerItemID
-
This refers to the general identifier for 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 (external) [0..1]
@@ -574,9 +584,9 @@
Predicates (object p
epo:hasSellerItemID
-
The general identifier for the concept as defined by the seller.
+
The general identifier assigned to the concept as defined by the Seller.
- WG Approval 16/05/2023
+ WG approval 16/05/2023
epo-cat:Item -> adms:Identifier (external) [0..1]
@@ -587,6 +597,21 @@
Predicates (object p
epo-cat:Item -> adms:Identifier (external) [0..1]
+
+
epo:hasUUID
+
A universally unique identifier for an instance of this document.
+
+ WG Approval 12/05/2020
+
Additional 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.
Proof that a Requirement is met.
+ Additional Information:
+ The class Evidence provides the means to support responses to Criteria or to a concrete
+ Information Requirement or to an Information Concept inside an Information Requirement.
+ The proof described by an Evidence can [1] verify a claim (i.e. is it true that John
+ is 25, yes/no), [2] prove a condition (i.e. is John 18+, yes/no), or [3] simply provide
+ data (i.e. the age of a person, namely 25). The proof can be given through documents
+ or extracts of base registries, independently from its structure, format or medium
+ 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.
+
Piece of information that the Evidence provides or the Requirement needs.
+
+ Additional Information:
+
+ The Information Concept class offers the ability to describe conceptually the Requirements
+ and provided facts in Evidences. In complementarity with the Supported Value class,
+ this is a (first) step towards facilitating the assessment of the requirements in
+ an automated way based on the Evidence provided.
+
+
+
cccev:InformationRequirement
+
Requested data that is to be proven by Evidence.
+
+ Additional Information:
+
+ Information Requirements are the most neutral kind of Requirements. They aim to request
+ information in any form, e.g. a person's date of birth or a company's turnover. They
+ represent requests for data that prove one or more facts of the real world in a formal
+ manner, or that leads to the source of such a proof. They can be understood as 'requests
+ for Evidences'. The response to an Information Requirement is an Evidence when the
+ issuer of the response is an authoritative source (e.g. a Civil Registry providing
+ data about a natural person for the provision of public service through the Single
+ Digital Gateway). In other cases, the responses might not be issued by an authoritative
+ source, but the issuer supports the responses with Evidences (or commits to support
+ them timely, e.g. a self-declaration or a declaration of oath). The Information Requirement
+ can require structured data or documents of any form. For structured data, the Requirement
+ can use 'Concepts' to specify the structure and type of the data expected in the response.
+ For both structured and unstructured data, the Information Requirement can indicate
+ the expected Type of Evidence, its format, source, and other properties related to
+ the Evidence.
cccev:Requirement
@@ -106,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
@@ -158,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.
@@ -232,10 +356,11 @@
Class names and defi
epo:Awarder
A Role of an Agent that signs the Award Decision.
- Additional Information:
+ Additional information:
BT-08 can be Awarding CBP; BG-03 is the Buyer. But Awarding CPB is not the same as
the Buyer; the organisations may differ for these roles. Having the Awarder Role allows
- us to specify which Organisation is involved in the Award Decision.
+ us to specify which Organisation is involved in the Award Decision.
+
epo:AwardEvaluationTerm
@@ -385,7 +510,7 @@
Class names and defi
The description has its own identity (+I) but is dependent (+D) on the concerned Entity.
- We say that ContextSpecificDescription *concerns* an Entity.
+ We say that ContextDescription *concerns* an Entity.
@@ -833,7 +958,7 @@
Class names and defi
epo:Period
A time interval or a Duration.
- (WG approval 28/04/2020)
+ WG approval 28/04/2020
@@ -1209,7 +1334,7 @@
Class names and defi
At tendering time, entities relied upon by the Economic Operators can be Subcontractors
or not.
- When modelling ESPD we well analyze whether we need or not a Role named "relied upon".
+ When modelling ESPD we will analyze whether we need or not a Role named "relied upon".
WG approval 05/08/2021
@@ -1253,6 +1378,13 @@
Class names and defi
epo:TechnicalAbilitySummary
+
+
epo:TechnicalSpecification
+
A set of documented Requirements applicable to the object of the Procurement.
+ Additional Information:
+ A specification often includes technical standards.
+ WG approval: 20/04/2021
+
epo:Technique
Method used for conducting Procurement Procedures.
@@ -1318,6 +1450,15 @@
Class names and defi
A Role of an Agent to whom a Lot is awarded.
WG approval 05/08/2021 (revised 26/10/2021)
+
+
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 05/03/2024
+
epo-cat:Batch
A production Lot in which the Item instances were produced.
@@ -1364,6 +1505,18 @@
Class names and defi
+
+
epo-cat:CatalogueResponse
+
+
+
+
epo-cat:CatalogueResponseInformation
+
+
+
+
epo-cat:CatalogueResponseLine
+
+
epo-cat:ChargeInformation
Information about tax, fee or duty imposed.
@@ -1602,6 +1755,14 @@
Class names and defi
epo-ful:Package
+
+
epo-ful:ReceiptAdvice
+
+
+
+
epo-ful:ReceiptAdviceLine
+
+
epo-ful:ShipmentAgreement
The Commercial Agreement between the Commercial Parties.
@@ -2228,6 +2389,52 @@
Class names and defi
WG approval 25/04/2023
+
+
epo-sub:CertificateInformation
+
Information about a Certificate.
+
+ WG approval 12/03/2024
+
+
+
epo-sub:ESPDResponse
+
A 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.
+
+ WG Approval 05/03/2024
+
+
+
epo-sub:LegalRepresentative
+
The Role of an Agent that can represent an Organization.
+
+ WG approval 05/03/2024
+
+
+
epo-sub:Mandate
+
An authorization to act as a representative of an Organization.
+
+ WG approval 05/03/2024
+
+
+
epo-sub:NationalPreQualificationData
+
Data that describe the distinctive features or characteristics that qualify an economic
+ operator to take part in a tendering process.
+
+ WG approval 05/03/2024
+
+
+
epo-sub:PowerOfAttorney
+
A legal document that grants someone the authority to make decisions on behalf of
+ an Organization.
+
+ WG approval 05/03/2024
+
+
+
epo-sub:Response
+
An answer given to a question that is part of an ESPD Request.
+
+ WG approval 12/03/2024
+
foaf:Agent
A Person, an Organisation, or a System that acts in Procurement or have the power
@@ -2334,6 +2541,12 @@
Attributes (datatype
be removed.
xsd:decimal [0..1]
+
+
cccev:SupportedValue
+
cccev:value
+
Value for the Information Concept that the Evidence supports.
An account of the resource.
@@ -2415,6 +2628,25 @@
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.
+
+ 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:
@@ -2521,6 +2753,20 @@
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.
+
+ 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:
@@ -2553,7 +2799,15 @@
A name given to the resource.
@@ -2594,7 +2848,7 @@
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.
@@ -2602,7 +2856,17 @@
Attributes (datatype
WG approval 30/05/2023 A name given to the resource.
WG approval 30/05/2023
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. 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.
Supplementary data about the instance of the concept.
@@ -2700,8 +2964,10 @@
Attributes (datatype
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
The unique identifier of the certificate.
WG approval 26/07/2022
-
rdf:PlainLiteral [1..1]
+
rdf:PlainLiteral [0..1]
epo:ChangeInformation
@@ -3681,7 +3947,7 @@
Attributes (datatype
epo:Notice
epo:hasOJSIssueNumber
-
rdf:PlainLiteral [0..1]
+
xsd:integer [0..1]
epo:Notice
@@ -4099,6 +4365,12 @@
Attributes (datatype
xsd:integer [0..1]
+
+
epo:SubmissionStatisticalInformation
+
epo:hasSMEReceivedTendersExcludingSubcontractors
+
+
xsd:integer [0..1]
+
epo:StrategicProcurement
epo:hasStrategicProcurementDescription
@@ -4223,7 +4495,7 @@
Attributes (datatype
xsd:integer [0..1]
-
epo:Fund epo:Certificate
+
cccev:Evidence epo:Fund
epo:hasURL
The identifier of a resource.
@@ -4239,7 +4511,8 @@
Attributes (datatype
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.
+ WG Approval 30/09/2019
+ The identifier of a resource.
Additional Information
@@ -4253,8 +4526,7 @@
Attributes (datatype
5. The URL of the system used to exchange information between Buyer and EO for questions
and clarifications;
- WG Approval 30/09/2019
-
+ WG Approval 30/09/2019
xsd:anyURI [0..1] xsd:anyURI [0..1]
@@ -4977,6 +5249,25 @@
Attributes (datatype
rdf:PlainLiteral [0..*]
+
+
epo-sub:CertificateInformation
+
epo-sub:coversAllSelectionCriteria
+
Indicator that the Certificate proves whether the Organization fulfils all Selection
+ Criteria.
+
+ WG approval 12/03/2024
Text 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/2024
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.
+
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. A unique identifier of the instance of the concept.
Additional Information
@@ -5234,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. 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.
+
+ 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. 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.
+
Information 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.
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.
A more specific Requirement that is part of the Requirement.
cccev:Requirement -> cccev:Requirement [0..*]
+
+
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
+ 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.
Information Concept providing facts found/inferred from the Evidence.
Additional Information:
- Examples of Information Concepts are values found explictly in the evidence such as
- a birth date or information derived from the Evidence such as "I am older that 18
- years" or "this is a FairTrade product".
+ 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..*]
@@ -5281,6 +5638,28 @@
Predicates (object p
Requirement for which the Evidence provides proof.
cccev:Evidence -> cccev:Requirement [0..*]
+
+
cccev:supportsValue
+
Supported Value that the Evidence contains. Supported Value that the Evidence contains. Supported Value that the Evidence contains.
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.
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.
A related resource that is supplanted, displaced, or superseded by the described resource.
@@ -5350,10 +5750,48 @@
Predicates (object p
Category to which the Requirement belongs.
cccev:Criterion -> at-voc:criterion [0..1]
+
+
eli:is_realized_by
+
Relates 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: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.
+ 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.
+
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.
+ 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.
+
The document to which a document is associated.
@@ -5433,7 +5881,7 @@
Predicates (object p
Relation indicating which label the certificate is about.
WG approval 28/07/2022
-
epo:Certificate -> epo:CertificationLabel [1]
+
epo:Certificate -> epo:CertificationLabel [0..1]
epo:bindsBuyer
@@ -5445,6 +5893,23 @@
Predicates (object p
Provides legal constraint on the Contractor.
epo:Contract -> epo:Contractor [0..*]
+
+
epo:canProvideNonDiscriminatoryEvidence
+
Relation 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/2024
+
org:Organization -> cccev:Evidence [0..*]
+
+
+
epo:canProvideTaxAndSocialSecuritiesEvidence
+
Relation showing that an Organization can supply an Evidence with regard to the payment
+ of social security contributions and taxes.
+
+ WG approval 12/03/2024
This refers to the identifier for the specific instance of the produced concept.
- WG Approval 16/05/2023
- This refers to the identifier for the specific instance of the produced concept.
- WG Approval 16/05/2023
+
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
The identifier for the instance of the concept based on a standard scheme.
+
The general identifier assigned to the concept based on a standard scheme.
Additional information:
- For example the GTIN scheme (Global Trade Item Number).
+ For example the GTIN scheme (Global Trade Item Number).
- WG Approval 24/02/2022
- The identifier for the instance of the concept based on a standard scheme.
+ 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).
+ For example the GTIN scheme (Global Trade Item Number).
- WG Approval 24/02/2022
-
This refers to the general identifier for the concept as defined by the manufacturer.
+
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
-
- This refers to the general identifier for the concept as defined by the manufacturer.
-
-
- WG Approval 16/05/2023
-
+ WG approval 16/05/2023
The general identifier for the concept as defined by the seller.
+
The general identifier assigned to the concept as defined by the Seller.
- WG Approval 16/05/2023
- The general identifier for 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
+ WG approval 16/05/2023
A universally unique identifier for an instance of this document.
- WG Approval 12/05/2020
-
epo:Document -> adms:Identifier [0..1]
+ 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
+
+
+ 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
+
Relation 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
+
+
An item that can be added to another item to enhance it.
@@ -7337,7 +7869,11 @@
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
The identifier used for tracking the goods item
+
+ 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
+
Additional 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.
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.
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
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
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
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 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
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
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
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
Relation indicating that an ESPD Response contains a Response.
+
+ WG approval 12/03/2024
+
epo-sub:ESPDResponse -> epo-sub:Response [1..*]
+
+
+
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
Associates any Resource with the corresponding Address.
diff --git a/glossary/ePO_core_glossary.html b/glossary/ePO_core_glossary.html
index 5faf89fd..a2ce502b 100644
--- a/glossary/ePO_core_glossary.html
+++ b/glossary/ePO_core_glossary.html
@@ -80,11 +80,48 @@
Class names and defi
cccev:Evidence
Proof that a Requirement is met.
+ Additional Information:
+ The class Evidence provides the means to support responses to Criteria or to a concrete
+ Information Requirement or to an Information Concept inside an Information Requirement.
+ The proof described by an Evidence can [1] verify a claim (i.e. is it true that John
+ is 25, yes/no), [2] prove a condition (i.e. is John 18+, yes/no), or [3] simply provide
+ data (i.e. the age of a person, namely 25). The proof can be given through documents
+ or extracts of base registries, independently from its structure, format or medium
+ used to exchange it: a pdf document, a video, a recording, etc.
cccev:InformationConcept
-
Piece of information that the Evidence provides or the Requirement needs.
+
Piece of information that the Evidence provides or the Requirement needs.
+
+ Additional Information:
+
+ The Information Concept class offers the ability to describe conceptually the Requirements
+ and provided facts in Evidences. In complementarity with the Supported Value class,
+ this is a (first) step towards facilitating the assessment of the requirements in
+ an automated way based on the Evidence provided.
+
+
+
cccev:InformationRequirement
+
Requested data that is to be proven by Evidence.
+
+ Additional Information:
+
+ Information Requirements are the most neutral kind of Requirements. They aim to request
+ information in any form, e.g. a person's date of birth or a company's turnover. They
+ represent requests for data that prove one or more facts of the real world in a formal
+ manner, or that leads to the source of such a proof. They can be understood as 'requests
+ for Evidences'. The response to an Information Requirement is an Evidence when the
+ issuer of the response is an authoritative source (e.g. a Civil Registry providing
+ data about a natural person for the provision of public service through the Single
+ Digital Gateway). In other cases, the responses might not be issued by an authoritative
+ source, but the issuer supports the responses with Evidences (or commits to support
+ them timely, e.g. a self-declaration or a declaration of oath). The Information Requirement
+ can require structured data or documents of any form. For structured data, the Requirement
+ can use 'Concepts' to specify the structure and type of the data expected in the response.
+ For both structured and unstructured data, the Information Requirement can indicate
+ the expected Type of Evidence, its format, source, and other properties related to
+ the Evidence.
cccev:Requirement
@@ -232,10 +269,11 @@
Class names and defi
epo:Awarder
A Role of an Agent that signs the Award Decision.
- Additional Information:
+ Additional information:
BT-08 can be Awarding CBP; BG-03 is the Buyer. But Awarding CPB is not the same as
the Buyer; the organisations may differ for these roles. Having the Awarder Role allows
- us to specify which Organisation is involved in the Award Decision.
+ us to specify which Organisation is involved in the Award Decision.
+
epo:AwardEvaluationTerm
@@ -385,7 +423,7 @@
Class names and defi
The description has its own identity (+I) but is dependent (+D) on the concerned Entity.
- We say that ContextSpecificDescription *concerns* an Entity.
+ We say that ContextDescription *concerns* an Entity.
@@ -833,7 +871,7 @@
Class names and defi
epo:Period
A time interval or a Duration.
- (WG approval 28/04/2020)
+ WG approval 28/04/2020
@@ -1209,7 +1247,7 @@
Class names and defi
At tendering time, entities relied upon by the Economic Operators can be Subcontractors
or not.
- When modelling ESPD we well analyze whether we need or not a Role named "relied upon".
+ When modelling ESPD we will analyze whether we need or not a Role named "relied upon".
WG approval 05/08/2021
@@ -1253,6 +1291,13 @@
Class names and defi
epo:TechnicalAbilitySummary
+
+
epo:TechnicalSpecification
+
A set of documented Requirements applicable to the object of the Procurement.
+ Additional Information:
+ A specification often includes technical standards.
+ WG approval: 20/04/2021
+
epo:Technique
Method used for conducting Procurement Procedures.
@@ -1491,7 +1536,7 @@
An account of the resource.
@@ -1529,6 +1574,12 @@
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.
+
+ 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.
@@ -1600,7 +1651,7 @@
Supplementary data about the instance of the concept.
@@ -1740,8 +1791,10 @@
Attributes (datatype
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
The unique identifier of the certificate.
WG approval 26/07/2022
-
rdf:PlainLiteral [1..1]
+
rdf:PlainLiteral [0..1]
epo:ChangeInformation
@@ -2693,7 +2746,7 @@
Attributes (datatype
epo:Notice
epo:hasOJSIssueNumber
-
rdf:PlainLiteral [0..1]
+
xsd:integer [0..1]
epo:Notice
@@ -3111,6 +3164,12 @@
Attributes (datatype
xsd:integer [0..1]
+
+
epo:SubmissionStatisticalInformation
+
epo:hasSMEReceivedTendersExcludingSubcontractors
+
+
xsd:integer [0..1]
+
epo:StrategicProcurement
epo:hasStrategicProcurementDescription
@@ -3235,7 +3294,7 @@
Attributes (datatype
xsd:integer [0..1]
-
epo:Fund epo:Certificate
+
cccev:Evidence epo:Fund
epo:hasURL
The identifier of a resource.
@@ -3251,7 +3310,8 @@
Attributes (datatype
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.
+ WG Approval 30/09/2019
+ The identifier of a resource.
Additional Information
@@ -3265,8 +3325,7 @@
Attributes (datatype
5. The URL of the system used to exchange information between Buyer and EO for questions
and clarifications;
- WG Approval 30/09/2019
-
+ WG Approval 30/09/2019
xsd:anyURI [0..1] xsd:anyURI [0..1]
@@ -3900,7 +3959,7 @@
Predicates (object p
adms:identifier
-
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.
+
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. A unique identifier of the instance of the concept.
Additional Information
@@ -3936,8 +3995,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.
+
+ 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.
+
Information 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.
A more specific Requirement that is part of the Requirement.
@@ -3973,9 +4046,9 @@
Predicates (object p
Information Concept providing facts found/inferred from the Evidence.
Additional Information:
- Examples of Information Concepts are values found explictly in the evidence such as
- a birth date or information derived from the Evidence such as "I am older that 18
- years" or "this is a FairTrade product".
+ 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".
Relation indicating which label the certificate is about.
WG approval 28/07/2022
-
epo:Certificate -> epo:CertificationLabel [1]
+
epo:Certificate -> epo:CertificationLabel [0..1]
epo:bindsBuyer
@@ -4030,6 +4103,23 @@
Predicates (object p
Provides legal constraint on the Contractor.
epo:Contract -> epo:Contractor [0..*]
+
+
epo:canProvideNonDiscriminatoryEvidence
+
Relation 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/2024
+
org:Organization -> cccev:Evidence [0..*]
+
+
+
epo:canProvideTaxAndSocialSecuritiesEvidence
+
Relation showing that an Organization can supply an Evidence with regard to the payment
+ of social security contributions and taxes.
+
+ WG approval 12/03/2024
Relation 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
+
+
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.
+
+
+
epo-sub:CertificateInformation
+
Information about a Certificate.
+
+ WG approval 12/03/2024
+
+
+
epo-sub:ESPDResponse
+
A 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.
+
+ WG Approval 05/03/2024
+
+
+
epo-sub:LegalRepresentative
+
The Role of an Agent that can represent an Organization.
+
+ WG approval 05/03/2024
+
+
+
epo-sub:Mandate
+
An authorization to act as a representative of an Organization.
+
+ WG approval 05/03/2024
+
+
+
epo-sub:NationalPreQualificationData
+
Data that describe the distinctive features or characteristics that qualify an economic
+ operator to take part in a tendering process.
+
+ WG approval 05/03/2024
+
+
+
epo-sub:PowerOfAttorney
+
A legal document that grants someone the authority to make decisions on behalf of
+ an Organization.
+
+ WG approval 05/03/2024
+
+
+
epo-sub:Response
+
An answer given to a question that is part of an ESPD Request.
+
+ WG approval 12/03/2024
+
+
+
+
Attributes (datatype properties) names and definitions
+
+
+
+
Class name
+
Attribute name
+
Definition
+
Data type / cardinality
+
+
+
+
+
cccev:SupportedValue
+
cccev:value
+
Value for the Information Concept that the Evidence supports.
+
rdf:PlainLiteral [0..*]
+
+
+
epo-sub:CertificateInformation
+
dct:description
+
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]
+
+
+
epo-sub:CertificateInformation
+
epo-sub:coversAllSelectionCriteria
+
Indicator that the Certificate proves whether the Organization fulfils all Selection
+ Criteria.
+
+ WG approval 12/03/2024
Text 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/2024
+
rdf:PlainLiteral [0..1]
+
+
+
+
Predicates (object properties) and definitions
+
+
+
+
Predicate name
+
Definition
+
Domain, Range and Cardinality
+
+
+
+
+
cccev:confidentialityLevelType
+
Security classification assigned to an Evidence e.g. classified, sensitive, public.
+
+ Additional Information:
+
+ Classifications should be defined by an organisation/country as an outcome of a security
+ assessment.
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
eProcurement UML model needs to conform to a set of UML conventions described
+ elsewhere. A conformance checking script was developed to execute tests to the UML
+ model and generate errors or warnings when encountered.
+
This document was automatically generated by the conformance checking script and
+ comprises the UML conformance violations.
+
The organisation of this document is based on major types of UML elements and
+ connectors that are employed in the eProcurement conceptual model. They are as
+ follows:
+ Classes, Enumerations, Datatypes, Packages, Objects, Associations, Dependencies, Realisations
+ and
+ Generalisations. Each major section lists model items that need correction of errors
+ or consideration of warnings.
+
The UML model in file eAccess.xml
+ was tested at 11:52 on March 21, 2024.
The class cccev:EvidenceType has no attributes provided. A class should define some
+ attributes.
+
+
+
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-acc:ESPDRequest
+
+
+
Unmet class conventions
+
The class epo-acc:ESPDRequest has no attributes provided. A class should define some
+ attributes.
+
+
+
Enumerations
+
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
+
Object
+
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.
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.
+
+
( - ) -> ( - ) (+)
+
+
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 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.
The connector is missing a description. It is recommended to
+ define and describe all the relations.
+
+
Realisations
+
Connectors with multiple usages
+
+
adms:identifier
+
+
The property is reused in multiple contexts, the meaning given by the definition is
+ the same. Here is the property usage:
+
+
Links a resource to an adms:Identifier class. (cccev:EvidenceType -> adms:Identifier
+ (+adms:identifier))
+
Links a resource to an adms:Identifier class. (cccev:EvidenceTypeList -> adms:Identifier
+ (+adms:identifier))
+
+
+
+
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
+
+
The property is reused in multiple contexts, the meaning given by the definition is
+ the same. Here is the property usage:
+
+
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:LegalExpression -> adms:Identifier (+eli:uri_schema))
+
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 (+eli:uri_schema))
+
+
+
Class attributes with multiple usages
+
+
dct:description
+
The attribute dct:description has different multiplicities in reuse contexts.
+ When a property is reused in multiple contexts, the multiplicity is expected to be
+ the same. Please see usage below:
+
+
cccev:EvidenceTypeList (rdf:PlainLiteral) [1..1]
+
eli:LegalExpression (rdfs:Literal) [0..*]
+
eli:LegalResource (rdfs:Literal) [1..1]
+
+
+
The attribute dct:description 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:
+
+
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 (cccev:EvidenceTypeList)
+
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
+ (eli:LegalExpression)
+
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
+ (eli:LegalResource)
+
+
+
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:EvidenceTypeList)
+
rdfs:Literal (eli:LegalExpression)
+
rdfs:Literal (eli:LegalResource)
+
+
+
+
General conventions
+
Only associations, dependecies, generalisations and realisation connectors are supported.
+ The following connector types were found in model and are not supported
+
+
NoteLink
+
+
+
Only Class, Package, Datatype, Enumeration, and Object elements are supported. The
+ following element types were found in model and are not supported
+