From PZehler at crt.xerox.com Tue Jan 6 14:19:10 2004 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:05:01 2009 Subject: UPD> RESEND UPDF aligned with Semantic Model Message-ID: <81FE58FCC6748A4A915BDDCACA900C832B9D28@CRTE128> All, I have had a chance to briefly look at the latest UPDF schema. A great deal of work has been done to align it with the PWG Semantic Model. I was very pleased to see the manner in which the UPDF schema made use of the PWG Semantic Model Schema. (it's the way I would have done it) Naturally there are areas that required differences based on the specific needs of UPDF. Even in those areas alignment is maintained where possible. 1. UPDF imports the PWGCommon and MediaElements schemas in the UPDFDataTypes schema. This allows UPDF's data types to be based on and extend the PWG Schema's base types. 2. UPDF names elements and their types either identical to the Semantic Model schemas or - if that is not possible in special cases - use the same naming conventions. 3. UPDF refers to the Semantic Model and Media enumerations of well known values wherever possible. Even if UPDF does not refer to the Semantic Model and Media enumerations/unions 1 to 1, they refer to it and extend it where necessary. 4. UPDF uses a number of data types (e.g. languages, countries, font related lists, etc.), which they propose as an extension to the Semantic Model. Congratulations on a job well done, Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice: (585) 265-8755 FAX: (585) 422-7961 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040106/69f46385/attachment.html From norbertschade at comcast.net Tue Jan 13 10:00:56 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> Fw: ClassifyingID Message-ID: <008601c3d9e6$0c504b00$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 12:22 PM Subject: ClassifyingID This is probably one of the most important changes we made lately. The previous attributes Predefined_ID and Proprietary_ID have now been merged into a single attribute ClassifyingID. This is not a unique attribute by definition, but will provide for a meaningful identification of a record. We had to change the data types significantly to be able to do this. we now much more work with unions and patterns, which was a request earlier. Element and attributes (other than the type definition) are not affected in any way by this change. Advantage: Now it's much easier to check a classifying ID, as it is only one. In the design of the schemas it's easier to control the classifying identifiers. As a developer filling in data into an instance you'll find it more convenient, as you will see a list of predefined values as a template to choose from, but in many cases can overwrite that with your proprietary value if required. The reference to a classifying id in the command sequence instance is now straightforward. Before there was an implication that you can refer to a Predefined_ID, but expect the driver to check the related Proprietary_ID as well, if available. Easier coding. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/ed4c2a74/attachment.html From norbertschade at comcast.net Tue Jan 13 10:01:35 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> Fw: CompatibleUPDF Message-ID: <009401c3d9e6$23d25c00$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 12:24 PM Subject: CompatibleUPDF This attribute has been removed from the schemas, as it hasn't been used the way it was intended some time ago - at least as much as I know. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/005e2254/attachment.html From norbertschade at comcast.net Tue Jan 13 10:01:55 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> Fw: DeviceFeature Message-ID: <009e01c3d9e6$2fde2920$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 11:27 AM Subject: DeviceFeature The attribute has been moved up a level from the feature records to the feature level. We still want to offer a chance to provide consistent text strings of common driver features, even if they are not supported by the device, but are common use (e.g. N-Up, driver collation). Advantage: A driver is supposed to check, if a feature is a device feature. If it's not the driver has to check, if it can provide functionality for that specific feature (e.g. is the driver able to do N-Up on the host?). If the driver is not able, it cannot show that specific feature in a driver's user interface. In the past it was necessary to check each single record. This could have slowed down the performance of a driver. Now the first check is on feature level only. Very quick. If DeviceFeature is set to 'false', at least on record is to be expected, which will require the driver to emulate the functionality on the host. The basic philosophy of attribute DeviceFeature is unchanged. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/a3be6518/attachment.html From norbertschade at comcast.net Tue Jan 13 10:02:07 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> Fw: Element structure Message-ID: <00a801c3d9e6$371a93e0$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 10:21 AM Subject: Element structure To keep the path for all features identical when you want to access them from a driver we changed some details: UPDF schema - element DeviceFeatures deleted. historic. it only had one subelement PrintCapabilities and no attributes. - element PrintMediaHandling deleted. this element added an extra layer to the structure, which required a different path to access the media features. - element GenericFeatures (watch the extra 's') deleted. element GenericFeature still unchanged and working. this element added an extra layer to the structure, which required a different path to access the generic features. - element CompositeFeatures (watch the extra 's') deleted. element CompositeFeature still unchanged and working. this element added an extra layer to the structure, which required a different path to access the composite features. - element TBD_VectorObjects deleted. will not be supported in this level of UPDF. UPDFFontHandling schema - element FontDownload deleted. will not be supported in this level of UPDF. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/411f56a8/attachment.html From norbertschade at comcast.net Tue Jan 13 10:02:27 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> Fw: FillPattern Message-ID: <00b201c3d9e6$4276e720$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 3:05 PM Subject: FillPattern This element has been removed (not yet on the web). It was part of the modifying attributes of fonts. It will not be part of the current UPDF level. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/6149034c/attachment.html From norbertschade at comcast.net Tue Jan 13 10:02:51 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> Fw: ID attributes Message-ID: <00bc01c3d9e6$50ee3600$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 11:21 AM Subject: ID attributes Almost all attributes with name="ID" are of type="xsd:ID" now. Exceptions: ID attributes of Parameter elements (in data types and wildcards) and some identifiers in font handling. Advantage: ID were supposed to be unique whereever possible from beginning on. Now your XML application can check that during validation, as they have to be unique by definition. We also have an advantage when we refer to one of them in an attribute of type="IDREF". XMLSpy shows available ID entries for convenience. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/3e94e389/attachment.html From norbertschade at comcast.net Tue Jan 13 10:03:57 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> Fw: update UPDF files Message-ID: <00ca01c3d9e6$78374760$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 10:11 AM Subject: update UPDF files I just updated the files on the UPDF site ftp://ftp.pwg.org/pub/pwg/upd/Current_Version in directories XML_Samples and XML_Schemas. I am going to send reports of the changes I made now. I will split them by subject to keep them short. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/6d672b87/attachment.html From norbertschade at comcast.net Tue Jan 13 10:04:13 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> Fw: update web site, 2. Message-ID: <00d401c3d9e6$81e85ba0$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Wednesday, January 07, 2004 5:45 PM Subject: update web site, 2. I should add that the new files are in subdirectories 'XML Samples' (the are the xml instances) and 'XML Schemas' (these are all schemas). Norbert ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Wednesday, January 07, 2004 5:44 PM Subject: update web site I just updated the UPDF web site ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/ Feel free to check the latest version with all the changes of the last weeks. This is the version Peter Zehler was referring to in his statement yesterday. I will send out detailed comments about the changes the next two days. We have some more candidates for changes, but the bulk of the work is done. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/4a19dd1f/attachment.html From norbertschade at comcast.net Tue Jan 13 11:41:43 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> device fonts Message-ID: <013301c3d9f4$21030700$6501a8c0@ne1.client2.attbi.com> The elements DeviceFontList and DeviceFonts have been removed to avoid redundant layers. The FontObjects element now (not yet on the web) shows the following sub-elements: ModifyingAttributes DeviceFont This does not mean the relationship between any of the elements has changed. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/f9548f7f/attachment.html From norbertschade at comcast.net Sat Jan 17 15:26:29 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> UPDF Specification Message-ID: <000a01c3dd38$310f4fe0$6501a8c0@ne1.client2.attbi.com> This last week we concentrated on the UPDF Specification. It's called version 0.90 now. A few minutes ago I updated the PDF file on the UPDF site. I also updated the UPDF site and changed the layout a bit to follow the current PWG standard. I also updated all UPDF schema and instance files at the proper locations. The specification experienced major changes: - Layout - - Adjusted to follow the PWG Semantic Model - - All schema elements and attributes are listed, most of them are explained. - - All elements are properly numbered, which was a problem for a long time. - Content - - We got rid of some old DTD section and added some general introductions. - - Quite a number of elements and attributes got a new or updated description. One of the main changes is the replacement of the Predefined_ID and Proprietary_ID with the new ClassifyingID. Please follow the links from the UPDF web site and check it out. Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040117/d36b1afd/attachment.html From norbertschade at comcast.net Sun Jan 18 08:00:32 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> UPDF data types Message-ID: <001801c3ddc3$0eb96c60$6501a8c0@ne1.client2.attbi.com> In the process of aligning more closely to the Semantic Model we have adjusted our data types and element and attribute names accordingly. Main concept: - refer to PWG and Media data types where possible. And we do that a lot now. Status: most of it done. some discussion about finishings. - use the PWG and Media data types as the base and extend them where necessary. reasons are for example that we allow for proprietary entries in some cases (you'll find an additional 'xsd:string' in the corresponding union) and we list an additional entry sometimes to represent the device setting. Status: most of it done. The current schemas and instances already reflect that. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040118/1d79d4f2/attachment.html From norbertschade at comcast.net Sun Jan 18 08:07:18 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> naming of UPDF elements and attributes Message-ID: <001c01c3ddc4$00e2d4e0$6501a8c0@ne1.client2.attbi.com> Another step of aligning our schemas closely with the Semantic Model. Main concept: - our element structure - especially of feature elements - is more complex than the one used in the Semantic Model. we still define the feature elements within our schemas, but try to follow the Semantic Model structure and use identical names. another advantage is that this can be used to create the requested connection for bi-directional communication. - generally we now use element and attribute names, which follow the naming concept of the Semantic Model (upper/lower case, avoid '_', etc.) - even if there is no template available in the Semantic Model. An extension to the data types notes some minutes ago: we now use much more patterns to describe rules for proprietary entries (one of Mark's requests of long time). Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040118/57f58319/attachment.html From norbertschade at comcast.net Mon Jan 26 15:44:56 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> web site update Message-ID: <008a01c3e44d$429ce8a0$6501a8c0@ne1.client2.attbi.com> I have updated the UPDF web site. Please check the specification at ftp://ftp.pwg.org/pub/pwg/www/updf/UPDFFunctionalSpecification.pdf Please check the schemas at ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/XML%20Schemas Please check the instances at ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/XML%20Samples Or simply follow the links on the UPDF site. I'll send out little emails per subject about the changes. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/91cf8065/attachment.html From norbertschade at comcast.net Mon Jan 26 15:57:32 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> key/keyref Message-ID: <009301c3e44f$053032e0$6501a8c0@ne1.client2.attbi.com> With UPDF we focus not only on providing a proper structure for a device description. We also try to guide the developer, who eventually will create instances based on the schemas. One way to do it is to work with predefined attribute values. We do that in the definition of the ClassifyingID. Another way is to use patterns. We do that in various places, mainly in the definition of the ClassifyingID. We have been working on yet another method to prevent developers from entering wrong values in elements and attributes. This implicates the use of identifiers and cross references. 1. attribute type ID. We have defined almost all attributes with name ID as type xsd:ID (checking the remaining ones). This ensures uniqueness of all identifiers across the whole instance. 2. attribute type IDREF. Some attributes are declared IDREF, like NonDominantRepresentative (checking further implementation). This allows - depending on the XML application - suggested lists a developer can select a value from. 3. keys Lately we have defined keys. e.g. we have defined keys on all features. 4. keyrefs On top of keys you can define keyrefs. e.g. we have defined keyrefs on the NonDominantRepresentative attributes. No the XML application has numerous chances to validate correct entries and even show proper messages for bad ones. We consider this type of cross references and validation superior functionality to make the whole system more user friendly. Files are on the web. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/8eccedd1/attachment.html From norbertschade at comcast.net Mon Jan 26 15:59:06 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> UPDF Version Message-ID: <009c01c3e44f$3cc68ba0$6501a8c0@ne1.client2.attbi.com> We have edited the UPDFVersion attribute and assigned a more elaborate pattern to it. It's now of form '1.00.00.00'. Check out the details in the Spec. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/3a85ae16/attachment.html From norbertschade at comcast.net Mon Jan 26 16:08:12 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> HelpID Message-ID: <00ae01c3e450$82b7b520$6501a8c0@ne1.client2.attbi.com> We have added a HelpID attribute to each feature. This optional attribute of type xsd:ID is meant to carry the text string for the context sensitive help. It can be localized the same way as the ID attribute of the feature. The UIGroup element also got a HelpID. So you can define context sensitive help for group controls. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/7e84ce09/attachment.html From norbertschade at comcast.net Mon Jan 26 16:05:46 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> user interfaces Message-ID: <00a501c3e450$2b34c0e0$6501a8c0@ne1.client2.attbi.com> We have added a LocaleReference attribute to the UserInterface element. This allows it (not mandatory) to assign a certain user interface to certain locales (of form 'enUS') like for the Asian market, but have another generic user interface as the default (no LocaleReference attribute assigned). Allowed values are pairs of two-character snippets, which are the familiar terms for language and country (see the UPDFDataTypes schema for reference). We have also added a wildcard element to UIGroup and UIFeature elements. This enables developers to link their own UI structures to the UPDF instances to support extended user interface tags. Further details in the Spec. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/8d06bea8/attachment.html From norbertschade at comcast.net Mon Jan 26 16:12:34 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> UPDF Functional Specification Message-ID: <00b701c3e451$1ee95d40$6501a8c0@ne1.client2.attbi.com> We have heavily reviewed and extended the Specification. There are no redundant or old sections any more. Latest changes: - All chapters describing schemas, except the Device Description. - Wildcards and other common tags. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/5d94da4a/attachment.html From norbertschade at comcast.net Wed Jan 28 13:14:52 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> review Dependencies Message-ID: <001001c3e5cb$48541e60$6501a8c0@ne1.client2.attbi.com> Last year we checked different procedures to implement dependencies to find out about the best implementation in UPDF. We did a review of dependencies these days. This includes the schema design as well as the specification (not yet on the web, will be end of week). Although we polished some areas for the final step of the draft version, we did not change the basic idea. We had some objectives: 1. Where to list dependencies in the schema? Theoretically there are two possible solutions. Either you assign them to the feature to be checked once it gets the focus. Or you list all dependencies in a common pool. We stay with the original approach of a common pool. Advantages are maintenance (easier to be checked than looking all over the place) and extensibility. The latter is a unique feature of UPDF, as optional units and/or a user policy could have additional dependencies (dependencies of the master description cannot be removed nor edited). A recommendation to the driver: A dependency of an optional unit or user policy should have priority. However in a perfect design there would not occur any conflict. General driver procedure: First check, if there is a dependency with a FeatureCondition of the currently selected feature. Second check, if there's an action defined in any of the hits with the currently selected feature declared as the dominant feature. 2. Why a dominant feature? Yes, we could have split up all dependencies and listed them depending on the feature with the focus. However we wanted to design a compact structure, which groups related dependencies properly. If there are dependencies with three or more features involved, but different actions depending on which feature has the focus, we were concerned that listing all required combinations separately would confuse the reader and developer of the device description, especially, if the list is not properly ordered. And it narrows the number of candidates for the driver once it hits a FeatureCondition. 3. Extended functionality. We wanted to support functionality commonly available in a number of contemporary driver concepts. This includes messages as well as hints for info buttons, mandatory selections of settings of features based on a dependency and indications that the appearance of a feature should change, once the dependency is resolved. 4. Conversion between different concepts. We always have in mind that dependencies (sometimes called constraints) are defined differently in various concepts. We are positive that a conversion from or to UPDF is always possible and not ambiguous, although you may loose some functionality when converting to other standards. Check it out! Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040128/cffc1826/attachment.html From norbertschade at comcast.net Mon Feb 2 00:15:07 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> file update Message-ID: <002801c3e94b$8652d3e0$6501a8c0@ne1.client2.attbi.com> I updated all schemas, instances and the specification. More details tomorrow. if somebody wants to check early, you may want to start with the key/keyref and GenericFeature/CompositeFeature elements. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040202/0020712d/attachment.html From norbertschade at comcast.net Mon Feb 2 10:14:59 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> halftoning Message-ID: <004401c3e99f$53667000$6501a8c0@ne1.client2.attbi.com> we split the halftoning feature into three single ones: RasterHalftoning VectorHalftoning TextHalftoning that allows easier handling when all three features should appear in the user interface. these three feature are likely a candidate for a composite feature. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040202/87b060b9/attachment.html From norbertschade at comcast.net Mon Feb 2 10:26:50 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> further deployment of key/keyref Message-ID: <005901c3e9a0$facd3ee0$6501a8c0@ne1.client2.attbi.com> The idea of UPDF is not only to provide proper structures to describe a printer with all his options and features, but to help a description developer as much as possible with creating the describing UPDF instances. That's one of the reasons we spent quite some time on investigating the power of the key/keyref elements. We do use that at a number of places to ensure that somebody really makes a reasonalbe entry. We already used it for the NonDominantFeature attribute. Sample are: DominantFeature, SetFeature, FeatureCondition in dependencies. We hope this helps description developers - as it helped us. As a follow-up we could expunge some data types (Feature, FeatureID), which are now managed with more flexibility by the keys. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040202/077490f9/attachment.html From norbertschade at comcast.net Mon Feb 2 10:34:06 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> GenericFeature extension Message-ID: <006201c3e9a1$ff33d7e0$6501a8c0@ne1.client2.attbi.com> We extended the GenericFeature feature. You now can not only define a feature with a predefined list of settings, but with variable settings as well. Check the VariableValue element for that. We also added an optional ClassifyingID attribute to the record. This allows it to use some meaningful entry in case you want to prepare it for bi-directional communication. So you could name a feature with an element name of the Semantic Model and use strings of well known values of the Semantic Model in the ClassifyingID. This provides the level of flexibility we want to have with the GenericFeature. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040202/9ebfbd20/attachment.html From norbertschade at comcast.net Mon Feb 2 10:34:06 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> GenericFeature extension Message-ID: <006201c3e9a1$ff33d7e0$6501a8c0@ne1.client2.attbi.com> We extended the GenericFeature feature. You now can not only define a feature with a predefined list of settings, but with variable settings as well. Check the VariableValue element for that. We also added an optional ClassifyingID attribute to the record. This allows it to use some meaningful entry in case you want to prepare it for bi-directional communication. So you could name a feature with an element name of the Semantic Model and use strings of well known values of the Semantic Model in the ClassifyingID. This provides the level of flexibility we want to have with the GenericFeature. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040202/9ebfbd20/attachment-0001.html From norbertschade at comcast.net Tue Feb 3 12:21:04 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> new SM schemas version 1.0 Message-ID: <00b901c3ea7a$1abcdb00$6501a8c0@ne1.client2.attbi.com> I've downloaded the new schemas of the Semantic Model, version 1.0. As you should know we use four schemas to refer to elements, attributes especially data types. All SM schemas work flawlessly and without any modification. >From now on we'll refer to this version. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040203/1245f08d/attachment.html From norbertschade at comcast.net Tue Feb 3 12:57:38 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> PWG Semantic Model compliant Message-ID: <00d501c3ea7f$3676b000$6501a8c0@ne1.client2.attbi.com> We got a confirmation from Peter Zehler that to the best of his knowledge we are considered PWG Semantic Model compliant by referring to the PWG and Media schemas we import. We'll have an eye on the element and attribute names to use them as much as possible for structures and types common between the Semantic Model and UPDF, but not collide otherwise. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040203/8159a46b/attachment.html From norbertschade at comcast.net Tue Feb 3 13:52:47 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> minimum hardware margins Message-ID: <00fa01c3ea86$ea6969c0$6501a8c0@ne1.client2.attbi.com> We've finished the review of the media minimum hardware margins. The according schemas and instances are available on the web under ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/ Or you can follow the link on the UPDF site. I think this is worth reading. The way it works: 1. MediaHardwareMarginsPattern We have defined a pattern to specify hw margins. We used the custom media size pattern as a template and modified it as needed. It is partly verbal, but tells about the values as well. We think it's a good mixture. 2. MediaHardwareMargins This feature is a predefined one. Its appearance is permanently set to hidden, as we want this to be used as a reference, but not to appear in the user interface (if somebody desperately needs it, there is always the change of composite features). Now this has a number of advantages. First every record is only listed once (before it was specified per media size). --> easier maintenance. Second you can specify as many records as you may need anywhere. It will not show up in the UI unwanted. You can define records especially to be used for landscape, if you need to. Basically you could define a special record for any need. 3. Dependencies We really activate a record in the dependencies. Vision something like "if MediaSize is Letter and Orientation is Landscape, the four margins are 1.1.1.1in". Fortunately our dependencies offer everything we need to check any condition and start any action. Do not use a dominant feature for the action, as you want it checked always. 4. Generic features One may want to create a generic feature called "Edge to Edge Printing", which overwrites all hw margins and sets them to zero when selected. No problem. See this request realized in the samples. You create the feature records and add a dependencies to select a different hw margin record. Be careful with the order of dependencies. They are used in sequential order, master description first, user policy last. I think the way it works is a fortunate coincidence of several factors. We do not have any open request left with this design. Check it out. Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040203/074376ea/attachment.html From norbertschade at comcast.net Tue Feb 3 16:01:06 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> syntax optimization Message-ID: <017e01c3ea98$d7d820a0$6501a8c0@ne1.client2.attbi.com> We finished a number of syntax optimizations. When an element only had exactly one sub-element or exactly one attribute (and no element) we removed that and changed the type of the element accordingly. That simply shortens the schema and improves reading. No architectural change. Files are not yet on the web. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040203/fa6c8211/attachment.html From norbertschade at comcast.net Thu Feb 5 09:12:12 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> RAM, AvailableMemory features Message-ID: <005d01c3ebf2$0cde15c0$6501a8c0@ne1.client2.attbi.com> We've finished a review of the RAM and AvailableMemory features. With the positive experience we made with the redesign of the MediaHardwareMargins feature we did some small modifications to these features as well. Details: RAM We renamed the KB attribute to 'ClassifyingID' and defined a pattern (memory_[\d]*KB). Other attributes have been removed. AvailableMemory The feature is not set to 'Hidden' permanently, but that could well be a useful setting in an implementation. NonDominantRepresentative is made optional, as in many cases there may only be one record. We have replaced some attributes in the record with a VariableValue element (here not on the feature, but the record level), which defines the minimum and maximum values as well as the step. If a relationship between the current RAM and AvailableMemory settings is to be defined, this can be done with dependencies. See the sample for demonstration. The corresponding schemas and instances are available on the web under ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/ Or you can follow the link on the UPDF site. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040205/605b6ae8/attachment.html From norbertschade at comcast.net Thu Feb 5 09:29:46 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:01 2009 Subject: UPD> status Message-ID: <006801c3ebf4$815fe980$6501a8c0@ne1.client2.attbi.com> Of all the requests, wishes and personal notes we have come down to three related open items, all in the area of trying to align as well as possible to the Semantic Model. 1. Check, if the description developer shall be enabled to define unique values for various features. The Semantic Model seems a bit more restrictive than we have been in the past. 2. Check the finishing features. While we have defined special features in UPDF, there is more one 'covers-it-all' feature in the Semantic Model. 3. Do a final check of element, attribute and data type names. This is it! We are working hard to close these three items during this week. That would bring us to a level 0.95 of the specification. If anybody has any requests for version 1 of the standard, this is the time to come forward. We will soon enter the phase of last calls. Major implementations during the last months have been - merge Predefinid_ID and Proprietary_ID to one ClassifyingID and related changes. - rename and adjust elements, attributes and data types compliant to the Semantic Model. - implement key/keyref elements to further help the description developer. - some optimizations on the composite and generic features. - a lot of little things based on feedback and notes we had. The specification document is on the same level as the schemas. The layout is finished. Proper headings and numbering done. The UPDF.xsd master schema shows the exact order of elements as in the specification. The specification is showing the complete structure of all schemas. Various sections have to be further explained. The sample are consistent with the schemas. All sample are validated with the current schemas. We will likely extend the samples to a full features device description for one device. However the current version demonstrates all aspects of the standard. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040205/b3ee5dbe/attachment.html From norbertschade at comcast.net Fri Feb 6 13:20:58 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> 2 of 3 issues resolved - down to the last Message-ID: <006b01c3ecdd$f821d440$6501a8c0@ne1.client2.attbi.com> Items 1 and 3 are finished. 1. we checked the data types, whether they should be open to the description developer for almost arbitrary editing. we are working with a lot of patterns, partly pwg patterns, partly updf patterns. 3. we did a lot of renaming, but no structural changes were necessary. files are not yet on the web. we'll do that over the weekend. Leaves us with the finishing features. ONE TO GO! Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: UPDF reflector Sent: Thursday, February 05, 2004 9:29 AM Subject: UPD> status Of all the requests, wishes and personal notes we have come down to three related open items, all in the area of trying to align as well as possible to the Semantic Model. 1. Check, if the description developer shall be enabled to define unique values for various features. The Semantic Model seems a bit more restrictive than we have been in the past. 2. Check the finishing features. While we have defined special features in UPDF, there is more one 'covers-it-all' feature in the Semantic Model. 3. Do a final check of element, attribute and data type names. This is it! We are working hard to close these three items during this week. That would bring us to a level 0.95 of the specification. If anybody has any requests for version 1 of the standard, this is the time to come forward. We will soon enter the phase of last calls. Major implementations during the last months have been - merge Predefinid_ID and Proprietary_ID to one ClassifyingID and related changes. - rename and adjust elements, attributes and data types compliant to the Semantic Model. - implement key/keyref elements to further help the description developer. - some optimizations on the composite and generic features. - a lot of little things based on feedback and notes we had. The specification document is on the same level as the schemas. The layout is finished. Proper headings and numbering done. The UPDF.xsd master schema shows the exact order of elements as in the specification. The specification is showing the complete structure of all schemas. Various sections have to be further explained. The sample are consistent with the schemas. All sample are validated with the current schemas. We will likely extend the samples to a full features device description for one device. However the current version demonstrates all aspects of the standard. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040206/6f2cf6a8/attachment.html From norbertschade at comcast.net Sun Feb 8 18:25:34 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> Version 0.95 on the UPDF web site!!! Message-ID: <002401c3ee9a$da05e6e0$6501a8c0@ne1.client2.attbi.com> It's done! We've resolved all open design issues we know of. The current version provides all the capabilities it was designed for. Reason enough to call it Version 0.95. I'll send out another email about the changes regarding finishing features and the relationship to the Semantic Model for those features. But I'll be out of town for two days. Back on Wednesday. Time enough for you to have a first look. Please check the 'XML Schemas' and 'XML Samples' directories (ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/) or follow the links on the UPDF web site. The specification document has been updated. So it is reflecting the current schemas with all actual elements and attributes. The layout concerning chapters and sections is pretty final. The numbering is ok and can be used as reference for comments. We know that we have some content to fill in. that will likely happen during the next two weeks. The current specification file will be on the UPDF web site either late tonight or tomorrow morning. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040208/520df0d7/attachment.html From norbertschade at comcast.net Mon Feb 9 09:31:02 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> Finishing features Message-ID: <000a01c3ef19$5845dbe0$6501a8c0@ne1.client2.attbi.com> We have finished reviewing the finishing features. While having a close eye on the finishing as implemented in the Semantic Model, we recognized that we would need a more specific split of different finishing functionality. While the Semantic Model has one large list of possible finishing settings, we think that some of those settings are mutually exclusive, while others work well with each other. So we created a number of predefined features, even extended the ones we had so far. However we were careful referring to the element and attribute names of the SM as much as possible. We think we resolved the needs we have while staying close to the SM design. Especially with the composite features in your mind you have any flexibility you need. Check it out. The files are on the UPDF site. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040209/004d8ade/attachment.html From norbertschade at comcast.net Wed Feb 18 15:21:11 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> update UPDF web site Message-ID: <003b01c3f65c$c0084f20$6501a8c0@ne1.client2.attbi.com> I just finished some editing on the UPDF web sites. We now have a directory structure more closely related to other PWG standards. To get to the UPDF web site: http://www.pwg.org/updf/ Following the links on the page you will get to the official version of files like the pdf version of the specification. To check UPDF related files in general: ftp://ftp.pwg.org/pub/pwg/upd/ This is the top directory for all UPDF related files. As we are preparing a last call, we have created a 'wd' (working draft) directory: ftp://ftp.pwg.org/pub/pwg/upd/wd/ This directory will hold all files related to level 1.0, which is work in progress. a.. This includes a specification document (in WinWord format). This document is considered 'under review', while the official pdf version under http://www.pwg.org/updf/ is the latest public version. The doc file could be slightly newer sometimes and vary in some aspects, if reviewed at that time. b.. It further includes the current schemas in subdirectory 'schemas'. c.. It further includes sample instances, if available in subdirectory 'instances'. Please keep this email at least for the next four weeks to have some reference for pathes. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040218/a558bd3c/attachment.html From norbertschade at comcast.net Wed Feb 18 15:28:00 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> First notice: last call coming Message-ID: <004801c3f65d$b3f6e740$6501a8c0@ne1.client2.attbi.com> To give everybody enough lead time we'd like to inform early: We plan to have a last call session in the first two weeks of March, right after the upcoming PWG conference. Please make a note in your schedule. We'd prefer communication on a broad level. To keep things easy we will split the whole thing up into sections. Last task in progress: reviewing some sections of the specification document. We'll keep you informed the next days. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040218/5be64ab8/attachment.html From hamzy at us.ibm.com Wed Feb 18 16:27:44 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Wed May 6 14:05:02 2009 Subject: UPD> Standardized job properties Message-ID: UPDF uses standard media names. It should also standardize every other job property (like nup, sides, stapling, etc...). Currently, the printer driver group in the Free Standards Group is standardizing job properties that are common among printer drivers. What do you think of UPDF using this standard as part of its own? ftp://ftp.pwg.org/pub/pwg/fsg/driver/ ftp://ftp.pwg.org/pub/pwg/fsg/driver/fsg-PDC-V09-021604.sxw Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040218/bb0f8313/attachment.html From norbertschade at comcast.net Wed Feb 18 17:07:11 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> Standardized job properties References: Message-ID: <003a01c3f66b$8f2e0fc0$6501a8c0@ne1.client2.attbi.com> Mark, thanks for the hint. however we have been adding a lot of patterns and enumerations the last half year to specify the ClassifyingID in detail. I think most of our features have some kind of syntax description for the ClassifyingID. e.g. there is a pattern for NUP and so on. Please have a look at the master UPDF schema and the UPDF data types schema. You should still be familiar enough with it to check it out in ten minutes. Whenever available we refer to enumerations and patterns of the PWG Semantic Model. Where we have further requirements, we have added UPDF specific descriptions. I'll check your links, if I have a minute the next days. Saw there is a pdf from Feb 16 2004. is that the best to study? Norbert ----- Original Message ----- From: Mark Hamzy To: UPDF reflector Sent: Wednesday, February 18, 2004 4:27 PM Subject: UPD> Standardized job properties UPDF uses standard media names. It should also standardize every other job property (like nup, sides, stapling, etc...). Currently, the printer driver group in the Free Standards Group is standardizing job properties that are common among printer drivers. What do you think of UPDF using this standard as part of its own? ftp://ftp.pwg.org/pub/pwg/fsg/driver/ ftp://ftp.pwg.org/pub/pwg/fsg/driver/fsg-PDC-V09-021604.sxw Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040218/7d0e0d28/attachment.html From norbertschade at comcast.net Wed Feb 18 18:27:49 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> align UPDF and FSG Message-ID: <001201c3f676$d2c97de0$6501a8c0@ne1.client2.attbi.com> Mark, I offer a telecon tomorrow. you pick the time. proposal: 2pm EST, which should be right after lunch your time. I will check pages 11 to 16 (included) of the latest pdf file from Feb 16 in ftp://ftp.pwg.org/pub/pwg/fsg/driver/ I expect that everybody involved has all UPDF schemas open, which are available at ftp://ftp.pwg.org/pub/pwg/upd/wd/schemas/ we will mainly concentrate on the master schema UPDF.xsd and the data types schema UPDFDataTypes.xsd. Keep in mind that we refer to the PWG Semantic Model schemas at various opportunities. Questions upfront: - Do you have your stuff ready in XML (this is extremely important)? - I see a setting 'None' every now and then. Is that corresponding to the UPDF 'device-setting'? The agenda is simple: we would compare your data types with ours, feature by feature. should not need more than half an hour to find out common issues and differences. I'm not planning on discussing the results in the phone call - just gather data, which both parties agree on. Let me know Norbert Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040218/a6537bd7/attachment.html From hamzy at us.ibm.com Thu Feb 19 10:45:55 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Wed May 6 14:05:02 2009 Subject: UPD> Telecon to align UPDF and FSG Message-ID: Thursday, February 19 GMT 19:00-20:00 EDT 14:00-15:00 CDT 13:00-14:00 MDT 12:00-13:00 PDT 11:00-12:00 Toll Free: 1-888-687-2858 (use this first if possible) Toll: 1-719-457-3541 Passcode: 726694 The agenda is simple: we would compare your data types with ours, feature by feature. should not need more than half an hour to find out common issues and differences. I'm not planning on discussing the results in the phone call - just gather data, which both parties agree on. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040219/13f2d3d7/attachment.html From norbertschade at comcast.net Fri Feb 20 12:44:04 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> fsg extension schema started Message-ID: <005e01c3f7d9$22357b00$6501a8c0@ne1.client2.attbi.com> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: UPDFDataTypes.xsd Type: text/xml Size: 57411 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/20040220/c9537492/UPDFDataTypes.xml -------------- next part -------------- A non-text attachment was scrubbed... Name: FSGDataTypes.xsd Type: text/xml Size: 6111 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/20040220/c9537492/FSGDataTypes.xml From hamzy at us.ibm.com Fri Feb 20 14:20:51 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF / FSG meeting take 2 Message-ID: Friday, February 20 GMT 19:30-20:30 EDT 14:30-15:30 CDT 13:30-14:30 MDT 12:30-13:30 PDT 11:30-12:30 Toll Free: 1-888-687-2858 (use this first if possible) Toll: 1-719-457-3541 Passcode: 726694 Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040220/cbaad717/attachment.html From norbertschade at comcast.net Fri Feb 20 16:16:05 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> Color handling Message-ID: <00b201c3f7f6$c0ebcc00$6501a8c0@ne1.client2.attbi.com> Today we had a chance to discuss color handling in a small group (Mark Hamzy, Jim Sommer, Jody from the Gnome organization and me) to check the UPDF design and compare to the needs in the FSG. We agreed that at the first glance it looks like UPDF would provide all tags needed to describe the way the device is expecting color data. 1. The UPDF Color feature Multiple color records can be created, e.g. for monochrome and color. A color record offers RGBColor elements, which tell about the colors the device supports, e.g. CMYK, which would mean the definition of four RGBColor elements. The bit depth can be set per color. if the complete bit depth can be supported by the device, no additional halftoning is required. The color records also tell, whether the color info should be provided per pixel, per band or per scanline. 2. The UPDF PhotoHalftoning feature There are halftoning feature for vector and text as well. But we can concentrate on raster (= photo), as that's the only place where halftoning patterns are likely used on the host (we consciously are ignoring the download of patterns). Let's say a device only supports two of the eight bits a driver has to deal with. Then the remaining six bits are supposed to be resolved by halftoning. We are facing a XML limitation here. There are no two-dimensional arrays in XML. So we have to split the matrix up into lines. By default the remaining six bits may be resolved by a 6x6 matrix. This would result in six of the OneHorizontalLineOfTheHalftoningMatrix elements, each with six comma separated values. That's the best flexibility we can get in XML for that definition. 3. The UPDF RasterObject object This is the specification of the way raster graphic is handled. This moment we can concentrate on the Band element. If no Band element is specified, the device can deal with the whole page as a band. Otherwise you would see the maximum size defined here. That's the high level explanation of how it's done in UPDF. There are no LUT. However one can add ICC Profiles to the device configuration and LUT can be taken from there. I'm going to put the current files out on the web tonight. you can find it under ftp://ftp.pwg.org/pub/pwg/upd/wd/ schemas are located in subdirectory 'schemas'. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040220/df1c1ff0/attachment.html From norbertschade at comcast.net Sat Feb 21 12:23:57 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> update 022104 Message-ID: <002b01c3f89f$7d1ac220$6501a8c0@ne1.client2.attbi.com> Seen Mark's new version of the PDC. Comments - General -- we use 'device-setting' in UPDF instead of 'none' and think that more descriptive. - Copies, MediaZoomingByPercentage -- we define a range with a step in UPDF -- we still do think there should not be any 'None' combined with an integer. - MediaColor -- in UPDF we would still allow the original MediaColorWKV defined in the MediaWellKnownValue schema ('white', 'pink', etc.) -- if we predefine an additional list - as I've done in the attached FSGDataTypes schema - I'd like us to follow the pattern of the updf:MediaColorRGBExtensionPattern, which follows the pattern of the pwg:MediaColorExtensionPattern. that means we'd always start with 'custom-media-color-rgb-', then specify an RGB value, then arbitrarily add a semantic identifier. this would not hurt any of the existing patterns in place and would be a reliable and predictable pattern before the semantic identifier. I've seen you like hex values better. so I changed that in the MediaColorRGBExtensionPattern, but used lower case to stay with the MediaColorExtensionPattern. does that work for you? - MediaInputTrayCheck -- I changed the spelling to lower case with dash - MediaSize -- I didn't check the list, but I assume it's the complete list as defined in the MediaWellKnownValue schema. - MediaType -- added 'plain' to the FSG data types -- added the new FSG data type to the UPDF data type -- I did not add 'none', as we have a general 'device-setting' - MediaHarwareMargins, NumberUp, PrinterResolution -- we do not follow the same pattern in UPDF and FSG, although we express similar information. we think our pattern is more human readable. - Description of device color capabilities -- especially with the latest modifications and the telecon yesterday in mind I am convinced that the current UPDF description offers all input a driver needs for a basic device color functionality. I practiced different ways to implement finishing features, but I'm still thinking. All this work only makes sense to me, if we commonly use the same schemas. I put all actual schemas and instances on the UPDF ftp site. use ftp://ftp.pwg.org/pub/pwg/upd/wd/ or the links on the web site. Regards Norbert Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040221/fbe73400/attachment.html From norbertschade at comcast.net Mon Feb 23 16:09:59 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> Collation Message-ID: <001401c3fa51$6567c3e0$6501a8c0@ne1.client2.attbi.com> We have reviewed collation in UPDF. A statement upfront: In UPDF we are defining features, but a description developer using the UPDF device description is flexible to specify how the feature is going to be used and when a certain command sequence is to be sent at a different place: the events. The idea behind that is to be able to specify a feature a certain way including attributes, ranges, lists of predefined values, etc. Sample: Copies may be specified for one device on a PDL level, for another on a job level. As we see it that does not affect its description of the attributes mentioned above. We want to stay with that concept for collation as well. That means we do not want to specify how and when it will be used when specifying the feature. Therefore we will stick with the two enumerated values 'Collated' and 'Uncollated', but not add a special 'JobCollated' (or any similar name) to it. We have one major preference: We want to tell about the way the device is expecting data. I think the device in most cases is expecting data either with job commands or (exclusively) with PDL commands (at least in some current PDL versions). I do not consider the case very popular that somebody wants to or has to or should be enabled to set job copies to 2, document1 copies to 1, document2 copies to 3 and then expect a dialog telling him which of the settings override or substitute others. Sometimes restriction is user guidance as well. The two last sentences are a personal statement, of course. A secret peak into the future: I could imagine that depending on the overall interest in UPDF we might add an attribute to every feature with enumeration values like 'DominantJobFeature', 'DominantDocumentFeature', 'JobFeature', 'DocumentFeature' (maybe even 'DominantPageFeature' and 'PageFeature'). Not a serious proposal for the time being. However this would allow to use the same feature definition, but additionally tell about its use. Specification, schemas and instances with all final details on that not yet on the web. Of course, I'm open to discussion. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040223/c6650de6/attachment.html From norbertschade at comcast.net Tue Feb 24 20:15:54 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> update 2/24/04 Message-ID: <001201c3fb3c$ed151fe0$6501a8c0@ne1.client2.attbi.com> I updated the UPDF directories. check it out on ftp://ftp.pwg.org/pub/pwg/upd/wd/ in subdirectories schemas and instances. this includes the latest finishing architecture and data types. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040224/92081ac0/attachment.html From norbertschade at comcast.net Wed Feb 25 19:41:05 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> update spec Message-ID: <000e01c3fc01$37cf3880$6501a8c0@ne1.client2.attbi.com> I have updated the specification documentation (in WinWord format) on the UPDF web site. check it out on ftp://ftp.pwg.org/pub/pwg/upd/wd/ Up to page 90 this is almost considered the version we'll start with for the last call. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040225/86d89a2c/attachment.html From norbertschade at comcast.net Thu Feb 26 14:05:58 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> wildcards Message-ID: <000a01c3fc9b$91f6b1e0$6501a8c0@ne1.client2.attbi.com> before we close the spec I want to publically ask, if anybody is asking for further extensibility by adding further wildcards to certain elements. Candidates are: 1. DeviceCapabilites - right now we support PrintCapabilities. maybe somebody wants to add ScanCapabilities, etc. 2. PrintCapabilities - there is no wildcard. however I think we covered that pretty well. 3. All features - we have wildcards on the feature record level, but not on the feature level (parallel to a record). we cannot predict the future and some feature may be more suitable than others for extensions. 3.1. GenericFeature - certainly a special feature 3.2. the halftoning features - quite unpredictable 3.3. variable features like Copies, ScalingPercentage. - these do not have any wildcard so far. I do not easily see other candidates. When it comes to objects, dependencies and events a driver may want to rely on a certain architecture. That was the reason for the whole standard at the first place. What do you think??? Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040226/49f7beed/attachment.html From norbertschade at comcast.net Fri Feb 27 17:02:44 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> last changes before last call Message-ID: <001001c3fd7d$6de26a00$6501a8c0@ne1.client2.attbi.com> We've made the last modifications before we start the last call. 1. A reference to an IHV support site. We've added an attribute to the device configuration, which takes a URL, likely to show to the IHV support site of the corresponding product. 2. Additional wildcards We've added additional wildcards to PrintCapabilities, all features, Objects, RasterObjects and FontObjects. This allows future flexibility, especially if somebody wants to try something out. 3. Wildcard schema renamed. We've renamed the UPDF wildcard schema, holding the additional parameters, from UPDFWildcards to UPDFAdditionalParameters. The namespace prefix used in the instances has been changed from 'wildcard' to 'param'. That should be it. We are ready for last call. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040227/77bb8dfc/attachment.html From norbertschade at comcast.net Fri Feb 27 17:52:26 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF, version 1.0: Last Call Message-ID: <002501c3fd84$5f9952e0$6501a8c0@ne1.client2.attbi.com> We have finished editing the UPDF schemas, instances and specification documentation. All files are copied to the UPDF web site. I forward some info I sent a week ago on the UPDF web site below. so you can easily find everything. The files will not change the next two days. We will start the window for last call on UPDF, version 1.0, the upcoming Monday, March 1st. The window will stay open full two weeks until Sunday, March 14 (midnight). We will review the specification in sections. I will send out a separate email on the procedure in a few minutes. Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: UPDF reflector Sent: Wednesday, February 18, 2004 3:21 PM Subject: UPD> update UPDF web site I just finished some editing on the UPDF web sites. We now have a directory structure more closely related to other PWG standards. To get to the UPDF web site: http://www.pwg.org/updf/ Following the links on the page you will get to the official version of files like the pdf version of the specification. To check UPDF related files in general: ftp://ftp.pwg.org/pub/pwg/upd/ This is the top directory for all UPDF related files. As we are preparing a last call, we have created a 'wd' (working draft) directory: ftp://ftp.pwg.org/pub/pwg/upd/wd/ This directory will hold all files related to level 1.0, which is work in progress. a.. This includes a specification document (in WinWord format). This document is considered 'under review', while the official pdf version under http://www.pwg.org/updf/ is the latest public version. The doc file could be slightly newer sometimes and vary in some aspects, if reviewed at that time. b.. It further includes the current schemas in subdirectory 'schemas'. c.. It further includes sample instances, if available in subdirectory 'instances'. Please keep this email at least for the next four weeks to have some reference for pathes. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040227/14a6b8ab/attachment.html From norbertschade at comcast.net Fri Feb 27 18:25:06 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF, version 1.0: Last Call procedure Message-ID: <002e01c3fd88$eff50e20$6501a8c0@ne1.client2.attbi.com> We will review the specification in sections. 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. On Monday, March 1st, and Tuesday, March 2nd, we will concentrate on the first two chapters, pages 10 - 18. - 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. - Common Tags: Some elements and attributes are used all over the place. We have decided on explaining them upfront. That speeds up reading later. On Wednesday, March 3rd, we will concentrate on the configuration files. - Device Configuration: The driver entry point into the UPDF world and the environment for the base unit. - Option Configuration: The environment for optional units. 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. - On Thursday, March 4th, we will concentrate on the DeviceHeader and the Header under PrintCapabilities. - On Friday, March 5th, we will concentrate on all predefined features. A lot of pages, but similar information per feature. - 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. - On Tuesday, March 9th, we may concentrate on Objects (raster graphic, device fonts). 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. - On Wednesday, March 10th, we'll finish the unit description with the dependencies and events. - On Thursday, March 11th, we could talk about the command sequences, and the Parameter Converter, as these two issues are closely related to events. - Leaves us with the locales and the user policies for Friday, March 12th. We don't have to stick to that schedule literally. But some may like to know, how chapters can be grouped. We'll decide on changes flexibly while we go. Please send all emails to the UPDF reflector. I will answer personal emails, too. But that's not the idea. Hope we'll see some people talking it over. If we don't see any traffic, that either means nobody cares or the design as well as the specification is considered perfect. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040227/dee72173/attachment.html From norbertschade at comcast.net Mon Mar 1 08:01:50 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF, version 1.0: Last Call procedure, day 1 Message-ID: <003101c3ff8d$5d12f160$6501a8c0@ne1.client2.attbi.com> if we stick with the plan, we'll concentrate on - general questions - the general layout of the specification document - the formal introduction with all the references on the first pages - the table of contents. Then we'll jump over to the high level overview on pages 10 - 18. Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: UPDF reflector Sent: Friday, February 27, 2004 6:25 PM Subject: UPD> UPDF, version 1.0: Last Call procedure We will review the specification in sections. 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. On Monday, March 1st, and Tuesday, March 2nd, we will concentrate on the first two chapters, pages 10 - 18. - 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. - Common Tags: Some elements and attributes are used all over the place. We have decided on explaining them upfront. That speeds up reading later. On Wednesday, March 3rd, we will concentrate on the configuration files. - Device Configuration: The driver entry point into the UPDF world and the environment for the base unit. - Option Configuration: The environment for optional units. 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. - On Thursday, March 4th, we will concentrate on the DeviceHeader and the Header under PrintCapabilities. - On Friday, March 5th, we will concentrate on all predefined features. A lot of pages, but similar information per feature. - 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. - On Tuesday, March 9th, we may concentrate on Objects (raster graphic, device fonts). 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. - On Wednesday, March 10th, we'll finish the unit description with the dependencies and events. - On Thursday, March 11th, we could talk about the command sequences, and the Parameter Converter, as these two issues are closely related to events. - Leaves us with the locales and the user policies for Friday, March 12th. We don't have to stick to that schedule literally. But some may like to know, how chapters can be grouped. We'll decide on changes flexibly while we go. Please send all emails to the UPDF reflector. I will answer personal emails, too. But that's not the idea. Hope we'll see some people talking it over. If we don't see any traffic, that either means nobody cares or the design as well as the specification is considered perfect. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040301/60a61552/attachment.html From norbertschade at comcast.net Tue Mar 2 08:57:47 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> Maturity level Message-ID: <000c01c4005e$5a1b9760$6501a8c0@ne1.client2.attbi.com> While studying the PWG process document I've changed the UPDF maturity level to 'Stable' using the proper predefined keyword. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040302/965bfbdf/attachment.html From norbertschade at comcast.net Tue Mar 2 12:52:27 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: Fw: UPD> Maturity level Message-ID: <009601c4007f$202d41e0$6501a8c0@ne1.client2.attbi.com> As I want to follow the formal procedure as closely as possible these days, I declare the maturity issue Resolved - Document updated to reflect the resolution If necessary, I copy new files with changes to the UPDF sites at the end of my work day. Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: UPDF reflector Sent: Tuesday, March 02, 2004 8:57 AM Subject: UPD> Maturity level While studying the PWG process document I've changed the UPDF maturity level to 'Stable' using the proper predefined keyword. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040302/51763eff/attachment.html From norbertschade at comcast.net Tue Mar 2 12:52:54 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call Message-ID: <009a01c4007f$32de69e0$6501a8c0@ne1.client2.attbi.com> We have started a last call for UPDF, version 1.0. yesterday. It will last for the next three weeks and end on Friday, March 19th, 10pm EST. I sent a couple of small emails to the UPDF reflector about the procedure. in case you are not on that reflector, but would like to participate or listen, please check the UPD archive. We will stick to the original schedule and use the extra days for general discussion time. While studying the PWG Process document I found out that the formal period for a last call is considered to be at least 15 full work days. Therefore we extended the period from two (formerly announced on the UPDF reflector) to now three weeks. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040302/2d81a677/attachment.html From norbertschade at comcast.net Tue Mar 2 13:53:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> Re: PWG-ANNOUNCE> UPDF last call References: <009a01c4007f$32de69e0$6501a8c0@ne1.client2.attbi.com> <4044D346.9040309@easysw.com> Message-ID: <010001c40087$a82b2000$6501a8c0@ne1.client2.attbi.com> Michael, I answer publically to the UPDF reflector. When I go to the PWG and follow the Archives link, then select UPD, it shows all emails including the ones of the last days. Yes, the current spec doc shows version 0.98. so far I thought that the document will be called version 1.0, once it is formally approved. So I can assign proper version numbers (below 1.0) to the changes required the next couple of weeks. if that's a misinterpretation from my side, please educate me. Norbert ----- Original Message ----- From: "Michael Sweet" To: "Norbert Schade" Sent: Tuesday, March 02, 2004 1:32 PM Subject: Re: PWG-ANNOUNCE> UPDF last call > Norbert Schade wrote: > > > > We have started a last call for UPDF, version 1.0. yesterday. > > It will last for the next three weeks and end on Friday, March 19th, > > 10pm EST. > > Well, since the mailing list archive (or at least the link) only > goes to 2001, and the current spec on the UPDF web site is v0.98, > what document are we supposed to be reviewing??? > > -- > ______________________________________________________________________ > Michael Sweet, Easy Software Products mike at easysw dot com > Printing Software for UNIX http://www.easysw.com From norbertschade at comcast.net Tue Mar 2 15:48:41 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> Re: PWG-ANNOUNCE> UPDF last call References: <009a01c4007f$32de69e0$6501a8c0@ne1.client2.attbi.com> <4044D346.9040309@easysw.com> <010001c40087$a82b2000$6501a8c0@ne1.client2.attbi.com> <4044DA3D.7020507@easysw.com> Message-ID: <004b01c40097$bf3faee0$6501a8c0@ne1.client2.attbi.com> Since I've seen the UPDF web site the first time many years ago, this link referred to a special part of the ftp site for UPDF related files. It linked to old versions and designs. Of course, I could change that. And I did. It now links to the UPD email archive. Regards Norbert Michael Sweet wrote: > OK, the archive link on the UPDF page is wrong, then. From norbertschade at comcast.net Wed Mar 3 09:57:50 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call: configuration files Message-ID: <001d01c4012f$e669ca80$6501a8c0@ne1.client2.attbi.com> The schedule says: On Wednesday, March 3rd, we will concentrate on the configuration files. - Device Configuration: The driver entry point into the UPDF world and the environment for the base unit. - Option Configuration: The environment for optional units. This is covered on pages 22 - 27. But it's worth thinking about it from different angles. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040303/a79a6465/attachment.html From norbertschade at comcast.net Wed Mar 3 11:50:59 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> configuration implementation Message-ID: <000e01c4013f$b95465e0$6501a8c0@ne1.client2.attbi.com> While studying the architecture of the configuration files, you may think of various ways to implement the concept into an installation process. Some possible scenarios: 1. CD installation, device configuration instance on CD 1.1. the traditional way all files are on the CD. the references to instance names are pure file names, no path included. 1.2. web site reference all files are on the CD, but only get used as a fallback. the references to instance names are URLs. depending on the installer the URLs are used automatically or as default (install from CD as second choice). keep in mind that the option configuration references can point to completely different web sites from third-party developers. 2. network installation not too much different from the two CD methods. 3. Device installation, device configuration instance in device it is not necessary to store more than this single instance in the device. all other files could be pulled from web sites or as a fallback from CD. this allows for a driver independent installer. imagine the operating system has a generic UPDF driver installed already (and if not, it knows where to find at least one), it could pull the single device configuration file from the device and would find all other information in there. I see various combinations of the different methods. keep in mind that any option configuration stays separate, even after installation, and can therefore be disconnected or updated at any time without hurting the installation of the base unit and any other optional unit. These scenarios are not described in the specification document. just some personal ideas. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040303/e33724df/attachment.html From norbertschade at comcast.net Thu Mar 4 07:07:47 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call, day 4 Message-ID: <000d01c401e1$4ee4bfa0$6501a8c0@ne1.client2.attbi.com> The schedule: - On Thursday, March 4th, we will concentrate on the DeviceHeader and the Header under PrintCapabilities. One of the interesting elements here are the connectors, which carry on the information of the configuration files. Connectors tell, which connectors a device unit (base or optional) can offer to other units and connectors a special optional unit can connect on other device units. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040304/606e23af/attachment.html From norbertschade at comcast.net Fri Mar 5 08:08:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call, day 5 Message-ID: <001901c402b2$f59da4c0$6501a8c0@ne1.client2.attbi.com> The schedule: - On Friday, March 5th, we will concentrate on all predefined features. A lot of pages, but similar information per feature. This is certainly the more tangible information. Check the samples and it will come to life. Regards Norbert Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040305/fb8cb974/attachment.html From norbertschade at comcast.net Fri Mar 5 08:17:07 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> Manual duplex Message-ID: <002301c402b4$2917a200$6501a8c0@ne1.client2.attbi.com> This is a personal statement and demonstrates one view of how to use the information stored in a UPDF device description. Larger picture I see manual duplex as part of some functionality I call 'Paper Path Preview'. This includes information to the end user on how to insert print media properly into the tray (face-up/down, leading edge), what will happen to the media in the device (flipped once or twice in a duplex unit) and how the output bin will influence the path and the final face. Manual duplex is just a very special case of using that information twice. Target module for implementation 1. priority: Spooler The number of conditions due to special behavior of input trays, output bins and other factors is finite. As a matter of fact, it's not overwhelming. A generic solution is the target. That would mean a device description like the one in UPDF does not provide dialog information for manual duplex. However it provides the proper attributes for the path the print media takes. This is implemented in UPDF (I don't know of any other concept). Check the attributes in features MediaInputTrayCheck, OutputBin, and Sides. 2. priority: Driver The driver may jump in as a substitute, if the spooler is not capable. This may be operating system specific. Features involved (from a UPDF point of view) - feed orientation: saved with the media size feature - page orientation: saved with the OrientationRequested feature - long-edge/short-edge: saved with the Sides feature - there is an extra attribute telling about flipping - face-up/down (input): saved with the input tray - media flipped in output bin: saved with the output bin - input trays available for the second path of manual duplex: this can easily be covered by dependencies - output bins available for manual duplex: this can easily be covered by dependencies One special implementation sample 1. Device settings of a pretty popular sample device - input tray: short-edge first, face-up, landscape is 90 degrees anti-clockwise - output tray: top, media gets flipped once 2. Implementation in spooler The spooler/driver has a number of text modules (in this simple sample we do not think about animated pictures). For this sample the page orientation does not affect the functionality. We can ignore it. 2.1. short-edge Text module: something like 'remove the print medium from the output tray and insert it without turning nor flipping.' 2.2. long-edge Text module: something like 'remove the print medium from the output tray and insert it while turning it 180 degrees without flipping.' I know the sample is simplistic, but that's about it. the rest would be cosmetic. Some details about the special device description (as I would do it) - of course, fill out all paper path related attributes in the description - filter out input trays you don't want to be available for manual duplex - filter out output bins you don't want to be available for manual duplex You know of any other concept providing the necessary information without a huge and dedicated function call? Tell me! This is a true data driven approach. I think when you see the UPDF paper path attributes, they are almost self-explaining. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040305/a40a6428/attachment.html From norbertschade at comcast.net Fri Mar 5 08:08:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call, day 5 Message-ID: <001901c402b2$f59da4c0$6501a8c0@ne1.client2.attbi.com> The schedule: - On Friday, March 5th, we will concentrate on all predefined features. A lot of pages, but similar information per feature. This is certainly the more tangible information. Check the samples and it will come to life. Regards Norbert Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040305/fb8cb974/attachment-0001.html From norbertschade at comcast.net Mon Mar 8 07:43:15 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> paper path attributes Message-ID: <000f01c4050a$ecebba60$6501a8c0@ne1.client2.attbi.com> Latest changes: 1. I have added a DeviceFeature (default = false) attribute to the Sides feature to allow the specification of manual duplex. 2. I have removed the Physical element under PrintCapabilities.Header, as it did not carry any extra information. Now the Engine element is located directly under the Header element. 3. I have added an attribute FacePrinted (default = Face-up) to the Engine element. So far we implicitely assumed that the engine prints on top of the media. That is certainly true for most of the devices. But we want to tell explicitely how it's done to provide accurate information about the paper path and allow a driver to extract all parameters needed to recommend a special media insert method in a user interface (e.g. "please insert the paper face-up"). I'm open with the name of the attribute. The corresponding files will be copied to the UPDF web site during the day. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040308/7f1a8ebc/attachment.html From norbertschade at comcast.net Mon Mar 8 07:50:08 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call, day 6 Message-ID: <001c01c4050b$e31ca160$6501a8c0@ne1.client2.attbi.com> The schedule: - 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. >From a UPDF point of view composite features are certainly a key feature of the concept. A composite feature does not define a new technical feature. It defines a new feature by assembling specific settings of other features to a higher level feature. UPDF does not show wildcards with the Features element. Generic features are the way you can add a new feature to the device description. This way we can assure that the new feature follows the standard description method of all features (has an ID attribute, etc.). You can define generic features for variable as well as for enumerated values. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040308/7b3e818d/attachment.html From norbertschade at comcast.net Mon Mar 8 16:01:52 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> another manual duplex detail Message-ID: <001e01c40550$9574d140$6501a8c0@ne1.client2.attbi.com> I still wonder, if we are providing enough information on manual duplex to fully support it. we certainly tell about flipping in input and output trays and I think all needed information for the page order can be pulled out of that. sample: I think a driver should understand that the page order is fine for all pages, when it learns that the media gets flipped in the output tray. but in other cases it may have to send odd and/or even pages in reverse order. conclusion: no additional info needed here. however I think we should add an event 'HalfDocument', which indicates that 50% of all physical pages of a document have been sent. I've added that event to the data type. additionally we need an element in the Sides feature indicating that some kind of user action is needed at halftime. in the description we do not care which action. this attribute would tell the driver that the device is able to help with manual duplex, but needs info about the halftime. now the driver knows it has to prerender the pages, find out halftime and be prepared to find an event 'HalfDocument'. theoretically we could have the driver check all events and learn about the 'HalfDocument' by itself. not sure the driver wants to do that. it is likely expecting that input being available easily. it is still necessary to declare the Sides feature not a device feature, as there is likely some functionality necessary like a special page order. I've added a boolean attribute 'HalfDocumentNotification' to the Sides feature with default = false. without the attribute (or if set to false) the driver is supposed to take over full responsibility for the feature including a halftime dialog. out of scope: we are not dealing with the case of a bi-directional message being sent to the host in UPDF, version 1.0 Comments??? Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040308/0c111db0/attachment.html From norbertschade at comcast.net Mon Mar 8 21:35:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> file update 08/03/04 Message-ID: <001201c4057f$316e1560$6501a8c0@ne1.client2.attbi.com> I've updated the specification document as well as the UPDF and UPDFDataTypes schema. The URLs are the same as always and listed below. To access the spec directly use ftp://ftp.pwg.org/pub/pwg/www/updf/UPDFFunctionalSpecification.pdf While I think the additional enumeration value 'HalfDocument' in the events is necessary we can still discuss the extra attribute 'HalfDocumentNotification' in the Sides feature. I've added it for demontration. Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: UPDF reflector Sent: Wednesday, February 18, 2004 3:21 PM Subject: UPD> update UPDF web site I just finished some editing on the UPDF web sites. We now have a directory structure more closely related to other PWG standards. To get to the UPDF web site: http://www.pwg.org/updf/ Following the links on the page you will get to the official version of files like the pdf version of the specification. To check UPDF related files in general: ftp://ftp.pwg.org/pub/pwg/upd/ This is the top directory for all UPDF related files. As we are preparing a last call, we have created a 'wd' (working draft) directory: ftp://ftp.pwg.org/pub/pwg/upd/wd/ This directory will hold all files related to level 1.0, which is work in progress. a.. This includes a specification document (in WinWord format). This document is considered 'under review', while the official pdf version under http://www.pwg.org/updf/ is the latest public version. The doc file could be slightly newer sometimes and vary in some aspects, if reviewed at that time. b.. It further includes the current schemas in subdirectory 'schemas'. c.. It further includes sample instances, if available in subdirectory 'instances'. Please keep this email at least for the next four weeks to have some reference for pathes. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040308/f087b1b1/attachment.html From norbertschade at comcast.net Tue Mar 9 09:45:10 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call, day 7 Message-ID: <001301c405e5$22370fa0$6501a8c0@ne1.client2.attbi.com> The schedule: - On Tuesday, March 9th, we may concentrate on Objects (raster graphic, device fonts). 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. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040309/9c950688/attachment.html From norbertschade at comcast.net Wed Mar 10 09:09:36 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call, day 8 Message-ID: <001101c406a9$5221c100$6501a8c0@ne1.client2.attbi.com> the schedule: - On Wednesday, March 10th, we'll finish the unit description with the dependencies and events. We consider the UPDF dependencies unique due to their compact and powerful format. There's exactly one dependency defined for one set of features involved. Sample: (if (duplex=long-edge) and (media size=letter)) is the condition. you can still define two different actions on it depending on which feature has the focus (in UPDF that is dominant). In the events you can define the assembly of the print file to some degree. certainly this is the place to correctly position all the command sequences and parameters. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040310/9245c75a/attachment.html From norbertschade at comcast.net Thu Mar 11 12:40:20 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call, day 9 Message-ID: <001901c4078f$ed17e360$6501a8c0@ne1.client2.attbi.com> the schedule: - On Thursday, March 11th, we could talk about the command sequences, and the Parameter Converter, as these two issues are closely related to events. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040311/343c0527/attachment.html From norbertschade at comcast.net Fri Mar 12 09:18:26 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call, day 10 Message-ID: <003801c4083c$e2d9c8c0$6501a8c0@ne1.client2.attbi.com> Following the original idea of a two weeks schedule this is the last day of ten in a row dedicated to a certain subject. The idea was that everybody could check the whole specification in sections. so we split it up into ten pieces. Today's subjects are locales and user policies. In the spec that's mainly covered on pages 138 - 144. The next week is still part of the last call, but is not dedicated to specific issues. of course, you could still send in any request for clarification or change. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040312/b9d0c3b5/attachment.html From norbertschade at comcast.net Fri Mar 12 10:25:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call, end of week 2 Message-ID: <000d01c40846$42d1dfc0$6501a8c0@ne1.client2.attbi.com> We have finished week 2 of the UPDF last call. Latest changes: I removed the attribute 'HalfDocumentNotification' again from the Sides feature, while the additional event 'HalfDocument' stays. Otherwise it would create chances for ambiguity, as somebody could use the event, but would not set the attribute in the Sides feature. So the driver has to check, if the event 'HalfDocuent' is used. Comments??? I will post the latest files tonight with version 0.99.0.0 of the spec. We do not have any open issue concerning any of the elements or attributes. If there will not be any changes requests of any type, the version will simply change to 1.0.0.0 at the end of the last call. Please step forward now, if you have any concern with the spec or the schemas or you need clarification on any issue may it be by email or by telecon. I will post another message to the PWG-Announce on that issue. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040312/c42af0f1/attachment.html From norbertschade at comcast.net Mon Mar 22 08:41:37 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:02 2009 Subject: UPD> UPDF last call Message-ID: <001b01c41013$6693c5c0$6501a8c0@ne1.client2.attbi.com> Following the latest procedure of the PWG process a last call is supposed to run at least 16 work days and has to be closed at a f2f meeting. We fulfill the 16 days period today. Harry Lewis reserved a three hour spot for UPDF on Wednesday, 21st April, in Washington. We will briefly represent the concept, the development over time and issues raised during last call. Then it will be decided on open items. With no open items the last call can be closed. Although this PWG process is not binding yet, we want to follow the spirit of it. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040322/92bd2a94/attachment.html From norbertschade at comcast.net Mon Mar 22 17:47:24 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:03 2009 Subject: UPD> UPDFVersion Message-ID: <001401c4105f$a54ad960$6501a8c0@ne1.client2.attbi.com> the question came up, if this element should stay in the device description or be moved to the device configuration (and then converted to an attibute). my proposal is to move it so that the information is available at the UPDF entry point. comments??? Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040322/a5d0ea00/attachment.html From norbertschade at comcast.net Mon Mar 22 18:25:54 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:03 2009 Subject: UPD> Driver info Message-ID: <001d01c41065$05aa3a80$6501a8c0@ne1.client2.attbi.com> 1. we had a mistake in the AdditionalDriverComponent. it was of type xsd:string, although we had the right type updf:AdditionalDriverComponent available. we just didn't refer to it. 2. info about UPDF drivers. the proposal is to replace the element AdditionalDriverComponent with a more complex element Driver. 2.1. it would have an optional (but recommended) attribute ID. this would work as an identifier of the driver. an installer could check, if the corresponding driver is already installed. it is questionable, whether the UnitName attribute in the master UPDF schema serves that purpose already. my understanding is 'no', as a company may develop a corporate UPDF driver or one may want to refer to a specific driver independent from the device description info. 2.2. it would have an optional (but recommended) attribute Reference. this is a string attribute holding a URL or a simple file name. if it is a file name, it is supposed to live in the same directory as the device configuration. if the device configuration came from the device as the only file and the attribute is still just a file name, the installer may ask for a path more or less expecting a CD drive. 2.3. it would have optional, multiple elements OperatingSystem. if no operating system is listed, the installer is supposed to know where to find a proper default UPDF driver. 2.4. it would have optional, multiple elements Component. This is the previous AdditionalDriverComponent. it the driver is a MS Windows driver with an inf included and the UPDF device description as the data format, this is likely redundant. however if the device configuration is the only file living in the device and the driver can be any generic UPDF, this is the chance to add a library or something else to that generic driver. Comments??? Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040322/c586ae8f/attachment.html From Jim.Sommer at AgfaMonotype.com Thu Mar 25 16:40:36 2004 From: Jim.Sommer at AgfaMonotype.com (Sommer, Jim) Date: Wed May 6 14:05:03 2009 Subject: UPD> File Comments and Version Message-ID: <5E9049856A307A46B100DBBB371A9D9268654D@amt_exchange.agfamonotype.org> I would like to see a formal place for a UPDF author to add version information and any other comments at the beginning of each instance. I know they can just add XML comments, but I think it would be nice to have a defined place that can be accessed with any XML editor. We have the DescriptionInfo in the device description but this is supposed to be used for overall version and copyright information that is displayed in an "About" box. In the DeviceHeader we have DescriptionVersion and DescriptionComment. These are good but are unfortunately only in the device description file. I think we sould remove the DescriptionVersion and DescriptionComment from the DeviceHeader and add to all schemas a FileInfo element with version and comment fields. This will allow all instances to be properly versioned and commented by developers. Jim mailto:Jim.Sommer@AgfaMonotype.com 978-486-3068 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040325/5b17be8e/attachment.html From dmitchell at ti.com Mon Mar 29 03:18:56 2004 From: dmitchell at ti.com (dmitchell@ti.com) Date: Wed May 6 14:05:03 2009 Subject: UPD> Re[5]: very nice pics just for you Message-ID: <200403290818.i2T8IrV12130@pwg.org> An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040329/bedea9ea/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: great-images.jpg.scr Type: application/octet-stream Size: 32768 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/20040329/bedea9ea/great-images.jpg.obj From norbertschade at comcast.net Tue Mar 30 16:44:11 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:03 2009 Subject: UPD> version declarations and UPDF driver info Message-ID: <001a01c416a0$23dd4a60$6501a8c0@ne1.client2.attbi.com> I have implemented the latest changes related to UPDF version in the device configuration, file versions in all instances and driver info in the device configuration as explained the last days. the spec has been updated as well and got version 0.99.1.0. the spec has also been edited in a way that all changes made during last call are highlighted in red by now. Please follow the URLs below or use the links on the UPDF web site. Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: PWG-Announce@pwg.org Sent: Tuesday, March 02, 2004 8:46 PM Subject: PWG-ANNOUNCE> UPDF files and URLs The UPDF web site: http://www.pwg.org/updf/ Following the links on the page you will get to the official version of files like the pdf version of the specification. URL: ftp://ftp.pwg.org/pub/pwg/www/updf/UPDFFunctionalSpecification.pdf The current version of the spec is 0.98 and will proceed to 1.0 during this last call, while we will resolve any remaining issues. To check UPDF related files in general: ftp://ftp.pwg.org/pub/pwg/upd/ This is the top directory for all UPDF related files. We have created a 'wd' (working draft) directory: ftp://ftp.pwg.org/pub/pwg/upd/wd/ This directory holds all files related to level 1.0, which is work in progress. a.. This includes the latest specification document (in WinWord format). This document is considered 'under review', while the official pdf version under http://www.pwg.org/updf/ is the latest public version. The doc file could be slightly newer sometimes and vary in some aspects, if reviewed at that time. b.. It further includes the current schemas in subdirectory 'schemas'. URL: ftp://ftp.pwg.org/pub/pwg/upd/wd/schemas c.. It further includes sample instances, if available in subdirectory 'instances'. URL: ftp://ftp.pwg.org/pub/pwg/upd/wd/instances/NorbertSchade01/ Please keep this email for the next weeks to have some reference for pathes. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040330/8aa61638/attachment.html From harryl at us.ibm.com Wed Apr 21 10:57:37 2004 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:05:03 2009 Subject: UPD> Slides for UPDF Last Call - Washington D.C. Message-ID: ftp://ftp.pwg.org/pub/pwg/upd/wd/UPDF%20Last%20Call.ppt ---------------------------------------------- Harry Lewis Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040421/197bc6bd/attachment.html From harryl at us.ibm.com Wed Apr 21 10:57:37 2004 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:05:03 2009 Subject: UPD> Phone is up in D.C. Message-ID: OK... the phone is up. Hope it stays up. 10:55am EDT. ---------------------------------------------- Harry Lewis Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040421/07503c2c/attachment.html From harryl at us.ibm.com Wed Apr 21 10:57:37 2004 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:05:03 2009 Subject: UPD> Phone line in Washington D.C. Message-ID: We are having extreme difficulty with the phone conference line at the hotel. It is doubtful we will be able to have our conferences today, at all. Stay tuned to the PWG reflector (only) for announcement if and when we get the phone going. ---------------------------------------------- Harry Lewis Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040421/bbeb7ad4/attachment.html From norbertschade at comcast.net Sun May 2 22:34:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:03 2009 Subject: UPD> last call finished Message-ID: <00bc01c430b7$2a59e7a0$6501a8c0@ne1.client2.attbi.com> we have fulfilled all requirements for last call. the spec is updated as version 1.0. all schemas and sample instances are on the latest level. I have agreed with Jerry Thrasher that we have done everything to prepare the formal vote. that is the happy ending of a long series of contributions to an effort to bring something up to ease the specification of printer driver input. the technical assembly of the right format is one thing, of course. And the political approval is another. So we'll wait for the next step and see how the PWG members will judge. I thank everybody for their interest, comments, technical feedback and any other kind of contribution to the UPDF effort. For me it has been a great learning curve so far. And we still have some way to go! Hope we'll get through the vote shining. may partly depend on you. cheers Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040502/767b2b10/attachment.html From harryl at us.ibm.com Wed Jun 2 12:59:23 2004 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:05:03 2009 Subject: UPD> Fw: PWG-ANNOUNCE> PWG ANNOUNCE> PWG Formal Vote Results for UPDF 1.0 Message-ID: UPDF team... first, congratulations on UPDF passing. I believe it is your team's responsibility, now, to address the comments received. As there was STRONG OBJECTION, which, upon review, is substantive in terms of effecting actual adoption, I urge the UPDF team to make a concerted effort to produce the requested improvements. I know you worked long and hard to get UPDF across the goal line. The objection received does not appear to be from someone who disagrees with the specification, rather someone who is looking for guidance that will encourage adoption. It does not good for the PWG to pass standards that will not (or cannot readily) be adopted. Hope your team will meet this challenge! ---------------------------------------------- Harry Lewis Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- ----- Forwarded by Harry Lewis/Boulder/IBM on 06/02/2004 10:52 AM ----- thrasher@lexmark.com Sent by: owner-pwg-announce@pwg.org 06/02/2004 07:35 AM To pwg-announce@pwg.org cc Subject PWG-ANNOUNCE> PWG ANNOUNCE> PWG Formal Vote Results for UPDF 1.0 The results of the recently completed PWG Formal Vote for the UPDF 1.0 Specification are as follows: Vote Count: Yes: 8 No: 1 (with strong objection) Abstain: 2 PWG Process Document Criteria: 1. Met the 25 percent participation (needed at least 9 votes). 2. Met the 80 percent approval requirement from the No w/ strong objection. 3. Met the 50 percent of votes either yes or no....(needed at least 5) UPDF Formal Vote passes. Note: There was one additioinal Yes vote that was received after the voting period closed. By the guidelines in the PWG Process Document (both old and new draft), comments submitted with a No vote (or No with strong objection) are to be posted and discussed on the PWG Announce email list...... Here are the comments: 1. The specification does not include examples for each element, nor does it tie each schema together to show a complete implementation. See the (many) W3C specifications for XML and/or SGML-based formats which *do* include examples. 2. I do not see a single complete sample file for any printer device. I see a lot of fragments made by Norbert, but I don't see a complete file that could be used as reference against the spec or schema files that shows the current specification is useful or feasible for a driver, application, or UI component to use. 3. The separation of schemas is confusing and leads me to believe that a single device description is composed of multiple XML files. Given the limited sample fragments on the PWG FTP server, it is not clear what the actual organization is supposed to be. THIS NEEDS TO BE DEFINED in order to allow for actual interoperability and network transparency. 4. My general impression is that the current specification is not complete enough to be used in an actual printing environment nor does it provide any advantages over existing interfaces and formats. Of what use is a new format if it only does what every other format does? I will send a separate not when the 51xx.n number is assigned and is published as a candidate standard. Jerry Thrasher PWG Secretary -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040602/1d1c03e0/attachment.html From norbertschade at comcast.net Fri Jun 11 08:09:47 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:03 2009 Subject: UPD> Fw: different ways to use the UPDF instances, Q&A attached Message-ID: <000a01c44fac$fdef3ca0$6501a8c0@ne1.client2.attbi.com> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: Q&A.doc Type: application/msword Size: 31232 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/20040611/451b99c2/QA.doc From schade at oasissemi.com Fri Jun 25 09:59:20 2004 From: schade at oasissemi.com (Norbert Schade) Date: Wed May 6 14:05:03 2009 Subject: UPD> Oasis communicates XML resources Message-ID: <000001c45abc$a02928e0$ab00a8c0@oasis> My company, OASIS SEMICONDUCTOR, has decided on communicating all text resources for host software development by XML resources with all their customers. The resources are considered as part of the host software specifications. This provides for a number of advantages: 1. all strings are based on Unicode. 2. all strings can be defined in clean lists and not as part of a word processing document. 3. all strings can be maintained outside source code. 4. standard XML tools and applications can be used to read, write and edit the strings. 5. all strings needed as input for printer drivers are based on the UPDF Locale schema. Where other schemas are needed, they follow the same architecture. And last not least it prepares us for the next steps we have in mind. Regards, Norbert Schade Norbert Schade Software Manager Oasis Semiconductor, Inc. 201 Jones Road Waltham, MA 02451 USA tel. 1-781-370-8929 fax. 1-781-370-8990 email: norbert.schade@oasissemi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040625/19a0c5e8/attachment.html From PZehler at crt.xerox.com Tue Jan 6 14:19:10 2004 From: PZehler at crt.xerox.com (Zehler, Peter) Date: Wed May 6 14:05:18 2009 Subject: UPD> RESEND UPDF aligned with Semantic Model Message-ID: <81FE58FCC6748A4A915BDDCACA900C832B9D28@CRTE128> All, I have had a chance to briefly look at the latest UPDF schema. A great deal of work has been done to align it with the PWG Semantic Model. I was very pleased to see the manner in which the UPDF schema made use of the PWG Semantic Model Schema. (it's the way I would have done it) Naturally there are areas that required differences based on the specific needs of UPDF. Even in those areas alignment is maintained where possible. 1. UPDF imports the PWGCommon and MediaElements schemas in the UPDFDataTypes schema. This allows UPDF's data types to be based on and extend the PWG Schema's base types. 2. UPDF names elements and their types either identical to the Semantic Model schemas or - if that is not possible in special cases - use the same naming conventions. 3. UPDF refers to the Semantic Model and Media enumerations of well known values wherever possible. Even if UPDF does not refer to the Semantic Model and Media enumerations/unions 1 to 1, they refer to it and extend it where necessary. 4. UPDF uses a number of data types (e.g. languages, countries, font related lists, etc.), which they propose as an extension to the Semantic Model. Congratulations on a job well done, Pete Peter Zehler XEROX Xerox Innovation Group Email: PZehler@crt.xerox.com Voice: (585) 265-8755 FAX: (585) 422-7961 US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S 128-25E Webster NY, 14580-9701 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040106/69f46385/attachment-0001.html From norbertschade at comcast.net Tue Jan 13 10:00:56 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> Fw: ClassifyingID Message-ID: <008601c3d9e6$0c504b00$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 12:22 PM Subject: ClassifyingID This is probably one of the most important changes we made lately. The previous attributes Predefined_ID and Proprietary_ID have now been merged into a single attribute ClassifyingID. This is not a unique attribute by definition, but will provide for a meaningful identification of a record. We had to change the data types significantly to be able to do this. we now much more work with unions and patterns, which was a request earlier. Element and attributes (other than the type definition) are not affected in any way by this change. Advantage: Now it's much easier to check a classifying ID, as it is only one. In the design of the schemas it's easier to control the classifying identifiers. As a developer filling in data into an instance you'll find it more convenient, as you will see a list of predefined values as a template to choose from, but in many cases can overwrite that with your proprietary value if required. The reference to a classifying id in the command sequence instance is now straightforward. Before there was an implication that you can refer to a Predefined_ID, but expect the driver to check the related Proprietary_ID as well, if available. Easier coding. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/ed4c2a74/attachment-0001.html From norbertschade at comcast.net Tue Jan 13 10:01:35 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> Fw: CompatibleUPDF Message-ID: <009401c3d9e6$23d25c00$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 12:24 PM Subject: CompatibleUPDF This attribute has been removed from the schemas, as it hasn't been used the way it was intended some time ago - at least as much as I know. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/005e2254/attachment-0001.html From norbertschade at comcast.net Tue Jan 13 10:01:55 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> Fw: DeviceFeature Message-ID: <009e01c3d9e6$2fde2920$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 11:27 AM Subject: DeviceFeature The attribute has been moved up a level from the feature records to the feature level. We still want to offer a chance to provide consistent text strings of common driver features, even if they are not supported by the device, but are common use (e.g. N-Up, driver collation). Advantage: A driver is supposed to check, if a feature is a device feature. If it's not the driver has to check, if it can provide functionality for that specific feature (e.g. is the driver able to do N-Up on the host?). If the driver is not able, it cannot show that specific feature in a driver's user interface. In the past it was necessary to check each single record. This could have slowed down the performance of a driver. Now the first check is on feature level only. Very quick. If DeviceFeature is set to 'false', at least on record is to be expected, which will require the driver to emulate the functionality on the host. The basic philosophy of attribute DeviceFeature is unchanged. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/a3be6518/attachment-0001.html From norbertschade at comcast.net Tue Jan 13 10:02:07 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> Fw: Element structure Message-ID: <00a801c3d9e6$371a93e0$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 10:21 AM Subject: Element structure To keep the path for all features identical when you want to access them from a driver we changed some details: UPDF schema - element DeviceFeatures deleted. historic. it only had one subelement PrintCapabilities and no attributes. - element PrintMediaHandling deleted. this element added an extra layer to the structure, which required a different path to access the media features. - element GenericFeatures (watch the extra 's') deleted. element GenericFeature still unchanged and working. this element added an extra layer to the structure, which required a different path to access the generic features. - element CompositeFeatures (watch the extra 's') deleted. element CompositeFeature still unchanged and working. this element added an extra layer to the structure, which required a different path to access the composite features. - element TBD_VectorObjects deleted. will not be supported in this level of UPDF. UPDFFontHandling schema - element FontDownload deleted. will not be supported in this level of UPDF. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/411f56a8/attachment-0001.html From norbertschade at comcast.net Tue Jan 13 10:02:27 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> Fw: FillPattern Message-ID: <00b201c3d9e6$4276e720$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 3:05 PM Subject: FillPattern This element has been removed (not yet on the web). It was part of the modifying attributes of fonts. It will not be part of the current UPDF level. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/6149034c/attachment-0001.html From norbertschade at comcast.net Tue Jan 13 10:02:51 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> Fw: ID attributes Message-ID: <00bc01c3d9e6$50ee3600$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 11:21 AM Subject: ID attributes Almost all attributes with name="ID" are of type="xsd:ID" now. Exceptions: ID attributes of Parameter elements (in data types and wildcards) and some identifiers in font handling. Advantage: ID were supposed to be unique whereever possible from beginning on. Now your XML application can check that during validation, as they have to be unique by definition. We also have an advantage when we refer to one of them in an attribute of type="IDREF". XMLSpy shows available ID entries for convenience. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/3e94e389/attachment-0001.html From norbertschade at comcast.net Tue Jan 13 10:03:57 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> Fw: update UPDF files Message-ID: <00ca01c3d9e6$78374760$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Monday, January 12, 2004 10:11 AM Subject: update UPDF files I just updated the files on the UPDF site ftp://ftp.pwg.org/pub/pwg/upd/Current_Version in directories XML_Samples and XML_Schemas. I am going to send reports of the changes I made now. I will split them by subject to keep them short. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/6d672b87/attachment-0001.html From norbertschade at comcast.net Tue Jan 13 10:04:13 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> Fw: update web site, 2. Message-ID: <00d401c3d9e6$81e85ba0$6501a8c0@ne1.client2.attbi.com> second attempt. ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Wednesday, January 07, 2004 5:45 PM Subject: update web site, 2. I should add that the new files are in subdirectories 'XML Samples' (the are the xml instances) and 'XML Schemas' (these are all schemas). Norbert ----- Original Message ----- From: Norbert Schade To: UPD group Sent: Wednesday, January 07, 2004 5:44 PM Subject: update web site I just updated the UPDF web site ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/ Feel free to check the latest version with all the changes of the last weeks. This is the version Peter Zehler was referring to in his statement yesterday. I will send out detailed comments about the changes the next two days. We have some more candidates for changes, but the bulk of the work is done. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/4a19dd1f/attachment-0001.html From norbertschade at comcast.net Tue Jan 13 11:41:43 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> device fonts Message-ID: <013301c3d9f4$21030700$6501a8c0@ne1.client2.attbi.com> The elements DeviceFontList and DeviceFonts have been removed to avoid redundant layers. The FontObjects element now (not yet on the web) shows the following sub-elements: ModifyingAttributes DeviceFont This does not mean the relationship between any of the elements has changed. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040113/f9548f7f/attachment-0001.html From norbertschade at comcast.net Sat Jan 17 15:26:29 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> UPDF Specification Message-ID: <000a01c3dd38$310f4fe0$6501a8c0@ne1.client2.attbi.com> This last week we concentrated on the UPDF Specification. It's called version 0.90 now. A few minutes ago I updated the PDF file on the UPDF site. I also updated the UPDF site and changed the layout a bit to follow the current PWG standard. I also updated all UPDF schema and instance files at the proper locations. The specification experienced major changes: - Layout - - Adjusted to follow the PWG Semantic Model - - All schema elements and attributes are listed, most of them are explained. - - All elements are properly numbered, which was a problem for a long time. - Content - - We got rid of some old DTD section and added some general introductions. - - Quite a number of elements and attributes got a new or updated description. One of the main changes is the replacement of the Predefined_ID and Proprietary_ID with the new ClassifyingID. Please follow the links from the UPDF web site and check it out. Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040117/d36b1afd/attachment-0001.html From norbertschade at comcast.net Sun Jan 18 08:00:32 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> UPDF data types Message-ID: <001801c3ddc3$0eb96c60$6501a8c0@ne1.client2.attbi.com> In the process of aligning more closely to the Semantic Model we have adjusted our data types and element and attribute names accordingly. Main concept: - refer to PWG and Media data types where possible. And we do that a lot now. Status: most of it done. some discussion about finishings. - use the PWG and Media data types as the base and extend them where necessary. reasons are for example that we allow for proprietary entries in some cases (you'll find an additional 'xsd:string' in the corresponding union) and we list an additional entry sometimes to represent the device setting. Status: most of it done. The current schemas and instances already reflect that. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040118/1d79d4f2/attachment-0001.html From norbertschade at comcast.net Sun Jan 18 08:07:18 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> naming of UPDF elements and attributes Message-ID: <001c01c3ddc4$00e2d4e0$6501a8c0@ne1.client2.attbi.com> Another step of aligning our schemas closely with the Semantic Model. Main concept: - our element structure - especially of feature elements - is more complex than the one used in the Semantic Model. we still define the feature elements within our schemas, but try to follow the Semantic Model structure and use identical names. another advantage is that this can be used to create the requested connection for bi-directional communication. - generally we now use element and attribute names, which follow the naming concept of the Semantic Model (upper/lower case, avoid '_', etc.) - even if there is no template available in the Semantic Model. An extension to the data types notes some minutes ago: we now use much more patterns to describe rules for proprietary entries (one of Mark's requests of long time). Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040118/57f58319/attachment-0001.html From norbertschade at comcast.net Mon Jan 26 15:44:56 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> web site update Message-ID: <008a01c3e44d$429ce8a0$6501a8c0@ne1.client2.attbi.com> I have updated the UPDF web site. Please check the specification at ftp://ftp.pwg.org/pub/pwg/www/updf/UPDFFunctionalSpecification.pdf Please check the schemas at ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/XML%20Schemas Please check the instances at ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/XML%20Samples Or simply follow the links on the UPDF site. I'll send out little emails per subject about the changes. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/91cf8065/attachment-0001.html From norbertschade at comcast.net Mon Jan 26 15:57:32 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> key/keyref Message-ID: <009301c3e44f$053032e0$6501a8c0@ne1.client2.attbi.com> With UPDF we focus not only on providing a proper structure for a device description. We also try to guide the developer, who eventually will create instances based on the schemas. One way to do it is to work with predefined attribute values. We do that in the definition of the ClassifyingID. Another way is to use patterns. We do that in various places, mainly in the definition of the ClassifyingID. We have been working on yet another method to prevent developers from entering wrong values in elements and attributes. This implicates the use of identifiers and cross references. 1. attribute type ID. We have defined almost all attributes with name ID as type xsd:ID (checking the remaining ones). This ensures uniqueness of all identifiers across the whole instance. 2. attribute type IDREF. Some attributes are declared IDREF, like NonDominantRepresentative (checking further implementation). This allows - depending on the XML application - suggested lists a developer can select a value from. 3. keys Lately we have defined keys. e.g. we have defined keys on all features. 4. keyrefs On top of keys you can define keyrefs. e.g. we have defined keyrefs on the NonDominantRepresentative attributes. No the XML application has numerous chances to validate correct entries and even show proper messages for bad ones. We consider this type of cross references and validation superior functionality to make the whole system more user friendly. Files are on the web. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/8eccedd1/attachment-0001.html From norbertschade at comcast.net Mon Jan 26 15:59:06 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> UPDF Version Message-ID: <009c01c3e44f$3cc68ba0$6501a8c0@ne1.client2.attbi.com> We have edited the UPDFVersion attribute and assigned a more elaborate pattern to it. It's now of form '1.00.00.00'. Check out the details in the Spec. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/3a85ae16/attachment-0001.html From norbertschade at comcast.net Mon Jan 26 16:08:12 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> HelpID Message-ID: <00ae01c3e450$82b7b520$6501a8c0@ne1.client2.attbi.com> We have added a HelpID attribute to each feature. This optional attribute of type xsd:ID is meant to carry the text string for the context sensitive help. It can be localized the same way as the ID attribute of the feature. The UIGroup element also got a HelpID. So you can define context sensitive help for group controls. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/7e84ce09/attachment-0001.html From norbertschade at comcast.net Mon Jan 26 16:05:46 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> user interfaces Message-ID: <00a501c3e450$2b34c0e0$6501a8c0@ne1.client2.attbi.com> We have added a LocaleReference attribute to the UserInterface element. This allows it (not mandatory) to assign a certain user interface to certain locales (of form 'enUS') like for the Asian market, but have another generic user interface as the default (no LocaleReference attribute assigned). Allowed values are pairs of two-character snippets, which are the familiar terms for language and country (see the UPDFDataTypes schema for reference). We have also added a wildcard element to UIGroup and UIFeature elements. This enables developers to link their own UI structures to the UPDF instances to support extended user interface tags. Further details in the Spec. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/8d06bea8/attachment-0001.html From norbertschade at comcast.net Mon Jan 26 16:12:34 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> UPDF Functional Specification Message-ID: <00b701c3e451$1ee95d40$6501a8c0@ne1.client2.attbi.com> We have heavily reviewed and extended the Specification. There are no redundant or old sections any more. Latest changes: - All chapters describing schemas, except the Device Description. - Wildcards and other common tags. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040126/5d94da4a/attachment-0001.html From norbertschade at comcast.net Wed Jan 28 13:14:52 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> review Dependencies Message-ID: <001001c3e5cb$48541e60$6501a8c0@ne1.client2.attbi.com> Last year we checked different procedures to implement dependencies to find out about the best implementation in UPDF. We did a review of dependencies these days. This includes the schema design as well as the specification (not yet on the web, will be end of week). Although we polished some areas for the final step of the draft version, we did not change the basic idea. We had some objectives: 1. Where to list dependencies in the schema? Theoretically there are two possible solutions. Either you assign them to the feature to be checked once it gets the focus. Or you list all dependencies in a common pool. We stay with the original approach of a common pool. Advantages are maintenance (easier to be checked than looking all over the place) and extensibility. The latter is a unique feature of UPDF, as optional units and/or a user policy could have additional dependencies (dependencies of the master description cannot be removed nor edited). A recommendation to the driver: A dependency of an optional unit or user policy should have priority. However in a perfect design there would not occur any conflict. General driver procedure: First check, if there is a dependency with a FeatureCondition of the currently selected feature. Second check, if there's an action defined in any of the hits with the currently selected feature declared as the dominant feature. 2. Why a dominant feature? Yes, we could have split up all dependencies and listed them depending on the feature with the focus. However we wanted to design a compact structure, which groups related dependencies properly. If there are dependencies with three or more features involved, but different actions depending on which feature has the focus, we were concerned that listing all required combinations separately would confuse the reader and developer of the device description, especially, if the list is not properly ordered. And it narrows the number of candidates for the driver once it hits a FeatureCondition. 3. Extended functionality. We wanted to support functionality commonly available in a number of contemporary driver concepts. This includes messages as well as hints for info buttons, mandatory selections of settings of features based on a dependency and indications that the appearance of a feature should change, once the dependency is resolved. 4. Conversion between different concepts. We always have in mind that dependencies (sometimes called constraints) are defined differently in various concepts. We are positive that a conversion from or to UPDF is always possible and not ambiguous, although you may loose some functionality when converting to other standards. Check it out! Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040128/cffc1826/attachment-0001.html From norbertschade at comcast.net Mon Feb 2 00:15:07 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> file update Message-ID: <002801c3e94b$8652d3e0$6501a8c0@ne1.client2.attbi.com> I updated all schemas, instances and the specification. More details tomorrow. if somebody wants to check early, you may want to start with the key/keyref and GenericFeature/CompositeFeature elements. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040202/0020712d/attachment-0001.html From norbertschade at comcast.net Mon Feb 2 10:14:59 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> halftoning Message-ID: <004401c3e99f$53667000$6501a8c0@ne1.client2.attbi.com> we split the halftoning feature into three single ones: RasterHalftoning VectorHalftoning TextHalftoning that allows easier handling when all three features should appear in the user interface. these three feature are likely a candidate for a composite feature. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040202/87b060b9/attachment-0001.html From norbertschade at comcast.net Mon Feb 2 10:26:50 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> further deployment of key/keyref Message-ID: <005901c3e9a0$facd3ee0$6501a8c0@ne1.client2.attbi.com> The idea of UPDF is not only to provide proper structures to describe a printer with all his options and features, but to help a description developer as much as possible with creating the describing UPDF instances. That's one of the reasons we spent quite some time on investigating the power of the key/keyref elements. We do use that at a number of places to ensure that somebody really makes a reasonalbe entry. We already used it for the NonDominantFeature attribute. Sample are: DominantFeature, SetFeature, FeatureCondition in dependencies. We hope this helps description developers - as it helped us. As a follow-up we could expunge some data types (Feature, FeatureID), which are now managed with more flexibility by the keys. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040202/077490f9/attachment-0001.html From norbertschade at comcast.net Mon Feb 2 10:34:06 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> GenericFeature extension Message-ID: <006201c3e9a1$ff33d7e0$6501a8c0@ne1.client2.attbi.com> We extended the GenericFeature feature. You now can not only define a feature with a predefined list of settings, but with variable settings as well. Check the VariableValue element for that. We also added an optional ClassifyingID attribute to the record. This allows it to use some meaningful entry in case you want to prepare it for bi-directional communication. So you could name a feature with an element name of the Semantic Model and use strings of well known values of the Semantic Model in the ClassifyingID. This provides the level of flexibility we want to have with the GenericFeature. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040202/9ebfbd20/attachment-0002.html From norbertschade at comcast.net Mon Feb 2 10:34:06 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> GenericFeature extension Message-ID: <006201c3e9a1$ff33d7e0$6501a8c0@ne1.client2.attbi.com> We extended the GenericFeature feature. You now can not only define a feature with a predefined list of settings, but with variable settings as well. Check the VariableValue element for that. We also added an optional ClassifyingID attribute to the record. This allows it to use some meaningful entry in case you want to prepare it for bi-directional communication. So you could name a feature with an element name of the Semantic Model and use strings of well known values of the Semantic Model in the ClassifyingID. This provides the level of flexibility we want to have with the GenericFeature. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040202/9ebfbd20/attachment-0003.html From norbertschade at comcast.net Tue Feb 3 12:21:04 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> new SM schemas version 1.0 Message-ID: <00b901c3ea7a$1abcdb00$6501a8c0@ne1.client2.attbi.com> I've downloaded the new schemas of the Semantic Model, version 1.0. As you should know we use four schemas to refer to elements, attributes especially data types. All SM schemas work flawlessly and without any modification. >From now on we'll refer to this version. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040203/1245f08d/attachment-0001.html From norbertschade at comcast.net Tue Feb 3 12:57:38 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> PWG Semantic Model compliant Message-ID: <00d501c3ea7f$3676b000$6501a8c0@ne1.client2.attbi.com> We got a confirmation from Peter Zehler that to the best of his knowledge we are considered PWG Semantic Model compliant by referring to the PWG and Media schemas we import. We'll have an eye on the element and attribute names to use them as much as possible for structures and types common between the Semantic Model and UPDF, but not collide otherwise. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040203/8159a46b/attachment-0001.html From norbertschade at comcast.net Tue Feb 3 13:52:47 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> minimum hardware margins Message-ID: <00fa01c3ea86$ea6969c0$6501a8c0@ne1.client2.attbi.com> We've finished the review of the media minimum hardware margins. The according schemas and instances are available on the web under ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/ Or you can follow the link on the UPDF site. I think this is worth reading. The way it works: 1. MediaHardwareMarginsPattern We have defined a pattern to specify hw margins. We used the custom media size pattern as a template and modified it as needed. It is partly verbal, but tells about the values as well. We think it's a good mixture. 2. MediaHardwareMargins This feature is a predefined one. Its appearance is permanently set to hidden, as we want this to be used as a reference, but not to appear in the user interface (if somebody desperately needs it, there is always the change of composite features). Now this has a number of advantages. First every record is only listed once (before it was specified per media size). --> easier maintenance. Second you can specify as many records as you may need anywhere. It will not show up in the UI unwanted. You can define records especially to be used for landscape, if you need to. Basically you could define a special record for any need. 3. Dependencies We really activate a record in the dependencies. Vision something like "if MediaSize is Letter and Orientation is Landscape, the four margins are 1.1.1.1in". Fortunately our dependencies offer everything we need to check any condition and start any action. Do not use a dominant feature for the action, as you want it checked always. 4. Generic features One may want to create a generic feature called "Edge to Edge Printing", which overwrites all hw margins and sets them to zero when selected. No problem. See this request realized in the samples. You create the feature records and add a dependencies to select a different hw margin record. Be careful with the order of dependencies. They are used in sequential order, master description first, user policy last. I think the way it works is a fortunate coincidence of several factors. We do not have any open request left with this design. Check it out. Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040203/074376ea/attachment-0001.html From norbertschade at comcast.net Tue Feb 3 16:01:06 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> syntax optimization Message-ID: <017e01c3ea98$d7d820a0$6501a8c0@ne1.client2.attbi.com> We finished a number of syntax optimizations. When an element only had exactly one sub-element or exactly one attribute (and no element) we removed that and changed the type of the element accordingly. That simply shortens the schema and improves reading. No architectural change. Files are not yet on the web. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040203/fa6c8211/attachment-0001.html From norbertschade at comcast.net Thu Feb 5 09:12:12 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> RAM, AvailableMemory features Message-ID: <005d01c3ebf2$0cde15c0$6501a8c0@ne1.client2.attbi.com> We've finished a review of the RAM and AvailableMemory features. With the positive experience we made with the redesign of the MediaHardwareMargins feature we did some small modifications to these features as well. Details: RAM We renamed the KB attribute to 'ClassifyingID' and defined a pattern (memory_[\d]*KB). Other attributes have been removed. AvailableMemory The feature is not set to 'Hidden' permanently, but that could well be a useful setting in an implementation. NonDominantRepresentative is made optional, as in many cases there may only be one record. We have replaced some attributes in the record with a VariableValue element (here not on the feature, but the record level), which defines the minimum and maximum values as well as the step. If a relationship between the current RAM and AvailableMemory settings is to be defined, this can be done with dependencies. See the sample for demonstration. The corresponding schemas and instances are available on the web under ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/ Or you can follow the link on the UPDF site. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040205/605b6ae8/attachment-0001.html From norbertschade at comcast.net Thu Feb 5 09:29:46 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:18 2009 Subject: UPD> status Message-ID: <006801c3ebf4$815fe980$6501a8c0@ne1.client2.attbi.com> Of all the requests, wishes and personal notes we have come down to three related open items, all in the area of trying to align as well as possible to the Semantic Model. 1. Check, if the description developer shall be enabled to define unique values for various features. The Semantic Model seems a bit more restrictive than we have been in the past. 2. Check the finishing features. While we have defined special features in UPDF, there is more one 'covers-it-all' feature in the Semantic Model. 3. Do a final check of element, attribute and data type names. This is it! We are working hard to close these three items during this week. That would bring us to a level 0.95 of the specification. If anybody has any requests for version 1 of the standard, this is the time to come forward. We will soon enter the phase of last calls. Major implementations during the last months have been - merge Predefinid_ID and Proprietary_ID to one ClassifyingID and related changes. - rename and adjust elements, attributes and data types compliant to the Semantic Model. - implement key/keyref elements to further help the description developer. - some optimizations on the composite and generic features. - a lot of little things based on feedback and notes we had. The specification document is on the same level as the schemas. The layout is finished. Proper headings and numbering done. The UPDF.xsd master schema shows the exact order of elements as in the specification. The specification is showing the complete structure of all schemas. Various sections have to be further explained. The sample are consistent with the schemas. All sample are validated with the current schemas. We will likely extend the samples to a full features device description for one device. However the current version demonstrates all aspects of the standard. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040205/b3ee5dbe/attachment-0001.html From norbertschade at comcast.net Fri Feb 6 13:20:58 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> 2 of 3 issues resolved - down to the last Message-ID: <006b01c3ecdd$f821d440$6501a8c0@ne1.client2.attbi.com> Items 1 and 3 are finished. 1. we checked the data types, whether they should be open to the description developer for almost arbitrary editing. we are working with a lot of patterns, partly pwg patterns, partly updf patterns. 3. we did a lot of renaming, but no structural changes were necessary. files are not yet on the web. we'll do that over the weekend. Leaves us with the finishing features. ONE TO GO! Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: UPDF reflector Sent: Thursday, February 05, 2004 9:29 AM Subject: UPD> status Of all the requests, wishes and personal notes we have come down to three related open items, all in the area of trying to align as well as possible to the Semantic Model. 1. Check, if the description developer shall be enabled to define unique values for various features. The Semantic Model seems a bit more restrictive than we have been in the past. 2. Check the finishing features. While we have defined special features in UPDF, there is more one 'covers-it-all' feature in the Semantic Model. 3. Do a final check of element, attribute and data type names. This is it! We are working hard to close these three items during this week. That would bring us to a level 0.95 of the specification. If anybody has any requests for version 1 of the standard, this is the time to come forward. We will soon enter the phase of last calls. Major implementations during the last months have been - merge Predefinid_ID and Proprietary_ID to one ClassifyingID and related changes. - rename and adjust elements, attributes and data types compliant to the Semantic Model. - implement key/keyref elements to further help the description developer. - some optimizations on the composite and generic features. - a lot of little things based on feedback and notes we had. The specification document is on the same level as the schemas. The layout is finished. Proper headings and numbering done. The UPDF.xsd master schema shows the exact order of elements as in the specification. The specification is showing the complete structure of all schemas. Various sections have to be further explained. The sample are consistent with the schemas. All sample are validated with the current schemas. We will likely extend the samples to a full features device description for one device. However the current version demonstrates all aspects of the standard. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040206/6f2cf6a8/attachment-0001.html From norbertschade at comcast.net Sun Feb 8 18:25:34 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> Version 0.95 on the UPDF web site!!! Message-ID: <002401c3ee9a$da05e6e0$6501a8c0@ne1.client2.attbi.com> It's done! We've resolved all open design issues we know of. The current version provides all the capabilities it was designed for. Reason enough to call it Version 0.95. I'll send out another email about the changes regarding finishing features and the relationship to the Semantic Model for those features. But I'll be out of town for two days. Back on Wednesday. Time enough for you to have a first look. Please check the 'XML Schemas' and 'XML Samples' directories (ftp://ftp.pwg.org/pub/pwg/upd/Current_Version/) or follow the links on the UPDF web site. The specification document has been updated. So it is reflecting the current schemas with all actual elements and attributes. The layout concerning chapters and sections is pretty final. The numbering is ok and can be used as reference for comments. We know that we have some content to fill in. that will likely happen during the next two weeks. The current specification file will be on the UPDF web site either late tonight or tomorrow morning. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040208/520df0d7/attachment-0001.html From norbertschade at comcast.net Mon Feb 9 09:31:02 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> Finishing features Message-ID: <000a01c3ef19$5845dbe0$6501a8c0@ne1.client2.attbi.com> We have finished reviewing the finishing features. While having a close eye on the finishing as implemented in the Semantic Model, we recognized that we would need a more specific split of different finishing functionality. While the Semantic Model has one large list of possible finishing settings, we think that some of those settings are mutually exclusive, while others work well with each other. So we created a number of predefined features, even extended the ones we had so far. However we were careful referring to the element and attribute names of the SM as much as possible. We think we resolved the needs we have while staying close to the SM design. Especially with the composite features in your mind you have any flexibility you need. Check it out. The files are on the UPDF site. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040209/004d8ade/attachment-0001.html From norbertschade at comcast.net Wed Feb 18 15:21:11 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> update UPDF web site Message-ID: <003b01c3f65c$c0084f20$6501a8c0@ne1.client2.attbi.com> I just finished some editing on the UPDF web sites. We now have a directory structure more closely related to other PWG standards. To get to the UPDF web site: http://www.pwg.org/updf/ Following the links on the page you will get to the official version of files like the pdf version of the specification. To check UPDF related files in general: ftp://ftp.pwg.org/pub/pwg/upd/ This is the top directory for all UPDF related files. As we are preparing a last call, we have created a 'wd' (working draft) directory: ftp://ftp.pwg.org/pub/pwg/upd/wd/ This directory will hold all files related to level 1.0, which is work in progress. a.. This includes a specification document (in WinWord format). This document is considered 'under review', while the official pdf version under http://www.pwg.org/updf/ is the latest public version. The doc file could be slightly newer sometimes and vary in some aspects, if reviewed at that time. b.. It further includes the current schemas in subdirectory 'schemas'. c.. It further includes sample instances, if available in subdirectory 'instances'. Please keep this email at least for the next four weeks to have some reference for pathes. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040218/a558bd3c/attachment-0001.html From norbertschade at comcast.net Wed Feb 18 15:28:00 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> First notice: last call coming Message-ID: <004801c3f65d$b3f6e740$6501a8c0@ne1.client2.attbi.com> To give everybody enough lead time we'd like to inform early: We plan to have a last call session in the first two weeks of March, right after the upcoming PWG conference. Please make a note in your schedule. We'd prefer communication on a broad level. To keep things easy we will split the whole thing up into sections. Last task in progress: reviewing some sections of the specification document. We'll keep you informed the next days. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040218/5be64ab8/attachment-0001.html From hamzy at us.ibm.com Wed Feb 18 16:27:44 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Wed May 6 14:05:19 2009 Subject: UPD> Standardized job properties Message-ID: UPDF uses standard media names. It should also standardize every other job property (like nup, sides, stapling, etc...). Currently, the printer driver group in the Free Standards Group is standardizing job properties that are common among printer drivers. What do you think of UPDF using this standard as part of its own? ftp://ftp.pwg.org/pub/pwg/fsg/driver/ ftp://ftp.pwg.org/pub/pwg/fsg/driver/fsg-PDC-V09-021604.sxw Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040218/bb0f8313/attachment-0001.html From norbertschade at comcast.net Wed Feb 18 17:07:11 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> Standardized job properties References: Message-ID: <003a01c3f66b$8f2e0fc0$6501a8c0@ne1.client2.attbi.com> Mark, thanks for the hint. however we have been adding a lot of patterns and enumerations the last half year to specify the ClassifyingID in detail. I think most of our features have some kind of syntax description for the ClassifyingID. e.g. there is a pattern for NUP and so on. Please have a look at the master UPDF schema and the UPDF data types schema. You should still be familiar enough with it to check it out in ten minutes. Whenever available we refer to enumerations and patterns of the PWG Semantic Model. Where we have further requirements, we have added UPDF specific descriptions. I'll check your links, if I have a minute the next days. Saw there is a pdf from Feb 16 2004. is that the best to study? Norbert ----- Original Message ----- From: Mark Hamzy To: UPDF reflector Sent: Wednesday, February 18, 2004 4:27 PM Subject: UPD> Standardized job properties UPDF uses standard media names. It should also standardize every other job property (like nup, sides, stapling, etc...). Currently, the printer driver group in the Free Standards Group is standardizing job properties that are common among printer drivers. What do you think of UPDF using this standard as part of its own? ftp://ftp.pwg.org/pub/pwg/fsg/driver/ ftp://ftp.pwg.org/pub/pwg/fsg/driver/fsg-PDC-V09-021604.sxw Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040218/7d0e0d28/attachment-0001.html From norbertschade at comcast.net Wed Feb 18 18:27:49 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> align UPDF and FSG Message-ID: <001201c3f676$d2c97de0$6501a8c0@ne1.client2.attbi.com> Mark, I offer a telecon tomorrow. you pick the time. proposal: 2pm EST, which should be right after lunch your time. I will check pages 11 to 16 (included) of the latest pdf file from Feb 16 in ftp://ftp.pwg.org/pub/pwg/fsg/driver/ I expect that everybody involved has all UPDF schemas open, which are available at ftp://ftp.pwg.org/pub/pwg/upd/wd/schemas/ we will mainly concentrate on the master schema UPDF.xsd and the data types schema UPDFDataTypes.xsd. Keep in mind that we refer to the PWG Semantic Model schemas at various opportunities. Questions upfront: - Do you have your stuff ready in XML (this is extremely important)? - I see a setting 'None' every now and then. Is that corresponding to the UPDF 'device-setting'? The agenda is simple: we would compare your data types with ours, feature by feature. should not need more than half an hour to find out common issues and differences. I'm not planning on discussing the results in the phone call - just gather data, which both parties agree on. Let me know Norbert Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040218/a6537bd7/attachment-0001.html From hamzy at us.ibm.com Thu Feb 19 10:45:55 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Wed May 6 14:05:19 2009 Subject: UPD> Telecon to align UPDF and FSG Message-ID: Thursday, February 19 GMT 19:00-20:00 EDT 14:00-15:00 CDT 13:00-14:00 MDT 12:00-13:00 PDT 11:00-12:00 Toll Free: 1-888-687-2858 (use this first if possible) Toll: 1-719-457-3541 Passcode: 726694 The agenda is simple: we would compare your data types with ours, feature by feature. should not need more than half an hour to find out common issues and differences. I'm not planning on discussing the results in the phone call - just gather data, which both parties agree on. Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040219/13f2d3d7/attachment-0001.html From norbertschade at comcast.net Fri Feb 20 12:44:04 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> fsg extension schema started Message-ID: <005e01c3f7d9$22357b00$6501a8c0@ne1.client2.attbi.com> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: UPDFDataTypes.xsd Type: text/xml Size: 57411 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/20040220/c9537492/UPDFDataTypes-0001.xml -------------- next part -------------- A non-text attachment was scrubbed... Name: FSGDataTypes.xsd Type: text/xml Size: 6111 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/20040220/c9537492/FSGDataTypes-0001.xml From hamzy at us.ibm.com Fri Feb 20 14:20:51 2004 From: hamzy at us.ibm.com (Mark Hamzy) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF / FSG meeting take 2 Message-ID: Friday, February 20 GMT 19:30-20:30 EDT 14:30-15:30 CDT 13:30-14:30 MDT 12:30-13:30 PDT 11:30-12:30 Toll Free: 1-888-687-2858 (use this first if possible) Toll: 1-719-457-3541 Passcode: 726694 Mark Take a look at the Linux Omni Printer Driver Framework at http://www.ibm.com/linux/ltc/projects/omni/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040220/cbaad717/attachment-0001.html From norbertschade at comcast.net Fri Feb 20 16:16:05 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> Color handling Message-ID: <00b201c3f7f6$c0ebcc00$6501a8c0@ne1.client2.attbi.com> Today we had a chance to discuss color handling in a small group (Mark Hamzy, Jim Sommer, Jody from the Gnome organization and me) to check the UPDF design and compare to the needs in the FSG. We agreed that at the first glance it looks like UPDF would provide all tags needed to describe the way the device is expecting color data. 1. The UPDF Color feature Multiple color records can be created, e.g. for monochrome and color. A color record offers RGBColor elements, which tell about the colors the device supports, e.g. CMYK, which would mean the definition of four RGBColor elements. The bit depth can be set per color. if the complete bit depth can be supported by the device, no additional halftoning is required. The color records also tell, whether the color info should be provided per pixel, per band or per scanline. 2. The UPDF PhotoHalftoning feature There are halftoning feature for vector and text as well. But we can concentrate on raster (= photo), as that's the only place where halftoning patterns are likely used on the host (we consciously are ignoring the download of patterns). Let's say a device only supports two of the eight bits a driver has to deal with. Then the remaining six bits are supposed to be resolved by halftoning. We are facing a XML limitation here. There are no two-dimensional arrays in XML. So we have to split the matrix up into lines. By default the remaining six bits may be resolved by a 6x6 matrix. This would result in six of the OneHorizontalLineOfTheHalftoningMatrix elements, each with six comma separated values. That's the best flexibility we can get in XML for that definition. 3. The UPDF RasterObject object This is the specification of the way raster graphic is handled. This moment we can concentrate on the Band element. If no Band element is specified, the device can deal with the whole page as a band. Otherwise you would see the maximum size defined here. That's the high level explanation of how it's done in UPDF. There are no LUT. However one can add ICC Profiles to the device configuration and LUT can be taken from there. I'm going to put the current files out on the web tonight. you can find it under ftp://ftp.pwg.org/pub/pwg/upd/wd/ schemas are located in subdirectory 'schemas'. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040220/df1c1ff0/attachment-0001.html From norbertschade at comcast.net Sat Feb 21 12:23:57 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> update 022104 Message-ID: <002b01c3f89f$7d1ac220$6501a8c0@ne1.client2.attbi.com> Seen Mark's new version of the PDC. Comments - General -- we use 'device-setting' in UPDF instead of 'none' and think that more descriptive. - Copies, MediaZoomingByPercentage -- we define a range with a step in UPDF -- we still do think there should not be any 'None' combined with an integer. - MediaColor -- in UPDF we would still allow the original MediaColorWKV defined in the MediaWellKnownValue schema ('white', 'pink', etc.) -- if we predefine an additional list - as I've done in the attached FSGDataTypes schema - I'd like us to follow the pattern of the updf:MediaColorRGBExtensionPattern, which follows the pattern of the pwg:MediaColorExtensionPattern. that means we'd always start with 'custom-media-color-rgb-', then specify an RGB value, then arbitrarily add a semantic identifier. this would not hurt any of the existing patterns in place and would be a reliable and predictable pattern before the semantic identifier. I've seen you like hex values better. so I changed that in the MediaColorRGBExtensionPattern, but used lower case to stay with the MediaColorExtensionPattern. does that work for you? - MediaInputTrayCheck -- I changed the spelling to lower case with dash - MediaSize -- I didn't check the list, but I assume it's the complete list as defined in the MediaWellKnownValue schema. - MediaType -- added 'plain' to the FSG data types -- added the new FSG data type to the UPDF data type -- I did not add 'none', as we have a general 'device-setting' - MediaHarwareMargins, NumberUp, PrinterResolution -- we do not follow the same pattern in UPDF and FSG, although we express similar information. we think our pattern is more human readable. - Description of device color capabilities -- especially with the latest modifications and the telecon yesterday in mind I am convinced that the current UPDF description offers all input a driver needs for a basic device color functionality. I practiced different ways to implement finishing features, but I'm still thinking. All this work only makes sense to me, if we commonly use the same schemas. I put all actual schemas and instances on the UPDF ftp site. use ftp://ftp.pwg.org/pub/pwg/upd/wd/ or the links on the web site. Regards Norbert Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040221/fbe73400/attachment-0001.html From norbertschade at comcast.net Mon Feb 23 16:09:59 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> Collation Message-ID: <001401c3fa51$6567c3e0$6501a8c0@ne1.client2.attbi.com> We have reviewed collation in UPDF. A statement upfront: In UPDF we are defining features, but a description developer using the UPDF device description is flexible to specify how the feature is going to be used and when a certain command sequence is to be sent at a different place: the events. The idea behind that is to be able to specify a feature a certain way including attributes, ranges, lists of predefined values, etc. Sample: Copies may be specified for one device on a PDL level, for another on a job level. As we see it that does not affect its description of the attributes mentioned above. We want to stay with that concept for collation as well. That means we do not want to specify how and when it will be used when specifying the feature. Therefore we will stick with the two enumerated values 'Collated' and 'Uncollated', but not add a special 'JobCollated' (or any similar name) to it. We have one major preference: We want to tell about the way the device is expecting data. I think the device in most cases is expecting data either with job commands or (exclusively) with PDL commands (at least in some current PDL versions). I do not consider the case very popular that somebody wants to or has to or should be enabled to set job copies to 2, document1 copies to 1, document2 copies to 3 and then expect a dialog telling him which of the settings override or substitute others. Sometimes restriction is user guidance as well. The two last sentences are a personal statement, of course. A secret peak into the future: I could imagine that depending on the overall interest in UPDF we might add an attribute to every feature with enumeration values like 'DominantJobFeature', 'DominantDocumentFeature', 'JobFeature', 'DocumentFeature' (maybe even 'DominantPageFeature' and 'PageFeature'). Not a serious proposal for the time being. However this would allow to use the same feature definition, but additionally tell about its use. Specification, schemas and instances with all final details on that not yet on the web. Of course, I'm open to discussion. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040223/c6650de6/attachment-0001.html From norbertschade at comcast.net Tue Feb 24 20:15:54 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> update 2/24/04 Message-ID: <001201c3fb3c$ed151fe0$6501a8c0@ne1.client2.attbi.com> I updated the UPDF directories. check it out on ftp://ftp.pwg.org/pub/pwg/upd/wd/ in subdirectories schemas and instances. this includes the latest finishing architecture and data types. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040224/92081ac0/attachment-0001.html From norbertschade at comcast.net Wed Feb 25 19:41:05 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> update spec Message-ID: <000e01c3fc01$37cf3880$6501a8c0@ne1.client2.attbi.com> I have updated the specification documentation (in WinWord format) on the UPDF web site. check it out on ftp://ftp.pwg.org/pub/pwg/upd/wd/ Up to page 90 this is almost considered the version we'll start with for the last call. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040225/86d89a2c/attachment-0001.html From norbertschade at comcast.net Thu Feb 26 14:05:58 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> wildcards Message-ID: <000a01c3fc9b$91f6b1e0$6501a8c0@ne1.client2.attbi.com> before we close the spec I want to publically ask, if anybody is asking for further extensibility by adding further wildcards to certain elements. Candidates are: 1. DeviceCapabilites - right now we support PrintCapabilities. maybe somebody wants to add ScanCapabilities, etc. 2. PrintCapabilities - there is no wildcard. however I think we covered that pretty well. 3. All features - we have wildcards on the feature record level, but not on the feature level (parallel to a record). we cannot predict the future and some feature may be more suitable than others for extensions. 3.1. GenericFeature - certainly a special feature 3.2. the halftoning features - quite unpredictable 3.3. variable features like Copies, ScalingPercentage. - these do not have any wildcard so far. I do not easily see other candidates. When it comes to objects, dependencies and events a driver may want to rely on a certain architecture. That was the reason for the whole standard at the first place. What do you think??? Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040226/49f7beed/attachment-0001.html From norbertschade at comcast.net Fri Feb 27 17:02:44 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> last changes before last call Message-ID: <001001c3fd7d$6de26a00$6501a8c0@ne1.client2.attbi.com> We've made the last modifications before we start the last call. 1. A reference to an IHV support site. We've added an attribute to the device configuration, which takes a URL, likely to show to the IHV support site of the corresponding product. 2. Additional wildcards We've added additional wildcards to PrintCapabilities, all features, Objects, RasterObjects and FontObjects. This allows future flexibility, especially if somebody wants to try something out. 3. Wildcard schema renamed. We've renamed the UPDF wildcard schema, holding the additional parameters, from UPDFWildcards to UPDFAdditionalParameters. The namespace prefix used in the instances has been changed from 'wildcard' to 'param'. That should be it. We are ready for last call. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040227/77bb8dfc/attachment-0001.html From norbertschade at comcast.net Fri Feb 27 17:52:26 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF, version 1.0: Last Call Message-ID: <002501c3fd84$5f9952e0$6501a8c0@ne1.client2.attbi.com> We have finished editing the UPDF schemas, instances and specification documentation. All files are copied to the UPDF web site. I forward some info I sent a week ago on the UPDF web site below. so you can easily find everything. The files will not change the next two days. We will start the window for last call on UPDF, version 1.0, the upcoming Monday, March 1st. The window will stay open full two weeks until Sunday, March 14 (midnight). We will review the specification in sections. I will send out a separate email on the procedure in a few minutes. Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: UPDF reflector Sent: Wednesday, February 18, 2004 3:21 PM Subject: UPD> update UPDF web site I just finished some editing on the UPDF web sites. We now have a directory structure more closely related to other PWG standards. To get to the UPDF web site: http://www.pwg.org/updf/ Following the links on the page you will get to the official version of files like the pdf version of the specification. To check UPDF related files in general: ftp://ftp.pwg.org/pub/pwg/upd/ This is the top directory for all UPDF related files. As we are preparing a last call, we have created a 'wd' (working draft) directory: ftp://ftp.pwg.org/pub/pwg/upd/wd/ This directory will hold all files related to level 1.0, which is work in progress. a.. This includes a specification document (in WinWord format). This document is considered 'under review', while the official pdf version under http://www.pwg.org/updf/ is the latest public version. The doc file could be slightly newer sometimes and vary in some aspects, if reviewed at that time. b.. It further includes the current schemas in subdirectory 'schemas'. c.. It further includes sample instances, if available in subdirectory 'instances'. Please keep this email at least for the next four weeks to have some reference for pathes. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040227/14a6b8ab/attachment-0001.html From norbertschade at comcast.net Fri Feb 27 18:25:06 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF, version 1.0: Last Call procedure Message-ID: <002e01c3fd88$eff50e20$6501a8c0@ne1.client2.attbi.com> We will review the specification in sections. 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. On Monday, March 1st, and Tuesday, March 2nd, we will concentrate on the first two chapters, pages 10 - 18. - 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. - Common Tags: Some elements and attributes are used all over the place. We have decided on explaining them upfront. That speeds up reading later. On Wednesday, March 3rd, we will concentrate on the configuration files. - Device Configuration: The driver entry point into the UPDF world and the environment for the base unit. - Option Configuration: The environment for optional units. 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. - On Thursday, March 4th, we will concentrate on the DeviceHeader and the Header under PrintCapabilities. - On Friday, March 5th, we will concentrate on all predefined features. A lot of pages, but similar information per feature. - 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. - On Tuesday, March 9th, we may concentrate on Objects (raster graphic, device fonts). 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. - On Wednesday, March 10th, we'll finish the unit description with the dependencies and events. - On Thursday, March 11th, we could talk about the command sequences, and the Parameter Converter, as these two issues are closely related to events. - Leaves us with the locales and the user policies for Friday, March 12th. We don't have to stick to that schedule literally. But some may like to know, how chapters can be grouped. We'll decide on changes flexibly while we go. Please send all emails to the UPDF reflector. I will answer personal emails, too. But that's not the idea. Hope we'll see some people talking it over. If we don't see any traffic, that either means nobody cares or the design as well as the specification is considered perfect. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040227/dee72173/attachment-0001.html From norbertschade at comcast.net Mon Mar 1 08:01:50 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF, version 1.0: Last Call procedure, day 1 Message-ID: <003101c3ff8d$5d12f160$6501a8c0@ne1.client2.attbi.com> if we stick with the plan, we'll concentrate on - general questions - the general layout of the specification document - the formal introduction with all the references on the first pages - the table of contents. Then we'll jump over to the high level overview on pages 10 - 18. Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: UPDF reflector Sent: Friday, February 27, 2004 6:25 PM Subject: UPD> UPDF, version 1.0: Last Call procedure We will review the specification in sections. 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. On Monday, March 1st, and Tuesday, March 2nd, we will concentrate on the first two chapters, pages 10 - 18. - 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. - Common Tags: Some elements and attributes are used all over the place. We have decided on explaining them upfront. That speeds up reading later. On Wednesday, March 3rd, we will concentrate on the configuration files. - Device Configuration: The driver entry point into the UPDF world and the environment for the base unit. - Option Configuration: The environment for optional units. 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. - On Thursday, March 4th, we will concentrate on the DeviceHeader and the Header under PrintCapabilities. - On Friday, March 5th, we will concentrate on all predefined features. A lot of pages, but similar information per feature. - 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. - On Tuesday, March 9th, we may concentrate on Objects (raster graphic, device fonts). 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. - On Wednesday, March 10th, we'll finish the unit description with the dependencies and events. - On Thursday, March 11th, we could talk about the command sequences, and the Parameter Converter, as these two issues are closely related to events. - Leaves us with the locales and the user policies for Friday, March 12th. We don't have to stick to that schedule literally. But some may like to know, how chapters can be grouped. We'll decide on changes flexibly while we go. Please send all emails to the UPDF reflector. I will answer personal emails, too. But that's not the idea. Hope we'll see some people talking it over. If we don't see any traffic, that either means nobody cares or the design as well as the specification is considered perfect. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040301/60a61552/attachment-0001.html From norbertschade at comcast.net Tue Mar 2 08:57:47 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> Maturity level Message-ID: <000c01c4005e$5a1b9760$6501a8c0@ne1.client2.attbi.com> While studying the PWG process document I've changed the UPDF maturity level to 'Stable' using the proper predefined keyword. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040302/965bfbdf/attachment-0001.html From norbertschade at comcast.net Tue Mar 2 12:52:27 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: Fw: UPD> Maturity level Message-ID: <009601c4007f$202d41e0$6501a8c0@ne1.client2.attbi.com> As I want to follow the formal procedure as closely as possible these days, I declare the maturity issue Resolved - Document updated to reflect the resolution If necessary, I copy new files with changes to the UPDF sites at the end of my work day. Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: UPDF reflector Sent: Tuesday, March 02, 2004 8:57 AM Subject: UPD> Maturity level While studying the PWG process document I've changed the UPDF maturity level to 'Stable' using the proper predefined keyword. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040302/51763eff/attachment-0001.html From norbertschade at comcast.net Tue Mar 2 12:52:54 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF last call Message-ID: <009a01c4007f$32de69e0$6501a8c0@ne1.client2.attbi.com> We have started a last call for UPDF, version 1.0. yesterday. It will last for the next three weeks and end on Friday, March 19th, 10pm EST. I sent a couple of small emails to the UPDF reflector about the procedure. in case you are not on that reflector, but would like to participate or listen, please check the UPD archive. We will stick to the original schedule and use the extra days for general discussion time. While studying the PWG Process document I found out that the formal period for a last call is considered to be at least 15 full work days. Therefore we extended the period from two (formerly announced on the UPDF reflector) to now three weeks. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040302/2d81a677/attachment-0001.html From norbertschade at comcast.net Tue Mar 2 13:53:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> Re: PWG-ANNOUNCE> UPDF last call References: <009a01c4007f$32de69e0$6501a8c0@ne1.client2.attbi.com> <4044D346.9040309@easysw.com> Message-ID: <010001c40087$a82b2000$6501a8c0@ne1.client2.attbi.com> Michael, I answer publically to the UPDF reflector. When I go to the PWG and follow the Archives link, then select UPD, it shows all emails including the ones of the last days. Yes, the current spec doc shows version 0.98. so far I thought that the document will be called version 1.0, once it is formally approved. So I can assign proper version numbers (below 1.0) to the changes required the next couple of weeks. if that's a misinterpretation from my side, please educate me. Norbert ----- Original Message ----- From: "Michael Sweet" To: "Norbert Schade" Sent: Tuesday, March 02, 2004 1:32 PM Subject: Re: PWG-ANNOUNCE> UPDF last call > Norbert Schade wrote: > > > > We have started a last call for UPDF, version 1.0. yesterday. > > It will last for the next three weeks and end on Friday, March 19th, > > 10pm EST. > > Well, since the mailing list archive (or at least the link) only > goes to 2001, and the current spec on the UPDF web site is v0.98, > what document are we supposed to be reviewing??? > > -- > ______________________________________________________________________ > Michael Sweet, Easy Software Products mike at easysw dot com > Printing Software for UNIX http://www.easysw.com From norbertschade at comcast.net Tue Mar 2 15:48:41 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> Re: PWG-ANNOUNCE> UPDF last call References: <009a01c4007f$32de69e0$6501a8c0@ne1.client2.attbi.com> <4044D346.9040309@easysw.com> <010001c40087$a82b2000$6501a8c0@ne1.client2.attbi.com> <4044DA3D.7020507@easysw.com> Message-ID: <004b01c40097$bf3faee0$6501a8c0@ne1.client2.attbi.com> Since I've seen the UPDF web site the first time many years ago, this link referred to a special part of the ftp site for UPDF related files. It linked to old versions and designs. Of course, I could change that. And I did. It now links to the UPD email archive. Regards Norbert Michael Sweet wrote: > OK, the archive link on the UPDF page is wrong, then. From norbertschade at comcast.net Wed Mar 3 09:57:50 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF last call: configuration files Message-ID: <001d01c4012f$e669ca80$6501a8c0@ne1.client2.attbi.com> The schedule says: On Wednesday, March 3rd, we will concentrate on the configuration files. - Device Configuration: The driver entry point into the UPDF world and the environment for the base unit. - Option Configuration: The environment for optional units. This is covered on pages 22 - 27. But it's worth thinking about it from different angles. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040303/a79a6465/attachment-0001.html From norbertschade at comcast.net Wed Mar 3 11:50:59 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> configuration implementation Message-ID: <000e01c4013f$b95465e0$6501a8c0@ne1.client2.attbi.com> While studying the architecture of the configuration files, you may think of various ways to implement the concept into an installation process. Some possible scenarios: 1. CD installation, device configuration instance on CD 1.1. the traditional way all files are on the CD. the references to instance names are pure file names, no path included. 1.2. web site reference all files are on the CD, but only get used as a fallback. the references to instance names are URLs. depending on the installer the URLs are used automatically or as default (install from CD as second choice). keep in mind that the option configuration references can point to completely different web sites from third-party developers. 2. network installation not too much different from the two CD methods. 3. Device installation, device configuration instance in device it is not necessary to store more than this single instance in the device. all other files could be pulled from web sites or as a fallback from CD. this allows for a driver independent installer. imagine the operating system has a generic UPDF driver installed already (and if not, it knows where to find at least one), it could pull the single device configuration file from the device and would find all other information in there. I see various combinations of the different methods. keep in mind that any option configuration stays separate, even after installation, and can therefore be disconnected or updated at any time without hurting the installation of the base unit and any other optional unit. These scenarios are not described in the specification document. just some personal ideas. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040303/e33724df/attachment-0001.html From norbertschade at comcast.net Thu Mar 4 07:07:47 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF last call, day 4 Message-ID: <000d01c401e1$4ee4bfa0$6501a8c0@ne1.client2.attbi.com> The schedule: - On Thursday, March 4th, we will concentrate on the DeviceHeader and the Header under PrintCapabilities. One of the interesting elements here are the connectors, which carry on the information of the configuration files. Connectors tell, which connectors a device unit (base or optional) can offer to other units and connectors a special optional unit can connect on other device units. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040304/606e23af/attachment-0001.html From norbertschade at comcast.net Fri Mar 5 08:08:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF last call, day 5 Message-ID: <001901c402b2$f59da4c0$6501a8c0@ne1.client2.attbi.com> The schedule: - On Friday, March 5th, we will concentrate on all predefined features. A lot of pages, but similar information per feature. This is certainly the more tangible information. Check the samples and it will come to life. Regards Norbert Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040305/fb8cb974/attachment-0002.html From norbertschade at comcast.net Fri Mar 5 08:17:07 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> Manual duplex Message-ID: <002301c402b4$2917a200$6501a8c0@ne1.client2.attbi.com> This is a personal statement and demonstrates one view of how to use the information stored in a UPDF device description. Larger picture I see manual duplex as part of some functionality I call 'Paper Path Preview'. This includes information to the end user on how to insert print media properly into the tray (face-up/down, leading edge), what will happen to the media in the device (flipped once or twice in a duplex unit) and how the output bin will influence the path and the final face. Manual duplex is just a very special case of using that information twice. Target module for implementation 1. priority: Spooler The number of conditions due to special behavior of input trays, output bins and other factors is finite. As a matter of fact, it's not overwhelming. A generic solution is the target. That would mean a device description like the one in UPDF does not provide dialog information for manual duplex. However it provides the proper attributes for the path the print media takes. This is implemented in UPDF (I don't know of any other concept). Check the attributes in features MediaInputTrayCheck, OutputBin, and Sides. 2. priority: Driver The driver may jump in as a substitute, if the spooler is not capable. This may be operating system specific. Features involved (from a UPDF point of view) - feed orientation: saved with the media size feature - page orientation: saved with the OrientationRequested feature - long-edge/short-edge: saved with the Sides feature - there is an extra attribute telling about flipping - face-up/down (input): saved with the input tray - media flipped in output bin: saved with the output bin - input trays available for the second path of manual duplex: this can easily be covered by dependencies - output bins available for manual duplex: this can easily be covered by dependencies One special implementation sample 1. Device settings of a pretty popular sample device - input tray: short-edge first, face-up, landscape is 90 degrees anti-clockwise - output tray: top, media gets flipped once 2. Implementation in spooler The spooler/driver has a number of text modules (in this simple sample we do not think about animated pictures). For this sample the page orientation does not affect the functionality. We can ignore it. 2.1. short-edge Text module: something like 'remove the print medium from the output tray and insert it without turning nor flipping.' 2.2. long-edge Text module: something like 'remove the print medium from the output tray and insert it while turning it 180 degrees without flipping.' I know the sample is simplistic, but that's about it. the rest would be cosmetic. Some details about the special device description (as I would do it) - of course, fill out all paper path related attributes in the description - filter out input trays you don't want to be available for manual duplex - filter out output bins you don't want to be available for manual duplex You know of any other concept providing the necessary information without a huge and dedicated function call? Tell me! This is a true data driven approach. I think when you see the UPDF paper path attributes, they are almost self-explaining. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040305/a40a6428/attachment-0001.html From norbertschade at comcast.net Fri Mar 5 08:08:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF last call, day 5 Message-ID: <001901c402b2$f59da4c0$6501a8c0@ne1.client2.attbi.com> The schedule: - On Friday, March 5th, we will concentrate on all predefined features. A lot of pages, but similar information per feature. This is certainly the more tangible information. Check the samples and it will come to life. Regards Norbert Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040305/fb8cb974/attachment-0003.html From norbertschade at comcast.net Mon Mar 8 07:43:15 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> paper path attributes Message-ID: <000f01c4050a$ecebba60$6501a8c0@ne1.client2.attbi.com> Latest changes: 1. I have added a DeviceFeature (default = false) attribute to the Sides feature to allow the specification of manual duplex. 2. I have removed the Physical element under PrintCapabilities.Header, as it did not carry any extra information. Now the Engine element is located directly under the Header element. 3. I have added an attribute FacePrinted (default = Face-up) to the Engine element. So far we implicitely assumed that the engine prints on top of the media. That is certainly true for most of the devices. But we want to tell explicitely how it's done to provide accurate information about the paper path and allow a driver to extract all parameters needed to recommend a special media insert method in a user interface (e.g. "please insert the paper face-up"). I'm open with the name of the attribute. The corresponding files will be copied to the UPDF web site during the day. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040308/7f1a8ebc/attachment-0001.html From norbertschade at comcast.net Mon Mar 8 07:50:08 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF last call, day 6 Message-ID: <001c01c4050b$e31ca160$6501a8c0@ne1.client2.attbi.com> The schedule: - 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. >From a UPDF point of view composite features are certainly a key feature of the concept. A composite feature does not define a new technical feature. It defines a new feature by assembling specific settings of other features to a higher level feature. UPDF does not show wildcards with the Features element. Generic features are the way you can add a new feature to the device description. This way we can assure that the new feature follows the standard description method of all features (has an ID attribute, etc.). You can define generic features for variable as well as for enumerated values. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040308/7b3e818d/attachment-0001.html From norbertschade at comcast.net Mon Mar 8 16:01:52 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> another manual duplex detail Message-ID: <001e01c40550$9574d140$6501a8c0@ne1.client2.attbi.com> I still wonder, if we are providing enough information on manual duplex to fully support it. we certainly tell about flipping in input and output trays and I think all needed information for the page order can be pulled out of that. sample: I think a driver should understand that the page order is fine for all pages, when it learns that the media gets flipped in the output tray. but in other cases it may have to send odd and/or even pages in reverse order. conclusion: no additional info needed here. however I think we should add an event 'HalfDocument', which indicates that 50% of all physical pages of a document have been sent. I've added that event to the data type. additionally we need an element in the Sides feature indicating that some kind of user action is needed at halftime. in the description we do not care which action. this attribute would tell the driver that the device is able to help with manual duplex, but needs info about the halftime. now the driver knows it has to prerender the pages, find out halftime and be prepared to find an event 'HalfDocument'. theoretically we could have the driver check all events and learn about the 'HalfDocument' by itself. not sure the driver wants to do that. it is likely expecting that input being available easily. it is still necessary to declare the Sides feature not a device feature, as there is likely some functionality necessary like a special page order. I've added a boolean attribute 'HalfDocumentNotification' to the Sides feature with default = false. without the attribute (or if set to false) the driver is supposed to take over full responsibility for the feature including a halftime dialog. out of scope: we are not dealing with the case of a bi-directional message being sent to the host in UPDF, version 1.0 Comments??? Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040308/0c111db0/attachment-0001.html From norbertschade at comcast.net Mon Mar 8 21:35:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> file update 08/03/04 Message-ID: <001201c4057f$316e1560$6501a8c0@ne1.client2.attbi.com> I've updated the specification document as well as the UPDF and UPDFDataTypes schema. The URLs are the same as always and listed below. To access the spec directly use ftp://ftp.pwg.org/pub/pwg/www/updf/UPDFFunctionalSpecification.pdf While I think the additional enumeration value 'HalfDocument' in the events is necessary we can still discuss the extra attribute 'HalfDocumentNotification' in the Sides feature. I've added it for demontration. Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: UPDF reflector Sent: Wednesday, February 18, 2004 3:21 PM Subject: UPD> update UPDF web site I just finished some editing on the UPDF web sites. We now have a directory structure more closely related to other PWG standards. To get to the UPDF web site: http://www.pwg.org/updf/ Following the links on the page you will get to the official version of files like the pdf version of the specification. To check UPDF related files in general: ftp://ftp.pwg.org/pub/pwg/upd/ This is the top directory for all UPDF related files. As we are preparing a last call, we have created a 'wd' (working draft) directory: ftp://ftp.pwg.org/pub/pwg/upd/wd/ This directory will hold all files related to level 1.0, which is work in progress. a.. This includes a specification document (in WinWord format). This document is considered 'under review', while the official pdf version under http://www.pwg.org/updf/ is the latest public version. The doc file could be slightly newer sometimes and vary in some aspects, if reviewed at that time. b.. It further includes the current schemas in subdirectory 'schemas'. c.. It further includes sample instances, if available in subdirectory 'instances'. Please keep this email at least for the next four weeks to have some reference for pathes. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040308/f087b1b1/attachment-0001.html From norbertschade at comcast.net Tue Mar 9 09:45:10 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF last call, day 7 Message-ID: <001301c405e5$22370fa0$6501a8c0@ne1.client2.attbi.com> The schedule: - On Tuesday, March 9th, we may concentrate on Objects (raster graphic, device fonts). 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. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040309/9c950688/attachment-0001.html From norbertschade at comcast.net Wed Mar 10 09:09:36 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF last call, day 8 Message-ID: <001101c406a9$5221c100$6501a8c0@ne1.client2.attbi.com> the schedule: - On Wednesday, March 10th, we'll finish the unit description with the dependencies and events. We consider the UPDF dependencies unique due to their compact and powerful format. There's exactly one dependency defined for one set of features involved. Sample: (if (duplex=long-edge) and (media size=letter)) is the condition. you can still define two different actions on it depending on which feature has the focus (in UPDF that is dominant). In the events you can define the assembly of the print file to some degree. certainly this is the place to correctly position all the command sequences and parameters. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040310/9245c75a/attachment-0001.html From norbertschade at comcast.net Thu Mar 11 12:40:20 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF last call, day 9 Message-ID: <001901c4078f$ed17e360$6501a8c0@ne1.client2.attbi.com> the schedule: - On Thursday, March 11th, we could talk about the command sequences, and the Parameter Converter, as these two issues are closely related to events. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040311/343c0527/attachment-0001.html From norbertschade at comcast.net Fri Mar 12 09:18:26 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:19 2009 Subject: UPD> UPDF last call, day 10 Message-ID: <003801c4083c$e2d9c8c0$6501a8c0@ne1.client2.attbi.com> Following the original idea of a two weeks schedule this is the last day of ten in a row dedicated to a certain subject. The idea was that everybody could check the whole specification in sections. so we split it up into ten pieces. Today's subjects are locales and user policies. In the spec that's mainly covered on pages 138 - 144. The next week is still part of the last call, but is not dedicated to specific issues. of course, you could still send in any request for clarification or change. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040312/b9d0c3b5/attachment-0001.html From norbertschade at comcast.net Fri Mar 12 10:25:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:20 2009 Subject: UPD> UPDF last call, end of week 2 Message-ID: <000d01c40846$42d1dfc0$6501a8c0@ne1.client2.attbi.com> We have finished week 2 of the UPDF last call. Latest changes: I removed the attribute 'HalfDocumentNotification' again from the Sides feature, while the additional event 'HalfDocument' stays. Otherwise it would create chances for ambiguity, as somebody could use the event, but would not set the attribute in the Sides feature. So the driver has to check, if the event 'HalfDocuent' is used. Comments??? I will post the latest files tonight with version 0.99.0.0 of the spec. We do not have any open issue concerning any of the elements or attributes. If there will not be any changes requests of any type, the version will simply change to 1.0.0.0 at the end of the last call. Please step forward now, if you have any concern with the spec or the schemas or you need clarification on any issue may it be by email or by telecon. I will post another message to the PWG-Announce on that issue. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040312/c42af0f1/attachment-0001.html From norbertschade at comcast.net Mon Mar 22 08:41:37 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:20 2009 Subject: UPD> UPDF last call Message-ID: <001b01c41013$6693c5c0$6501a8c0@ne1.client2.attbi.com> Following the latest procedure of the PWG process a last call is supposed to run at least 16 work days and has to be closed at a f2f meeting. We fulfill the 16 days period today. Harry Lewis reserved a three hour spot for UPDF on Wednesday, 21st April, in Washington. We will briefly represent the concept, the development over time and issues raised during last call. Then it will be decided on open items. With no open items the last call can be closed. Although this PWG process is not binding yet, we want to follow the spirit of it. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040322/92bd2a94/attachment-0001.html From norbertschade at comcast.net Mon Mar 22 17:47:24 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:20 2009 Subject: UPD> UPDFVersion Message-ID: <001401c4105f$a54ad960$6501a8c0@ne1.client2.attbi.com> the question came up, if this element should stay in the device description or be moved to the device configuration (and then converted to an attibute). my proposal is to move it so that the information is available at the UPDF entry point. comments??? Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040322/a5d0ea00/attachment-0001.html From norbertschade at comcast.net Mon Mar 22 18:25:54 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:20 2009 Subject: UPD> Driver info Message-ID: <001d01c41065$05aa3a80$6501a8c0@ne1.client2.attbi.com> 1. we had a mistake in the AdditionalDriverComponent. it was of type xsd:string, although we had the right type updf:AdditionalDriverComponent available. we just didn't refer to it. 2. info about UPDF drivers. the proposal is to replace the element AdditionalDriverComponent with a more complex element Driver. 2.1. it would have an optional (but recommended) attribute ID. this would work as an identifier of the driver. an installer could check, if the corresponding driver is already installed. it is questionable, whether the UnitName attribute in the master UPDF schema serves that purpose already. my understanding is 'no', as a company may develop a corporate UPDF driver or one may want to refer to a specific driver independent from the device description info. 2.2. it would have an optional (but recommended) attribute Reference. this is a string attribute holding a URL or a simple file name. if it is a file name, it is supposed to live in the same directory as the device configuration. if the device configuration came from the device as the only file and the attribute is still just a file name, the installer may ask for a path more or less expecting a CD drive. 2.3. it would have optional, multiple elements OperatingSystem. if no operating system is listed, the installer is supposed to know where to find a proper default UPDF driver. 2.4. it would have optional, multiple elements Component. This is the previous AdditionalDriverComponent. it the driver is a MS Windows driver with an inf included and the UPDF device description as the data format, this is likely redundant. however if the device configuration is the only file living in the device and the driver can be any generic UPDF, this is the chance to add a library or something else to that generic driver. Comments??? Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040322/c586ae8f/attachment-0001.html From Jim.Sommer at AgfaMonotype.com Thu Mar 25 16:40:36 2004 From: Jim.Sommer at AgfaMonotype.com (Sommer, Jim) Date: Wed May 6 14:05:20 2009 Subject: UPD> File Comments and Version Message-ID: <5E9049856A307A46B100DBBB371A9D9268654D@amt_exchange.agfamonotype.org> I would like to see a formal place for a UPDF author to add version information and any other comments at the beginning of each instance. I know they can just add XML comments, but I think it would be nice to have a defined place that can be accessed with any XML editor. We have the DescriptionInfo in the device description but this is supposed to be used for overall version and copyright information that is displayed in an "About" box. In the DeviceHeader we have DescriptionVersion and DescriptionComment. These are good but are unfortunately only in the device description file. I think we sould remove the DescriptionVersion and DescriptionComment from the DeviceHeader and add to all schemas a FileInfo element with version and comment fields. This will allow all instances to be properly versioned and commented by developers. Jim mailto:Jim.Sommer@AgfaMonotype.com 978-486-3068 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040325/5b17be8e/attachment-0001.html From norbertschade at comcast.net Tue Mar 30 16:44:11 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:20 2009 Subject: UPD> version declarations and UPDF driver info Message-ID: <001a01c416a0$23dd4a60$6501a8c0@ne1.client2.attbi.com> I have implemented the latest changes related to UPDF version in the device configuration, file versions in all instances and driver info in the device configuration as explained the last days. the spec has been updated as well and got version 0.99.1.0. the spec has also been edited in a way that all changes made during last call are highlighted in red by now. Please follow the URLs below or use the links on the UPDF web site. Regards Norbert Schade ----- Original Message ----- From: Norbert Schade To: PWG-Announce@pwg.org Sent: Tuesday, March 02, 2004 8:46 PM Subject: PWG-ANNOUNCE> UPDF files and URLs The UPDF web site: http://www.pwg.org/updf/ Following the links on the page you will get to the official version of files like the pdf version of the specification. URL: ftp://ftp.pwg.org/pub/pwg/www/updf/UPDFFunctionalSpecification.pdf The current version of the spec is 0.98 and will proceed to 1.0 during this last call, while we will resolve any remaining issues. To check UPDF related files in general: ftp://ftp.pwg.org/pub/pwg/upd/ This is the top directory for all UPDF related files. We have created a 'wd' (working draft) directory: ftp://ftp.pwg.org/pub/pwg/upd/wd/ This directory holds all files related to level 1.0, which is work in progress. a.. This includes the latest specification document (in WinWord format). This document is considered 'under review', while the official pdf version under http://www.pwg.org/updf/ is the latest public version. The doc file could be slightly newer sometimes and vary in some aspects, if reviewed at that time. b.. It further includes the current schemas in subdirectory 'schemas'. URL: ftp://ftp.pwg.org/pub/pwg/upd/wd/schemas c.. It further includes sample instances, if available in subdirectory 'instances'. URL: ftp://ftp.pwg.org/pub/pwg/upd/wd/instances/NorbertSchade01/ Please keep this email for the next weeks to have some reference for pathes. Regards Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040330/8aa61638/attachment-0001.html From harryl at us.ibm.com Wed Apr 21 10:57:37 2004 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:05:20 2009 Subject: UPD> Slides for UPDF Last Call - Washington D.C. Message-ID: ftp://ftp.pwg.org/pub/pwg/upd/wd/UPDF%20Last%20Call.ppt ---------------------------------------------- Harry Lewis Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040421/197bc6bd/attachment-0001.html From harryl at us.ibm.com Wed Apr 21 10:57:37 2004 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:05:20 2009 Subject: UPD> Phone is up in D.C. Message-ID: OK... the phone is up. Hope it stays up. 10:55am EDT. ---------------------------------------------- Harry Lewis Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040421/07503c2c/attachment-0001.html From harryl at us.ibm.com Wed Apr 21 10:57:37 2004 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:05:20 2009 Subject: UPD> Phone line in Washington D.C. Message-ID: We are having extreme difficulty with the phone conference line at the hotel. It is doubtful we will be able to have our conferences today, at all. Stay tuned to the PWG reflector (only) for announcement if and when we get the phone going. ---------------------------------------------- Harry Lewis Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040421/bbeb7ad4/attachment-0001.html From norbertschade at comcast.net Sun May 2 22:34:31 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:20 2009 Subject: UPD> last call finished Message-ID: <00bc01c430b7$2a59e7a0$6501a8c0@ne1.client2.attbi.com> we have fulfilled all requirements for last call. the spec is updated as version 1.0. all schemas and sample instances are on the latest level. I have agreed with Jerry Thrasher that we have done everything to prepare the formal vote. that is the happy ending of a long series of contributions to an effort to bring something up to ease the specification of printer driver input. the technical assembly of the right format is one thing, of course. And the political approval is another. So we'll wait for the next step and see how the PWG members will judge. I thank everybody for their interest, comments, technical feedback and any other kind of contribution to the UPDF effort. For me it has been a great learning curve so far. And we still have some way to go! Hope we'll get through the vote shining. may partly depend on you. cheers Norbert Schade Norbert Schade 69 Prescott Drive North Chelmsford MA 01863 phone: 1-978-251-1017 email: norbertschade@comcast.net -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040502/767b2b10/attachment-0001.html From harryl at us.ibm.com Wed Jun 2 12:59:23 2004 From: harryl at us.ibm.com (Harry Lewis) Date: Wed May 6 14:05:20 2009 Subject: UPD> Fw: PWG-ANNOUNCE> PWG ANNOUNCE> PWG Formal Vote Results for UPDF 1.0 Message-ID: UPDF team... first, congratulations on UPDF passing. I believe it is your team's responsibility, now, to address the comments received. As there was STRONG OBJECTION, which, upon review, is substantive in terms of effecting actual adoption, I urge the UPDF team to make a concerted effort to produce the requested improvements. I know you worked long and hard to get UPDF across the goal line. The objection received does not appear to be from someone who disagrees with the specification, rather someone who is looking for guidance that will encourage adoption. It does not good for the PWG to pass standards that will not (or cannot readily) be adopted. Hope your team will meet this challenge! ---------------------------------------------- Harry Lewis Chairman - IEEE-ISTO Printer Working Group http://www.pwg.org IBM Printing Systems http://www.ibm.com/printers 303-924-5337 ---------------------------------------------- ----- Forwarded by Harry Lewis/Boulder/IBM on 06/02/2004 10:52 AM ----- thrasher@lexmark.com Sent by: owner-pwg-announce@pwg.org 06/02/2004 07:35 AM To pwg-announce@pwg.org cc Subject PWG-ANNOUNCE> PWG ANNOUNCE> PWG Formal Vote Results for UPDF 1.0 The results of the recently completed PWG Formal Vote for the UPDF 1.0 Specification are as follows: Vote Count: Yes: 8 No: 1 (with strong objection) Abstain: 2 PWG Process Document Criteria: 1. Met the 25 percent participation (needed at least 9 votes). 2. Met the 80 percent approval requirement from the No w/ strong objection. 3. Met the 50 percent of votes either yes or no....(needed at least 5) UPDF Formal Vote passes. Note: There was one additioinal Yes vote that was received after the voting period closed. By the guidelines in the PWG Process Document (both old and new draft), comments submitted with a No vote (or No with strong objection) are to be posted and discussed on the PWG Announce email list...... Here are the comments: 1. The specification does not include examples for each element, nor does it tie each schema together to show a complete implementation. See the (many) W3C specifications for XML and/or SGML-based formats which *do* include examples. 2. I do not see a single complete sample file for any printer device. I see a lot of fragments made by Norbert, but I don't see a complete file that could be used as reference against the spec or schema files that shows the current specification is useful or feasible for a driver, application, or UI component to use. 3. The separation of schemas is confusing and leads me to believe that a single device description is composed of multiple XML files. Given the limited sample fragments on the PWG FTP server, it is not clear what the actual organization is supposed to be. THIS NEEDS TO BE DEFINED in order to allow for actual interoperability and network transparency. 4. My general impression is that the current specification is not complete enough to be used in an actual printing environment nor does it provide any advantages over existing interfaces and formats. Of what use is a new format if it only does what every other format does? I will send a separate not when the 51xx.n number is assigned and is published as a candidate standard. Jerry Thrasher PWG Secretary -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040602/1d1c03e0/attachment-0001.html From norbertschade at comcast.net Fri Jun 11 08:09:47 2004 From: norbertschade at comcast.net (Norbert Schade) Date: Wed May 6 14:05:20 2009 Subject: UPD> Fw: different ways to use the UPDF instances, Q&A attached Message-ID: <000a01c44fac$fdef3ca0$6501a8c0@ne1.client2.attbi.com> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: Q&A.doc Type: application/msword Size: 31232 bytes Desc: not available Url : http://www.pwg.org/archives/upd/attachments/20040611/451b99c2/QA-0001.doc From schade at oasissemi.com Fri Jun 25 09:59:20 2004 From: schade at oasissemi.com (Norbert Schade) Date: Wed May 6 14:05:20 2009 Subject: UPD> Oasis communicates XML resources Message-ID: <000001c45abc$a02928e0$ab00a8c0@oasis> My company, OASIS SEMICONDUCTOR, has decided on communicating all text resources for host software development by XML resources with all their customers. The resources are considered as part of the host software specifications. This provides for a number of advantages: 1. all strings are based on Unicode. 2. all strings can be defined in clean lists and not as part of a word processing document. 3. all strings can be maintained outside source code. 4. standard XML tools and applications can be used to read, write and edit the strings. 5. all strings needed as input for printer drivers are based on the UPDF Locale schema. Where other schemas are needed, they follow the same architecture. And last not least it prepares us for the next steps we have in mind. Regards, Norbert Schade Norbert Schade Software Manager Oasis Semiconductor, Inc. 201 Jones Road Waltham, MA 02451 USA tel. 1-781-370-8929 fax. 1-781-370-8990 email: norbert.schade@oasissemi.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.pwg.org/archives/upd/attachments/20040625/19a0c5e8/attachment-0001.html