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
In February 2023 it was proposed that the metadata element of icarResource (and certainly icarEventCoreResource) should be made a required field, and that the source and sourceId components of that icarMetadataType should be made required.
This is potentially a breaking change to implementations and would normally have to wait until a major version - ADE 2.0.
Members of the technical working group have confirmed that as far as they are aware, these fields are treated as mandatory in all their implementations, and on that basis it might be possible to bring this in when ADE 1.4 is released in late 2023 instead.
However, there may be other implementations of the ICAR ADE specification of which we are not aware. This therefore is notice to all users. Please ask your interoperability partners to also read and respond to this notice. Let us know if you are using ADE and whether this would be a breaking change for your implementation.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
In February 2023 it was proposed that the metadata element of
icarResource(and certainlyicarEventCoreResource) should be made a required field, and that the source and sourceId components of thaticarMetadataTypeshould be made required.See issue #366
This is potentially a breaking change to implementations and would normally have to wait until a major version - ADE 2.0.
Members of the technical working group have confirmed that as far as they are aware, these fields are treated as mandatory in all their implementations, and on that basis it might be possible to bring this in when ADE 1.4 is released in late 2023 instead.
However, there may be other implementations of the ICAR ADE specification of which we are not aware. This therefore is notice to all users. Please ask your interoperability partners to also read and respond to this notice. Let us know if you are using ADE and whether this would be a breaking change for your implementation.
Beta Was this translation helpful? Give feedback.
All reactions