Beyond | IT : Office

FedEx QuickShip Revisited

john.mullinax — Thu, 17 Sep 2009 21:14:00 GMT

Jon Box has short post today talking about our partnership with FedEx a while back to help them build and launch their FedEx QuickShip service. The formal launch was on stage with Bill Gates at the Office Developers Conference – exciting times!

I think FedEx has been pretty pleased with the reception of FedEx QuickShip by our mutual customers. Two of the guys involved on the FedEx side are Ben Baker and Matt Howell – FedEx recently made a video of them talking about FedEx QuickShip.

For more info on this solution from FedEx, checkout my earlier posts, here. And do check out Jon’s post for links to case studies and some great quotes about how FedEx can make life better for their customers by building customer solutions on top of Microsoft Office.

Technorati Tags: FedEx,QuickShip,Office Development

Democratizing DITA, DITA Exchange, and Danish Beer: 20 Questions with Steffen Frederiksen of Content Technologies

john.mullinax — Tue, 17 Jun 2008 19:13:13 GMT

Content Technologies presented at the Content Management Strategies conference in Santa Clara, California, this past April on their DITA Exchange product. Being a DITA XML authoring, collaboration, and publication management solution built on MOSS 2007 makes DITA Exchange pretty interesting. Even more interesting, Content Technologies unveiled an OBA (Office Business Application) during their talk in Santa Clara. Basically, it’s an add-in for Word 2007 that lets subject matter experts contribute DITA XML content using Office Word without ever having to even see an XML tag. Cool! I wouldn’t call myself a DITA expert by any stretch – but I started looking at DITA about 9 or ten months ago. My impression was that DITA was a pretty valuable concept… structured topic-based SME authoring, document assembly – really good stuff.

But I also noticed that successfully adopting DITA in the real world seemed to require a significant investment in specialist tooling and training that eroded the actual payoff of DITA. So Gabor Fari (also of Microsoft) and I began discussing a Word-based OBA with Content Technologies that could complement DITA Exchange. Would a Word OBA for DITA Exchange, I wondered, help Content Technologies take a great idea – DITA – from the specialist Content Management community and democratize it? In other words, could Content Technologies successfully leverage the familiarity and ubiquity of Office to make DITA approachable and practical for widespread SME use?

Gabor and I recently had the chance to catch up with Steffen Frederiksen, one of Content Technologies founders, via email on DITA and OXML, their OBA, and Danish beer. Here’s our version of “20 Questions”.

JM: Tell me a little bit about yourselves

SF: We all have an extensive background in the content- and document management space. Some of us have worked with structured writing methods since 1990 - and with SGML and later XML since 1996. Managing the total content life cycle – with nothing left out – has played a major role in our professional lives: Making it easy to find and read content, collaborate around content, enabling content reuse, doing single-source publishing, making XML really useful even for people with no XML expertise and changing technical documentation from being a cost center into a real business asset – these are all key themes for us: Make it simple, to make it work!

JM: Tell me a little about Content Technologies

SF: Content Technologies was founded in 2000. Throughout its life, the company has focused on XML-based authoring tools and content management solutions – but in 2006, we redefined the company around the release of SharePoint 2007. This new version of the SharePoint platform held enormous potential for building real business solutions – and we wanted to go there with everything we had.

JM: Content Technologies has a solution built on MOSS called DITA Exchange – what is DITA?

SF: DITA (Darwin Information Typing Architecture) is really two things: It is a topic-based content architecture and it is an XML-based open standard for creating and publishing reusable content. It was originally developed by IBM for internal use and has since been released to the open-source community (now under the guidance of OASIS). The DITA OASIS Standard defines an XML architecture for designing, writing, managing, and publishing strongly typed topics, mostly for technical documentation on print and on the Web. DITA builds content reuse into the authoring process for document creation and management.

Focusing on a common topic model as a conceptual unit of authoring, DITA provides a core set of topic types derived from concept, task, and reference. DITA defines a specialization mechanism for extending markup to represent either new topic types or new domains of markup common across sets of topic types. DITA maps can combine topics into various kinds of deliverables. Content can be shared among maps or topics. Class-based processing ensures that new specializations can be supported with existing tools, speeding up the testing and adoption of new designs.

