Currently i am travelling to Redmond and i got a chance to attend a MSDN in person event about OBAF and live services on 15th November.
It was a power series supposed to talk about OBAF and live services. Here are some interesting point which i got out of the OBAF session which i attended
1) Office developer map :- It helps in identifying the tools which might help in developing various office applications. Its a click once application which can be installed on desktop. (I'll give it a try to validate that i understood the discussion about the map correctly)
2) Microsoft is having a set of tools which can help develop an office application. The tools are BDC/ VSTO/ Sharepoint portal
3) The discussion got deviated towards office in between and i found that office 2007 uses a COM SHIM to actually display the ribbon controls
4) One more discussion which happened out of deviation again was about the file formats of office 2007 files. Now i knew that they are xmls embedded inside a zip file however one thought which came into my mind while attending this session was why does the outlook object model still has to be so complex. Why not represent all the message classes like IPM.Appointment, IPM.Post as simple xmls and store them in psts like that. It was discussed in the forum and Joe (Presenter) believed that it might be because of the pst being already an efficient format to store these message classes. I agree with him however it is not an open standard. I believe even .doc was not a bad format. It was converted to .docx to make it more open and we should do the same for message classes in outlook. I would be interested in finding out why it is actually not changed.
I would make a different post for the session about live services.