attachment-0001

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2800.1106" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT size=2> <DIV><FONT size=2>We will review the specification in sections.</FONT></DIV></FONT></DIV> <DIV><FONT size=2> </DIV> <DIV>While the first ten pages of the specification show the formal declaration of the document and the table of contents, the first chapter starts on page 10.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>On Monday, March 1st, and Tuesday, March 2nd, we will concentrate on the first two chapters, pages 10 - 18.</FONT></DIV> <DIV><FONT size=2>- The Idea: This is the high level overview and tells about the UPDF concept and the main components involved. If somebody does not want to dive in deeply, this is the best chance to understand the background and getting familiar to the terminology.</FONT></DIV> <DIV><FONT size=2>- Common Tags: Some elements and attributes are used all over the place. We have decided on explaining them upfront. That speeds up reading later.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>On Wednesday, March 3rd, we will concentrate on the configuration files.</FONT></DIV> <DIV><FONT size=2>- Device Configuration: The driver entry point into the UPDF world and the environment for the base unit.</FONT></DIV> <DIV><FONT size=2>- Option Configuration: The environment for optional units.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>As you should have warmed up by then, we will discuss the unit description schema - the heart of the concept - the next five work days.</FONT></DIV> <DIV><FONT size=2>- On Thursday, March 4th, we will concentrate on the DeviceHeader and the Header under PrintCapabilities.</FONT></DIV> <DIV><FONT size=2>- On Friday, March 5th, we will concentrate on all predefined features. A lot of pages, but similar information per feature.</FONT></DIV> <DIV><FONT size=2>- On Monday, March 8th, we finish the features with the generic and composite features, plus the user interfaces, as they are closely related to the features.</FONT></DIV> <DIV><FONT size=2>- On Tuesday, March 9th, we may concentrate on Objects (raster graphic, device fonts). </FONT></DIV> <DIV><FONT size=2>We will only talk about device font details on special request, as that is an area for the absolute experts. But we can handle that.</FONT></DIV> <DIV><FONT size=2>- On Wednesday, March 10th, we'll finish the unit description with the dependencies and events.</FONT></DIV> <DIV><FONT size=2>- On Thursday, March 11th, we could talk about the command sequences, and the Parameter Converter, as these two issues are closely related to events.</FONT></DIV> <DIV><FONT size=2>- Leaves us with the locales and the user policies for Friday, March 12th.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>We don't have to stick to that schedule literally.</FONT></DIV> <DIV><FONT size=2>But some may like to know, how chapters can be grouped.</FONT></DIV> <DIV><FONT size=2>We'll decide on changes flexibly while we go.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Please send all emails to the UPDF reflector.</FONT></DIV> <DIV><FONT size=2>I will answer personal emails, too. But that's not the idea.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Hope we'll see some people talking it over.</FONT></DIV> <DIV><FONT size=2>If we don't see any traffic, that either means nobody cares or the design as well as the specification is considered perfect.</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Regards</FONT></DIV> <DIV><FONT size=2>Norbert Schade</FONT></DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2></FONT> </DIV> <DIV><FONT size=2>Norbert Schade<BR>69 Prescott Drive<BR>North Chelmsford<BR>MA 01863<BR>phone: 1-978-251-1017<BR>email: <A href="mailto:norbertschade@comcast.net">norbertschade@comcast.net</A></FONT></DIV></BODY></HTML>