DITA has been and is being adopted by Fortune 1000 companies around the world with an unprecedented speed at the moment. The business drivers in this are both huge potential cost savings and (equally or even more important) reduced time-to-market for products and services.

JM: Why would someone use DITA vs. OXML or a proprietary schema for high end xml content management?

SF: First of all, building solutions based on proprietary XML schemas is something a lot of companies have tried – and in many cases failed with: It leaves you alone, with no-one else to share tools, costs, or even your content with. Been there, done that – and it just did not provide the business value it was supposed to deliver. Secondly, the direct comparison of DITA and OXML is a false one:

DITA is strongly typed and has very strict rules for content structure and sequence in reusable topics. OXML on the other hand has been designed to be able to handle both unstructured and structured content, both transient content and reusable content: OXML has to be able to handle any kind of content in any kind of structure (including pure ”spaghetti information”) that anyone could ever think of putting in a Word document. Not an easy task – but I think the OXML folks have actually met this objective. As an example of this enormous flexibility in OXML – it can actually host the strongly typed DITA topics!
OXML is like a large container ship: It can handle thousands of different containers – with whatever goods they might contain. DITA is more like 5 specially designed containers – that can only accomodate a special type of cargo.

JM: What makes DITA Exchange different than other DITA solutions – or other doc assembly, single-source publishing, topic-based authoring solutions?

SF: Four words: Standard, Open, Simple, and SharePoint! Our solution combines the strengths of the DITA standard and the SharePoint market standard. It is extremely open, so users can collaborate on DITA content using their favorite XML editor, Word 2007, or just a browser. It is simple: You can get started and produce results without being confronted by even a single XML tag – and without having to be a DITA expert. And then DITA Exchange offers our customers the richness of the SharePoint platform: Collaboration, authentication, records management, web parts, versioning, workflows, skinning, personalization, LOB connections, etc. All in all, this is a very hard cocktail to beat for our competitors.

Furthermore, we offer DITA Exchange either as a hosted service or as an inhouse solution – with a highly scalable monthly fee per user: This makes it very easy and fast to get started with DITA Exchange, with a minimal up-front investment. You can demonstrate real business value from day 5! Again, this is quite different from most of our competitors.

JM: Why did you start Content Technologies?

SF: Well, at least for the restructuring around DITA Exchange: We spotted this gaping hole in the market. There was a huge latent demand for an easy to use yet sophisticated DITA solution based on SharePoint. We had the ideas and skills needed to fill this gap and bring the solution to the customers.

JM: You just presented at the Content Management Strategies conference – what was that like?

SF: It was a very nice experience – for many reasons: Many are just taken by the ease-of-use and richness of a SharePoint-based solution. Others have chosen to implement the DITA standard – at the same time that their company has decided to use SharePoint as the common platform – so they have been strugling with this “two-standard-compliance”. Obviously this is a perfect match for DITA Exchange.

JM: What kind of response did you get?

SF: Well, 4 large companies asked us at the conference how they could get started with DITA Exchange asap, 3 other companies wanted to sign up with us as distributors or resellers – and then there was a large number of companies that wanted us to get back to them with more information and to setup webinar demos. Not bad.
Interestingly, several of our direct competitors in the DITA CMS space came to us to discretely tell us: “You have some really good stuf there”. That felt good.

JM: Why did you decide to build DITA Exchange on MOSS?

SF: SharePoint 2007 added a number of critically important features that made it possible to implement a full content management solution based on a complex XML standard on the platform. Furthermore, there is just no way any large company get a succesful DITA implementation if it is based on a highly specialized, closed XML-based content management solution: This will lead to an isolated “inside the tech-doc-silo” solution – and the real business value of DITA (cost savings and faster time-to-market) will evaporate.

To get the full value of DITA, you need an open, scalable, corporate collaboration platform – and SharePoint 2007 is currently being chosen by companies around the globe.

