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

Un-deprecate CustomerInfo/CustomerMessage



    • Type: Bug
    • Status: Implemented (View Workflow)
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.7
    • Component/s: Resources
    • Labels:


      In JDF 1.5, the CustomerInfo/CustomerMessage element was deprecated, with a deprecation note of "Use Comment instead."  When I asked Rainer about this, the thinking was that the element name "CustomerMessage" seemed as if it was a simple message, which, yes, could be replaced by a Comment.

      However, the CustomerMessage element is much more than that.  It defines a mechanism for a sender of the JDF to get notifications about the job, and a fairly complicated mechanism at that, with filtering of messages, different languages, a list of parameters to include in the message, and so on.  This could definitely not be replaced by a Comment element.

      Rainer said that he thought it was a mistake in JDF 1.5 to deprecate this, or at least to deprecate it with an incorrect deprecation note.

      I also pointed out that usage of the CustomerMessage element is recommended in the "Application Note for the IDP ICS", an official CIP4 document.  Admittedly, the document hasn't been updated since 2006, but it is nonetheless an official document.

      When Rainer heard about the Application Note recommendation, he said that he thought we should un-deprecate this element in JDF 1.7, and asked me to write the Jira issue.  Here it is.

      I will raise a question: should this be a 1.6 Errata issue?  On the one hand, we're getting fairly late to be adding errata to 1.6, but on the other hand, if it is a clear mistake, it seems only right to reinstate this in 1.6 as well as 1.7.  I will open as a 1.6 Errata issue, and we can remove that indication if we decide otherwise.






              • Assignee:
                denniscarney Dennis Carney
              • Votes:
                0 Vote for this issue
                2 Start watching this issue


                • Created: