<div id="RTEContent">01/18/06 Accessibility meeting <br><br>Gunnar Schmidt<br>Olaf Schmidt<br>Bill Haneman<br>Janina Sajka<br>John Goldthwaite<br>Doug Beattie<br>Earl Johnson<br>Peter Korn <br><br>Janina is having computer problems so no agenda for today. The minutes from the prior meeting were just distributed prior to the meeting so weíll hold them for review and approval next week.<br><br>Janina called several studios. Some were as low as $35 but most were 75 to more than a $100. So with domain knowledge, $100 is easily justified. We approved Janinaís invoiced amount at $100 per hour.<br><br>Topics for today- Sign on to KDE open desktop initiative. Finish Keyboard. AT-API. <br> <br>Peter- ODF meeting was scheduled for next week but has been postponed. With change in administration, the tenor of meeting is changing.
<br>Janina- any follow up on the RFC?<br>Earl- no new comments. I authored a reminder email and sent it to Janina for review.<br>Peter- Did we send it to any of the MacIntosh accessibility lists? - should send to Mac visionary, technical lists - <br>Peter will send message to these lists.<br>Earl- will send out reminders this weekend. Weíre getting close to the end of the comment period, less than 2 weeks.<br><br>Janina- is there objection to signing on to the open desktop letter? No objection, so Accessibility has signed on to the letter. <br>Olaf- I will let Aaron know.<br><br>Janina- Missing some key people to continue the discussion from last week on balancing what we can achieve on AT-SPI vs. completion of the keyboard spec as George was outlining. <br>Earl- The plan was to wait until after comment period and work with Bill to get raw content. Then Iíll edit it into XKB spec. Iíll talk with Bill about a schedule. Bill and Earl will work
on details offline.<br>Olaf- talking about the XKB ABI and the test case for that, the functionality described in the spec is more than xkb by itself. You need XKB to implement that but it is only a small part of what is demanded in specification. So why would the testing be at the XKB layer? Is it easier to test? The keyboard spec describes a lot of functionality which is not provided by XKB itself.<br>Bill- two aspects to the specification- functional spec which we have created and the ABI spec. which is independent.<br><br>Olaf- so the ABI would be used by those who would implement the specification?<br>Bill- No neccessarily, The ABI is there not just for those who implement; if the spec is implemented by the platform, it doesnít matter how it is implemented, though you are correct in saying its 99% chance it is implemented using the ABI. It is there so that other clients such as assistive technologies at are independent of the Access X
functional spec, can rely on the ABI being there. For example an on-screen keyboard can get sticky keys and get notifications, etc. They are related but the relationship is implied, the could be satisfied independently.<br>Olaf- Okay, also need to see how applications using the API interact with the desktop environment. If you start GOK on KDE, it will turn on sticky keys and set Gnome settings. Then if someone goes to the KDE settings, Iím not sure they get the correct information.<br>Bill- I think they do, the way GOK is written, if the Gnome settings are not available, Gok will interact with sticky keys directly.<br>Olaf- depends on how the KDE code is implemented, it needs to detect that there is a change.<br>Bill- if it is the only agent that interacts with XKB, then that is correct. Your desktop environment has to be listening to XKB notifications as well as directly calling XKB.<br>Olaf- what if there are several applications, each insisting on their own XKB
settings.<br>Bill- right, that isnít something we need to directly specify, just make an implementation note- clients shouldnít assume they are the only application running. That is a universal software problem.<br>Olaf- describing the functionality only has the advantage that, for example, MacIntosh could support the spec. So the test cases for XKB are an optimal path for using X using..<br>Bill- I disagree, why would XKB prevent MacIntosh from complying? <br>Olaf- is the XKB ABI tied to X?<br>Bill- yes, but MacIntosh uses X server. <br>Olaf- Okay, I didnít know that, say why wouldnít Microsoft support the spec?<br>Bill- Microsoft canít support LSB unless they provide a bunch of libraries<br>Olaf- they might want to support the accessibility specification.<br>Bill- XKB client ABI could in theory could be implemented by whatever Window calls display environment. Do think it will happen anytime soon, but no reason<br>Olaf- okay, letís say imbedded Linux
or any system that doesnít have X. What we could do is specify the XKB compliance. If you are using X to implement this, then you need to<br>Bill- I think we could do to say- if they have a keyboard<br>Earl- If Windows want to support the spec., they are going to be required to include XKB on the platform to make the spec? It that case it (doesnít?) makes sense to include XKB if it is meeting the functional specs in a different way.<br>Bill- I disagree, Windows has to support any ABI component we are specifying as part of LSB. But Windows doesnít support any of LSB, so what difference does it make. The History of LSB has been about entirely about ABI compliance. This ABI portion of the spec is entirely consistent with what FSG and LSB have always done. The Functional spec is what is abnormal and may meet with resistance. The ABI is what they require as part of any spec.<br>Olaf- If, for example, you have a Linux PDA using tutopia or whatever, does the LSB spec say
you need to have an X server?<br>Bill- you need to have a client library that conforms to an ABI<br>Olaf- which is the X ABI<br>Bill-no, the XKB ABI<br>Gunnar- which is a small part of X ABI<br>Bill- but we are talking about the client ABI, being a layered client/server architecture X has a number of ABIís. It has a protocol ABI, etc., we wonít be specifying protocol. Weíre just saying there will be client binding that look like this. The underlying protocol could be something other than the official X protocol or it could be tinyX or imbedded X, it could be some other frame buffer port. <br>The purpose of ABI specs, my understanding is that the ABI spec is to provide assurance to the application that it will able to dynamically link and run on a conformant platform. So a binary Linux executable for an assistive technology that uses XKB, can drop code in and it will run. Doesnít mean there has to be a complete Xserver, has to look as
if there is an Xserver from the point of view of application. Has to see libc and core libraries, must be present and functional. Can I write an application for the platform; will it run?<br><br>Olaf- I totally agree, apps that wish to run of system if spec, need to know what function calls to use, etc. Only question is current keyboard access spec doesnít address this aspect of applications at all. It says which functionality must be provided to the user of the desktop. It would possible to split this into two parts, the part for the application and the part for the user. For our conformance test, we need to tests of both. It might be possible to pick out the functional part, the ABI doesnít make sense because you have a completely different system anyway. If it is too much hassle to divide into parts, then its possible to provide such an ABI on Imbedded Linux without bringing in all kind of X stuff then thatís not an important thing more me.<br>Doug - the LSB was set
up to be modular. They have base specs, but have others for desktop and imbedded. That will vary based on what they can provide. We can have a Base spec of our own and additional modular ones based on other things being there from LSB.<br>Olaf- this is why I asked, there is a LSB spec for Imbedded Linux isnít there?<br>Doug- base spec. is there. It has been designed since 2.0 to be modular so that other things can be added, or in the case of imbedded device have things taken from it. It will grow over time, it is a living document that allows modularity. <br>Olaf- are there any X ABIís specified for the Imbedded version?<br>Doug- Iím not sure on the Imbedded, on core piece the ABI is there for the server. For desktop, other pieces are added.<br>Olaf- Isnít the core used for everything? <br>Doug- the core is there for the sever, for desktop there are other little piece that get added on.<br>Olaf- if there already some X ABIís in the core, then wouldnít
change so much to add a few of the. On other had, I donít know if need X ABI on the server.<br>Doug- Iíll find the link to the X libís that are in the core so that you can take a look at them. <br><br>Janina- So Earl, is the decision that we are going ahead with the ABI spec?<br>Earl- You mean the ABI? I think so but we need to be sensitive to the right way to present it. <br>Olaf- I have no objection to going forward with that. We just need to see what we need for server, desktop and imbedded and whether in needs to be modular or one big piece.<br>Earl- So, will proceed as planned with an eye toward addressing that issue.<br>Janina- any sense of how long it will take?<br>Earl- no. <br><br>Janina- The other agenda for the year is AT-SPI, that is the other reason to talk about when a face-to-face might be most useful. We had suggested to meet in July at the developer forum in Ottawa. Developers conference is Monday, July 17 and 18 so we would go a couple
of days before or after it. <br>Bill- that time is possible for me.<br>Peter- should be reasonable for me also. July sounds like it is a good candidate.<br>Janina- Good, I donít have anything else today, see you next week, same time. We do have audio now, so we have that for review.<br>Doug- I sent out the link to the info on the 3 platforms <br><br> <br> <br> </div><BR><BR>John Goldthwaite<br>email@example.com<br>828 885-5304<p>
<hr size=1>Yahoo! Photos Ė Showcase holiday pictures in hardcover<br>
<a href="http://us.rd.yahoo.com/mail_us/taglines/photobooks/*http://pa.yahoo.com/*http://us.rd.yahoo.com/mail_us/taglines/photos/evt=38088/*http://pg.photos.yahoo.com/ph//page?.file=photobook_splash.html">Photo Books</a>. You design it and weíll bind it!