JM: I know you mentioned something about a Word 2007 OBA for DITA Exchange in your CMS presentation – what can you tell us about that? For example, what does it do? Is it for general SMEs? xml specialists? Everyone? Is it generally available? Has it been hard to build? (and why or why not?)

SF: The main objective for the Word 2007 OBA is to allow subject-matter experts and DITA experts to use the rich, familiar Word 2007 environment while participating in DITA content collaboration projects and workflows within the DITA Exchange/SharePoint 2007 platform. The idea has been to reuse all the MOSS-integration features in Word 2007 while replacing all Word’s formatting with one single ribbon, that contains and handles all the formatting available in the DITA standard. The OBA actually converts DITA xml to OXML (using custom xml parts within the OXML) and back in order to allow users to use the Word canvas for editing – plus it offers a handful of nice features that support the DITA authoring process in general.

By far the hardest part to accomplish this is to include and support the entire DITA schema from within Word 2007. The DITA schemas are complex, and although Word supports custom schemas, Word 2007 is basically an OXML-editor tightly bound to the OXML schema. The OBA is built from scratch with Visual studio 2008 using VSTO 3.0, .NET 3.5 and the SDK for Open XML (which is still in beta). From way back in the days with Word 97, we have a lot of experience in designing and developing similar solutions that provides topic-bases content authoring by using VBA and custom COM add-ins. Moving to managed code, utilizing Word’s XML-features (since 2003) and now the OXML-format gives us some obvious advantages and allows us to produce this OBA a lot faster than back in the VBA-days.

The OBA will be available as part of the DITA Exchange license around July 1^st.

JM: What has the reaction been like to the OBA so far?

SF: A lot of companies are even VERY excited about the OBA solution: This will open the door to collaborate effortlessly between XML, tech-doc specialists and engineers, product management, marketing and other subject matter experts. So far, this kind of collaboration required that you could ”force” a special XML editor on all of these people – and they tend not to respond favorably to this! This has been a real stopping block in many organizations that we work with.

JM: Content Technologies is based in Denmark, and I know you’ve had the chance to work with a number of different companies in the US and Europe and maybe other places as well – have you noticed any regional differences in how people approach DITA and Content Management?

SF: Practically all of the companies we are working with are really global companies, trying to deal with global issues. Furthermore, the DITA standard – and the SharePoint standard - provides us with a common understanding, or a shared conceptual framework – that makes it easy to communicate around the globe.

So the answer really is: No, we have not found this to be the case at all.

JM: Your solution is very robust – something that a big enterprise would want to use. But your company is fairly small and young (how big are you again?) – what is it like serving big companies, but not being a big company? Are there special challenges that go with that? How do you handle them?

SF: First of all, a lot of the robustness of our solution is actually derived from the SharePoint platform. So thanks to the SharePoint folks in Redmond. Secondly, we are busy implementing a global network of DITA Exchange implementation partners. Right now, I think we are represented like this in 15 countries. These partners will do a lot of the implementation and customization work with our large customers – leaving the core product development and overall marketing and support to us.

This model has proven itself to be very effective and profitable for our customers, for our partners, and for us.

GF: Content Technologies is a very small company, and Microsoft is a very large organization. Can you tell us a bit about what your experience has been so far, working with the Microsoft team to develop this OBA?

SF: We are indeed a small company, but we thought we had a big idea – and it was a real pleasure to find that the people in Microsoft we are working with (primarily John Mullinax and Gabor Fari) enthusiastically supported this. They have really been extremely helpful and responsive, provided us with prospects, helped expand our network of partners, provided direct access to technical expertise inside the Redmond product teams – as well as provide vital feedback on some of our ideas for the product. In other words: It has been a pleasure!

JM: I understand you offer DITA Exchange as either on-premise software or as a hosted solution…. Are there differences between them? Can customers use the OBA in either model? Can customers tap into line-of-business systems data with either model?

SF: Yes, DITA Exchange with the OBA can be used in both models. We have taken great care to design our solution inside the SharePoint “envelope”. This means we profit from all the SharePoint connections and wiring.

