In our case, the response is always empty since it is indeed difficult to determine which Notifications to return. Some error events may have been resolved in the mean time. Milestones only make sense when handled immediately to show progress in UI.
Ok, I understand. Thank you very much for your answer.
If you look at JDF 1.6, the specification implies (albeit does not enforce) notifications as Signals: From JDF 1.6:
Notification messages are generally sent as Signals.
QueryNotification is defined to allow subscriptions for Notification messages.
Notification elements are also used to signal usual events due to any activities of a device, operator, etc. (e.g.,scanning a bar code).
Such a Signal always has a @Type="Notification".
Therefore I don't see any reason and certainly no specification requirement to retain Signals. (Note the RepeatMessages Query does, bit it is neither mentioned in an ICS nor is it widely implemented).
Powered by a free Atlassian Confluence Open Source Project License granted to CIP4. Evaluate Confluence today.