JIPP can process these as "KeyValues" but this is unsatisfying because well-known keys and frequently well-known values exist, but neither keys nor values appear in as IANA defined terms. Manually retyping these into client/server code can lead to bugs.
It would be ideal to identify the relevant specs and where possible extract the acceptable fields and values wherever possible.
These have snuck into several specs as Octet Strings with well-defined form. For example, https://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext3v10-20120727-5100.13.pdf defines several keys such as
printer-output-tray
.JIPP can process these as "KeyValues" but this is unsatisfying because well-known keys and frequently well-known values exist, but neither keys nor values appear in as IANA defined terms. Manually retyping these into client/server code can lead to bugs.
It would be ideal to identify the relevant specs and where possible extract the acceptable fields and values wherever possible.