Hi Mike,
I have been seeing the exact same issue in the 3D space.
If we are able to create a parallel 3D document, I can promote it via AMSC and ISO/IEC JTC1 efforts and then ask for feedback when developers start following the guidelines and building sample applications to test.
Thanks.
Best Regards,
/Paul
Sent from my iPhone
> On Dec 1, 2017, at 9:44 AM, Michael Sweet <msweet at apple.com> wrote:
>> Bill,
>>> On Nov 30, 2017, at 5:58 PM, wamwagner at comcast.net wrote:
>>>> All,
>> Interesting project. We could argue the outline order a bit. Although a clear presentation the basics is necessary, IPP as a way to interface with printers (lower case, hardcopy image-making device) has been around for ages and probably would not cause much excitement. Perhaps there would be more interest (and there certainly is more need) in aspects where there is not much implementation (and great potential); infra/cloud and scanning/image handling. And I wonder how much interest there would be from application developers without first getting their managers aware of the product advantages?
>> I've been getting a lot of questions from application/framework developers on Linux (trying to modernize the Linux printing stack) as well as cloud service developers using things like Node.js to support printing. In both cases we are talking about the client-side interactions with an IPP Printer (locally or in "the cloud"), with the developer unsure about how IPP works or how to accomplish their task.
>> What *I'm* envisioning is more of a high-level how-to guide for using IPP - that first chapter will get people needing to print (managers included) excited about IPP because a) it solves their problem and b) they know they will learn how to use it by reading the rest of the book.
>> If we expand the scope too far (particularly into areas that haven't been widely implemented) then it (IMHO) will make the material less compelling and harder to approach.
>> We don't need to document everything in one place. We don't need to answer every question. But we do need a way for new developers to get comfortable using IPP...
>> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer
>>