1
0
-1

I found these two sets of information regarding device capabilities support:

  • XJDF no longer provides a CIP4 defined syntax for defining device capabilities. It relies instead on XML schemas (XSD) to provide details of the supported subset of XJDF. This removes some features and capabilities but allows use of standard XML schema enabled tools which should allow for more rapid adoption. For instance, there are tools that convert XML to schemas and can create sample XML files for schemas. With these standard tools, combined with the simplified design of XJDF, the goal of plug & play for XJDF becomes achievable.
  • Since XJDF relies on subset schema in the official namespace for device capabilities, you could also be a bit liberal in your interpretation of subset and simply add the respective proprietary features to your device schema.

This provides very little insight as to how one would build a syntax for defining their own device capabilities that includes constraints. So I have some questions:

  1. Are there any existing examples of defined syntax for defining device capabilities - particularly for printers?
  2. Must we keep within the existing CIP4 JDFSchema_2_0 or can we create an entirely different schema
  3. Is any version of XML supported - or only 1.0 Fifth edition? Would the use of XML 1.1/XSD 1.1 be appropriate (it can be used to support constraints) - or is that not supported.
  4. Do you have any recommendations or starting points to defining device capabilities - particularly for printers - which must include a fairly complicated set of constraints.
    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      See also my reply to XJDF: does XJDF support XML 1.1?

      Now your questions:

      1.) Currently not on the example site.

      2.) you definitely need to retain the official namespace for the official features, else there is no way to vaildate the official XJDF part. If you absolutely need proprietary extensions, these - and ony these - can be in your own namespace, but this is discouraged.

      3a.) in real life XML 1.0 should be used.

      3b.) currently only XSD 1.0 is supported but encouraging support for XSD 1.1 is a great idea. See JDF-662 - Define use of XSD 1.1 for device constraints Drafting for a follow up.

      4.) this sounds like a topic for the JDF technical working group: JDF Technical WG. We meet every second thursday (teleconference) but note that summer has arrived leading to vacations in Europe and thus a few cancellations

        CommentAdd your comment...