attachment

<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>  <style>  </style> </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Hi everybody,<o:p></o:p> I wonder who is still on the reflector.<o:p></o:p> Thought i’d share some news on the use of UPDF.<o:p></o:p> <o:p> </o:p> Some of you may remember that i joined Oasis Semiconductor in 2004 (BTW: Oasis has been acquired by SigmaTel in September 2005. but our host software department was not affected too much).<o:p></o:p> <o:p> </o:p> Pretty soon after i joined the group we decided that the set of UPDF schemas could help us well in some areas.<o:p></o:p> We started using it as part of our specifications to avoid ambiguous descriptions of driver features and according parameters. That proved to be very reliable and we are still doing it today.<o:p></o:p> <o:p> </o:p> A bit later we thought about using the same xml instances we already got due to the specifications in the real drivers.<o:p></o:p> Ok, a larger effort.<o:p></o:p> And we needed some time.<o:p></o:p> Guess what? We have it working.<o:p></o:p> We are making extensive use of the PWG schemas with focus on the UPDF schemas in our print and fax drivers. Even in our scanner drivers we use the string handling as designed in UPDF.<o:p></o:p> If anybody wants to know further details, i’d be quite open to talk it over.<o:p></o:p> <o:p> </o:p> Just to mention two cute issues we now love to have:<o:p></o:p> <![if !supportLists]>-          <![endif]>string handling we can change any string in any of our xml locale instances and immediately validate it in the corresponding UI – without re-compilation. So we can easily simulate a translator’s job at the customer’s site. No translator has to deal with C code or header files. Any common XML editor will do. Even standard text editors are ok (however i would not recommend them, as i love the validation feature of the xml editors).<o:p></o:p> <![if !supportLists]>-          <![endif]>Device description it’s convenient to add another media size record to the xml based device description or just change its values and see it used. I can even do that after installation. The biggest advantage is that we can easily agree on unambiguous parameters with customers. They don’t have to understand any source code to see how it’s used.<o:p></o:p> I like it. Ok, may be that’s not too much of a surprise.<o:p></o:p> <o:p> </o:p> As a side effect we could prove that all schemas are perfectly usable for driver development – with one little exception. And it’s certainly not the typical day-by-day use.<o:p></o:p> But i will explain that in a separate email in a minute.<o:p></o:p> Other than that everything is just fine.<o:p></o:p> Our drivers have passed a number of QA cycles in the last half year. So we are confident we have thoroughly investigated all circumstances.<o:p></o:p> we have drivers now based on the Semantic Model and the UPDF schemas under Windows platforms starting from 98SE up to XP.<o:p></o:p> And if at any time we would face an operating system that makes a more intense use of xml to describe device capabilities, i wonder, if i could actually enjoy that. what platform could that be :>)))<o:p></o:p> <o:p> </o:p> Just thought this might be of interest to the group.<o:p></o:p> Regards<o:p></o:p> <st1:PersonName w:st="on">Norbert Schade</st1:PersonName><o:p></o:p> <o:p> </o:p> <o:p> </o:p> <st1:PersonName w:st="on">Norbert Schade</st1:PersonName> Host Software Manager SigmaTel, Inc. 201 Jones Road Waltham, MA 02451 USA tel. 1-781-370-8929 fax. 1-781-370-8990 email:<a href="mailto:norbert.schade@sigmatel.com" title="mailto:norbert.schade@oasissemi.com">norbert.schade@sigmatel.com</a><o:p></o:p> This email message and any attachments are confidential, proprietary, and may be privileged. If you are not the intended recipient, please notify Oasis Semiconductor, Inc. immediately -- by replying to this message and/or calling 781-370-8989 -- and immediately destroy all copies of this message and any attachments. Furthermore, you are hereby notified that any copying, disclosure, dissemination, or distribution of this email communication is strictly prohibited. Thank you.<o:p></o:p> <o:p> </o:p> </div> </body> </html>