JM: Describe the ideal customer situation for DITA Exchange – where it can really shine.

SF: Here are some key characteristics for the “ideal” customer and use case:

Global company, with operations around the world
A lot of reusable content, for example product documentation
A lot of translation needed
Fast product cycles, many product variations
A lot of compliance issues
Multi-platform publishing needs
Dynamic web publishing
Many sub-contractors (need to exchange component documentation in standard format)
Time-to-market is critical

JM: What kind of scenario would NOT be right for DITA Exchange?

SF: Keywords:

Content is created ad-hoc, no reusability
no translation needs
no component doc to customers or from sub-contractors
no compliance issues
no SharePoint installation or plans
no DITA decision

JM: What’s next for Content Technologies?

SF: Serving our customers! Marketing the OBA solution. Expanding our network. And then all the new stuff that we are busy with behind the scenes…
Our mission is simple: We want to create the best SharePoint-based DITA solution in the world.

JM: If I come to visit you in Denmark, what is the best beer that I should try?

SF: …. Sam Adams (no, that was a joke). Go for “FUR Renæssance”

JM: Anything else you want to add?

SF: “Simplicity is the ultimate sophistication” - Leonardo da Vinci

More information on Content Technologies and DITA Exchange can be found at http://www.dita-exchange.com.

Technorati Tags: DITA,DITA Exchange,OXML,OBA,Structured Content Authoring,Content Technologies,Microsoft Office

Out Of The Box : Scared of the Office Ribbon?

john.mullinax — Tue, 29 Apr 2008 19:35:07 GMT

Jon Box has produced another interesting post -- this time on the Office Ribbon (aka the Fluent UI). In particular, he points out a cool add-in from Office Labs that called "Search Commands" that will help you find your favorite commands in the new UI. People are different, and like a lot of other things, how long it takes someone to adapt to the new UI can be plotted on a distribution. If you happen to fall on the end of the distribution that takes a bit longer to adjust, you might find the Search Commands add-in that Jon talks about to be helpful. I tried it myself some time back (before it was publicly available), and while I almost never actually used it, there were one or two times when it really helped.

As a coincidence, the Office 2007 UI (aka the Fluent UI) came up at dinner last night with Josh Holmes and others. (Yes, this is what Microsoft people talk about at dinner ). One person said that it only took a very short time to get comfortable with the new UI. Another person at our table claimed that it took them a month to get used to the new UI because they were a "power user". That's an assertion I've heard before -- that power users take longer to adapt. I think the rationale is that the more commands you use in the old version, the more commands you need to re-locate in the new version. I think there's some truth to this in the aggregate, and yet it's not true to say that a power user will take a long time to gain equivalent proficiency with the new UI.

Which brings us back to distributions. For a refresher, here is a picture of a normal distribution (the red line) -- often called the bell curve. This is not a histogram, but it's similar -- in a histogram, the x-access plots an observed value, and the y-axis plots the how many times that value is observed. In the chart of the normal distribution, the red curve is a probability function that predicts the likely-hood of any observation. The connection between the two is that for many phenomena in the natural and behavioral sciences, if you took an infinite sample and plotted the observations on a histogram the result would be the shape of a normal curve (thanks to the central limit theorem).

And now (finally) coming back to the Fluent UI, there are many independent factors that determine where someone falls on distribution curve of how long it takes to gain an equivalent level of proficiency with the Fluent UI that they had in the last version of Office -- the degree of "power user-ness" is just one. It may be true that power users, as a group, tend to be toward one side of the normal curve (the side that takes longer to gain proficiency with the Fluent UI equivalent to what they had in Office 2003), but that does not mean that an individual power user definitely *will* take longer to adjust to the Fluent UI.

For example, I would consider myself a power user of Office 2003 (especially Excel) and it took me less than 2 days to get comfortable with the Fluent UI in Office 2007. In fact, I would say that within a week I could do significantly more significantly more quickly in Office 2007 vs. Office 2003. So if degree of power user-ness is not the only driving factor, what else helps predict the adaptation rate? I'm sure I don't have a complete list, but would hypothesize the following factors could help predict how fast a person adapts to the Fluent UI:

The particular commands a person uses -- few people use more than 25% of Office capabilities, but there are thousands of capabilities and we all use different ones. If you tend to use commands that are surfaced in the top two context layers of the Fluent UI -- as most people do -- then you will probably have an easier time adapting. If you often use commands that are more rarely used and got less prime real estate on the Fluent UI, then the adaptation process may tend to take a little longer (all other things being equal).
Innate orientation toward change -- some times change is easy, sometimes it is hard, and sometimes it is harder. I don't have anything precise here, but I suspect some part of that equation comes down to us -- our personalities and strengths/weaknesses. We all have strengths and weaknesses, but they're not all the same.
Attitude -- for someone who loves being the person in the department who knows how to do (formerly) complex things, and who takes pride in helping others tap into the Office "power features", the Fluent UI could be a bit of a blow. Now, for example, pivot tables are easy for everyone. I imagine the irritation around the Fluent UI for someone in this situation would only partly be that they now do pivot tables differently (after all, they invested the time to learn how to do it when it was much more difficult... now that it's become simple it surely is not beyond their capacity). Rather, there may be a sense of loss in play as the power user's Office expertise becomes just a little less valuable when others can do more for themselves.
I'm sure there are others -- what would you add?

After all of this, the larger point is don't be afraid of the new UI -- even if you are a power user. Think about where you are likely to fall on the distribution curve, and pick a good time to upgrade (e.g., not the night before a big PowerPoint presentation or an important Excel analysis is due). In the end, most people find that before long they can do more, more easily in Office 2007 than in Office 2003 -- even many power users -- because in Office 2007 they are almost instantly capable of many features that were previously hidden deep in the Office 2003 menu structure.

Where adaptation challenges are most significant, I suspect it's for folks who need the commands that are obscure in both the old and new versions of Office (but obscure in different ways). If you think you might fall toward the longer side of the adaptation curve, or need commands that are obscure in both versions of Office, definitely go to Jon Box's post and grab the Search Commands add-in from Office Labs. You may also want to check out the Office team's "Help and How-to" site, as well as the especially cool, Community Clips (also from Office Labs)!

If you've not heard of Community Clips, the site describes itself like this:

If you've ever struggled with a feature in Office, if you want to increase your Office know-how, if you want to show others your favorite feature or trick, or if you've had trouble explaining to your friends how to do something, start using Community Clips today!

It's basically a video sharing site dedicated to sharing short screen-casts on how to do different things in Office.

Technorati Tags: Office 2007,Fluent UI

Brian Jones: Open XML Formats

john.mullinax — Wed, 02 Apr 2008 23:38:39 GMT

In case you missed it, ISO has approved Open XML as a standard. Brian Jones has more here. What does this mean? Well, among other things it means that the next version of Office ("Office 14" is the inspiring code name) will use an ISO standard as it's native file format. And going forward, the evolution of the format will be managed through ISO. Office file formats have not always been open, but have been a defacto standard for years. Opening the file formats and making Open XML an official document format standard shifts control to Microsoft customers and the national standards bodies that make up ISO.

Microsoft has long supported partners building on Office as a platform, and this continues to be true. Hopefully, making the format specification open and independently managed will give customers and third party solution providers an even greater level of confidence and certainty when directly implementing the standard themselves -- for example by programmatically creating, reading, and manipulating Open XML documents.

Similar in spirit, you might also be interested in Microsoft's "Open Specification Promise".

On a personal note, as I travel around and meet with customers and partners, people often say things to me like "Microsoft has changed in the last few years -- you guys are more open, humbler, and better at listening to customers and partners." I love hearing this, and hope that things like supporting ISO standardization for OXML, OSP, our collaboration with Novell/SuSE and Miguel de Icaza around Mono, the WS-* work, implementing part of the CLR on multiple platforms for Silverlight, etc, will help us keep moving in the right direction. :-)

Technorati Tags: Office XML,ISO,OSP,Microsoft

