From f2768df75fe248662a97a5bd03b8c5a7cb73586e Mon Sep 17 00:00:00 2001 From: EmidioStani Date: Mon, 27 May 2024 15:45:59 +0200 Subject: [PATCH] update m8g serialization --- releases/m8g/m8g.jsonld | 3203 +++++++++++++++++++++++++++++++++++++++ releases/m8g/m8g.nt | 768 +++++++--- releases/m8g/m8g.rdf | 1725 +++++++++++---------- releases/m8g/m8g.ttl | 1111 ++++++++++---- 4 files changed, 5367 insertions(+), 1440 deletions(-) create mode 100644 releases/m8g/m8g.jsonld diff --git a/releases/m8g/m8g.jsonld b/releases/m8g/m8g.jsonld new file mode 100644 index 0000000..5d34439 --- /dev/null +++ b/releases/m8g/m8g.jsonld @@ -0,0 +1,3203 @@ +[ + { + "@id": "http://data.europa.eu/m8g/AccountingDocument", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Financial and non-financial information as a result of an activity of an organisation." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Accounting Document" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Accounting documents, might include:\r\n" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/AdminUnit", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A detailed administrative unit organized in a hierarchy." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Administrative Unit" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "This class should be used whenever a classification mechanism is in place, in alternative to the properties adminUnitL1 and adminUnitL2 of the Address class which allow free text." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/BusinessEvent", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A Business Event is a specific situation or event in the lifecycle of a business that fulfils one or more needs or (legal) obligations of that business at this specific point in time." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Business Event" + } + ], + "http://www.w3.org/2000/01/rdf-schema#subClassOf": [ + { + "@id": "http://data.europa.eu/m8g/Event" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "A Business Event requires a set of public services to be delivered and consumed in order for the associated business need(s) or obligation(s) to be fulfilled. Business Events are defined within the context of a particular Member State. In other words, a Business Event groups together a number of public services that need to be delivered for completing that particular event." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/Channel", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A medium through which an Agent provides, uses or interacts in another way with a Public Service." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Channel" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Typical examples include online services, phone, walk-in centres etc." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/Constraint", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Limitation applied to an Information Concept." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Constraint" + } + ], + "http://www.w3.org/2000/01/rdf-schema#subClassOf": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Constraints are requirements in themselves, since they impose prerequisites which influence the definition, use and/or fulfilment of the requirement. They represent hard conditions such as minimum or maximum expressions which can be used to evaluate pieces of information, the required age, income, involvement in activities, etc. An example from the eProcurement domain is a threshold as the minimum turnover required by the buying organisation to select the candidates. Note that CCCEV does not provide any specific guidance on when which kind of Requirement should be used. Users of this vocabulary should make decisions on this topic in their specific context." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/ContactPoint", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Information (e.g. e-mail address, telephone number) of a person or department through which the user can get in touch with." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Contact Point" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The Core Public Organization Vocabulary defines properties for telephone number, e-mail address and opening hours although it is noteworthy that the class is based on schema.org's ContactPoint class that has additional properties that some implementations may find useful." + }, + { + "@language": "en", + "@value": "Similarly to the Channel class, a Contact Point may have regular opening hours that are then overridden by, for example, public holidays, using the Temporal Entity class." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/Cost", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The Cost class represents any costs related to the execution of a Public Service that the Agent consuming it needs to pay." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Cost" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/Criterion", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Condition for evaluation or assessment." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Criterion" + } + ], + "http://www.w3.org/2000/01/rdf-schema#subClassOf": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "In general, Criteria are used for comparison, filtering or selection purposes. Criteria usually set minimum conditions (e.g. limits, intervals, thresholds, etc.) that need to be met in order to pass the requirements or to fulfil them to a certain degree or quality. The concept of Criteria is broader than the concept of Constraint since it covers more usages. The evaluation of the fulfilment is usually supported by the provision of Evidence. \r\nFor example in the eProcurement domain, the eProcurement Ontology defines different subclasses of Criterion such as exclusion grounds, selection criteria or award criteria. A concrete example of a Criterion is 'participation in a criminal organisation' which could also be considered as an exclusion ground criterion in the procurement domain or for requiring a public service." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/Event", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "This class represents an event that can be of any type that triggers, makes use of, or in some way is related to, a Public Service." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Event" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "It is not expected to be used directly, rather, one or other of its subclasses should be used. The properties of the class are, of course, inherited by those subclasses. The Event class is used as a hook either to a single related Public Service, such as diagnosis of illness being related to application for sickness benefit; or to a group of Public Services, such as all those related to the establishment of a new business." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/Evidence", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The Evidence class is defined in the Core Criterion and Core Evidence vocabulary (CCCEV) as any resource that can prove that a specific requirement is met." + }, + { + "@language": "en", + "@value": "Proof that a Requirement is met." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Evidence" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Although the wording of the definition is different, the semantics are an exact match for CPSV's Input class which it replaces.\r\n\r\nEvidence can be any resource - document, artefact - anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered.\r\n\r\nIn some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s)." + }, + { + "@language": "en", + "@value": "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. \r\n\r\nThe 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).\r\nThe 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." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/EvidenceType", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Information about the characteristics of an Evidence." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Evidence Type" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "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)." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/EvidenceTypeList", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Group of Evidence Types for conforming to a Requirement." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Evidence Type List" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "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. \r\n\r\nThe 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." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/GenericDate", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The date data type is the union of xs:date, xs:gYearMonth and xs:gYear" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Generic date" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/ImageObject", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A logo to describe / represent an entity." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Image Object" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/InformationConcept", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Piece of information that the Evidence provides or the Requirement needs." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Information Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "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." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/InformationRequirement", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Requested data that is to be proven by Evidence." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Information Requirement" + } + ], + "http://www.w3.org/2000/01/rdf-schema#subClassOf": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "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." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/LifeEvent", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The Life Event class represents an important event or situation in a citizen's life where public services are required." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Life Event" + } + ], + "http://www.w3.org/2000/01/rdf-schema#subClassOf": [ + { + "@id": "http://data.europa.eu/m8g/Event" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Note on the scope: an individual will encounter any number of 'events'; in the general sense of the word. In the context of the CPSV-AP, the Life Event class only represents an event to which a Public Service is related. For example, a couple becoming engaged is not a CPSV-AP Life Event, getting married is, since only the latter has any relevance to public services." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/Output", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "An output can be any resource - document, artefact - anything produced by the Public Service. In the context of a Public Service, the output provides an official document or other artefact of the Competent Authority (Public Organization) that permits/authorises/entitles an Agent to (do) something." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Output" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "In some cases, the Output of one Public Service will be used as evidence to fulfil a requirement of another Public Service. Such relationships should be described in the associated Rule(s)." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/Participation", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The Participation class allows to define roles within a certain context." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Participation" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The CPSV-AP recognises a common role connected with public services, i.e. the Competent Authority.\r\n

\r\nThis simple structure does not allow statements to be made about those participants, such as the start and end date of a contract, nor does it support the inclusion of other roles. The Participation class supports this extra complexity if required, for instance, the description of a service user or a service provider. The model is consistent with the CPOV which in turn is based on the W3C Organization Ontology that supports the common cases simply but allows the complex cases where necessary. The Participation class can be mapped to the Organization Ontology's Membership class that allows more complex relationships and richer metadata to be applied to a role filled by a given Agent." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/PublicEvent", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Something that happens at a particular place and time,\r\norganised by one or more agents for a particular purpose, and is of interest to a general\r\n audience. This definition excludes natural events such as earthquakes and volcanic \r\neruptions." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Public Event" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/PublicOrganisation", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "An Organization that is defined as being part of the public sector by a legal framework at any level." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Public Organisation" + }, + { + "@language": "en", + "@value": "Public Organization" + } + ], + "http://www.w3.org/2000/01/rdf-schema#subClassOf": [ + { + "@id": "http://www.w3.org/ns/org#Organization" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Organizations which exist to provide services for its citizens and companies are called Public Organizations. The Public Organization class represents the organization. One organization may comprise several sub-organizations and any organization may have one or more organizational units. Each of these is described using the same properties and relationships.\r\n

\r\nThis definition is consistent with the more detailed definition of a \"public sector body\" as given in the PSI Directive: \"the State, regional or local authorities, bodies governed by public law and associations formed by one or several such authorities or one or several such bodies governed by public law\". It further defines a body governed by public law as any body \"(a) established for the specific purpose of meeting needs in the general interest, not having an industrial or commercial character; and (b) having legal personality; and (c) financed, for the most part by the State, or regional or local authorities, or other bodies governed by public law; or subject to management supervision by those bodies; or having an administrative, managerial or supervisory board, more than half of whose members are appointed by the State, regional or local authorities or by other bodies governed by public law\"." + }, + { + "@language": "en", + "@value": "Organizations which exist to provide services for its citizens and companies are called Public Organizations. The Public Organization class represents the organization. One organization may comprise several sub-organizations and any organization may have one or more organizational units. Each of these is described using the same properties and relationships.\r\n

\r\nThis definition is consistent with the more detailed definition of a \"public sector body\" as given in the PSI Directive: \"the State, regional or local authorities, bodies governed by public law and associations formed by one or several such authorities or one or several such bodies governed by public law\". It further defines a body governed by public law as any body \"(a) established for the specific purpose of meeting needs in the general interest, not having an industrial or commercial character; and (b) having legal personality; and (c) financed, for the most part by the State, or regional or local authorities, or other bodies governed by public law; or subject to management supervision by those bodies; or having an administrative, managerial or supervisory board, more than half of whose members are appointed by the State, regional or local authorities or by other bodies governed by public law\"." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/ReferenceFramework", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Legislation or official policy from which Requirements are derived." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Reference Framework" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Usual Reference Frameworks are legal and non-legal specifications. Examples include procedures, tendering legislation, etc." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/Requirement", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Condition or prerequisite that is to be proven by Evidence." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Requirement" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Not all public services are needed or are used by everyone. For example, the visa service operated by European countries is not needed by European citizens but is needed by some citizens from elsewhere, or public services offering unemployment benefits and grants are targeting specific societal groups. The CPSV-AP reuses the Core Criterion and Core Evidence Vocabulary for this class.\r\n\r\nRequirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent.\r\nTo illustrate the notion: the European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy." + }, + { + "@language": "en", + "@value": "Requirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent. The European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/ServiceConcessionContract", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Concessions are contracts for pecuniary interest by means of which one or more contracting authorities or contracting entities entrusts the execution of works, or the provision and the management of services, to one or more economic operators." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Service Concession Contract" + } + ], + "http://www.w3.org/2000/01/rdf-schema#subClassOf": [ + { + "@id": "http://data.europa.eu/a4g/ontology#ConcessionContract" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The object of such contracts is the procurement of works or services by means of a concession, the consideration of which consists in the right to exploit the works or services or in that right together with payment. Such contracts may, but do not necessarily, involve a transfer of ownership to contracting authorities or contracting entities, but contracting authorities or contracting entities always obtain the benefits of the works or services in\r\nquestion. The definition comes from the Directive 2014/23/EU." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/SupportedValue", + "@type": [ + "http://www.w3.org/2002/07/owl#Class" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Value for an Information Concept that is provided by an Evidence." + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "Supported Value" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The notion of Supported Value is closely related to actual data exchange between two parties: \r\n(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 \r\n(b) the Evidence provider, i.e. the Agent supplying information to an information request expressed as Requirements.\r\n\r\nThe 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. \r\n\r\nThe 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.\r\n\r\nImplementers are free to choose their language. It is recommended to document the made agreements well.\r\n" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/accessibility", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Information about how the Public Event can be approached, reached or entered, in particular for people with special needs." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/PublicEvent" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "accessibility" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "This property may be provided in multiple languages with multiple instances of the accessibility property." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/audience", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The target group of people for whom the Public Event is created." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/PublicEvent" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "audience" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/bias", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Parameter used to adjust the evaluation of the Criterion." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Criterion" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "bias" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2001/XMLSchema#decimal" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "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." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/birthDate", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The point in time on which the Person was born." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/ns/person#Person" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "date of birth" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/GenericDate" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/code", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The classification of the administrative unit." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/AdminUnit" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "code" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/confidentialityLevelType", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Security classification assigned to an Evidence e.g. classified, sensitive, public." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Evidence" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "confidentiality level type" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Classifications should be defined by an organisation/country as an outcome of a security assessment." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/constrains", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Information Concept about which a Constraint expresses a limitation." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Constraint" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "constrains" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/InformationConcept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "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." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/contactPage", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A web page that could be used to reach out the Contact Point." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/ContactPoint" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "contact page" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://xmlns.com/foaf/0.1/Document" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/contactPoint", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The main contact information of the resource." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "contact point" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Note that the contact information should be relevant to the Public Service which may not be the same as contact information for the Competent Authority or any Participant." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/coordinates", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "\tA list of geographic coordinates that define the extent of the Geometry." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/ns/locn#Geometry" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "coordinates" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2001/XMLSchema#string" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Can be expressed as longitude, latitude, elevation." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/crs", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "An identifier for the coordinate reference system." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/ns/locn#Geometry" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "crs" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2001/XMLSchema#anyURI" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Can be a coordinate-based local, regional or global system used to locate geographical entities." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/currency", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The currency in which the Cost needs to be paid and the value of the Cost is expressed." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "currency" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The possible values for this property are described in the controlled vocabulary \r\nCurrency Authority Table of Publications Office." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/deathDate", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The point in time on which the Person died." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/ns/person#Person" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "date of death" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/GenericDate" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/email", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "An electronic address through which the Contact Point can be contacted." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/ContactPoint" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has email" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2000/01/rdf-schema#Literal" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/establishedUnder", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It links a Service Concession Contract to relevant legislation or policy documents i.e.\r\nthe Legal Resource under which the Service Concession Contracts are being defined." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "established under" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/eventNumber", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The sequence position of the Public Event." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/PublicEvent" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "event number" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Examples could be the ''4th\" or \"2022\"." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/eventStatus", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": " This property defines the overall status of the event." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/PublicEvent" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "event status" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The recomended code list is the Event Status Controlled vocabulary maintained by the Publications Office of the EU." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/evidenceTypeClassification", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Category to which the Evidence Type belongs." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/EvidenceType" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "evidence type classification" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The categories agreed are left open but could for example specify the layout and content expected for an Evidence. An example could be id cards." + }, + { + "@language": "en", + "@value": "The categories agreed are left open but could for example specify the layout and content expected for an Evidence." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/expectedNumberOfParticipants", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The number of participants expected to participate in the event." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/PublicEvent" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "expected number of participants" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2001/XMLSchema#integer" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/expressionOfExpectedValue", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Formulation in a formal language of the expected value(s) for the Information Concept which is aligned with the concepts from the Requirements defined and must be respected by the supplied Supported Values ." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/InformationConcept" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "expression of expected value" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2000/01/rdf-schema#Literal" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The property encapsulates all kind of expectations on the required and provided values one could have. \r\nThis may range from representational expectations such as the type (e.g. the value is expected to be a xsd:decimal) to expectations that reduce the allowed value range. Commonly this is done using min or max bounderary expressions (e.g. the maximum value is 1 Million Euro).\r\nOther usage could be to harmonise the supplied values (e.g. rounding, turning to percentages) to facilitate further processing.\r\n\r\nImplementers are free to use their own approach for defining the expected values in more details. For instance, this can be by defining their own datatypes extending or encapsulating common xsd datatypes. But also by using more complex languages such as XPath, Object Constraint Language (OCL), JavaScript and Rule Interchange Format (RIF).\r\nBecause of this freedom, implementers are recommended to well-document their usage of this property (and related information). \r\n\r\n\r\n \r\n\r\n" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/format", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A plan of organisation or arrangement of the Public Event." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/PublicEvent" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "format" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Examples include conference call, physical meeting or hybrid." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/frequency", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The recurrence of an instant or period." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/2006/time#TemporalEntity" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "frequency" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "It is recommended to use the frequency from an existing vocabulary like the Frequency from the Publications Office." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/fulfils", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The Rules that the requiremens fulfils." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "fulfils" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/gender", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The identities, expressions and societal roles of the Person." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/ns/person#Person" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "gender" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The gender of an individual should be recorded using a controlled vocabulary that is appropriate for the specific context. In some cases, the chromosomal or physical state of an individual will be more important than the gender that they express, in others the reverse will be true. What is always important is that the controlled vocabulary used to describe an individual's gender is stated explicitly." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/geometryType", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The classification of the Geometry." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/ns/locn#Geometry" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "geometry type" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Can be a point, line or polygon." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasChannel", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It links the Public Service to any Channel through which an Agent provides, uses or otherwise interacts with the Public Service, such as an online service, phone number or office." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has channel" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasCompetentAuthority", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It links a Public Service to a Public Organization, which is the responsible Agent for the delivery of the Public Service." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has competent authority" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Whether the particular Public Organization provides the public service directly or outsources it is not relevant. The Public Organization that is the Competent Authority of the service is the one that is ultimately responsible for managing and providing the public service. The term Competent Authority is defined in the Services Directive (2006/123/EC) in the following way: \"Any body or authority which has a supervisory or regulatory role in a Member State in relation to service activities, including, in particular, administrative authorities, including courts acting as such, professional bodies, and those professional associations or other professional organisations which, in the exercise of their legal autonomy, regulate in a collective manner access to service activities or the exercise thereof\"." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasConcept", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Information Concept for which a value is expected by the Requirement." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has concept" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/InformationConcept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Information Concepts defined for specific Requirements also represent the basis for specifying the Supported Value an Evidence should provide." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasContractingAuthority", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It links a Service Concession Contract with the Contracting Authority which is ultimately responsible for a public service." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has contracting authority" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasCost", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It indicates the costs related to the execution of a Public Service for the citizen or business related to the execution of the particular Public Service." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has cost" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Where the cost varies depending on the channel through which the service is accessed, it can be linked to the channel using the If Accessed Through relationship." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasEconomicOperator", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It links a Service Concession Contract with the Economic Operator in charge for the provision and the management of public services." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has economic operator" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasEvidenceTypeList", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Evidence Type List that specifies the Evidence Types that are needed to meet the Requirement." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has evidence type list" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/EvidenceTypeList" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "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." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasInputType", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It links a Public Service to one or more instances of the EvidenceType class." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has input type" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasLegalResource", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It indicates the Legal Resource (e.g. legislation) to which the Public Service relates, operates or has its legal basis." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has legal resource" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasParticipant", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The Agent involved in the Participation." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has participant" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasParticipation", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The way how a resource is organized." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has participation" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The Participation class facilitates the detailed description of how an Agent participates in or interacts with a Public Service and may include temporal and spatial information." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasQualifiedRelation", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Described and/or categorised relation to another Requirement." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has qualified relation" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "This property leaves the possiblity to define a qualified relation from Requirement to Information Requirement or Constraint as well as a qualified relation from Requirement to Requirement. A use case would be to specialize an EU requirement in Member States' specific requirements." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasRelatedService", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The Public Service related to the Event." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has related service" + } + ], + "http://www.w3.org/2000/01/rdf-schema#subPropertyOf": [ + { + "@id": "http://purl.org/dc/terms/relation" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "This property is a sub-property of dct:relation." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasRequirement", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A more specific Requirement that is part of the Requirement." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has requirement" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasSupportingEvidence", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Evidence that supplies information, proof or support for the Requirement." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has supporting evidence" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/Evidence" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/hasValue", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A numeric value indicating the amount of the Cost." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has value" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/holdsRequirement", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It links a Public Service to a class that describes the Requirement." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "holds requirement" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Usage: It describes the needing or using the service, such as residency in a given location, being over a certain age etc. The Requirement class is defined in the Core Criterion and Core Evidence Vocabulary." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/ifAccessedThrough", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The costs created by the use of different Channels." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "if accessed through" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "For example, if accessed through an online service cf. accessed at a physical location, the cost can be linked to the channel using the If Accessed Through property." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/isClassifiedBy", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It allows to classify the Public Service with any Concept other than those already foreseen and defined explicitly in the CPSV-AP (Thematic Area, Sector, etc.)." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "is classified by" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "It is a generic property which can be further specialised to make the classification explicit, for instance for classifying public services according level of digitisation,\r\ntype of audience, etc. The Concept is at its turn related to a Collection, which groups the different concepts into a controlled vocabulary." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/isDefinedBy", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It links the Cost class to one or more instances of the Public Organization class." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "is defined by" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "This property indicates which Public Organization is the Competent Authority for defining the costs associated with the delivery of a particular Public Service." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/isDerivedFrom", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Reference Framework on which the Requirement is based, such as a law or regulation." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "is derived from" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/ReferenceFramework" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Note that a Requirement can have several Reference Frameworks from which it is derived." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/isGroupedBy", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "It links the Public Service to the Event class." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "is grouped by" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Several Public Services may be associated with a particular Event and, likewise, the same Public Service may be associated with several different Events." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/isRequirementOf", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A reference between a sub-Requirement and its parent Requirement." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "is requirement of" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "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.\r\n\r\nIn the case where the purpose is to link the two Requirements without additional information, the simple relationship as proposed here can be directly used." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/isSpecifiedIn", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Evidence Type List in which the Evidence Type is included." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/EvidenceType" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "is specified in" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/EvidenceTypeList" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/latitude", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The geographic coordinate that specifies the north / south position of the Geomerty on the Earth's surface." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/ns/locn#Geometry" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "latitude" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2001/XMLSchema#string" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/level", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The level of the administrative unit in the hierarchy." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/AdminUnit" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "level" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The recommended code list to indicate the level of an Admin Unit is the Administrative territorial unit type Controlled Vocabulary maintained by the Publications Office of the EU. " + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/longitude", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The geographic coordinate that specifies the east / west position of the Geometry on the Earth's surface." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/ns/locn#Geometry" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "longitude" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2001/XMLSchema#string" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/matronymicName", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Name based on the given name of the Person's mother." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/ns/person#Person" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "matronymic name" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/openingHours", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A time at which the resource is normally available." + }, + { + "@language": "en", + "@value": "The time at which the Contact Point is normally available." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "opening hours" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Like the Contact Point, a Channel may be available at a certain time.\r\n

\r\nFor a simple description of the time use the description property of TemporalEntity.\r\n

\r\nFor more structured data use the model in Time Ontology, see an example." + }, + { + "@language": "en", + "@value": "For a simple description of the time use the description property of TemporalEntity.\r\n\r\nFor more structured data use the model in Time Ontology, see an example. This relation can be used to indicate exceptional closures such as being closed on public holidays." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/ownedBy", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The owner of a specific Channel through which a Public Service is being delivered." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "owned by" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/participates", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The participation in which an Agent is involved." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "participates" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The Participation class facilitates the detailed description of how an Agent participates in or interacts with a Public Service and may include temporal and spatial information." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/processingTime", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The (estimated) time needed for executing a Public Service. The actual information is provided using the ISO8601 syntax for durations." + }, + { + "@language": "en", + "@value": "The (estimated) time needed for executing a Public Service which may depend on the Channel chosen." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "processing time" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Some examples are provided below:\r\nDuration Syntax - Syntax\r\n5 years - P5Y\r\n1 month - P1M\r\n3 days - P3D\r\n2 days 4 hours - P2DT4H\r\n\r\nDurations begin with an uppercase P followed by the number and the relevant designator, formally: P[n]Y[n]M[n]DT[n]H[n]M[n]S, where Y is for years, M for months etc. \r\n\r\nNote that days and times are separated by an uppercase T which also\r\ndisambiguates M as meaning month (P2M means 2 months) or minute (PT2M means 2 minutes). Durations may also be defined as a number of weeks so P4W means 4 weeks. A full explanation is provided in the Wikipedia page that references the official ISO standard.\r\n\r\nThis approach is consistent with both schema.org and the W3C OWL Time Ontology." + }, + { + "@language": "en", + "@value": "The actual information is provided using the ISO8601 syntax for durations." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/providesValueFor", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Information Concept for which the Supported Value provides a value." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/SupportedValue" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "provides value for" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/InformationConcept" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/query", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Search statement that allows the value for the Information Concept to be retrieved from the Evidence data." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/SupportedValue" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "query" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2000/01/rdf-schema#Literal" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The query must be executed on the business data provided by the supporting Evidence. In order to be able to evaluate the query on the provided data, the format of the provided data must be aligned with the query expression. For instance if the provided data is XML, a query in XPath could be expected. This alignment is part of the implementation agreements that implementors must make." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/registrationDate", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The date on which the legal entity has registered in some jurisdiction for regulatory and / or for tax purposes." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/ns/legal#LegalEntity" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "registration date" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2001/XMLSchema#date" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/registrationPage", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A web page that provides means to attend the Public Event." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/PublicEvent" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "registration page" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://xmlns.com/foaf/0.1/Document" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/relatedService", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A Public Service related to the particular instance of the Public Service class." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "related service" + } + ], + "http://www.w3.org/2000/01/rdf-schema#subPropertyOf": [ + { + "@id": "http://purl.org/dc/terms/relation" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "This property is a sub-property of dct:relation." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/role", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The function of an Agent within a Participation." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Participation" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "role" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "This should be provided using a controlled vocabulary.\r\nSince this is an extension mechanism for the CSPV-AP, the controlled vocabulary should be decided to suit local implementations." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/sector", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The industry or sector a Public Service relates to, or is intended for." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "sector" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "For example: environment, safety, housing. Note that a single Public Service may relate to multiple sectors. The possible values for this property are provided as a controlled vocabulary. The possible values for this property are described in the controlled vocabulary Data theme Authority Table of the Publications Office." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/sex", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The organism's biological sex." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://www.w3.org/ns/person#Person" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "sex" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The recommended controlled vocabulary for this property is the sex authority table of the Publications Office." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/specialOpeningHoursSpecification", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A time during which the resource is not available." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "availability restriction" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "Like the Contact Point, a Channel may not be available at a certain time.\r\n

\r\nFor a simple description of the time use the description property of TemporalEntity.\r\n

\r\nFor more structured data use the model in Time Ontology, see an example." + }, + { + "@language": "en", + "@value": "For a simple description of the time use the description property of TemporalEntity.\r\n\r\nFor more structured data use the model in Time Ontology, see an example." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/specifiesEvidenceType", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Evidence Type included in this Evidence Type List." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/EvidenceTypeList" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "specifies evidence type" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/EvidenceType" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/supportsConcept", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Information Concept providing facts found/inferred from the Evidence." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Evidence" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "supports concept" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/InformationConcept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "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\"." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/supportsRequirement", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Requirement for which the Evidence provides proof." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Evidence" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "supports requirement" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/Requirement" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/supportsValue", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Supported Value that the Evidence contains." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Evidence" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "supports value" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://data.europa.eu/m8g/SupportedValue" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/telephone", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "A telephone number through which the Contact Point can be contacted." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/ContactPoint" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "has telephone" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2000/01/rdf-schema#Literal" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/thematicArea", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "The Thematic Area of a Public Service." + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "thematic area" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "For example: social protection, health, recreation, culture and religion, family, traveling economic affairs, tax, staff, environment, etc." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/validityPeriod", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Period of Time during which the Evidence holds true or has force." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Evidence" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "validity period" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2006/time#ProperInterval" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/validityPeriodConstraint", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Temporal condition on the validity period of the Evidence Type." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/EvidenceType" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "validity period constraint" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2006/time#ProperInterval" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "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." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/value", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Value for the Information Concept that the Evidence supports." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/SupportedValue" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "value" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2000/01/rdf-schema#Literal" + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/weight", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Relative importance of the Criterion." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Criterion" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "weight" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2001/XMLSchema#decimal" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "The weight must be between 0 and 1. Usually, all Criteria can be integrated within a weighted sum equal to 1." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/weightingConsiderationDescription", + "@type": [ + "http://www.w3.org/2002/07/owl#DatatypeProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Explanation of how the weighting of a Criterion is to be used." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Criterion" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "weighting consideration description" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2001/XMLSchema#string" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "This description gives the view of the creator of the Criterion weights on how to interpret and use them during the evaluation process." + } + ] + }, + { + "@id": "http://data.europa.eu/m8g/weightingType", + "@type": [ + "http://www.w3.org/2002/07/owl#ObjectProperty" + ], + "http://www.w3.org/2000/01/rdf-schema#comment": [ + { + "@language": "en", + "@value": "Indication of how the weight should be interpreted in a complex evaluation expression, e.g. as a percentage in an evaluation expression." + } + ], + "http://www.w3.org/2000/01/rdf-schema#domain": [ + { + "@id": "http://data.europa.eu/m8g/Criterion" + } + ], + "http://www.w3.org/2000/01/rdf-schema#isDefinedBy": [ + { + "@id": "http://data.europa.eu/m8g" + } + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@language": "en", + "@value": "weighting type" + } + ], + "http://www.w3.org/2000/01/rdf-schema#range": [ + { + "@id": "http://www.w3.org/2004/02/skos/core#Concept" + } + ], + "http://www.w3.org/2004/02/skos/core#scopeNote": [ + { + "@language": "en", + "@value": "An existing codelist which can be used is OP's Number weigth controlled vocabulary" + } + ] + } +] \ No newline at end of file diff --git a/releases/m8g/m8g.nt b/releases/m8g/m8g.nt index 519fc91..f7228a4 100644 --- a/releases/m8g/m8g.nt +++ b/releases/m8g/m8g.nt @@ -1,285 +1,567 @@ - . - . - _:genid1 . - . - _:genid2 . - "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\". [https://trade.ec.europa.eu/doclib/docs/2018/september/tradoc_157319.pdf]\nWhen quantified, this systematic error can be removed."@en . + . + "Image Object"@en . + "A logo to describe / represent an entity."@en . + . + . + "Public Organisation"@en . + "Public Organization"@en . + "An Organization that is defined as being part of the public sector by a legal framework at any level."@en . + . + . + "Organizations which exist to provide services for its citizens and companies are called Public Organizations. The Public Organization class represents the organization. One organization may comprise several sub-organizations and any organization may have one or more organizational units. Each of these is described using the same properties and relationships.\r\n

\r\nThis definition is consistent with the more detailed definition of a \"public sector body\" as given in the PSI Directive: \"the State, regional or local authorities, bodies governed by public law and associations formed by one or several such authorities or one or several such bodies governed by public law\". It further defines a body governed by public law as any body \"(a) established for the specific purpose of meeting needs in the general interest, not having an industrial or commercial character; and (b) having legal personality; and (c) financed, for the most part by the State, or regional or local authorities, or other bodies governed by public law; or subject to management supervision by those bodies; or having an administrative, managerial or supervisory board, more than half of whose members are appointed by the State, regional or local authorities or by other bodies governed by public law\"."@en . + "Organizations which exist to provide services for its citizens and companies are called Public Organizations. The Public Organization class represents the organization. One organization may comprise several sub-organizations and any organization may have one or more organizational units. Each of these is described using the same properties and relationships.\r\n

\r\nThis definition is consistent with the more detailed definition of a \"public sector body\" as given in the PSI Directive: \"the State, regional or local authorities, bodies governed by public law and associations formed by one or several such authorities or one or several such bodies governed by public law\". It further defines a body governed by public law as any body \"(a) established for the specific purpose of meeting needs in the general interest, not having an industrial or commercial character; and (b) having legal personality; and (c) financed, for the most part by the State, or regional or local authorities, or other bodies governed by public law; or subject to management supervision by those bodies; or having an administrative, managerial or supervisory board, more than half of whose members are appointed by the State, regional or local authorities or by other bodies governed by public law\"."@en . + . + "Reference Framework"@en . + "Legislation or official policy from which Requirements are derived."@en . + . + "Usual Reference Frameworks are legal and non-legal specifications. Examples include procedures, tendering legislation, etc."@en . + . + "contact page"@en . + "A web page that could be used to reach out the Contact Point."@en . + . + . + . + . + "has email"@en . + "An electronic address through which the Contact Point can be contacted."@en . + . + . + . + . + "frequency"@en . + "The recurrence of an instant or period."@en . + . + . + . + "It is recommended to use the frequency from an existing vocabulary like the Frequency from the Publications Office."@en . + . + "has telephone"@en . + "A telephone number through which the Contact Point can be contacted."@en . + . + . + . + . + "Contact Point"@en . + "Information (e.g. e-mail address, telephone number) of a person or department through which the user can get in touch with."@en . + . + "The Core Public Organization Vocabulary defines properties for telephone number, e-mail address and opening hours although it is noteworthy that the class is based on schema.org's ContactPoint class that has additional properties that some implementations may find useful."@en . + "Similarly to the Channel class, a Contact Point may have regular opening hours that are then overridden by, for example, public holidays, using the Temporal Entity class."@en . + . + "date of birth"@en . + "The point in time on which the Person was born."@en . + . + . + . + "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n
    \r\n
  • - 1980-09-16^^xs:date
    • \r\n
  • - 1980-09^^xs:gYearMonth
    • \r\n
  • - 1980^^xs:gYear
    • \r\n
"@en . + . + "date of death"@en . + "The point in time on which the Person died."@en . + . + . + . + "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n
    \r\n
  • - 1980-09-16^^xs:date
    • \r\n
  • - 1980-09^^xs:gYearMonth
    • \r\n
  • - 1980^^xs:gYear
    • \r\n
"@en . + . + "gender"@en . + "The identities, expressions and societal roles of the Person."@en . + . + . + . + "The gender of an individual should be recorded using a controlled vocabulary that is appropriate for the specific context. In some cases, the chromosomal or physical state of an individual will be more important than the gender that they express, in others the reverse will be true. What is always important is that the controlled vocabulary used to describe an individual's gender is stated explicitly."@en . + . + "matronymic name"@en . + "Name based on the given name of the Person's mother."@en . + . + . + . + . + "sex"@en . + "The organism's biological sex."@en . + . + . + . + "The recommended controlled vocabulary for this property is the sex authority table of the Publications Office."@en . + . + "Generic date"@en . + "The date data type is the union of xs:date, xs:gYearMonth and xs:gYear"@en . + . + . + "The (estimated) time needed for executing a Public Service. The actual information is provided using the ISO8601 syntax for durations."@en . + "The (estimated) time needed for executing a Public Service which may depend on the Channel chosen."@en . + "processing time"@en . + "Some examples are provided below:\r\nDuration Syntax - Syntax\r\n5 years - P5Y\r\n1 month - P1M\r\n3 days - P3D\r\n2 days 4 hours - P2DT4H\r\n\r\nDurations begin with an uppercase P followed by the number and the relevant designator, formally: P[n]Y[n]M[n]DT[n]H[n]M[n]S, where Y is for years, M for months etc. \r\n\r\nNote that days and times are separated by an uppercase T which also\r\ndisambiguates M as meaning month (P2M means 2 months) or minute (PT2M means 2 minutes). Durations may also be defined as a number of weeks so P4W means 4 weeks. A full explanation is provided in the Wikipedia page that references the official ISO standard.\r\n\r\nThis approach is consistent with both schema.org and the W3C OWL Time Ontology."@en . + "The actual information is provided using the ISO8601 syntax for durations."@en . + . + "The industry or sector a Public Service relates to, or is intended for."@en . + "sector"@en . + "For example: environment, safety, housing. Note that a single Public Service may relate to multiple sectors. The possible values for this property are provided as a controlled vocabulary. The possible values for this property are described in the controlled vocabulary Data theme Authority Table of the Publications Office."@en . + . + "The Thematic Area of a Public Service."@en . + "thematic area"@en . + "For example: social protection, health, recreation, culture and religion, family, traveling economic affairs, tax, staff, environment, etc."@en . + . + "The main contact information of the resource."@en . + "contact point"@en . + "Note that the contact information should be relevant to the Public Service which may not be the same as contact information for the Competent Authority or any Participant."@en . + . + "It links the Public Service to any Channel through which an Agent provides, uses or otherwise interacts with the Public Service, such as an online service, phone number or office."@en . + "has channel"@en . + . + "It links a Public Service to a Public Organization, which is the responsible Agent for the delivery of the Public Service."@en . + "has competent authority"@en . + "Whether the particular Public Organization provides the public service directly or outsources it is not relevant. The Public Organization that is the Competent Authority of the service is the one that is ultimately responsible for managing and providing the public service. The term Competent Authority is defined in the Services Directive (2006/123/EC) in the following way: \"Any body or authority which has a supervisory or regulatory role in a Member State in relation to service activities, including, in particular, administrative authorities, including courts acting as such, professional bodies, and those professional associations or other professional organisations which, in the exercise of their legal autonomy, regulate in a collective manner access to service activities or the exercise thereof\"."@en . + . + "It indicates the costs related to the execution of a Public Service for the citizen or business related to the execution of the particular Public Service."@en . + "has cost"@en . + "Where the cost varies depending on the channel through which the service is accessed, it can be linked to the channel using the If Accessed Through relationship."@en . + . + "It links a Public Service to one or more instances of the EvidenceType class."@en . + "has input type"@en . + . + "It indicates the Legal Resource (e.g. legislation) to which the Public Service relates, operates or has its legal basis."@en . + "has legal resource"@en . + . + "The way how a resource is organized."@en . + "has participation"@en . + "The Participation class facilitates the detailed description of how an Agent participates in or interacts with a Public Service and may include temporal and spatial information."@en . + . + "It links a Public Service to a class that describes the Requirement."@en . + "holds requirement"@en . + "Usage: It describes the needing or using the service, such as residency in a given location, being over a certain age etc. The Requirement class is defined in the Core Criterion and Core Evidence Vocabulary."@en . + . + "It allows to classify the Public Service with any Concept other than those already foreseen and defined explicitly in the CPSV-AP (Thematic Area, Sector, etc.)."@en . + "is classified by"@en . + "It is a generic property which can be further specialised to make the classification explicit, for instance for classifying public services according level of digitisation,\r\ntype of audience, etc. The Concept is at its turn related to a Collection, which groups the different concepts into a controlled vocabulary."@en . + . + "It links the Public Service to the Event class."@en . + "is grouped by"@en . + "Several Public Services may be associated with a particular Event and, likewise, the same Public Service may be associated with several different Events."@en . + . + "A Public Service related to the particular instance of the Public Service class."@en . + "related service"@en . + "This property is a sub-property of dct:relation."@en . + . . - "Optional class. This class represents a Business Event, which specialises Event. A Business Event is a specific situation or event in the lifecycle of a business that fulfils one or more needs or (legal) obligations of that business at this specific point in time. A Business Event requires a set of public services to be delivered and consumed in order for the associated business need(s) or obligation(s) to be fulfilled. Business Events are defined within the context of a particular Member State. In other words, a Business Event groups together a number of public services that need to be delivered for completing that particular event."@en . - "BusinessEvent"@en . + "A Business Event is a specific situation or event in the lifecycle of a business that fulfils one or more needs or (legal) obligations of that business at this specific point in time."@en . + "Business Event"@en . + "A Business Event requires a set of public services to be delivered and consumed in order for the associated business need(s) or obligation(s) to be fulfilled. Business Events are defined within the context of a particular Member State. In other words, a Business Event groups together a number of public services that need to be delivered for completing that particular event."@en . + . . - "Optional class. The Channel class represents the medium through which an Agent provides, uses or interacts in another way with a Public Service. Typical examples include online services, phone, walk-in centres etc."@en . - . + "A medium through which an Agent provides, uses or interacts in another way with a Public Service."@en . "Channel"@en . - . - . - _:genid3 . - . - _:genid4 . - "Classifications should be defined by an organisation/country as an outcome of a security assessment."@en . - . - . - . - . - "Constraints are requirements in themselves, since they impose prerequisites which influence the definition, use and/or fulfilment of the requirement. They represent hard conditions such as minimum or maximum expressions which can be used to evaluate pieces of information, the required age, income, involvement in activities, etc. An example from the eProcurement domain is a threshold as the minimum turnover required by the buying organisation to select the candidates. Note that CCCEV does not provide any specific guidance on when which kind of Requirement should be used. Users of this vocabulary should make decisions on this topic in their specific context."@en . + "Typical examples include online services, phone, walk-in centres etc."@en . + . + "A time during which the resource is not available."@en . + "availability restriction"@en . + "Like the Contact Point, a Channel may not be available at a certain time.\r\n

\r\nFor a simple description of the time use the description property of TemporalEntity.\r\n

\r\nFor more structured data use the model in Time Ontology, see an example."@en . + "For a simple description of the time use the description property of TemporalEntity.\r\n\r\nFor more structured data use the model in Time Ontology, see an example."@en . + . + "A time at which the resource is normally available."@en . + "The time at which the Contact Point is normally available."@en . + "opening hours"@en . + "Like the Contact Point, a Channel may be available at a certain time.\r\n

\r\nFor a simple description of the time use the description property of TemporalEntity.\r\n

\r\nFor more structured data use the model in Time Ontology, see an example."@en . + "For a simple description of the time use the description property of TemporalEntity.\r\n\r\nFor more structured data use the model in Time Ontology, see an example. This relation can be used to indicate exceptional closures such as being closed on public holidays."@en . + . + "The owner of a specific Channel through which a Public Service is being delivered."@en . + "owned by"@en . . - "Optional class. The Cost class represents any costs related to the execution of a Public Service that the Agent consuming it needs to pay."@en . - . + "The Cost class represents any costs related to the execution of a Public Service that the Agent consuming it needs to pay."@en . "Cost"@en . - "2018-07-09"^^ . - . - "The original CPSV-AP was prepared in the context of Action 1.3 \u2013 Accessing Member State information resources at European level \u2013 Catalogue of Services of the European Commission\u2019s Interoperability for European Public Administrations (ISA) programme. The CPSV-AP has been seen as a first step for creating a model for describing public services related to business events, to facilitate the set-up of catalogues of services in the context of the Services Directive. Update to version 2.2 finds its motivation in the experience of implementing version 2.1 of the CPSV-AP by different MSs and stakeholders and consequent requests received from them, as detailed in https://github.com/catalogue-of-services-isa/CPSV-AP/issues."@en . - . - . - "Core Public Service Vocabulary Application Profile"@en . - . - "cpsvap" . - . - . - . - . - . - . - . - . - "In general, Criteria are used for comparison, filtering or selection purposes. Criteria usually set minimum conditions (e.g. limits, intervals, thresholds, etc.) that need to be met in order to pass the requirements or to fulfil them to a certain degree or quality. The concept of Criteria is broader than the concept of Constraint since it covers more usages. The evaluation of the fulfilment is usually supported by the provision of Evidence. \nFor example in the eProcurement domain, the eProcurement Ontology defines different subclasses of Criterion such as exclusion grounds, selection criteria or award criteria. A concrete example of a Criterion is 'participation in a criminal organisation' which could also be considered as an exclusion ground criterion in the procurement domain or for requiring a public service."@en . - "Optional class. Not all public services are needed or usable by everyone. For example, the visa service operated by European countries is not needed by European citizens but is needed by some citizens from elsewhere, or public services offering unemployment benefits and grants are targeting specific societal groups. The CPSV reuses the Core Criterion and Core Evidence Vocabulary for this class. The CCCEV provides more details but the CriterionRequirement class has three mandatory properties."@en . - . - . - "CriterionRequirement"@en . - "The CPSV-AP v2.0 recommends to use as controlled vocabulary the European Publications Office's Currencies Named Authority List (NAL) (http://publications.europa.eu/mdr/authority/currency/index.html)."@en . . - "Cardinality [0..1]. This property represents the currency in which the Cost needs to be paid and the value of the Cost is expressed. The possible values for this property are described in a controlled vocabulary."@en . + "The currency in which the Cost needs to be paid and the value of the Cost is expressed."@en . "currency"@en . - . + "The possible values for this property are described in the controlled vocabulary \r\nCurrency Authority Table of Publications Office."@en . + . + "A numeric value indicating the amount of the Cost."@en . + "has value"@en . + . + "The costs created by the use of different Channels."@en . + "if accessed through"@en . + "For example, if accessed through an online service cf. accessed at a physical location, the cost can be linked to the channel using the If Accessed Through property."@en . + . + "It links the Cost class to one or more instances of the Public Organization class."@en . + "is defined by"@en . + "This property indicates which Public Organization is the Competent Authority for defining the costs associated with the delivery of a particular Public Service."@en . . - "Optional class. This class represents an event that can be of any type that triggers, makes use of, or in some way is related to, a Public Service. It is not expected to be used directly, rather, one or other of its subclasses should be used. The properties of the class are, of course, inherited by those subclasses."@en . - . + "This class represents an event that can be of any type that triggers, makes use of, or in some way is related to, a Public Service."@en . "Event"@en . - "Optional class. Evidence can be any resource - document, artefact \u2013 anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered. In some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s)."@en . + "It is not expected to be used directly, rather, one or other of its subclasses should be used. The properties of the class are, of course, inherited by those subclasses. The Event class is used as a hook either to a single related Public Service, such as diagnosis of illness being related to application for sickness benefit; or to a group of Public Services, such as all those related to the establishment of a new business."@en . + . + "The Public Service related to the Event."@en . + "has related service"@en . + "This property is a sub-property of dct:relation."@en . + . . - . + "The Evidence class is defined in the Core Criterion and Core Evidence vocabulary (CCCEV) as any resource that can prove that a specific requirement is met."@en . + "Proof that a Requirement is met."@en . "Evidence"@en . - . - . - _:genid5 . - . - _:genid6 . - "The categories agreed are left open but could for example specify the layout and content expected for an Evidence."@en . - . - . - . - "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. \n\nThe 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."@en . - . + "Although the wording of the definition is different, the semantics are an exact match for CPSV's Input class which it replaces.\r\n\r\nEvidence can be any resource - document, artefact - anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered.\r\n\r\nIn some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s)."@en . + "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. \r\n\r\nThe 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).\r\nThe 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."@en . + . + . + "Requirement for which the Evidence provides proof."@en . + "supports requirement"@en . + . + . + . . - . + "Information about the characteristics of an Evidence."@en . + "Evidence Type"@en . "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)."@en . - . + . + . + "Category to which the Evidence Type belongs."@en . + "evidence type classification"@en . + "The categories agreed are left open but could for example specify the layout and content expected for an Evidence. An example could be id cards."@en . + "The categories agreed are left open but could for example specify the layout and content expected for an Evidence."@en . + . + . + . + . + "The Life Event class represents an important event or situation in a citizen's life where public services are required."@en . + "Life Event"@en . + "Note on the scope: an individual will encounter any number of 'events'; in the general sense of the word. In the context of the CPSV-AP, the Life Event class only represents an event to which a Public Service is related. For example, a couple becoming engaged is not a CPSV-AP Life Event, getting married is, since only the latter has any relevance to public services."@en . + . + . + "An output can be any resource - document, artefact - anything produced by the Public Service. In the context of a Public Service, the output provides an official document or other artefact of the Competent Authority (Public Organization) that permits/authorises/entitles an Agent to (do) something."@en . + "Output"@en . + "In some cases, the Output of one Public Service will be used as evidence to fulfil a requirement of another Public Service. Such relationships should be described in the associated Rule(s)."@en . + . + "The Participation class allows to define roles within a certain context."@en . + "Participation"@en . + "The CPSV-AP recognises a common role connected with public services, i.e. the Competent Authority.\r\n

\r\nThis simple structure does not allow statements to be made about those participants, such as the start and end date of a contract, nor does it support the inclusion of other roles. The Participation class supports this extra complexity if required, for instance, the description of a service user or a service provider. The model is consistent with the CPOV which in turn is based on the W3C Organization Ontology that supports the common cases simply but allows the complex cases where necessary. The Participation class can be mapped to the Organization Ontology's Membership class that allows more complex relationships and richer metadata to be applied to a role filled by a given Agent."@en . + . + . + "The function of an Agent within a Participation."@en . + "role"@en . + "This should be provided using a controlled vocabulary.\r\nSince this is an extension mechanism for the CSPV-AP, the controlled vocabulary should be decided to suit local implementations."@en . + . + . + . + . + "The Agent involved in the Participation."@en . + "has participant"@en . + . + "Condition or prerequisite that is to be proven by Evidence."@en . + "Requirement"@en . + "Not all public services are needed or are used by everyone. For example, the visa service operated by European countries is not needed by European citizens but is needed by some citizens from elsewhere, or public services offering unemployment benefits and grants are targeting specific societal groups. The CPSV-AP reuses the Core Criterion and Core Evidence Vocabulary for this class.\r\n\r\nRequirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent.\r\nTo illustrate the notion: the European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy."@en . + "Requirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent. The European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy."@en . + . + . + "The Rules that the requiremens fulfils."@en . + "fulfils"@en . + . + "Evidence that supplies information, proof or support for the Requirement."@en . + "has supporting evidence"@en . + . + . + . + . + "Concessions are contracts for pecuniary interest by means of which one or more contracting authorities or contracting entities entrusts the execution of works, or the provision and the management of services, to one or more economic operators."@en . + "Service Concession Contract"@en . + "The object of such contracts is the procurement of works or services by means of a concession, the consideration of which consists in the right to exploit the works or services or in that right together with payment. Such contracts may, but do not necessarily, involve a transfer of ownership to contracting authorities or contracting entities, but contracting authorities or contracting entities always obtain the benefits of the works or services in\r\nquestion. The definition comes from the Directive 2014/23/EU."@en . + . + . + "It links a Service Concession Contract to relevant legislation or policy documents i.e.\r\nthe Legal Resource under which the Service Concession Contracts are being defined."@en . + "established under"@en . + . + "It links a Service Concession Contract with the Contracting Authority which is ultimately responsible for a public service."@en . + "has contracting authority"@en . + . + "It links a Service Concession Contract with the Economic Operator in charge for the provision and the management of public services."@en . + "has economic operator"@en . + . + "The participation in which an Agent is involved."@en . + "participates"@en . + "The Participation class facilitates the detailed description of how an Agent participates in or interacts with a Public Service and may include temporal and spatial information."@en . + . + "Information Requirement"@en . + "Requested data that is to be proven by Evidence."@en . + . + . + "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."@en . + . + "bias"@en . + "Parameter used to adjust the evaluation of the Criterion."@en . + . + . + . + "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."@en . + . + "confidentiality level type"@en . + "Security classification assigned to an Evidence e.g. classified, sensitive, public."@en . + . + . + . + "Classifications should be defined by an organisation/country as an outcome of a security assessment."@en . + . + "constrains"@en . + "Information Concept about which a Constraint expresses a limitation."@en . + . + . + . + "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."@en . . - _:genid7 . + "expression of expected value"@en . + "Formulation in a formal language of the expected value(s) for the Information Concept which is aligned with the concepts from the Requirements defined and must be respected by the supplied Supported Values ."@en . + . . - _:genid8 . - "The property encapsulates all kind of expectations on the required and provided values one could have. \nThis may range from representational expectations such as the type (e.g. the value is expected to be a xsd:decimal) to expectations that reduce the allowed value range. Commonly this is done using min or max bounderary expressions (e.g. the maximum value is 1 Million Euro).\nOther usage could be to harmonise the supplied values (e.g. rounding, turning to percentages) to facilitate further processing.\n\nImplementers are free to use their own approach for defining the expected values in more details. For instance, this can be by defining their own datatypes extending or encapsulating common xsd datatypes. But also by using more complex languages such as XPath, Object Constraint Language (OCL), JavaScript and Rule Interchange Format (RIF).\n\nBecause of this freedom, implementers are recommended to well-document their usage of this property (and related information). \n"@en . - . - "Cardinality [0..1]. This property represents an Address related to an Agent. Asserting the address relationship implies that the Agent has an Address."@en . - "hasAddress"@en . - . - . - "Cardinality [0..n]. This property links the Public Service to any Channel through which an Agent provides, uses or otherwise interacts with the Public Service, such as an online service, phone number or office."@en . - "hasChannel"@en . - . - . - "Cardinality [1..1]. This property links a Public Service to a Public Organisation, which is the responsible Agent for the delivery of the Public Service. Whether the particular Public Organisation provides the public service directly or outsources it is not relevant. The Public Organisation that is the Competent Authority of the service is the one that is ultimately responsible for managing and providing the public service."@en . - "hasCompetentAuthority"@en . - . - . - "Cardinality [0..n]. A contact point for the service is almost always helpful. The value of this property, the contact information itself, should be provided using VCard. Note that the contact information should be relevant to the Public Service which may not be the same as contact information for the Competent Authority or any Participant."@en . - "hasContactPoint"@en . - . - . - "Cardinality [0..n]. The Has Cost property links a Public Service to one or more instances of the Cost class. It indicates the costs related to the execution of a Public Service for the citizen or business related to the execution of the particular Public Service. Where the cost varies depending on the channel through which the service is accessed, it can be linked to the channel using the If Accessed Through relationship."@en . - "hasCost"@en . - . - . - "Cardinality [0..n]. Links a Public Service to a class that describes the criteria for needing or using the service, such as residency in a given location, being over a certain age etc. The Criterion class is defined in the Core Criterion and Core Evidence Vocabulary."@en . - "hasCriterion"@en . - . - . - "Cardinality [0..n]. The Has Legal Resource property links a Public Service to a Legal Resource. It indicates the Legal Resource (e.g. legislation) to which the Public Service relates, operates or has its legal basis."@en . - "hasLegalResource"@en . - . - . - "Cardinality [0..n]. The CPSV-AP defines the three basic roles of Competent Authority, Service Provider and Service User but this simple model can be extended if required using the Has Participation property that links to the Participation class ."@en . - "hasParticipation"@en . - . - . + . + "The property encapsulates all kind of expectations on the required and provided values one could have. \r\nThis may range from representational expectations such as the type (e.g. the value is expected to be a xsd:decimal) to expectations that reduce the allowed value range. Commonly this is done using min or max bounderary expressions (e.g. the maximum value is 1 Million Euro).\r\nOther usage could be to harmonise the supplied values (e.g. rounding, turning to percentages) to facilitate further processing.\r\n\r\nImplementers are free to use their own approach for defining the expected values in more details. For instance, this can be by defining their own datatypes extending or encapsulating common xsd datatypes. But also by using more complex languages such as XPath, Object Constraint Language (OCL), JavaScript and Rule Interchange Format (RIF).\r\nBecause of this freedom, implementers are recommended to well-document their usage of this property (and related information). \r\n\r\n\r\n \r\n\r\n"@en . + . + "has concept"@en . + "Information Concept for which a value is expected by the Requirement."@en . + . + . + . + "Information Concepts defined for specific Requirements also represent the basis for specifying the Supported Value an Evidence should provide."@en . + . + "has evidence type list"@en . + "Evidence Type List that specifies the Evidence Types that are needed to meet the Requirement."@en . + . + . + . + "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."@en . . - _:genid9 . + "has qualified relation"@en . + "Described and/or categorised relation to another Requirement."@en . + . . - _:genid10 . + . "This property leaves the possiblity to define a qualified relation from Requirement to Information Requirement or Constraint as well as a qualified relation from Requirement to Requirement. A use case would be to specialize an EU requirement in Member States' specific requirements."@en . - . . - _:genid11 . + "has requirement"@en . + "A more specific Requirement that is part of the Requirement."@en . + . . - _:genid12 . - . - "Cardinality [0..1]. Where the cost varies depending on the channel used, for example, if accessed through an online service cf. accessed at a physical location, the cost can be linked to the channel using the If Accessed Through property."@en . - "ifAccesseThrough"@en . - . - . - . - . - "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."@en . - . - . - . - . - "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."@en . - . - "Cardinality [0..n]. The Is Classified By property allows to classify the Public Service with any Concept, other than those already foreseen and defined explicitely in the CPSV-AP (Thematic Area, Sector, \u2026). It is a generic property which can be further specialised to make the classification explicit, for instance for classifying public services according level of digitisation, type of audience \u2026 The Concept is at its turn related to a Collection, which groups the different concepts into a controlled vocabulary."@en . - "isClassifiedBy"@en . - . - . - "Cardinality [0..n]. This property links the Cost class with one or more instances of the Public Organisation class. This property indicates which Public Organisation is the Competent Authority for defining the costs associated with the delivery of a particular Public Service."@en . - "isDefinedBy"@en . - . - . - "Cardinality [0..n]. The Is Described At property links a Public Service to the dataset where it belongs to. It is used to track the metadata of the origin of the public service descriptions."@en . - "isDescribedAt"@en . - . - . - "Cardinality [0..n]. This property links the Public Service to the Event class. Several Public Services may be associated with a particular Event and, likewise, the same Public Service may be associated with several different Events."@en . - "isGroupedBy"@en . - . - . - . - _:genid13 . - . - _:genid14 . - "Agents transmitting Evidence are usually the Agents requesting the Evidence or service providers acting on behalf of the requesting Agents such as software developer companies."@en . - . + . + . + "is derived from"@en . + "Reference Framework on which the Requirement is based, such as a law or regulation."@en . + . + . + . + "Note that a Requirement can have several Reference Frameworks from which it is derived."@en . . - _:genid15 . + "is requirement of"@en . + "A reference between a sub-Requirement and its parent Requirement."@en . + . . - _:genid16 . - "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.\n\nIn the case where the purpose is to link the two Requirements without additional information, the simple relationship as proposed here can be directly used."@en . - . + . + "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.\r\n\r\nIn the case where the purpose is to link the two Requirements without additional information, the simple relationship as proposed here can be directly used."@en . . - _:genid17 . + "is specified in"@en . + "Evidence Type List in which the Evidence Type is included."@en . + . . - _:genid18 . - . - "Optional class. The Life Event class represents an important event or situations in a citizen's life where public services may be required. Note the scope: an individual will encounter any number of 'events' in the general sense of the word. In the context of the CPSV-AP, the Life Event class only represents an event for which a Public Service is related. For example, a couple becoming engaged is not a CPSV-AP Life Event, getting married is, since only the latter has any relevance to public services."@en . - "LifeEvent"@en . - . - "Optional class. Outputs can be any resource - document, artefact \u2013 anything produced by the Public Service. In the context of a Public Service, the output provides an official document or other artefact of the Competent Authority (Public Organisation) that permits/authorises/entitles an Agent to (do) something."@en . - . - "Output"@en . - . - "Cardinality [0..n]. This property links the Channel class with one or more instances of the Public Organisation class. This property indicates the owner of a specific Channel through which a Public Service is being delivered."@en . - "ownedBy"@en . - . - "Optional class. The CPSV-AP recognises a common role connected with public services, i.e. the Competent Authority. However, this simple structure does not allow statements to be made about those participants, such the start and end date of a contract, nor does it support the inclusion of other roles. The Participation class supports this extra complexity if required, for instance, the description of a service user or a service provider. The model is consistent with the CPOV which in turn is based on the W3C Organization Ontology that supports the common cases simply but allows the complex cases where necessary. The Participation class can be mapped to the Organization Ontology\u2019s Membership class that allows more complex relationships and richer metadata to be applied to a role filled by a given Agent."@en . - . - . - "Participation"@en . - . - "Cardinality [0..n]. This property links an Agent to the Participation class. The Participation class facilitates the detailed description of how an Agent participates in or interacts with a Public Service and may include temporal and spatial constraints on that participation."@en . - "playsRole"@en . - . - . - "Cardinality [0..1]. The value of this property is the (estimated) time needed for executing a Public Service. The actual information is provided using the ISO8601 syntax for durations."@en . - "processingTime"@en . - . - . + . . - _:genid19 . + "provides value for"@en . + "Information Concept for which the Supported Value provides a value."@en . + . . - _:genid20 . - "Mandatory class. The CPSV-AP reuses the Core Public Organisation Vocabulary that defines the concept of a Public Organisation and associated properties and relationships. It is largely based on the W3C Organization Ontology."@en . - . - . - "PublicOrganisation"@en . - "Optional class. The CPSV-AP reuses the Data Catalog Vocabulary (DCAT) for the creation of the Public Service Dataset class. The Public Service Dataset, is a specialisation of the Dataset class of the Data Catalog Vocabulary (DCAT) and inherits all its properties. The class describes the metadata of where the dataset is being described, for instance on a regional public service portal or a national eGovernment portal."@en . - . - "PublicServiceDataset"@en . - . + . . - _:genid21 . + "query"@en . + "Search statement that allows the value for the Information Concept to be retrieved from the Evidence data."@en . + . . - _:genid22 . - "The query must be executed on the business data provided by the supporting Evidence. In order to be able to evaluate the query on the provided data, the format of the provided data must be aligned with the query expression. For instance if the provided data is XML, a query in XPath could be expected. This alignment is part of the implementation agreements that implementors must make."@en . - . - . - . - "Usual Reference Frameworks are legal and non-legal specifications. Examples include procedures, tendering legislation, etc."@en . - . - . - . - "Requirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent. The European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy."@en . - . - "Cardinality [1..n]. Provides the role played. This should be provided using a controlled vocabulary. Since this is an extension mechanism for the CPSV-AP, the controlled vocabulary should be decided to suit local implementations."@en . - "role"@en . - . - "The CPSV-AP v2.0 recommends to use as controlled vocabulary the List of NACE codes (http://ec.europa.eu/competition/mergers/cases/index/nace_all.html)."@en . - . - "Cardinality [0..n]. This property represents the industry or sector a Public Service relates to, or is intended for. For example: environment, safety, housing. Note that a single Public Service may relate to multiple sectors. The possible values for this property are provided as a controlled vocabulary."@en . - "sector"@en . - . - . + . + "The query must be executed on the business data provided by the supporting Evidence. In order to be able to evaluate the query on the provided data, the format of the provided data must be aligned with the query expression. For instance if the provided data is XML, a query in XPath could be expected. This alignment is part of the implementation agreements that implementors must make."@en . . - _:genid23 . + "specifies evidence type"@en . + "Evidence Type included in this Evidence Type List."@en . + . . - _:genid24 . - . - . - . - "The notion of Supported Value is closely related to actual data exchange between two parties: \n(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 \n(b) the Evidence provider, i.e. the Agent supplying information to an information request expressed as Requirements.\n\nThe 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. \n\nThe 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.\n\nImplementers are free to choose their language. It is recommended to document the made agreements well.\n"@en . - . - . - _:genid25 . - . - _:genid26 . - . + . + . + "supports concept"@en . + "Information Concept providing facts found/inferred from the Evidence."@en . + . + . + . + "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\"."@en . . - _:genid27 . + "supports value"@en . + "Supported Value that the Evidence contains."@en . + . . - _:genid28 . - "Cardinality [0..n]. This property represents the Thematic Area of a Public Service as described in a controlled vocabulary, for instance social protection, health, recreation, culture and religion, family, traveling economic affairs, tax, staff, environment..."@en . - . - "thematicArea"@en . - . - . + . + . + "validity period"@en . + "Period of Time during which the Evidence holds true or has force."@en . + . + . + . . - _:genid31 . + "validity period constraint"@en . + "Temporal condition on the validity period of the Evidence Type."@en . + . . - _:genid32 . + . "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."@en . - . - . - _:genid29 . - . - _:genid30 . . - "Cardinality [0..1]. This property represents a numeric value indicating the amount of the Cost."@en . "value"@en . - . - . + "Value for the Information Concept that the Evidence supports."@en . + . + . + . + . + "weight"@en . + "Relative importance of the Criterion."@en . + . + . + . + "The weight must be between 0 and 1. Usually, all Criteria can be integrated within a weighted sum equal to 1."@en . . - _:genid37 . + "weighting consideration description"@en . + "Explanation of how the weighting of a Criterion is to be used."@en . + . . - _:genid38 . + . "This description gives the view of the creator of the Criterion weights on how to interpret and use them during the evaluation process."@en . - . . - _:genid39 . + "weighting type"@en . + "Indication of how the weight should be interpreted in a complex evaluation expression, e.g. as a percentage in an evaluation expression."@en . + . . - _:genid40 . - "An existing codelist http://publications.europa.eu/resource/authority/number-weight\nExample see: https://docs.ted.europa.eu/eforms/0.3.0/index.html#awardCriteriaSection"@en . - . - . - _:genid35 . - . - _:genid36 . - "The weight must be between 0 and 1. Usually, all Criteria can be integrated within a weighted sum equal to 1."@en . + . + "An existing codelist which can be used is OP's Number weigth controlled vocabulary"@en . + . + "Constraint"@en . + "Limitation applied to an Information Concept."@en . + . + . + "Constraints are requirements in themselves, since they impose prerequisites which influence the definition, use and/or fulfilment of the requirement. They represent hard conditions such as minimum or maximum expressions which can be used to evaluate pieces of information, the required age, income, involvement in activities, etc. An example from the eProcurement domain is a threshold as the minimum turnover required by the buying organisation to select the candidates. Note that CCCEV does not provide any specific guidance on when which kind of Requirement should be used. Users of this vocabulary should make decisions on this topic in their specific context."@en . + . + "Evidence Type List"@en . + "Group of Evidence Types for conforming to a Requirement."@en . + . + "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. \r\n\r\nThe 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."@en . + . + "Criterion"@en . + "Condition for evaluation or assessment."@en . + . + . + "In general, Criteria are used for comparison, filtering or selection purposes. Criteria usually set minimum conditions (e.g. limits, intervals, thresholds, etc.) that need to be met in order to pass the requirements or to fulfil them to a certain degree or quality. The concept of Criteria is broader than the concept of Constraint since it covers more usages. The evaluation of the fulfilment is usually supported by the provision of Evidence. \r\nFor example in the eProcurement domain, the eProcurement Ontology defines different subclasses of Criterion such as exclusion grounds, selection criteria or award criteria. A concrete example of a Criterion is 'participation in a criminal organisation' which could also be considered as an exclusion ground criterion in the procurement domain or for requiring a public service."@en . + . + "Supported Value"@en . + "Value for an Information Concept that is provided by an Evidence."@en . + . + "The notion of Supported Value is closely related to actual data exchange between two parties: \r\n(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 \r\n(b) the Evidence provider, i.e. the Agent supplying information to an information request expressed as Requirements.\r\n\r\nThe 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. \r\n\r\nThe 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.\r\n\r\nImplementers are free to choose their language. It is recommended to document the made agreements well.\r\n"@en . + . + "Information Concept"@en . + "Piece of information that the Evidence provides or the Requirement needs."@en . + . + "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."@en . + . + "accessibility"@en . + "Information about how the Public Event can be approached, reached or entered, in particular for people with special needs."@en . + . + . + . + "This property may be provided in multiple languages with multiple instances of the accessibility property."@en . + . + "audience"@en . + "The target group of people for whom the Public Event is created."@en . + . + . + . + . + "event number"@en . + "The sequence position of the Public Event."@en . + . + . + . + "Examples could be the ''4th\" or \"2022\"."@en . + . + "event status"@en . + " This property defines the overall status of the event."@en . + . + . + . + "The recomended code list is the Event Status Controlled vocabulary maintained by the Publications Office of the EU."@en . + . + "expected number of participants"@en . + "The number of participants expected to participate in the event."@en . + . + . + . + . + "format"@en . + "A plan of organisation or arrangement of the Public Event."@en . + . + . + . + "Examples include conference call, physical meeting or hybrid."@en . + . + "registration page"@en . + "A web page that provides means to attend the Public Event."@en . + . + . + . + . + "Public Event"@en . + "Something that happens at a particular place and time,\r\norganised by one or more agents for a particular purpose, and is of interest to a general\r\n audience. This definition excludes natural events such as earthquakes and volcanic \r\neruptions."@en . + . + . + "Accounting Document"@en . + "Financial and non-financial information as a result of an activity of an organisation."@en . + . + "Accounting documents, might include:\r\n
    \r\n
  • Financial statements (incl. the list of participating interests, subsidiary undertakings and associated undertakings, their registered office address and proportion of capital held), audit reports.
    • \r\n
  • Non-financial statements, management reports and other statements or reports.
    • \r\n
  • Annual financial reports.
    • \r\n
"@en . + . + "registration date"@en . + "The date on which the legal entity has registered in some jurisdiction for regulatory and / or for tax purposes."@en . + . + . + . + . + "code"@en . + "The classification of the administrative unit."@en . + . + . + . + . + "coordinates"@en . + "\tA list of geographic coordinates that define the extent of the Geometry."@en . + . + . + . + "Can be expressed as longitude, latitude, elevation."@en . + . + "crs"@en . + "An identifier for the coordinate reference system."@en . + . + . + . + "Can be a coordinate-based local, regional or global system used to locate geographical entities."@en . + . + "geometry type"@en . + "The classification of the Geometry."@en . + . + . + . + "Can be a point, line or polygon."@en . + . + "latitude"@en . + "The geographic coordinate that specifies the north / south position of the Geomerty on the Earth's surface."@en . + . + . + . + . + "level"@en . + "The level of the administrative unit in the hierarchy."@en . + . + . + . + "The recommended code list to indicate the level of an Admin Unit is the Administrative territorial unit type Controlled Vocabulary maintained by the Publications Office of the EU. "@en . + . + "longitude"@en . + "The geographic coordinate that specifies the east / west position of the Geometry on the Earth's surface."@en . + . + . + . + . + "Administrative Unit"@en . + "A detailed administrative unit organized in a hierarchy."@en . + . + "This class should be used whenever a classification mechanism is in place, in alternative to the properties adminUnitL1 and adminUnitL2 of the Address class which allow free text."@en . \ No newline at end of file diff --git a/releases/m8g/m8g.rdf b/releases/m8g/m8g.rdf index 8bacbb5..78669c6 100644 --- a/releases/m8g/m8g.rdf +++ b/releases/m8g/m8g.rdf @@ -1,731 +1,696 @@ - - - - - - - - - - - - - - - - - - - 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". [https://trade.ec.europa.eu/doclib/docs/2018/september/tradoc_157319.pdf] -When quantified, this systematic error can be removed. - - - - - - Optional class. This class represents a Business Event, which specialises Event. A Business Event is a specific situation or event in the lifecycle of a business that fulfils one or more needs or (legal) obligations of that business at this specific point in time. A Business Event requires a set of public services to be delivered and consumed in order for the associated business need(s) or obligation(s) to be fulfilled. Business Events are defined within the context of a particular Member State. In other words, a Business Event groups together a number of public services that need to be delivered for completing that particular event. - - - BusinessEvent - - - - - - Optional class. The Channel class represents the medium through which an Agent provides, uses or interacts in another way with a Public Service. Typical examples include online services, phone, walk-in centres etc. - - - - - - Channel - - - - - - - - - - - - - - - - - - Classifications should be defined by an organisation/country as an outcome of a security assessment. - - - - - - - - - - - - - - - Constraints are requirements in themselves, since they impose prerequisites which influence the definition, use and/or fulfilment of the requirement. They represent hard conditions such as minimum or maximum expressions which can be used to evaluate pieces of information, the required age, income, involvement in activities, etc. An example from the eProcurement domain is a threshold as the minimum turnover required by the buying organisation to select the candidates. Note that CCCEV does not provide any specific guidance on when which kind of Requirement should be used. Users of this vocabulary should make decisions on this topic in their specific context. - - - - - - Optional class. The Cost class represents any costs related to the execution of a Public Service that the Agent consuming it needs to pay. - - - - - - Cost - - - 2018-07-09 - - - - - - The original CPSV-AP was prepared in the context of Action 1.3 – Accessing Member State information resources at European level – Catalogue of Services of the European Commission’s Interoperability for European Public Administrations (ISA) programme. The CPSV-AP has been seen as a first step for creating a model for describing public services related to business events, to facilitate the set-up of catalogues of services in the context of the Services Directive. Update to version 2.2 finds its motivation in the experience of implementing version 2.1 of the CPSV-AP by different MSs and stakeholders and consequent requests received from them, as detailed in https://github.com/catalogue-of-services-isa/CPSV-AP/issues. - - - - - - - - - Core Public Service Vocabulary Application Profile - - - - - - cpsvap - - - - - - - - - - - - - - - - - - - - - - - - - - - In general, Criteria are used for comparison, filtering or selection purposes. Criteria usually set minimum conditions (e.g. limits, intervals, thresholds, etc.) that need to be met in order to pass the requirements or to fulfil them to a certain degree or quality. The concept of Criteria is broader than the concept of Constraint since it covers more usages. The evaluation of the fulfilment is usually supported by the provision of Evidence. -For example in the eProcurement domain, the eProcurement Ontology defines different subclasses of Criterion such as exclusion grounds, selection criteria or award criteria. A concrete example of a Criterion is 'participation in a criminal organisation' which could also be considered as an exclusion ground criterion in the procurement domain or for requiring a public service. - - - Optional class. Not all public services are needed or usable by everyone. For example, the visa service operated by European countries is not needed by European citizens but is needed by some citizens from elsewhere, or public services offering unemployment benefits and grants are targeting specific societal groups. The CPSV reuses the Core Criterion and Core Evidence Vocabulary for this class. The CCCEV provides more details but the CriterionRequirement class has three mandatory properties. - - - - - - - - - CriterionRequirement - - - The CPSV-AP v2.0 recommends to use as controlled vocabulary the European Publications Office's Currencies Named Authority List (NAL) (http://publications.europa.eu/mdr/authority/currency/index.html). - - - - - - Cardinality [0..1]. This property represents the currency in which the Cost needs to be paid and the value of the Cost is expressed. The possible values for this property are described in a controlled vocabulary. - - - currency - - - - - - - - - Optional class. This class represents an event that can be of any type that triggers, makes use of, or in some way is related to, a Public Service. It is not expected to be used directly, rather, one or other of its subclasses should be used. The properties of the class are, of course, inherited by those subclasses. - - - - - - Event - - - Optional class. Evidence can be any resource - document, artefact – anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered. In some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s). - - - - - - - - - Evidence - - - - - - - - - - - - - - - - - - The categories agreed are left open but could for example specify the layout and content expected for an Evidence. - - - - - - - - - - - - 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. - - - - - - - - - - - - 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). - - - - - - - - - - - - - - - - - - The property encapsulates all kind of expectations on the required and provided values one could have. + + + + + Image Object + A logo to describe / represent an entity. + + + + + Public Organisation + Public Organization + An Organization that is defined as being part of the public sector by a legal framework at any level. + + + Organizations which exist to provide services for its citizens and companies are called Public Organizations. The Public Organization class represents the organization. One organization may comprise several sub-organizations and any organization may have one or more organizational units. Each of these is described using the same properties and relationships. +<br/><br/> +This definition is consistent with the more detailed definition of a "public sector body" as given in the <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32019L1024&qid=1706001352901">PSI Directive</a>: "the State, regional or local authorities, bodies governed by public law and associations formed by one or several such authorities or one or several such bodies governed by public law". It further defines a body governed by public law as any body "(a) established for the specific purpose of meeting needs in the general interest, not having an industrial or commercial character; and (b) having legal personality; and (c) financed, for the most part by the State, or regional or local authorities, or other bodies governed by public law; or subject to management supervision by those bodies; or having an administrative, managerial or supervisory board, more than half of whose members are appointed by the State, regional or local authorities or by other bodies governed by public law". + Organizations which exist to provide services for its citizens and companies are called Public Organizations. The Public Organization class represents the organization. One organization may comprise several sub-organizations and any organization may have one or more organizational units. Each of these is described using the same properties and relationships. +<br/><br/> +This definition is consistent with the more detailed definition of a "public sector body" as given in the PSI Directive: "the State, regional or local authorities, bodies governed by public law and associations formed by one or several such authorities or one or several such bodies governed by public law". It further defines a body governed by public law as any body "(a) established for the specific purpose of meeting needs in the general interest, not having an industrial or commercial character; and (b) having legal personality; and (c) financed, for the most part by the State, or regional or local authorities, or other bodies governed by public law; or subject to management supervision by those bodies; or having an administrative, managerial or supervisory board, more than half of whose members are appointed by the State, regional or local authorities or by other bodies governed by public law". + + + + Reference Framework + Legislation or official policy from which Requirements are derived. + + Usual Reference Frameworks are legal and non-legal specifications. Examples include procedures, tendering legislation, etc. + + + + contact page + A web page that could be used to reach out the Contact Point. + + + + + + + has email + An electronic address through which the Contact Point can be contacted. + + + + + + + frequency + The recurrence of an instant or period. + + + + It is recommended to use the frequency from an existing vocabulary like the <a href="https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/frequency">Frequency</a> from the Publications Office. + + + + has telephone + A telephone number through which the Contact Point can be contacted. + + + + + + + Contact Point + Information (e.g. e-mail address, telephone number) of a person or department through which the user can get in touch with. + + The Core Public Organization Vocabulary defines properties for telephone number, e-mail address and opening hours although it is noteworthy that the class is based on schema.org's <a href="http://schema.org/ContactPoint"> ContactPoint </a> class that has additional properties that some implementations may find useful. + Similarly to the Channel class, a Contact Point may have regular opening hours that are then overridden by, for example, public holidays, using the Temporal Entity class. + + + + date of birth + The point in time on which the Person was born. + + + + The date of birth could be expressed as date, gYearMonth or gYear, example: +<ul> +<li>- 1980-09-16^^xs:date</li> +<li>- 1980-09^^xs:gYearMonth</li> +<li>- 1980^^xs:gYear</li> +</ul> + + + + date of death + The point in time on which the Person died. + + + + The date of birth could be expressed as date, gYearMonth or gYear, example: +<ul> +<li>- 1980-09-16^^xs:date</li> +<li>- 1980-09^^xs:gYearMonth</li> +<li>- 1980^^xs:gYear</li> +</ul> + + + + gender + The identities, expressions and societal roles of the Person. + + + + The gender of an individual should be recorded using a controlled vocabulary that is appropriate for the specific context. In some cases, the chromosomal or physical state of an individual will be more important than the gender that they express, in others the reverse will be true. What is always important is that the controlled vocabulary used to describe an individual's gender is stated explicitly. + + + + matronymic name + Name based on the given name of the Person's mother. + + + + + + + sex + The organism's biological sex. + + + + The recommended controlled vocabulary for this property is <a href="https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/human-sex">the sex authority table of the Publications Office.</a> + + + + Generic date + The date data type is the union of xs:date, xs:gYearMonth and xs:gYear + + + + + The (estimated) time needed for executing a Public Service. The actual information is provided using the ISO8601 syntax for durations. + The (estimated) time needed for executing a Public Service which may depend on the Channel chosen. + processing time + Some examples are provided below: +Duration Syntax - Syntax +5 years - P5Y +1 month - P1M +3 days - P3D +2 days 4 hours - P2DT4H + +Durations begin with an uppercase P followed by the number and the relevant designator, formally: P[n]Y[n]M[n]DT[n]H[n]M[n]S, where Y is for years, M for months etc. + +Note that days and times are separated by an uppercase T which also +disambiguates M as meaning month (P2M means 2 months) or minute (PT2M means 2 minutes). Durations may also be defined as a number of weeks so P4W means 4 weeks. A full explanation is provided in the <a href="https://en.wikipedia.org/wiki/ISO_8601#Durations">Wikipedia page</a> that references the official <a href="https://www.iso.org/standard/40874.html">ISO standard</a>. + +This approach is consistent with both schema.org and the W3C OWL Time Ontology. + The actual information is provided using the ISO8601 syntax for durations. + + + + The industry or sector a Public Service relates to, or is intended for. + sector + For example: environment, safety, housing. Note that a single Public Service may relate to multiple sectors. The possible values for this property are provided as a controlled vocabulary. The possible values for this property are described in the controlled vocabulary <a href=" https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/data-theme">Data theme</a> Authority Table of the Publications Office. + + + + The Thematic Area of a Public Service. + thematic area + For example: social protection, health, recreation, culture and religion, family, traveling economic affairs, tax, staff, environment, etc. + + + + The main contact information of the resource. + contact point + Note that the contact information should be relevant to the Public Service which may not be the same as contact information for the Competent Authority or any Participant. + + + + It links the Public Service to any Channel through which an Agent provides, uses or otherwise interacts with the Public Service, such as an online service, phone number or office. + has channel + + + + It links a Public Service to a Public Organization, which is the responsible Agent for the delivery of the Public Service. + has competent authority + Whether the particular Public Organization provides the public service directly or outsources it is not relevant. The Public Organization that is the Competent Authority of the service is the one that is ultimately responsible for managing and providing the public service. The term Competent Authority is defined in the Services Directive (2006/123/EC) in the following way: "Any body or authority which has a supervisory or regulatory role in a Member State in relation to service activities, including, in particular, administrative authorities, including courts acting as such, professional bodies, and those professional associations or other professional organisations which, in the exercise of their legal autonomy, regulate in a collective manner access to service activities or the exercise thereof". + + + + It indicates the costs related to the execution of a Public Service for the citizen or business related to the execution of the particular Public Service. + has cost + Where the cost varies depending on the channel through which the service is accessed, it can be linked to the channel using the If Accessed Through relationship. + + + + It links a Public Service to one or more instances of the EvidenceType class. + has input type + + + + It indicates the Legal Resource (e.g. legislation) to which the Public Service relates, operates or has its legal basis. + has legal resource + + + + The way how a resource is organized. + has participation + The Participation class facilitates the detailed description of how an Agent participates in or interacts with a Public Service and may include temporal and spatial information. + + + + It links a Public Service to a class that describes the Requirement. + holds requirement + Usage: It describes the needing or using the service, such as residency in a given location, being over a certain age etc. The Requirement class is defined in the Core Criterion and Core Evidence Vocabulary. + + + + It allows to classify the Public Service with any Concept other than those already foreseen and defined explicitly in the CPSV-AP (Thematic Area, Sector, etc.). + is classified by + It is a generic property which can be further specialised to make the classification explicit, for instance for classifying public services according level of digitisation, +type of audience, etc. The Concept is at its turn related to a Collection, which groups the different concepts into a controlled vocabulary. + + + + It links the Public Service to the Event class. + is grouped by + Several Public Services may be associated with a particular Event and, likewise, the same Public Service may be associated with several different Events. + + + + A Public Service related to the particular instance of the Public Service class. + related service + This property is a sub-property of dct:relation. + + + + + A Business Event is a specific situation or event in the lifecycle of a business that fulfils one or more needs or (legal) obligations of that business at this specific point in time. + Business Event + A Business Event requires a set of public services to be delivered and consumed in order for the associated business need(s) or obligation(s) to be fulfilled. Business Events are defined within the context of a particular Member State. In other words, a Business Event groups together a number of public services that need to be delivered for completing that particular event. + + + + + A medium through which an Agent provides, uses or interacts in another way with a Public Service. + Channel + Typical examples include online services, phone, walk-in centres etc. + + + + A time during which the resource is not available. + availability restriction + Like the Contact Point, a Channel may not be available at a certain time. +<br/><br/> +For a simple description of the time use the description property of TemporalEntity. +<br/><br/> +For more structured data use the model in Time Ontology, see an <a href="https://www.w3.org/TR/owl-time/#dtd-vs-dt">example</a>. + For a simple description of the time use the description property of TemporalEntity. + +For more structured data use the model in Time Ontology, see an <a href="https://www.w3.org/TR/owl-time/#dtd-vs-dt">example</a>. + + + + A time at which the resource is normally available. + The time at which the Contact Point is normally available. + opening hours + Like the Contact Point, a Channel may be available at a certain time. +<br/><br/> +For a simple description of the time use the description property of TemporalEntity. +<br/><br/> +For more structured data use the model in Time Ontology, see an <a href="https://www.w3.org/TR/owl-time/#dtd-vs-dt">example</a>. + For a simple description of the time use the description property of TemporalEntity. + +For more structured data use the model in Time Ontology, see an <a href="https://www.w3.org/TR/owl-time/#dtd-vs-dt">example</a>. This relation can be used to indicate exceptional closures such as being closed on public holidays. + + + + The owner of a specific Channel through which a Public Service is being delivered. + owned by + + + + The Cost class represents any costs related to the execution of a Public Service that the Agent consuming it needs to pay. + Cost + + + + The currency in which the Cost needs to be paid and the value of the Cost is expressed. + currency + The possible values for this property are described in the controlled vocabulary +<a href="https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/currency">Currency</a> Authority Table of Publications Office. + + + + A numeric value indicating the amount of the Cost. + has value + + + + The costs created by the use of different Channels. + if accessed through + For example, if accessed through an online service cf. accessed at a physical location, the cost can be linked to the channel using the If Accessed Through property. + + + + It links the Cost class to one or more instances of the Public Organization class. + is defined by + This property indicates which Public Organization is the Competent Authority for defining the costs associated with the delivery of a particular Public Service. + + + + This class represents an event that can be of any type that triggers, makes use of, or in some way is related to, a Public Service. + Event + It is not expected to be used directly, rather, one or other of its subclasses should be used. The properties of the class are, of course, inherited by those subclasses. The Event class is used as a hook either to a single related Public Service, such as diagnosis of illness being related to application for sickness benefit; or to a group of Public Services, such as all those related to the establishment of a new business. + + + + The Public Service related to the Event. + has related service + This property is a sub-property of dct:relation. + + + + + The Evidence class is defined in the Core Criterion and Core Evidence vocabulary (CCCEV) as any resource that can prove that a specific requirement is met. + Proof that a Requirement is met. + Evidence + Although the wording of the definition is different, the semantics are an exact match for CPSV's Input class which it replaces. + +Evidence can be any resource - document, artefact - anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered. + +In some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s). + 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. + + + + + Requirement for which the Evidence provides proof. + supports requirement + + + + + + + Information about the characteristics of an Evidence. + Evidence Type + 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). + + + + + Category to which the Evidence Type belongs. + evidence type classification + The categories agreed are left open but could for example specify the layout and content expected for an Evidence. An example could be id cards. + The categories agreed are left open but could for example specify the layout and content expected for an Evidence. + + + + + + + The Life Event class represents an important event or situation in a citizen's life where public services are required. + Life Event + Note on the scope: an individual will encounter any number of 'events'; in the general sense of the word. In the context of the CPSV-AP, the Life Event class only represents an event to which a Public Service is related. For example, a couple becoming engaged is not a CPSV-AP Life Event, getting married is, since only the latter has any relevance to public services. + + + + + An output can be any resource - document, artefact - anything produced by the Public Service. In the context of a Public Service, the output provides an official document or other artefact of the Competent Authority (Public Organization) that permits/authorises/entitles an Agent to (do) something. + Output + In some cases, the Output of one Public Service will be used as evidence to fulfil a requirement of another Public Service. Such relationships should be described in the associated Rule(s). + + + + The Participation class allows to define roles within a certain context. + Participation + The CPSV-AP recognises a common role connected with public services, i.e. the Competent Authority. +<br/><br/> +This simple structure does not allow statements to be made about those participants, such as the start and end date of a contract, nor does it support the inclusion of other roles. The Participation class supports this extra complexity if required, for instance, the description of a service user or a service provider. The model is consistent with the CPOV which in turn is based on the W3C Organization Ontology that supports the common cases simply but allows the complex cases where necessary. The Participation class can be mapped to the Organization Ontology&#39;s Membership class that allows more complex relationships and richer metadata to be applied to a role filled by a given Agent. + + + + + The function of an Agent within a Participation. + role + This should be provided using a controlled vocabulary. +Since this is an extension mechanism for the CSPV-AP, the controlled vocabulary should be decided to suit local implementations. + + + + + + + The Agent involved in the Participation. + has participant + + + + Condition or prerequisite that is to be proven by Evidence. + Requirement + Not all public services are needed or are used by everyone. For example, the visa service operated by European countries is not needed by European citizens but is needed by some citizens from elsewhere, or public services offering unemployment benefits and grants are targeting specific societal groups. The CPSV-AP reuses the Core Criterion and Core Evidence Vocabulary for this class. + +Requirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent. +To illustrate the notion: the European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy. + Requirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent. The European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy. + + + + + The Rules that the requiremens fulfils. + fulfils + + + + Evidence that supplies information, proof or support for the Requirement. + has supporting evidence + + + + + + + Concessions are contracts for pecuniary interest by means of which one or more contracting authorities or contracting entities entrusts the execution of works, or the provision and the management of services, to one or more economic operators. + Service Concession Contract + The object of such contracts is the procurement of works or services by means of a concession, the consideration of which consists in the right to exploit the works or services or in that right together with payment. Such contracts may, but do not necessarily, involve a transfer of ownership to contracting authorities or contracting entities, but contracting authorities or contracting entities always obtain the benefits of the works or services in +question. The definition comes from the Directive <a href="https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32014L0023&from=EN">2014/23/EU</a>. + + + + + It links a Service Concession Contract to relevant legislation or policy documents i.e. +the Legal Resource under which the Service Concession Contracts are being defined. + established under + + + + It links a Service Concession Contract with the Contracting Authority which is ultimately responsible for a public service. + has contracting authority + + + + It links a Service Concession Contract with the Economic Operator in charge for the provision and the management of public services. + has economic operator + + + + The participation in which an Agent is involved. + participates + The Participation class facilitates the detailed description of how an Agent participates in or interacts with a Public Service and may include temporal and spatial information. + + + + Information Requirement + Requested data that is to be proven by Evidence. + + + 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. + + + + bias + Parameter used to adjust the evaluation of the Criterion. + + + + 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. + + + + confidentiality level type + Security classification assigned to an Evidence e.g. classified, sensitive, public. + + + + Classifications should be defined by an organisation/country as an outcome of a security assessment. + + + + constrains + Information Concept about which a Constraint expresses a limitation. + + + Constraint + Limitation applied to an Information Concept. + + + Constraints are requirements in themselves, since they impose prerequisites which influence the definition, use and/or fulfilment of the requirement. They represent hard conditions such as minimum or maximum expressions which can be used to evaluate pieces of information, the required age, income, involvement in activities, etc. An example from the eProcurement domain is a threshold as the minimum turnover required by the buying organisation to select the candidates. Note that CCCEV does not provide any specific guidance on when which kind of Requirement should be used. Users of this vocabulary should make decisions on this topic in their specific context. + + + + + + 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. + + + + expression of expected value + Formulation in a formal language of the expected value(s) for the Information Concept which is aligned with the concepts from the Requirements defined and must be respected by the supplied Supported Values . + + + + The property encapsulates all kind of expectations on the required and provided values one could have. This may range from representational expectations such as the type (e.g. the value is expected to be a xsd:decimal) to expectations that reduce the allowed value range. Commonly this is done using min or max bounderary expressions (e.g. the maximum value is 1 Million Euro). Other usage could be to harmonise the supplied values (e.g. rounding, turning to percentages) to facilitate further processing. -Implementers are free to use their own approach for defining the expected values in more details. For instance, this can be by defining their own datatypes extending or encapsulating common xsd datatypes. But also by using more complex languages such as XPath, Object Constraint Language (OCL), JavaScript and Rule Interchange Format (RIF). - +Implementers are free to use their own approach for defining the expected values in more details. For instance, this can be by defining their own datatypes extending or encapsulating common xsd datatypes. But also by using more complex languages such as <a href="https://www.w3.org/TR/xpath-31/">XPath</a>, <a href="https://www.omg.org/spec/OCL/">Object Constraint Language</a> (OCL), <a href="https://www.javascript.com/">JavaScript</a> and <a href="https://www.w3.org/TR/rif-overview/">Rule Interchange Format</a> (RIF). Because of this freedom, implementers are recommended to well-document their usage of this property (and related information). - - - - - - - Cardinality [0..1]. This property represents an Address related to an Agent. Asserting the address relationship implies that the Agent has an Address. - - - hasAddress - - - - - - - - - Cardinality [0..n]. This property links the Public Service to any Channel through which an Agent provides, uses or otherwise interacts with the Public Service, such as an online service, phone number or office. - - - hasChannel - - - - - - - - - Cardinality [1..1]. This property links a Public Service to a Public Organisation, which is the responsible Agent for the delivery of the Public Service. Whether the particular Public Organisation provides the public service directly or outsources it is not relevant. The Public Organisation that is the Competent Authority of the service is the one that is ultimately responsible for managing and providing the public service. - - - hasCompetentAuthority - - - - - - - - - Cardinality [0..n]. A contact point for the service is almost always helpful. The value of this property, the contact information itself, should be provided using VCard. Note that the contact information should be relevant to the Public Service which may not be the same as contact information for the Competent Authority or any Participant. - - - hasContactPoint - - - - - - - - - Cardinality [0..n]. The Has Cost property links a Public Service to one or more instances of the Cost class. It indicates the costs related to the execution of a Public Service for the citizen or business related to the execution of the particular Public Service. Where the cost varies depending on the channel through which the service is accessed, it can be linked to the channel using the If Accessed Through relationship. - - - hasCost - - - - - - - - - Cardinality [0..n]. Links a Public Service to a class that describes the criteria for needing or using the service, such as residency in a given location, being over a certain age etc. The Criterion class is defined in the Core Criterion and Core Evidence Vocabulary. - - - hasCriterion - - - - - - - - - Cardinality [0..n]. The Has Legal Resource property links a Public Service to a Legal Resource. It indicates the Legal Resource (e.g. legislation) to which the Public Service relates, operates or has its legal basis. - - - hasLegalResource - - - - - - - - - Cardinality [0..n]. The CPSV-AP defines the three basic roles of Competent Authority, Service Provider and Service User but this simple model can be extended if required using the Has Participation property that links to the Participation class . - - - hasParticipation - - - - - - - - - - - - - - - - - - - - - This property leaves the possiblity to define a qualified relation from Requirement to Information Requirement or Constraint as well as a qualified relation from Requirement to Requirement. A use case would be to specialize an EU requirement in Member States' specific requirements. - - - - - - - - - - - - - - - - - - - - - Cardinality [0..1]. Where the cost varies depending on the channel used, for example, if accessed through an online service cf. accessed at a physical location, the cost can be linked to the channel using the If Accessed Through property. - - - ifAccesseThrough - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - 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. - - - - - - Cardinality [0..n]. The Is Classified By property allows to classify the Public Service with any Concept, other than those already foreseen and defined explicitely in the CPSV-AP (Thematic Area, Sector, …). It is a generic property which can be further specialised to make the classification explicit, for instance for classifying public services according level of digitisation, type of audience … The Concept is at its turn related to a Collection, which groups the different concepts into a controlled vocabulary. - - - isClassifiedBy - - - - - - - - - Cardinality [0..n]. This property links the Cost class with one or more instances of the Public Organisation class. This property indicates which Public Organisation is the Competent Authority for defining the costs associated with the delivery of a particular Public Service. - - - isDefinedBy - - - - - - - - - Cardinality [0..n]. The Is Described At property links a Public Service to the dataset where it belongs to. It is used to track the metadata of the origin of the public service descriptions. - - - isDescribedAt - - - - - - - - - Cardinality [0..n]. This property links the Public Service to the Event class. Several Public Services may be associated with a particular Event and, likewise, the same Public Service may be associated with several different Events. - - - isGroupedBy - - - - - - - - - - - - - - - - - - - - - Agents transmitting Evidence are usually the Agents requesting the Evidence or service providers acting on behalf of the requesting Agents such as software developer companies. - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - - - - - Optional class. The Life Event class represents an important event or situations in a citizen's life where public services may be required. Note the scope: an individual will encounter any number of 'events' in the general sense of the word. In the context of the CPSV-AP, the Life Event class only represents an event for which a Public Service is related. For example, a couple becoming engaged is not a CPSV-AP Life Event, getting married is, since only the latter has any relevance to public services. - - - LifeEvent - - - - - - Optional class. Outputs can be any resource - document, artefact – anything produced by the Public Service. In the context of a Public Service, the output provides an official document or other artefact of the Competent Authority (Public Organisation) that permits/authorises/entitles an Agent to (do) something. - - - - - - Output - - - - - - Cardinality [0..n]. This property links the Channel class with one or more instances of the Public Organisation class. This property indicates the owner of a specific Channel through which a Public Service is being delivered. - - - ownedBy - - - - - - Optional class. The CPSV-AP recognises a common role connected with public services, i.e. the Competent Authority. However, this simple structure does not allow statements to be made about those participants, such the start and end date of a contract, nor does it support the inclusion of other roles. The Participation class supports this extra complexity if required, for instance, the description of a service user or a service provider. The model is consistent with the CPOV which in turn is based on the W3C Organization Ontology that supports the common cases simply but allows the complex cases where necessary. The Participation class can be mapped to the Organization Ontology’s Membership class that allows more complex relationships and richer metadata to be applied to a role filled by a given Agent. - - - - - - - - - Participation - - - - - - Cardinality [0..n]. This property links an Agent to the Participation class. The Participation class facilitates the detailed description of how an Agent participates in or interacts with a Public Service and may include temporal and spatial constraints on that participation. - - - playsRole - - - - - - - - - Cardinality [0..1]. The value of this property is the (estimated) time needed for executing a Public Service. The actual information is provided using the ISO8601 syntax for durations. - - - processingTime - - - - - - - - - - - - - - - - - - - - - Mandatory class. The CPSV-AP reuses the Core Public Organisation Vocabulary that defines the concept of a Public Organisation and associated properties and relationships. It is largely based on the W3C Organization Ontology. - - - - - - - - - PublicOrganisation - - - Optional class. The CPSV-AP reuses the Data Catalog Vocabulary (DCAT) for the creation of the Public Service Dataset class. The Public Service Dataset, is a specialisation of the Dataset class of the Data Catalog Vocabulary (DCAT) and inherits all its properties. The class describes the metadata of where the dataset is being described, for instance on a regional public service portal or a national eGovernment portal. - - - - - - PublicServiceDataset - - - - - - - - - - - - - - - - - - The query must be executed on the business data provided by the supporting Evidence. In order to be able to evaluate the query on the provided data, the format of the provided data must be aligned with the query expression. For instance if the provided data is XML, a query in XPath could be expected. This alignment is part of the implementation agreements that implementors must make. - - - - - - - - - - - - Usual Reference Frameworks are legal and non-legal specifications. Examples include procedures, tendering legislation, etc. - - - - - - - - - - - - Requirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent. The European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy. - - - - - - Cardinality [1..n]. Provides the role played. This should be provided using a controlled vocabulary. Since this is an extension mechanism for the CPSV-AP, the controlled vocabulary should be decided to suit local implementations. - - - role - - - - - - The CPSV-AP v2.0 recommends to use as controlled vocabulary the List of NACE codes (http://ec.europa.eu/competition/mergers/cases/index/nace_all.html). - - - - - - Cardinality [0..n]. This property represents the industry or sector a Public Service relates to, or is intended for. For example: environment, safety, housing. Note that a single Public Service may relate to multiple sectors. The possible values for this property are provided as a controlled vocabulary. - - - sector - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - The notion of Supported Value is closely related to actual data exchange between two parties: + + + + + + + + + has concept + Information Concept for which a value is expected by the Requirement. + + + + Information Concepts defined for specific Requirements also represent the basis for specifying the Supported Value an Evidence should provide. + + + + has evidence type list + Evidence Type List that specifies the Evidence Types that are needed to meet the Requirement. + + + + 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. + + + + has qualified relation + Described and/or categorised relation to another Requirement. + + + + This property leaves the possiblity to define a qualified relation from Requirement to Information Requirement or Constraint as well as a qualified relation from Requirement to Requirement. A use case would be to specialize an EU requirement in Member States' specific requirements. + + + + has requirement + A more specific Requirement that is part of the Requirement. + + + + + + + is derived from + Reference Framework on which the Requirement is based, such as a law or regulation. + + + + Note that a Requirement can have several Reference Frameworks from which it is derived. + + + + is requirement of + A reference between a sub-Requirement and its parent Requirement. + + + + 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. + + + + is specified in + Evidence Type List in which the Evidence Type is included. + + + + + + + provides value for + Information Concept for which the Supported Value provides a value. + + + + + + + query + Search statement that allows the value for the Information Concept to be retrieved from the Evidence data. + + + + The query must be executed on the business data provided by the supporting Evidence. In order to be able to evaluate the query on the provided data, the format of the provided data must be aligned with the query expression. For instance if the provided data is XML, a query in <a href="https://www.w3.org/TR/xpath-31/">XPath</a> could be expected. This alignment is part of the implementation agreements that implementors must make. + + + + specifies evidence type + Evidence Type included in this Evidence Type List. + + + + + + + supports concept + Information Concept providing facts found/inferred from the Evidence. + + + + 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". + + + + supports value + Supported Value that the Evidence contains. + + + + + + + validity period + Period of Time during which the Evidence holds true or has force. + + + + + + + validity period constraint + Temporal condition on the validity period of the Evidence Type. + + + + 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. + + + + value + Value for the Information Concept that the Evidence supports. + + + + + + + weight + Relative importance of the Criterion. + + + + The weight must be between 0 and 1. Usually, all Criteria can be integrated within a weighted sum equal to 1. + + + + weighting consideration description + Explanation of how the weighting of a Criterion is to be used. + + + + This description gives the view of the creator of the Criterion weights on how to interpret and use them during the evaluation process. + + + + weighting type + Indication of how the weight should be interpreted in a complex evaluation expression, e.g. as a percentage in an evaluation expression. + + + + An existing codelist which can be used is <a href="https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/number-weight" >OP's Number weigth controlled vocabulary</a> + + + + Evidence Type List + Group of Evidence Types for conforming to a Requirement. + + 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. + + + + Criterion + Condition for evaluation or assessment. + + + In general, Criteria are used for comparison, filtering or selection purposes. Criteria usually set minimum conditions (e.g. limits, intervals, thresholds, etc.) that need to be met in order to pass the requirements or to fulfil them to a certain degree or quality. The concept of Criteria is broader than the concept of Constraint since it covers more usages. The evaluation of the fulfilment is usually supported by the provision of Evidence. +For example in the eProcurement domain, the eProcurement Ontology defines different subclasses of Criterion such as exclusion grounds, selection criteria or award criteria. A concrete example of a Criterion is 'participation in a criminal organisation' which could also be considered as an exclusion ground criterion in the procurement domain or for requiring a public service. + + + + Supported Value + Value for an Information Concept that is provided by an Evidence. + + 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. @@ -734,148 +699,170 @@ The Requirement processor has expressed its expectations (both business as techn 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. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Cardinality [0..n]. This property represents the Thematic Area of a Public Service as described in a controlled vocabulary, for instance social protection, health, recreation, culture and religion, family, traveling economic affairs, tax, staff, environment... - - - - - - thematicArea - - - - - - - - - - - - - - - - - - - - - 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. - - - - - - - - - - - - - - - - - - - - - Cardinality [0..1]. This property represents a numeric value indicating the amount of the Cost. - - - value - - - - - - - - - - - - - - - - - - - - - This description gives the view of the creator of the Criterion weights on how to interpret and use them during the evaluation process. - - - - - - - - - - - - - - - - - - An existing codelist http://publications.europa.eu/resource/authority/number-weight -Example see: https://docs.ted.europa.eu/eforms/0.3.0/index.html#awardCriteriaSection - - - - - - - - - - - - - - - - - - The weight must be between 0 and 1. Usually, all Criteria can be integrated within a weighted sum equal to 1. - - + + + + + Information Concept + Piece of information that the Evidence provides or the Requirement needs. + + 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. + + + + accessibility + Information about how the Public Event can be approached, reached or entered, in particular for people with special needs. + + + + This property may be provided in multiple languages with multiple instances of the accessibility property. + + + + audience + The target group of people for whom the Public Event is created. + + + + + + + event number + The sequence position of the Public Event. + + + + Examples could be the ''4th" or "2022". + + + + event status + This property defines the overall status of the event. + + + + The recomended code list is the <a href="https://op.europa.eu/en/web/eu-vocabularies/concept-scheme/-/resource?uri=http://publications.europa.eu/resource/authority/event-status"> Event Status Controlled vocabulary </a> maintained by the Publications Office of the EU. + + + + expected number of participants + The number of participants expected to participate in the event. + + + + + + + format + A plan of organisation or arrangement of the Public Event. + + + + Examples include conference call, physical meeting or hybrid. + + + + registration page + A web page that provides means to attend the Public Event. + + + + + + + Public Event + Something that happens at a particular place and time, +organised by one or more agents for a particular purpose, and is of interest to a general + audience. This definition excludes natural events such as earthquakes and volcanic +eruptions. + + + + + Accounting Document + Financial and non-financial information as a result of an activity of an organisation. + + Accounting documents, might include: +<ul> +<li> Financial statements (incl. the list of participating interests, subsidiary undertakings and associated undertakings, their registered office address and proportion of capital held), audit reports.</li> +<li> Non-financial statements, management reports and other statements or reports.</li> +<li> Annual financial reports.</li> +</ul> + + + + registration date + The date on which the legal entity has registered in some jurisdiction for regulatory and / or for tax purposes. + + + + + + + code + The classification of the administrative unit. + + + + + + + coordinates + A list of geographic coordinates that define the extent of the Geometry. + + + + Can be expressed as longitude, latitude, elevation. + + + + crs + An identifier for the coordinate reference system. + + + + Can be a coordinate-based local, regional or global system used to locate geographical entities. + + + + geometry type + The classification of the Geometry. + + + + Can be a point, line or polygon. + + + + latitude + The geographic coordinate that specifies the north / south position of the Geomerty on the Earth's surface. + + + + + + + level + The level of the administrative unit in the hierarchy. + + + + The recommended code list to indicate the level of an Admin Unit is the <a href=https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/atu-type>Administrative territorial unit type</a> Controlled Vocabulary maintained by the Publications Office of the EU. + + + + longitude + The geographic coordinate that specifies the east / west position of the Geometry on the Earth's surface. + + + + + + + Administrative Unit + A detailed administrative unit organized in a hierarchy. + + This class should be used whenever a classification mechanism is in place, in alternative to the properties adminUnitL1 and adminUnitL2 of the Address class which allow free text. + + + \ No newline at end of file diff --git a/releases/m8g/m8g.ttl b/releases/m8g/m8g.ttl index ed4eaa5..a1040f1 100644 --- a/releases/m8g/m8g.ttl +++ b/releases/m8g/m8g.ttl @@ -1,402 +1,857 @@ +@prefix owl: . +@prefix rdfs: . +@prefix org: . +@prefix skos: . +@prefix foaf: . +@prefix time: . @prefix rdf: . +@prefix dc: . +@prefix xsd: . - - a ; - "Optional class. This class represents a Business Event, which specialises Event. A Business Event is a specific situation or event in the lifecycle of a business that fulfils one or more needs or (legal) obligations of that business at this specific point in time. A Business Event requires a set of public services to be delivered and consumed in order for the associated business need(s) or obligation(s) to be fulfilled. Business Events are defined within the context of a particular Member State. In other words, a Business Event groups together a number of public services that need to be delivered for completing that particular event."@en ; - "BusinessEvent"@en . + + a owl:Class ; + rdfs:label "Image Object"@en ; + rdfs:comment "A logo to describe / represent an entity."@en ; + rdfs:isDefinedBy . - - a ; - "Optional class. The Channel class represents the medium through which an Agent provides, uses or interacts in another way with a Public Service. Typical examples include online services, phone, walk-in centres etc."@en ; - ; - "Channel"@en . + + a owl:Class ; + rdfs:label "Public Organisation"@en, "Public Organization"@en ; + rdfs:comment "An Organization that is defined as being part of the public sector by a legal framework at any level."@en ; + rdfs:isDefinedBy ; + rdfs:subClassOf org:Organization ; + skos:scopeNote """Organizations which exist to provide services for its citizens and companies are called Public Organizations. The Public Organization class represents the organization. One organization may comprise several sub-organizations and any organization may have one or more organizational units. Each of these is described using the same properties and relationships. +

+This definition is consistent with the more detailed definition of a "public sector body" as given in the PSI Directive: "the State, regional or local authorities, bodies governed by public law and associations formed by one or several such authorities or one or several such bodies governed by public law". It further defines a body governed by public law as any body "(a) established for the specific purpose of meeting needs in the general interest, not having an industrial or commercial character; and (b) having legal personality; and (c) financed, for the most part by the State, or regional or local authorities, or other bodies governed by public law; or subject to management supervision by those bodies; or having an administrative, managerial or supervisory board, more than half of whose members are appointed by the State, regional or local authorities or by other bodies governed by public law"."""@en, """Organizations which exist to provide services for its citizens and companies are called Public Organizations. The Public Organization class represents the organization. One organization may comprise several sub-organizations and any organization may have one or more organizational units. Each of these is described using the same properties and relationships. +

+This definition is consistent with the more detailed definition of a "public sector body" as given in the PSI Directive: "the State, regional or local authorities, bodies governed by public law and associations formed by one or several such authorities or one or several such bodies governed by public law". It further defines a body governed by public law as any body "(a) established for the specific purpose of meeting needs in the general interest, not having an industrial or commercial character; and (b) having legal personality; and (c) financed, for the most part by the State, or regional or local authorities, or other bodies governed by public law; or subject to management supervision by those bodies; or having an administrative, managerial or supervisory board, more than half of whose members are appointed by the State, regional or local authorities or by other bodies governed by public law"."""@en . - - a , ; - ; - ; - "Constraints are requirements in themselves, since they impose prerequisites which influence the definition, use and/or fulfilment of the requirement. They represent hard conditions such as minimum or maximum expressions which can be used to evaluate pieces of information, the required age, income, involvement in activities, etc. An example from the eProcurement domain is a threshold as the minimum turnover required by the buying organisation to select the candidates. Note that CCCEV does not provide any specific guidance on when which kind of Requirement should be used. Users of this vocabulary should make decisions on this topic in their specific context."@en . + + a owl:Class ; + rdfs:label "Reference Framework"@en ; + rdfs:comment "Legislation or official policy from which Requirements are derived."@en ; + rdfs:isDefinedBy ; + skos:scopeNote "Usual Reference Frameworks are legal and non-legal specifications. Examples include procedures, tendering legislation, etc."@en . + + + a owl:ObjectProperty ; + rdfs:label "contact page"@en ; + rdfs:comment "A web page that could be used to reach out the Contact Point."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range foaf:Document . + + + a owl:DatatypeProperty ; + rdfs:label "has email"@en ; + rdfs:comment "An electronic address through which the Contact Point can be contacted."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range rdfs:Literal . + + + a owl:ObjectProperty ; + rdfs:label "frequency"@en ; + rdfs:comment "The recurrence of an instant or period."@en ; + rdfs:domain time:TemporalEntity ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept ; + skos:scopeNote "It is recommended to use the frequency from an existing vocabulary like the Frequency from the Publications Office."@en . + + + a owl:DatatypeProperty ; + rdfs:label "has telephone"@en ; + rdfs:comment "A telephone number through which the Contact Point can be contacted."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range rdfs:Literal . + + + a owl:Class ; + rdfs:label "Contact Point"@en ; + rdfs:comment "Information (e.g. e-mail address, telephone number) of a person or department through which the user can get in touch with."@en ; + rdfs:isDefinedBy ; + skos:scopeNote "The Core Public Organization Vocabulary defines properties for telephone number, e-mail address and opening hours although it is noteworthy that the class is based on schema.org's ContactPoint class that has additional properties that some implementations may find useful."@en, "Similarly to the Channel class, a Contact Point may have regular opening hours that are then overridden by, for example, public holidays, using the Temporal Entity class."@en . + + + a owl:DatatypeProperty ; + rdfs:label "date of birth"@en ; + rdfs:comment "The point in time on which the Person was born."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range ; + skos:scopeNote """The date of birth could be expressed as date, gYearMonth or gYear, example: +
    +
  • - 1980-09-16^^xs:date
    • +
  • - 1980-09^^xs:gYearMonth
    • +
  • - 1980^^xs:gYear
    • +
"""@en . + + + a owl:DatatypeProperty ; + rdfs:label "date of death"@en ; + rdfs:comment "The point in time on which the Person died."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range ; + skos:scopeNote """The date of birth could be expressed as date, gYearMonth or gYear, example: +
    +
  • - 1980-09-16^^xs:date
    • +
  • - 1980-09^^xs:gYearMonth
    • +
  • - 1980^^xs:gYear
    • +
"""@en . + + + a owl:ObjectProperty ; + rdfs:label "gender"@en ; + rdfs:comment "The identities, expressions and societal roles of the Person."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept ; + skos:scopeNote "The gender of an individual should be recorded using a controlled vocabulary that is appropriate for the specific context. In some cases, the chromosomal or physical state of an individual will be more important than the gender that they express, in others the reverse will be true. What is always important is that the controlled vocabulary used to describe an individual's gender is stated explicitly."@en . + + + a owl:DatatypeProperty ; + rdfs:label "matronymic name"@en ; + rdfs:comment "Name based on the given name of the Person's mother."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range rdf:langString . + + + a owl:ObjectProperty ; + rdfs:label "sex"@en ; + rdfs:comment "The organism's biological sex."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept ; + skos:scopeNote "The recommended controlled vocabulary for this property is the sex authority table of the Publications Office."@en . + + + a owl:Class ; + rdfs:label "Generic date"@en ; + rdfs:comment "The date data type is the union of xs:date, xs:gYearMonth and xs:gYear"@en ; + rdfs:isDefinedBy . - - a ; - "Optional class. The Cost class represents any costs related to the execution of a Public Service that the Agent consuming it needs to pay."@en ; - ; - "Cost"@en . + + a owl:DatatypeProperty ; + rdfs:comment "The (estimated) time needed for executing a Public Service. The actual information is provided using the ISO8601 syntax for durations."@en, "The (estimated) time needed for executing a Public Service which may depend on the Channel chosen."@en ; + rdfs:label "processing time"@en ; + skos:scopeNote """Some examples are provided below: +Duration Syntax - Syntax +5 years - P5Y +1 month - P1M +3 days - P3D +2 days 4 hours - P2DT4H - - a , ; - ; - ; - """In general, Criteria are used for comparison, filtering or selection purposes. Criteria usually set minimum conditions (e.g. limits, intervals, thresholds, etc.) that need to be met in order to pass the requirements or to fulfil them to a certain degree or quality. The concept of Criteria is broader than the concept of Constraint since it covers more usages. The evaluation of the fulfilment is usually supported by the provision of Evidence. -For example in the eProcurement domain, the eProcurement Ontology defines different subclasses of Criterion such as exclusion grounds, selection criteria or award criteria. A concrete example of a Criterion is 'participation in a criminal organisation' which could also be considered as an exclusion ground criterion in the procurement domain or for requiring a public service."""@en . +Durations begin with an uppercase P followed by the number and the relevant designator, formally: P[n]Y[n]M[n]DT[n]H[n]M[n]S, where Y is for years, M for months etc. - - "Optional class. Not all public services are needed or usable by everyone. For example, the visa service operated by European countries is not needed by European citizens but is needed by some citizens from elsewhere, or public services offering unemployment benefits and grants are targeting specific societal groups. The CPSV reuses the Core Criterion and Core Evidence Vocabulary for this class. The CCCEV provides more details but the CriterionRequirement class has three mandatory properties."@en ; - a ; - ; - "CriterionRequirement"@en . +Note that days and times are separated by an uppercase T which also +disambiguates M as meaning month (P2M means 2 months) or minute (PT2M means 2 minutes). Durations may also be defined as a number of weeks so P4W means 4 weeks. A full explanation is provided in the Wikipedia page that references the official ISO standard. - - a ; - "Optional class. This class represents an event that can be of any type that triggers, makes use of, or in some way is related to, a Public Service. It is not expected to be used directly, rather, one or other of its subclasses should be used. The properties of the class are, of course, inherited by those subclasses."@en ; - ; - "Event"@en . +This approach is consistent with both schema.org and the W3C OWL Time Ontology."""@en, "The actual information is provided using the ISO8601 syntax for durations."@en . - - "Optional class. Evidence can be any resource - document, artefact – anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered. In some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s)."@en ; - a ; - ; - "Evidence"@en . + + a owl:ObjectProperty ; + rdfs:comment "The industry or sector a Public Service relates to, or is intended for."@en ; + rdfs:label "sector"@en ; + skos:scopeNote "For example: environment, safety, housing. Note that a single Public Service may relate to multiple sectors. The possible values for this property are provided as a controlled vocabulary. The possible values for this property are described in the controlled vocabulary Data theme Authority Table of the Publications Office."@en . - - a , ; - ; - "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)."@en . + + a owl:ObjectProperty ; + rdfs:comment "The Thematic Area of a Public Service."@en ; + rdfs:label "thematic area"@en ; + skos:scopeNote "For example: social protection, health, recreation, culture and religion, family, traveling economic affairs, tax, staff, environment, etc."@en . - - a , ; - ; - """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. + + a owl:ObjectProperty ; + rdfs:comment "The main contact information of the resource."@en ; + rdfs:label "contact point"@en ; + skos:scopeNote "Note that the contact information should be relevant to the Public Service which may not be the same as contact information for the Competent Authority or any Participant."@en . -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."""@en . + + a owl:ObjectProperty ; + rdfs:comment "It links the Public Service to any Channel through which an Agent provides, uses or otherwise interacts with the Public Service, such as an online service, phone number or office."@en ; + rdfs:label "has channel"@en . - - a , ; - ; - "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."@en . + + a owl:ObjectProperty ; + rdfs:comment "It links a Public Service to a Public Organization, which is the responsible Agent for the delivery of the Public Service."@en ; + rdfs:label "has competent authority"@en ; + skos:scopeNote "Whether the particular Public Organization provides the public service directly or outsources it is not relevant. The Public Organization that is the Competent Authority of the service is the one that is ultimately responsible for managing and providing the public service. The term Competent Authority is defined in the Services Directive (2006/123/EC) in the following way: \"Any body or authority which has a supervisory or regulatory role in a Member State in relation to service activities, including, in particular, administrative authorities, including courts acting as such, professional bodies, and those professional associations or other professional organisations which, in the exercise of their legal autonomy, regulate in a collective manner access to service activities or the exercise thereof\"."@en . - - a , ; - ; - ; - "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."@en . + + a owl:ObjectProperty ; + rdfs:comment "It indicates the costs related to the execution of a Public Service for the citizen or business related to the execution of the particular Public Service."@en ; + rdfs:label "has cost"@en ; + skos:scopeNote "Where the cost varies depending on the channel through which the service is accessed, it can be linked to the channel using the If Accessed Through relationship."@en . - - a ; - "Optional class. The Life Event class represents an important event or situations in a citizen's life where public services may be required. Note the scope: an individual will encounter any number of 'events' in the general sense of the word. In the context of the CPSV-AP, the Life Event class only represents an event for which a Public Service is related. For example, a couple becoming engaged is not a CPSV-AP Life Event, getting married is, since only the latter has any relevance to public services."@en ; - "LifeEvent"@en . + + a owl:ObjectProperty ; + rdfs:comment "It links a Public Service to one or more instances of the EvidenceType class."@en ; + rdfs:label "has input type"@en . - - a ; - "Optional class. Outputs can be any resource - document, artefact – anything produced by the Public Service. In the context of a Public Service, the output provides an official document or other artefact of the Competent Authority (Public Organisation) that permits/authorises/entitles an Agent to (do) something."@en ; - ; - "Output"@en . + + a owl:ObjectProperty ; + rdfs:comment "It indicates the Legal Resource (e.g. legislation) to which the Public Service relates, operates or has its legal basis."@en ; + rdfs:label "has legal resource"@en . - - "Optional class. The CPSV-AP recognises a common role connected with public services, i.e. the Competent Authority. However, this simple structure does not allow statements to be made about those participants, such the start and end date of a contract, nor does it support the inclusion of other roles. The Participation class supports this extra complexity if required, for instance, the description of a service user or a service provider. The model is consistent with the CPOV which in turn is based on the W3C Organization Ontology that supports the common cases simply but allows the complex cases where necessary. The Participation class can be mapped to the Organization Ontology’s Membership class that allows more complex relationships and richer metadata to be applied to a role filled by a given Agent."@en ; - a ; - ; - "Participation"@en . + + a owl:ObjectProperty ; + rdfs:comment "The way how a resource is organized."@en ; + rdfs:label "has participation"@en ; + skos:scopeNote "The Participation class facilitates the detailed description of how an Agent participates in or interacts with a Public Service and may include temporal and spatial information."@en . - - "Mandatory class. The CPSV-AP reuses the Core Public Organisation Vocabulary that defines the concept of a Public Organisation and associated properties and relationships. It is largely based on the W3C Organization Ontology."@en ; - a ; - ; - "PublicOrganisation"@en . + + a owl:ObjectProperty ; + rdfs:comment "It links a Public Service to a class that describes the Requirement."@en ; + rdfs:label "holds requirement"@en ; + skos:scopeNote "Usage: It describes the needing or using the service, such as residency in a given location, being over a certain age etc. The Requirement class is defined in the Core Criterion and Core Evidence Vocabulary."@en . - - "Optional class. The CPSV-AP reuses the Data Catalog Vocabulary (DCAT) for the creation of the Public Service Dataset class. The Public Service Dataset, is a specialisation of the Dataset class of the Data Catalog Vocabulary (DCAT) and inherits all its properties. The class describes the metadata of where the dataset is being described, for instance on a regional public service portal or a national eGovernment portal."@en ; - a ; - "PublicServiceDataset"@en . + + a owl:ObjectProperty ; + rdfs:comment "It allows to classify the Public Service with any Concept other than those already foreseen and defined explicitly in the CPSV-AP (Thematic Area, Sector, etc.)."@en ; + rdfs:label "is classified by"@en ; + skos:scopeNote """It is a generic property which can be further specialised to make the classification explicit, for instance for classifying public services according level of digitisation, +type of audience, etc. The Concept is at its turn related to a Collection, which groups the different concepts into a controlled vocabulary."""@en . - - a , ; - ; - "Usual Reference Frameworks are legal and non-legal specifications. Examples include procedures, tendering legislation, etc."@en . + + a owl:ObjectProperty ; + rdfs:comment "It links the Public Service to the Event class."@en ; + rdfs:label "is grouped by"@en ; + skos:scopeNote "Several Public Services may be associated with a particular Event and, likewise, the same Public Service may be associated with several different Events."@en . + + + a owl:ObjectProperty ; + rdfs:comment "A Public Service related to the particular instance of the Public Service class."@en ; + rdfs:label "related service"@en ; + skos:scopeNote "This property is a sub-property of dct:relation."@en ; + rdfs:subPropertyOf dc:relation . - - a , ; - ; - "Requirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent. The European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy."@en . + + a owl:Class ; + rdfs:comment "A Business Event is a specific situation or event in the lifecycle of a business that fulfils one or more needs or (legal) obligations of that business at this specific point in time."@en ; + rdfs:label "Business Event"@en ; + skos:scopeNote "A Business Event requires a set of public services to be delivered and consumed in order for the associated business need(s) or obligation(s) to be fulfilled. Business Events are defined within the context of a particular Member State. In other words, a Business Event groups together a number of public services that need to be delivered for completing that particular event."@en ; + rdfs:subClassOf . - - a , ; - ; - """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. + + a owl:Class ; + rdfs:comment "A medium through which an Agent provides, uses or interacts in another way with a Public Service."@en ; + rdfs:label "Channel"@en ; + skos:scopeNote "Typical examples include online services, phone, walk-in centres etc."@en . + + + a owl:ObjectProperty ; + rdfs:comment "A time during which the resource is not available."@en ; + rdfs:label "availability restriction"@en ; + skos:scopeNote """Like the Contact Point, a Channel may not be available at a certain time. +

+For a simple description of the time use the description property of TemporalEntity. +

+For more structured data use the model in Time Ontology, see an example."""@en, """For a simple description of the time use the description property of TemporalEntity. + +For more structured data use the model in Time Ontology, see an example."""@en . + + + a owl:ObjectProperty ; + rdfs:comment "A time at which the resource is normally available."@en, "The time at which the Contact Point is normally available."@en ; + rdfs:label "opening hours"@en ; + skos:scopeNote """Like the Contact Point, a Channel may be available at a certain time. +

+For a simple description of the time use the description property of TemporalEntity. +

+For more structured data use the model in Time Ontology, see an example."""@en, """For a simple description of the time use the description property of TemporalEntity. + +For more structured data use the model in Time Ontology, see an example. This relation can be used to indicate exceptional closures such as being closed on public holidays."""@en . -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. + + a owl:ObjectProperty ; + rdfs:comment "The owner of a specific Channel through which a Public Service is being delivered."@en ; + rdfs:label "owned by"@en . -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. + + a owl:Class ; + rdfs:comment "The Cost class represents any costs related to the execution of a Public Service that the Agent consuming it needs to pay."@en ; + rdfs:label "Cost"@en . -Implementers are free to choose their language. It is recommended to document the made agreements well. -"""@en . + + a owl:ObjectProperty ; + rdfs:comment "The currency in which the Cost needs to be paid and the value of the Cost is expressed."@en ; + rdfs:label "currency"@en ; + skos:scopeNote """The possible values for this property are described in the controlled vocabulary +Currency Authority Table of Publications Office."""@en . - - a rdf:Property, ; - _:genid1 ; - ; - _:genid2 ; - """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\". [https://trade.ec.europa.eu/doclib/docs/2018/september/tradoc_157319.pdf] -When quantified, this systematic error can be removed."""@en . + + a owl:DatatypeProperty ; + rdfs:comment "A numeric value indicating the amount of the Cost."@en ; + rdfs:label "has value"@en . - - a rdf:Property, ; - _:genid3 ; - ; - _:genid4 ; - "Classifications should be defined by an organisation/country as an outcome of a security assessment."@en . - - - "2018-07-09"^^ ; - ; - "The original CPSV-AP was prepared in the context of Action 1.3 – Accessing Member State information resources at European level – Catalogue of Services of the European Commission’s Interoperability for European Public Administrations (ISA) programme. The CPSV-AP has been seen as a first step for creating a model for describing public services related to business events, to facilitate the set-up of catalogues of services in the context of the Services Directive. Update to version 2.2 finds its motivation in the experience of implementing version 2.1 of the CPSV-AP by different MSs and stakeholders and consequent requests received from them, as detailed in https://github.com/catalogue-of-services-isa/CPSV-AP/issues."@en ; - ; - ; - "Core Public Service Vocabulary Application Profile"@en ; - ; - "cpsvap" ; - a , , ; - . + + a owl:ObjectProperty ; + rdfs:comment "The costs created by the use of different Channels."@en ; + rdfs:label "if accessed through"@en ; + skos:scopeNote "For example, if accessed through an online service cf. accessed at a physical location, the cost can be linked to the channel using the If Accessed Through property."@en . - - "The CPSV-AP v2.0 recommends to use as controlled vocabulary the European Publications Office's Currencies Named Authority List (NAL) (http://publications.europa.eu/mdr/authority/currency/index.html)."@en ; - a ; - "Cardinality [0..1]. This property represents the currency in which the Cost needs to be paid and the value of the Cost is expressed. The possible values for this property are described in a controlled vocabulary."@en ; - "currency"@en ; - . + + a owl:ObjectProperty ; + rdfs:comment "It links the Cost class to one or more instances of the Public Organization class."@en ; + rdfs:label "is defined by"@en ; + skos:scopeNote "This property indicates which Public Organization is the Competent Authority for defining the costs associated with the delivery of a particular Public Service."@en . - - a rdf:Property, ; - _:genid5 ; - ; - _:genid6 ; - "The categories agreed are left open but could for example specify the layout and content expected for an Evidence."@en . + + a owl:Class ; + rdfs:comment "This class represents an event that can be of any type that triggers, makes use of, or in some way is related to, a Public Service."@en ; + rdfs:label "Event"@en ; + skos:scopeNote "It is not expected to be used directly, rather, one or other of its subclasses should be used. The properties of the class are, of course, inherited by those subclasses. The Event class is used as a hook either to a single related Public Service, such as diagnosis of illness being related to application for sickness benefit; or to a group of Public Services, such as all those related to the establishment of a new business."@en . + + + a owl:ObjectProperty ; + rdfs:comment "The Public Service related to the Event."@en ; + rdfs:label "has related service"@en ; + skos:scopeNote "This property is a sub-property of dct:relation."@en ; + rdfs:subPropertyOf dc:relation . - - a rdf:Property, ; - _:genid7 ; - ; - _:genid8 ; - """The property encapsulates all kind of expectations on the required and provided values one could have. -This may range from representational expectations such as the type (e.g. the value is expected to be a xsd:decimal) to expectations that reduce the allowed value range. Commonly this is done using min or max bounderary expressions (e.g. the maximum value is 1 Million Euro). -Other usage could be to harmonise the supplied values (e.g. rounding, turning to percentages) to facilitate further processing. + + a owl:Class ; + rdfs:comment "The Evidence class is defined in the Core Criterion and Core Evidence vocabulary (CCCEV) as any resource that can prove that a specific requirement is met."@en, "Proof that a Requirement is met."@en ; + rdfs:label "Evidence"@en ; + skos:scopeNote """Although the wording of the definition is different, the semantics are an exact match for CPSV's Input class which it replaces. -Implementers are free to use their own approach for defining the expected values in more details. For instance, this can be by defining their own datatypes extending or encapsulating common xsd datatypes. But also by using more complex languages such as XPath, Object Constraint Language (OCL), JavaScript and Rule Interchange Format (RIF). +Evidence can be any resource - document, artefact - anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered. -Because of this freedom, implementers are recommended to well-document their usage of this property (and related information). -"""@en . +In some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s)."""@en, """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. - - a ; - "Cardinality [0..1]. This property represents an Address related to an Agent. Asserting the address relationship implies that the Agent has an Address."@en ; - "hasAddress"@en ; - . +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."""@en ; + rdfs:isDefinedBy . - - a ; - "Cardinality [0..n]. This property links the Public Service to any Channel through which an Agent provides, uses or otherwise interacts with the Public Service, such as an online service, phone number or office."@en ; - "hasChannel"@en ; - . + + a owl:ObjectProperty ; + rdfs:comment "Requirement for which the Evidence provides proof."@en ; + rdfs:label "supports requirement"@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range . - - a ; - "Cardinality [1..1]. This property links a Public Service to a Public Organisation, which is the responsible Agent for the delivery of the Public Service. Whether the particular Public Organisation provides the public service directly or outsources it is not relevant. The Public Organisation that is the Competent Authority of the service is the one that is ultimately responsible for managing and providing the public service."@en ; - "hasCompetentAuthority"@en ; - . + + a owl:Class ; + rdfs:comment "Information about the characteristics of an Evidence."@en ; + rdfs:label "Evidence Type"@en ; + skos:scopeNote "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)."@en ; + rdfs:isDefinedBy . - - a ; - "Cardinality [0..n]. A contact point for the service is almost always helpful. The value of this property, the contact information itself, should be provided using VCard. Note that the contact information should be relevant to the Public Service which may not be the same as contact information for the Competent Authority or any Participant."@en ; - "hasContactPoint"@en ; - . + + a owl:ObjectProperty ; + rdfs:comment "Category to which the Evidence Type belongs."@en ; + rdfs:label "evidence type classification"@en ; + skos:scopeNote "The categories agreed are left open but could for example specify the layout and content expected for an Evidence. An example could be id cards."@en, "The categories agreed are left open but could for example specify the layout and content expected for an Evidence."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept . - - a ; - "Cardinality [0..n]. The Has Cost property links a Public Service to one or more instances of the Cost class. It indicates the costs related to the execution of a Public Service for the citizen or business related to the execution of the particular Public Service. Where the cost varies depending on the channel through which the service is accessed, it can be linked to the channel using the If Accessed Through relationship."@en ; - "hasCost"@en ; - . + + a owl:Class ; + rdfs:comment "The Life Event class represents an important event or situation in a citizen's life where public services are required."@en ; + rdfs:label "Life Event"@en ; + skos:scopeNote "Note on the scope: an individual will encounter any number of 'events'; in the general sense of the word. In the context of the CPSV-AP, the Life Event class only represents an event to which a Public Service is related. For example, a couple becoming engaged is not a CPSV-AP Life Event, getting married is, since only the latter has any relevance to public services."@en ; + rdfs:subClassOf . - - a ; - "Cardinality [0..n]. Links a Public Service to a class that describes the criteria for needing or using the service, such as residency in a given location, being over a certain age etc. The Criterion class is defined in the Core Criterion and Core Evidence Vocabulary."@en ; - "hasCriterion"@en ; - . + + a owl:Class ; + rdfs:comment "An output can be any resource - document, artefact - anything produced by the Public Service. In the context of a Public Service, the output provides an official document or other artefact of the Competent Authority (Public Organization) that permits/authorises/entitles an Agent to (do) something."@en ; + rdfs:label "Output"@en ; + skos:scopeNote "In some cases, the Output of one Public Service will be used as evidence to fulfil a requirement of another Public Service. Such relationships should be described in the associated Rule(s)."@en . - - a ; - "Cardinality [0..n]. The Has Legal Resource property links a Public Service to a Legal Resource. It indicates the Legal Resource (e.g. legislation) to which the Public Service relates, operates or has its legal basis."@en ; - "hasLegalResource"@en ; - . + + a owl:Class ; + rdfs:comment "The Participation class allows to define roles within a certain context."@en ; + rdfs:label "Participation"@en ; + skos:scopeNote """The CPSV-AP recognises a common role connected with public services, i.e. the Competent Authority. +

+This simple structure does not allow statements to be made about those participants, such as the start and end date of a contract, nor does it support the inclusion of other roles. The Participation class supports this extra complexity if required, for instance, the description of a service user or a service provider. The model is consistent with the CPOV which in turn is based on the W3C Organization Ontology that supports the common cases simply but allows the complex cases where necessary. The Participation class can be mapped to the Organization Ontology's Membership class that allows more complex relationships and richer metadata to be applied to a role filled by a given Agent."""@en ; + rdfs:isDefinedBy . - - a ; - "Cardinality [0..n]. The CPSV-AP defines the three basic roles of Competent Authority, Service Provider and Service User but this simple model can be extended if required using the Has Participation property that links to the Participation class ."@en ; - "hasParticipation"@en ; - . + + a owl:ObjectProperty ; + rdfs:comment "The function of an Agent within a Participation."@en ; + rdfs:label "role"@en ; + skos:scopeNote """This should be provided using a controlled vocabulary. +Since this is an extension mechanism for the CSPV-AP, the controlled vocabulary should be decided to suit local implementations."""@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept . + + + a owl:ObjectProperty ; + rdfs:comment "The Agent involved in the Participation."@en ; + rdfs:label "has participant"@en . - - a rdf:Property, ; - _:genid9 ; - ; - _:genid10 ; - "This property leaves the possiblity to define a qualified relation from Requirement to Information Requirement or Constraint as well as a qualified relation from Requirement to Requirement. A use case would be to specialize an EU requirement in Member States' specific requirements."@en . + + a owl:Class ; + rdfs:comment "Condition or prerequisite that is to be proven by Evidence."@en ; + rdfs:label "Requirement"@en ; + skos:scopeNote """Not all public services are needed or are used by everyone. For example, the visa service operated by European countries is not needed by European citizens but is needed by some citizens from elsewhere, or public services offering unemployment benefits and grants are targeting specific societal groups. The CPSV-AP reuses the Core Criterion and Core Evidence Vocabulary for this class. + +Requirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent. +To illustrate the notion: the European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy."""@en, "Requirement is a generic class representing any type of prerequisite that may be desired, needed or imposed as an obligation. CCCEV recommends to not use the Requirement class directly, but rather a more semantically-enriched subclass such as Criterion, Information Requirement or Constraint. Also note that the Requirement class is specified at a more abstract level and is not to be used as the instantiation of a Requirement for a specific Agent. The European Directive on services in the internal market defines requirement as any obligation, prohibition, condition or limit provided for in the laws, regulations or administrative provisions of the Member States or in consequence of case-law, administrative practice, the rules of professional bodies, or the collective rules of professional associations or other professional organisations, adopted in the exercise of their legal autonomy."@en ; + rdfs:isDefinedBy . + + + a owl:ObjectProperty ; + rdfs:comment "The Rules that the requiremens fulfils."@en ; + rdfs:label "fulfils"@en . + + + a owl:ObjectProperty ; + rdfs:comment "Evidence that supplies information, proof or support for the Requirement."@en ; + rdfs:label "has supporting evidence"@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range . + + + a owl:Class ; + rdfs:comment "Concessions are contracts for pecuniary interest by means of which one or more contracting authorities or contracting entities entrusts the execution of works, or the provision and the management of services, to one or more economic operators."@en ; + rdfs:label "Service Concession Contract"@en ; + skos:scopeNote """The object of such contracts is the procurement of works or services by means of a concession, the consideration of which consists in the right to exploit the works or services or in that right together with payment. Such contracts may, but do not necessarily, involve a transfer of ownership to contracting authorities or contracting entities, but contracting authorities or contracting entities always obtain the benefits of the works or services in +question. The definition comes from the Directive 2014/23/EU."""@en ; + rdfs:subClassOf . + + + a owl:ObjectProperty ; + rdfs:comment """It links a Service Concession Contract to relevant legislation or policy documents i.e. +the Legal Resource under which the Service Concession Contracts are being defined."""@en ; + rdfs:label "established under"@en . + + + a owl:ObjectProperty ; + rdfs:comment "It links a Service Concession Contract with the Contracting Authority which is ultimately responsible for a public service."@en ; + rdfs:label "has contracting authority"@en . + + + a owl:ObjectProperty ; + rdfs:comment "It links a Service Concession Contract with the Economic Operator in charge for the provision and the management of public services."@en ; + rdfs:label "has economic operator"@en . + + + a owl:ObjectProperty ; + rdfs:comment "The participation in which an Agent is involved."@en ; + rdfs:label "participates"@en ; + skos:scopeNote "The Participation class facilitates the detailed description of how an Agent participates in or interacts with a Public Service and may include temporal and spatial information."@en . - - a rdf:Property, ; - _:genid11 ; - ; - _:genid12 . + + a owl:Class ; + rdfs:label "Information Requirement"@en ; + rdfs:comment "Requested data that is to be proven by Evidence."@en ; + rdfs:isDefinedBy ; + rdfs:subClassOf ; + skos:scopeNote "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."@en . - - a ; - "Cardinality [0..1]. Where the cost varies depending on the channel used, for example, if accessed through an online service cf. accessed at a physical location, the cost can be linked to the channel using the If Accessed Through property."@en ; - "ifAccesseThrough"@en ; - . + + a owl:DatatypeProperty ; + rdfs:label "bias"@en ; + rdfs:comment "Parameter used to adjust the evaluation of the Criterion."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range xsd:decimal ; + skos:scopeNote "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."@en . - - a ; - "Cardinality [0..n]. The Is Classified By property allows to classify the Public Service with any Concept, other than those already foreseen and defined explicitely in the CPSV-AP (Thematic Area, Sector, …). It is a generic property which can be further specialised to make the classification explicit, for instance for classifying public services according level of digitisation, type of audience … The Concept is at its turn related to a Collection, which groups the different concepts into a controlled vocabulary."@en ; - "isClassifiedBy"@en ; - . + + a owl:ObjectProperty ; + rdfs:label "confidentiality level type"@en ; + rdfs:comment "Security classification assigned to an Evidence e.g. classified, sensitive, public."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept ; + skos:scopeNote "Classifications should be defined by an organisation/country as an outcome of a security assessment."@en . + + + a owl:ObjectProperty ; + rdfs:label "constrains"@en ; + rdfs:comment "Information Concept about which a Constraint expresses a limitation."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range ; + skos:scopeNote "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."@en . - - a ; - "Cardinality [0..n]. This property links the Cost class with one or more instances of the Public Organisation class. This property indicates which Public Organisation is the Competent Authority for defining the costs associated with the delivery of a particular Public Service."@en ; - "isDefinedBy"@en ; - . + + a owl:DatatypeProperty ; + rdfs:label "expression of expected value"@en ; + rdfs:comment "Formulation in a formal language of the expected value(s) for the Information Concept which is aligned with the concepts from the Requirements defined and must be respected by the supplied Supported Values ."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range rdfs:Literal ; + skos:scopeNote """The property encapsulates all kind of expectations on the required and provided values one could have. +This may range from representational expectations such as the type (e.g. the value is expected to be a xsd:decimal) to expectations that reduce the allowed value range. Commonly this is done using min or max bounderary expressions (e.g. the maximum value is 1 Million Euro). +Other usage could be to harmonise the supplied values (e.g. rounding, turning to percentages) to facilitate further processing. - - a ; - "Cardinality [0..n]. The Is Described At property links a Public Service to the dataset where it belongs to. It is used to track the metadata of the origin of the public service descriptions."@en ; - "isDescribedAt"@en ; - . +Implementers are free to use their own approach for defining the expected values in more details. For instance, this can be by defining their own datatypes extending or encapsulating common xsd datatypes. But also by using more complex languages such as XPath, Object Constraint Language (OCL), JavaScript and Rule Interchange Format (RIF). +Because of this freedom, implementers are recommended to well-document their usage of this property (and related information). - - a ; - "Cardinality [0..n]. This property links the Public Service to the Event class. Several Public Services may be associated with a particular Event and, likewise, the same Public Service may be associated with several different Events."@en ; - "isGroupedBy"@en ; - . - - - a rdf:Property, ; - _:genid13 ; - ; - _:genid14 ; - "Agents transmitting Evidence are usually the Agents requesting the Evidence or service providers acting on behalf of the requesting Agents such as software developer companies."@en . - - a rdf:Property, ; - _:genid15 ; - ; - _:genid16 ; - """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."""@en . +"""@en . - - a rdf:Property, ; - _:genid17 ; - ; - _:genid18 . + + a owl:ObjectProperty ; + rdfs:label "has concept"@en ; + rdfs:comment "Information Concept for which a value is expected by the Requirement."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range ; + skos:scopeNote "Information Concepts defined for specific Requirements also represent the basis for specifying the Supported Value an Evidence should provide."@en . + + + a owl:ObjectProperty ; + rdfs:label "has evidence type list"@en ; + rdfs:comment "Evidence Type List that specifies the Evidence Types that are needed to meet the Requirement."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range ; + skos:scopeNote "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."@en . - - a ; - "Cardinality [0..n]. This property links the Channel class with one or more instances of the Public Organisation class. This property indicates the owner of a specific Channel through which a Public Service is being delivered."@en ; - "ownedBy"@en ; - . + + a owl:ObjectProperty ; + rdfs:label "has qualified relation"@en ; + rdfs:comment "Described and/or categorised relation to another Requirement."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range ; + skos:scopeNote "This property leaves the possiblity to define a qualified relation from Requirement to Information Requirement or Constraint as well as a qualified relation from Requirement to Requirement. A use case would be to specialize an EU requirement in Member States' specific requirements."@en . - - a ; - "Cardinality [0..n]. This property links an Agent to the Participation class. The Participation class facilitates the detailed description of how an Agent participates in or interacts with a Public Service and may include temporal and spatial constraints on that participation."@en ; - "playsRole"@en ; - . + + a owl:ObjectProperty ; + rdfs:label "has requirement"@en ; + rdfs:comment "A more specific Requirement that is part of the Requirement."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range . + + + a owl:ObjectProperty ; + rdfs:label "is derived from"@en ; + rdfs:comment "Reference Framework on which the Requirement is based, such as a law or regulation."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range ; + skos:scopeNote "Note that a Requirement can have several Reference Frameworks from which it is derived."@en . - - a ; - "Cardinality [0..1]. The value of this property is the (estimated) time needed for executing a Public Service. The actual information is provided using the ISO8601 syntax for durations."@en ; - "processingTime"@en ; - . + + a owl:ObjectProperty ; + rdfs:label "is requirement of"@en ; + rdfs:comment "A reference between a sub-Requirement and its parent Requirement."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range ; + skos:scopeNote """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. - - a rdf:Property, ; - _:genid19 ; - ; - _:genid20 . +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."""@en . - - a rdf:Property, ; - _:genid21 ; - ; - _:genid22 ; - "The query must be executed on the business data provided by the supporting Evidence. In order to be able to evaluate the query on the provided data, the format of the provided data must be aligned with the query expression. For instance if the provided data is XML, a query in XPath could be expected. This alignment is part of the implementation agreements that implementors must make."@en . + + a owl:ObjectProperty ; + rdfs:label "is specified in"@en ; + rdfs:comment "Evidence Type List in which the Evidence Type is included."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range . - - a ; - "Cardinality [1..n]. Provides the role played. This should be provided using a controlled vocabulary. Since this is an extension mechanism for the CPSV-AP, the controlled vocabulary should be decided to suit local implementations."@en ; - "role"@en ; - . + + a owl:ObjectProperty ; + rdfs:label "provides value for"@en ; + rdfs:comment "Information Concept for which the Supported Value provides a value."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range . - - "The CPSV-AP v2.0 recommends to use as controlled vocabulary the List of NACE codes (http://ec.europa.eu/competition/mergers/cases/index/nace_all.html)."@en ; - a ; - "Cardinality [0..n]. This property represents the industry or sector a Public Service relates to, or is intended for. For example: environment, safety, housing. Note that a single Public Service may relate to multiple sectors. The possible values for this property are provided as a controlled vocabulary."@en ; - "sector"@en ; - . + + a owl:DatatypeProperty ; + rdfs:label "query"@en ; + rdfs:comment "Search statement that allows the value for the Information Concept to be retrieved from the Evidence data."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range rdfs:Literal ; + skos:scopeNote "The query must be executed on the business data provided by the supporting Evidence. In order to be able to evaluate the query on the provided data, the format of the provided data must be aligned with the query expression. For instance if the provided data is XML, a query in XPath could be expected. This alignment is part of the implementation agreements that implementors must make."@en . - a rdf:Property, ; - _:genid23 ; - ; - _:genid24 . - - - a rdf:Property, ; - _:genid25 ; - ; - _:genid26 . + a owl:ObjectProperty ; + rdfs:label "specifies evidence type"@en ; + rdfs:comment "Evidence Type included in this Evidence Type List."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range . + + + a owl:ObjectProperty ; + rdfs:label "supports concept"@en ; + rdfs:comment "Information Concept providing facts found/inferred from the Evidence."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range ; + skos:scopeNote "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\"."@en . - a rdf:Property, ; - _:genid27 ; - ; - _:genid28 . - - - "Cardinality [0..n]. This property represents the Thematic Area of a Public Service as described in a controlled vocabulary, for instance social protection, health, recreation, culture and religion, family, traveling economic affairs, tax, staff, environment..."@en ; - a ; - "thematicArea"@en ; - . + a owl:ObjectProperty ; + rdfs:label "supports value"@en ; + rdfs:comment "Supported Value that the Evidence contains."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range . - a rdf:Property, ; - _:genid29 ; - ; - _:genid30 . + a owl:ObjectProperty ; + rdfs:label "validity period"@en ; + rdfs:comment "Period of Time during which the Evidence holds true or has force."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range time:ProperInterval . - a rdf:Property, ; - _:genid31 ; - ; - _:genid32 ; - "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."@en . + a owl:ObjectProperty ; + rdfs:label "validity period constraint"@en ; + rdfs:comment "Temporal condition on the validity period of the Evidence Type."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range time:ProperInterval ; + skos:scopeNote "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."@en . - a ; - "Cardinality [0..1]. This property represents a numeric value indicating the amount of the Cost."@en ; - "value"@en ; - . + a owl:DatatypeProperty ; + rdfs:label "value"@en ; + rdfs:comment "Value for the Information Concept that the Evidence supports."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range rdfs:Literal . - a rdf:Property, ; - _:genid35 ; - ; - _:genid36 ; - "The weight must be between 0 and 1. Usually, all Criteria can be integrated within a weighted sum equal to 1."@en . + a owl:DatatypeProperty ; + rdfs:label "weight"@en ; + rdfs:comment "Relative importance of the Criterion."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range xsd:decimal ; + skos:scopeNote "The weight must be between 0 and 1. Usually, all Criteria can be integrated within a weighted sum equal to 1."@en . - a rdf:Property, ; - _:genid37 ; - ; - _:genid38 ; - "This description gives the view of the creator of the Criterion weights on how to interpret and use them during the evaluation process."@en . + a owl:DatatypeProperty ; + rdfs:label "weighting consideration description"@en ; + rdfs:comment "Explanation of how the weighting of a Criterion is to be used."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range xsd:string ; + skos:scopeNote "This description gives the view of the creator of the Criterion weights on how to interpret and use them during the evaluation process."@en . - a rdf:Property, ; - _:genid39 ; - ; - _:genid40 ; - """An existing codelist http://publications.europa.eu/resource/authority/number-weight -Example see: https://docs.ted.europa.eu/eforms/0.3.0/index.html#awardCriteriaSection"""@en . + a owl:ObjectProperty ; + rdfs:label "weighting type"@en ; + rdfs:comment "Indication of how the weight should be interpreted in a complex evaluation expression, e.g. as a percentage in an evaluation expression."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept ; + skos:scopeNote "An existing codelist which can be used is OP's Number weigth controlled vocabulary"@en . + + + a owl:Class ; + rdfs:label "Constraint"@en ; + rdfs:comment "Limitation applied to an Information Concept."@en ; + rdfs:isDefinedBy ; + rdfs:subClassOf ; + skos:scopeNote "Constraints are requirements in themselves, since they impose prerequisites which influence the definition, use and/or fulfilment of the requirement. They represent hard conditions such as minimum or maximum expressions which can be used to evaluate pieces of information, the required age, income, involvement in activities, etc. An example from the eProcurement domain is a threshold as the minimum turnover required by the buying organisation to select the candidates. Note that CCCEV does not provide any specific guidance on when which kind of Requirement should be used. Users of this vocabulary should make decisions on this topic in their specific context."@en . + + + a owl:Class ; + rdfs:label "Evidence Type List"@en ; + rdfs:comment "Group of Evidence Types for conforming to a Requirement."@en ; + rdfs:isDefinedBy ; + skos:scopeNote """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."""@en . + + a owl:Class ; + rdfs:label "Criterion"@en ; + rdfs:comment "Condition for evaluation or assessment."@en ; + rdfs:isDefinedBy ; + rdfs:subClassOf ; + skos:scopeNote """In general, Criteria are used for comparison, filtering or selection purposes. Criteria usually set minimum conditions (e.g. limits, intervals, thresholds, etc.) that need to be met in order to pass the requirements or to fulfil them to a certain degree or quality. The concept of Criteria is broader than the concept of Constraint since it covers more usages. The evaluation of the fulfilment is usually supported by the provision of Evidence. +For example in the eProcurement domain, the eProcurement Ontology defines different subclasses of Criterion such as exclusion grounds, selection criteria or award criteria. A concrete example of a Criterion is 'participation in a criminal organisation' which could also be considered as an exclusion ground criterion in the procurement domain or for requiring a public service."""@en . + + + a owl:Class ; + rdfs:label "Supported Value"@en ; + rdfs:comment "Value for an Information Concept that is provided by an Evidence."@en ; + rdfs:isDefinedBy ; + skos:scopeNote """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. +"""@en . + + + a owl:Class ; + rdfs:label "Information Concept"@en ; + rdfs:comment "Piece of information that the Evidence provides or the Requirement needs."@en ; + rdfs:isDefinedBy ; + skos:scopeNote "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."@en . + + + a owl:DatatypeProperty ; + rdfs:label "accessibility"@en ; + rdfs:comment "Information about how the Public Event can be approached, reached or entered, in particular for people with special needs."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range rdf:langString ; + skos:scopeNote "This property may be provided in multiple languages with multiple instances of the accessibility property."@en . + + + a owl:ObjectProperty ; + rdfs:label "audience"@en ; + rdfs:comment "The target group of people for whom the Public Event is created."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept . + + + a owl:DatatypeProperty ; + rdfs:label "event number"@en ; + rdfs:comment "The sequence position of the Public Event."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range rdf:langString ; + skos:scopeNote "Examples could be the ''4th\" or \"2022\"."@en . + + + a owl:ObjectProperty ; + rdfs:label "event status"@en ; + rdfs:comment " This property defines the overall status of the event."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept ; + skos:scopeNote "The recomended code list is the Event Status Controlled vocabulary maintained by the Publications Office of the EU."@en . + + + a owl:DatatypeProperty ; + rdfs:label "expected number of participants"@en ; + rdfs:comment "The number of participants expected to participate in the event."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range xsd:integer . + + + a owl:ObjectProperty ; + rdfs:label "format"@en ; + rdfs:comment "A plan of organisation or arrangement of the Public Event."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept ; + skos:scopeNote "Examples include conference call, physical meeting or hybrid."@en . + + + a owl:ObjectProperty ; + rdfs:label "registration page"@en ; + rdfs:comment "A web page that provides means to attend the Public Event."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range foaf:Document . + + + a owl:Class ; + rdfs:label "Public Event"@en ; + rdfs:comment """Something that happens at a particular place and time, +organised by one or more agents for a particular purpose, and is of interest to a general + audience. This definition excludes natural events such as earthquakes and volcanic +eruptions."""@en ; + rdfs:isDefinedBy . + + + a owl:Class ; + rdfs:label "Accounting Document"@en ; + rdfs:comment "Financial and non-financial information as a result of an activity of an organisation."@en ; + rdfs:isDefinedBy ; + skos:scopeNote """Accounting documents, might include: +
    +
  • Financial statements (incl. the list of participating interests, subsidiary undertakings and associated undertakings, their registered office address and proportion of capital held), audit reports.
    • +
  • Non-financial statements, management reports and other statements or reports.
    • +
  • Annual financial reports.
    • +
"""@en . + + + a owl:DatatypeProperty ; + rdfs:label "registration date"@en ; + rdfs:comment "The date on which the legal entity has registered in some jurisdiction for regulatory and / or for tax purposes."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range xsd:date . + + + a owl:ObjectProperty ; + rdfs:label "code"@en ; + rdfs:comment "The classification of the administrative unit."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept . + + + a owl:DatatypeProperty ; + rdfs:label "coordinates"@en ; + rdfs:comment """ A list of geographic coordinates that define the extent of the Geometry."""@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range xsd:string ; + skos:scopeNote "Can be expressed as longitude, latitude, elevation."@en . + + + a owl:DatatypeProperty ; + rdfs:label "crs"@en ; + rdfs:comment "An identifier for the coordinate reference system."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range xsd:anyURI ; + skos:scopeNote "Can be a coordinate-based local, regional or global system used to locate geographical entities."@en . + + + a owl:ObjectProperty ; + rdfs:label "geometry type"@en ; + rdfs:comment "The classification of the Geometry."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept ; + skos:scopeNote "Can be a point, line or polygon."@en . + + + a owl:DatatypeProperty ; + rdfs:label "latitude"@en ; + rdfs:comment "The geographic coordinate that specifies the north / south position of the Geomerty on the Earth's surface."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range xsd:string . + + + a owl:ObjectProperty ; + rdfs:label "level"@en ; + rdfs:comment "The level of the administrative unit in the hierarchy."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range skos:Concept ; + skos:scopeNote "The recommended code list to indicate the level of an Admin Unit is the Administrative territorial unit type Controlled Vocabulary maintained by the Publications Office of the EU. "@en . + + + a owl:DatatypeProperty ; + rdfs:label "longitude"@en ; + rdfs:comment "The geographic coordinate that specifies the east / west position of the Geometry on the Earth's surface."@en ; + rdfs:domain ; + rdfs:isDefinedBy ; + rdfs:range xsd:string . + + + a owl:Class ; + rdfs:label "Administrative Unit"@en ; + rdfs:comment "A detailed administrative unit organized in a hierarchy."@en ; + rdfs:isDefinedBy ; + skos:scopeNote "This class should be used whenever a classification mechanism is in place, in alternative to the properties adminUnitL1 and adminUnitL2 of the Address class which allow free text."@en . \ No newline at end of file