Skip to content
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

New eForms subtype required #745

Open
csnyulas opened this issue Feb 20, 2025 · 1 comment
Open

New eForms subtype required #745

csnyulas opened this issue Feb 20, 2025 · 1 comment
Labels
aux: mapping it is related to the TED-SWS mappings project
Milestone

Comments

@csnyulas
Copy link

Starting with eForms SDK v1.12 there is a new eForms subtype E6:
https://docs.ted.europa.eu/eforms/1.12/reference/code-lists/notice-subtype.html
(which was not present in SDK 1.11)

So, to allow a complete mapping of the values of field OPP-070-notice, we need a new subclass of epo-not:eFormsNotice, called epo-not:NoticeE6

This new class should appear in future version of this diagram:
https://docs.ted.europa.eu/EPO/latest/_attachments/html_reports/eNotice/index.html?goto=2:1:141

BTW, I am not sure why the epo-not:NoticeX01 and epo-not:NoticeX02 are not present in ePO, but once we will start mapping those notices as well, we will need those two classes as well.

@csnyulas csnyulas added the aux: mapping it is related to the TED-SWS mappings project label Feb 20, 2025
@andreea-pasare andreea-pasare added this to the 5.0.0 milestone Feb 20, 2025
@muricna
Copy link
Collaborator

muricna commented Feb 20, 2025

X01 and X02 are not required they are not procurement specific notices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aux: mapping it is related to the TED-SWS mappings project
Projects
None yet
Development

No branches or pull requests

3 participants