The point of ISO standardization of Office file formats...

john.mullinax — Fri, 14 Mar 2008 00:52:50 GMT

Most of the debate around ISO standardization of Open Office XML file formats -- the native file format of Office 2007 -- is terribly acrimonious and FUD-filled. For a different and interesting take on the debate, see here. Why interesting? The blog makes argues that the point of of ISO standardization is to actually take control of OXML away from Microsoft and place it in the public domain -- something important to society given how many people use Office.

Rob seems to be under the impression that ISO-approval is some kind of quality badge of honor that you can proudly carry around. First of all, I think we can all agree that ODF itself is a clear example that ISO-approval not necessarily implies quality, interoperability and clearness. Secondly, how the specification was made is not the first priority when talking ISO-approval. The first priority should be:

We need to take control of OOXML out of the hands of Microsoft and back into society as a whole

This was imho the focal point of Patrick Durusau's support of DIS 29500 approval. Amongst other things he said that

Patrick Durusau: The cost of rejection is that ordinary users, governments, smaller interests, all lose a seat at the table where the next version of the Office standard is being written (bold emphasis from original post).

Technorati Tags: OXML,Office,ISO

BillG Keynote at ODC -- see the video and screenshots from the FedEx demo

john.mullinax — Tue, 12 Feb 2008 00:34:00 GMT

If you weren't at ODC live to see BillG's keynote, you can see the video here. [Note: updated link so it works again.]

Also, FedEx showed a number of cool things during BillG's keynote at ODC today. The demo was really packed, so there wasn't a lot of time for to really dwell on / explore the interesting things they've put together. Here are a few screenshots for the different scenarios that were shown:

The FedEx QuickShip toolbar for Microsoft Office Outlook.

As a reminder, FedEx QuickShip is the Office Outlook add-in that FedEx is launched today. You can learn more, and download the add-in free of charge at the FedEx site here.

Printing to FedEx Kinkos from Office Word 2007. This was built using Visual Studio 2008 and VSTO 3. This is a prototype that FedEx is very excited about. Keep in mind it might change significantly when/if FedEx brings it to production.

While FedEx already has a printer driver type of capability called FPFK (File Print FedEx Kinkos) that lets you print to Kinkos from any Windows application (including Word), the kind of experience that FedEx showed today is far richer. In addition to connecting users to Kinkos services, it also provides the contextual information and visualizations to help people make decisions about how to leverage Kinkos services.

A "MyFedEx-style" site template that customers can use from within their own SharePoint environment. Uses ASP.NET AJAX, and pulls in mapping data from Virtual Earth -- in addition to the FedEx services, of course. Let's users find the rates for shipping packages, manage shipments, and see where there shipments are, and the route they've taken.

This is also a prototype that could change if/when it comes to production. One thing to keep in mind, customers could build this for themselves using SharePoint and FedEx's services. You can learn more about how to build with FedEx's services at the FedEx Developer Resource Center (DRC).

FedEx capabilities within Office Live Small Business. This screenshot shows tracking for FedEx shipments and Kinkos print orders within Office Live. This was built using Office Live Small Business and FedEx's HTML plugins available through the FedEx DRC.

Technorati Tags: ODC,BillG,FedEx QuickShip

FedEx joins BillG on stage at ODC 2008 to announce FedEx QuickShip, and show off Office as a platform, S+S

john.mullinax — Mon, 11 Feb 2008 21:33:00 GMT

(Update 1:41pm PST: See screenshots and video here!)

I'm at the Office Developers Conference 2008 this week, and BillG is on stage doing Q&A, having just finished the keynote. A number of the highlights involved FedEx.

In fact, FedEx SVP David Zanca joined BillG on stage and announced the public launch of FedEx QuickShip. FedEx QuickShip is an easy way to use FedEx tools and services from within Office. Very cool! Jon Box and I have been working with FedEx behind the scenes on FedEx QuickShip for a while now, so it's very exciting to see it finally get officially "born"!

Maybe even cooler is what's to come: Zanca also showed how FedEx is thinking very broadly about using Microsoft Office as a platform for accessing and interacting with FedEx shipping and printing services. Among other things, he showed:

Printing from Word 2007 directly to Kinkos -- complete with the ability to select finishing options like bindings (color, paper size), to see visualizations of the document as options are selected and deselected, and to see how the prices change in context.
Sharepoint site template that can give you something like a "MyFedEx" -- but for your own sharepoint site. Among other things, it leverages Virtual Earth to show where your package is and where it's been.

For customers, it's a way to get access to the power of FedEx -- and do it directly from within the environments where they do their work. For FedEx, it's a new way to reach customers, and to differentiate FedEx, by serving customers in ways that help people work better.

Beyond Office at the client level (Outlook, Word) and Office at the server level (Sharepoint), the Office Live team also showed how FedEx services can be brought into people's Office Live services environments.

Taken together, what FedEx showed is a great example of the kinds of differentiating user experiences that can be created across the full Office platform. It's also a great example of Microsoft's Software + Services vision. While S+S is a term that Microsoft tends to use, the concept is something we're seeing get a lot of traction in the industry today. For example, Rob Carter recently said:

“The Internet doesn’t mean a customer destination like a Web site—it means connections. For FedEx, that means finding more ways to integrate its offerings into what people are doing in work and life.”

It's been a lot of fun for Jon Box and I to work with the FedEx team on all of this!

One more bit of fun... at the end of the Zanca's demo, a FedEx courier came up on stage and delivered a Guitar Hero III Les Paul model guitar to BillG! We're going to give that guitar -- autographed by BillG and Zanca -- away to someone at ODC near the end of the conference! If you're at the ODC, come check it out at the FedEx ODC event booth! (Update: See the guitar here!)

And if you do, don't forget to stop by the Microsoft booth next door and say "Hi" -- Jon and I will be there off and on throughout the conference.

Technorati Tags: Office Platform,ODC,FedEx,S+S,Software+Services

Miss your chance to see BillG keynote CES? See him keynote the Office Developers Conference 2008!

john.mullinax — Tue, 08 Jan 2008 21:01:13 GMT

The Office Developers Conference (ODC) is coming up quick, starting 10-Feb-2008 in San Jose this year. Should be an awesome event! Office 2007 is by far the best Office yet to build solutions on, and now that it's got a year on the market under it's belt I can't wait to see what everyone is showing off!

As an added bonus, Bill Gates will keynote the event to kick things off -- his last ODC Keynote as a full-time Microsoft employee. So if you missed him at CES, don't miss him here! After that, you can look forward to a few great days getting inspired and learning how to put that inspiration into practice.

More info below - grabbed from the conference registration site: www.odc2008.com.

I will sure be there, and look forward to seeing many of you there, too! :-)

LIVE DEMOS. REAL CODE. HOT NEW INFO.

The 2008 Microsoft Office System Developer Conference

February 10-13, San Jose California

ODC 2008 is the premier event for Microsoft Office and SharePoint developers, bringing together architects, developers, industry technical experts, Microsoft insiders, and key partners to redefine what it means to build on the Office system.

Opening Keynote by
Microsoft Chairman, Bill Gates

We have incredible keynotes by senior Microsoft executives, starting with a special opening keynote by Microsoft Chairman Bill Gates. We’ll have hot new sessions that bring together diverse topics, from application composition to Software+Services, SharePoint & Silverlight to VOIP & OOXML, and everything in between!
We have 5 technical tracks, and 70+ breakout sessions and hands-on labs. And for the first time ever, we will have an Executive Track where analysts, Microsoft and industry executives will get together to discuss the how and why of Office business applications and their competitive advantages.
We look forward to seeing you there!

Additional Executive Keynotes:

Kurt DelBene - CVP, Office Business Platform Group
Rajesh Jha - CVP, Office Live
Richard McAniff – CVP, Microsoft Office
Gurdeep Singh Pall - CVP, Microsoft Unified Communications Group

Technorati tags: ODC2008, Bill Gates, Microsoft, Office, Conference