Uploaded image for project: 'XJDF / JDF'
  1. XJDF / JDF
  2. JDF-516

Review Event / Notification messages

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: TSC VERIFY (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 1.7, 2.1
    • Component/s: JMF
    • Labels:
      None

      Description

      Events are a bit useless when seen out of context of the current status (e.g. exact counter values)

      we have multiple options to fix this:
      a.) add events to DeviceInfo (and JobPhase?)
      b.) add semantics to JMF/XJMF packages
      c.) use Activity elements for events

        Draft

        7.10.3 SignalNotification
        SignalNotification SHOULD be used to send milestone events.
        Machine events SHOULD be provided in the context of a SignalStatus or SignalResource in order to provide additional context of the event such as counter values and job identifiers and SHOULD NOT be sent in SignalNotification messages.

        Table 7.53: ResourceInfo Element

        Event * element Event MAY be used to specify machine-dependent codes that triggered a SignalResource or AuditResource.

        Table 7.xx: DeviceInfo Element

        Event * element Event MAY be used to specify machine-dependent codes that triggered a SignalStatus or AuditStatus.

        <Make Event a top-level subelement with referenced by header etc.>
        8.23.1 Event
        This element provides additional information for common events. Events are designed to enable devices to send individual event or error codes. These codes SHOULD NOT be used to transport status transitions or resource information that is standardized in ##ref DeviceInfo, ResourceInfo or their descendent elements.

        7.18.2.2 Activity
        Activity elements allow tracking of device and operator tasks. in addition to the global definition of @Status and @StatusDetails. An Activity SHOULD define a task that has a duration. Singular events SHOULD be specified in DeviceInfo/Event.

        ====== Draft 2 =====
        <Make semi-unconditional for 1.7 and 2.1 see below for 1.7 fixes>
        <Also fix the missing "New in" Flags>

        ResourceInfo:
        Event MAY be used to specify machine-dependent codes that triggered a
        Signal/@Type=Resource or AuditResource.

        DeviceInfo:
        Table 7.67: DeviceInfo Element
        Event MAY be used to specify machine-dependent codes that triggered a
        Signal/@Type=Status or AuditStatus.

        5.34 Notification
        Notification messages are generally sent as Signals. Query/[@Type="Notification"] is defined to allow subscriptions for
        Notification messages. Notification elements are MAY also be 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".

        Machine events SHOULD be provided in the context of a Signal/@Type="Status" or Signal/@Type="Resource" in order to provide additional context of the event such as counter values and job identifiers and SHOULD NOT be sent in Signal/@Type="Notification" messages.

         

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                prosi Rainer Prosi
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: