You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Different elements that nowadays are represented as codes in the ProcedureType CL are not actually procedures. For those cases, which are Legal Basis, Legal Regimes or Attributes, ESPD could analyse the extension of the class "procedure" (in UBL 2.3) to refer to these elements without using them as Codes per se.
This issue is specifically for the analysis of "RESTRICTED_ACCELERATED" and how it could be applied to ensure its correct usage. The proposal would be to extend the class "Procedure", where the code refers to using the new version of UBL 2.3.
The text was updated successfully, but these errors were encountered:
hricolor
added
the
TBD
Needs analysis and discussion with the requester and the rest of stakeholders
label
Mar 30, 2020
After the analysis and discussion on the topic, it has been concluded the next release of ESPD will not include information regarding the procedure, but only Exclusion and Selection grounds. The information referencing the procedure will come from eForms. Therefore, as eForms has already extended the XSD to meet its business requirements, there is no need to extend the ESPD schema. This would create an extra complexity, and it does not make sense to extend an international standard if it could create complexity.
Different elements that nowadays are represented as codes in the ProcedureType CL are not actually procedures. For those cases, which are Legal Basis, Legal Regimes or Attributes, ESPD could analyse the extension of the class "procedure" (in UBL 2.3) to refer to these elements without using them as Codes per se.
This issue is specifically for the analysis of "RESTRICTED_ACCELERATED" and how it could be applied to ensure its correct usage. The proposal would be to extend the class "Procedure", where the code refers to using the new version of UBL 2.3.
The text was updated successfully, but these errors were encountered: