Change Notice and efbc:ChangedNoticeIdentifier

[pietropalermo2IT]

It the specifications there is an example that "clarifies" that the efbc::ChangedNoticeIdentifier contains the Notice Identifier (BT-701) of the changed notice, but there are two issues:
1- using eNotice it is clear that the notice number (e.g. 79191-2026) must be put in instead;
2 - it is not specified which notice number must be put in when there are more than one CN: the second CN must contain the notice number of the original notice or the notice number of the first CN?
Thanks.

[YvesJo]

Hi,
When creating a Change on a Competition notice (formerly Contract Notice) make sure to refer to the latest Competition, should it also be already a Change Notice. Please note that a Change may only be created on a published notice.
KR

[pietropalermo2IT]

Hi, I guess I was not clear: the example reports
efbc:ChangedNoticeIdentifier schemeName="notice-id-ref">755db7f6-6aa1-453b-9087-1df5f7725112-02</efbc:ChangedNoticeIdentifier>
but it is not correct: the reference is TED number such 2026-xxxxxx and there is not a schemeID

[YvesJo]

The example 755db7f6-6aa1-453b-9087-1df5f7725112-02 is using the notice-id-ref format (i.e. UUID-v):

• UUID = 755db7f6-6aa1-453b-9087-1df5f7725112
• version = 02

[pietropalermo2IT]

When we implemented the eForm via eSender in Italy, we tried to use the uuid and we received errors from TED so we converted to the use of the ojs-notice-id. Anyway, since you stated that it is all ok, we can close the discussion: our attempt was simply to help other eSenders not to be involved in same troubles. Kind regards.

[YvesJo]

Hi,
When I understand, you're letting me know about a discrepancy between the documentation and the implementation, right?
I will check that and clarify the course of action.
Thanks

[YvesJo]

I couldn't confirm the issue. If you would have further details to share, please do so.
KR

[AHenselCsx]

Hm, it IS a bit difficulty (and need concentration) to differentiate those UUID references, i.e. when to use the one or the other, as all have the same pattern. Confusingly some values (like the "notice-id-ref") are not a plain UUID, but a UUID plus an extension and still look like a regular UUID.