I found these two sets of information regarding device capabilities support:
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:
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
Define use of XSD 1.1 for device constraints
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
Powered by a free Atlassian Confluence Open Source Project License granted to CIP4. Evaluate Confluence today.