-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Questions regarding the purely national EG in ESPD-EDM v3.x.x #interproc #334
Comments
We are working on this part also in our application. Would be great to get an answer to this question. |
This is a very important question! Would be great with input on this. |
Hello, Thank you for your questions. For Question 1, the answer is yes. The logic that you expressed regarding the "Purely National EG" criterion is correct. We have created an xml file test from a copy of the ESPD-request that includes the question subgroup with multiple cardinality "1..n" replicated twice, as proposed above. The file has passed the validation with the ESPD Validator available at "https://www.itb.ec.europa.eu/espd/upload". That means that the multiple cardinality "1..n" allows to provide more than one Purely National EG criterion. The model is consistent whether there is only one or several corresponding eCertis criterion. Please feel free to reproduce the test taking the ESPD-request file from the master branch and come back to us if you encounter any troubles: https://github.com/OP-TED/ESPD-EDM/blob/master/xml-examples/ESPD-Request.xml. For Question 2, as discussed during the last OUC meeting held on 16 June 2022, the issue is under discussion on eCertis side. The ESPD only reuses the existing Purely National EG criterion from eCertis. Kind regards, |
Hi @pascalinelaur |
Hello @Nikanoras, Hello @konstantinosraptis91, Thank you for your follow-up question. Indeed, there is a difference between the mockup (from the online technical handbook documentation on exclusion criteria) and the data structure of criterion C24 nati-ground Purely national exclusion grounds. We have analysed this difference and here is our first outcome. We have to decide whether to :
Or to :
We will come back to you as soon as a clear choice between the two options has been made. Kind regards, |
Dear ESPD Team! Open User Community Meeting Report states that "Issue #334, regarding the purely national Exclusion Grounds in ESPD-EDM v3.x.x, will not be solved within the next few months and require a change request on eCertis side". Could you please provide a time estimate when we can expect the solution on eCertis side? Thank you in advance! |
@Frantzenna We currently collect all requirements for eCertis and plan to update it in the course of next year. |
Github issue #334 6 Subtasks of Jira ticket TEDSPD-297 Jira ticket TEDSPD-369 Jira ticket TEDSPD-367 Jira ticket TEDSPD-368 Jira ticket TEDSPD-371 Jira ticket TEDSPD-372 Jira ticket TEDSPD-379
Hello @Nikanoras, Hello @konstantinosraptis91, Thank you again for your follow-up question. After discussions, it has been agreed to update the Data Structure because it is by nesting the evidence to its related Question Subgroup that the semantic link between both is created. This is mandatory especially when the related Question Subgroup is of multiple cardinality. However, when the cardinality is single, the update (nesting the Question Group or Subgroup for providing Evidence) can still be performed for semantic and maintenance purpose. Hence, the update will be made for multiple and also single cardinality of the related Question Subgroup. For the criterion C24 EG nati-ground (EG-Purely_national), the update will look like the following screenshot: This update will be generalized for the whole Criterion Excel file and will be available in a future release. Kind regards, |
Hello,
Thank you for your reply. Best regards, Ajda |
Thank you for your question @AJDAKOST ,
Kind regards |
Hello,
Thank you. Best regards, Ajda |
Hello ESPD team
In the context of the InterProc project, we are trying to understand how to implement the "Purely National EG" in ESPD version 3.x.x. According to the technical handbook and more specifically in Figure 88 it is possible to have multiple purely national EG and the text above the figure says that those national criteria that are displayed in the figure have been captured from e-Certis. As we see by retrieving the "Purely National EG" parent criterion (EU Criterion) from e-Certis, there is a sub-Criteria list in the XML format, which includes all "the purely national EG" for different countries/jurisdictions that are available in e-Certis. By looking at the relevant criterion from the ESPD perspective in the Taxonomy, we see that the placeholder for those "Purely National EG" is different at the syntax binding level in the ESPD-EDM.
Figure 1 - Purely National EG Criterion Original Structure
Figure 2 - Purely National EG Criterion Structure which includes 2 Purely National EG Criteria
If we understand it correctly the structure of this particular criterion in Taxonomy doesn't include a sub-criteria list, but instead of that uses the internal sub-group with cardinality one-to-many as a placeholder for multiple "Purely National EG". So for instance, if we had a case where a country has two "Purely National EG" the structure would expand like in Figure-2 to include both of those "Purely National EG". If our logic is correct and in combination with the first requirement mentioned in the technical handbook (see Figure 3) the e-Certis service MUST be able to provide those two individual "Purely National EG" criteria and also allow the Member State to include individual "Purely National EG".
Figure 3 - First Requirement in Purely National Criteria Section
Question 1
Is the logic expressed above regarding the "Purely National EG" correct?
Question 2
Is e-Certis capable of providing multiple "Purely National EG" criteria? Because by looking at the available options from e-Certis's perspective as an editor we are not sure if it is possible to edit the "Purely National EG" criterion to add more "Purely National EG" criteria.
The text was updated successfully, but these errors were encountered: