Re: canonical ipp json encoding
Benjamin Gordon via ipp <[email protected]>
| Newsgroups | gmane.ietf.ipp |
|---|---|
| Message-ID | <CADaYBq1SvYnCCUk8FM8B2AhE8rWs+qNBaWTwbfzstgtLyD8BaA@mail.gmail.com> |
Resending since it seems that the original email got dropped somewhere. From today's call, it sounded like the JS library at https://github.com/williamkapke/ipp and/or https://github.com/sealsystems/node-ipp has a representation that's already along the right lines, but there might be some cases that they don't address. What do people think about formalizing something based on those? Thanks, Benjamin On Thu, Mar 23, 2023 at 4:33 AM Benjamin Gordon <[email protected]> wrote: > > Hi all, > > We have recently started some discussions internally about what a web-based printing API might look like. Rather than inventing yet another new way to describe printers and states and jobs and so on, I've been advocating for building on all the PWG's hard work with IPP. The sticking point is that binary IPP frames aren't very ergonomic to work with in Javascript. Has there ever been any consideration of defining a canonical JSON encoding? If we brought forward a proposal for such a thing in the next couple of months, would there be interest in moving it through the whole standardization process? > > Thanks, > Benjamin _______________________________________________ ipp mailing list [email protected] https://www.pwg.org/mailman/listinfo/ipp