A follow up on our story about the Corel patent case and the more confusing case of a developers licence to use the MS Office ribbon interface.

As we noted, the Microsoft page that explained the rules for using the Office interface were ‘retired’ even though they are still relevant.  Even more relevant since Corel lost it’s case against Microsoft on that subject.

It would be in Microsoft’s interests to make the legal position clear for developers of non-Office, non-competing products.  Expecting developers to dig into the detail of multiple and overlapping licences doesn’t encourage use of the interface.

We asked Microsoft, some specific questions:

1. What are the current Office UI Licencing arrangements?
2. The current, presumed, legal arrangements seem to only apply to developers using Microsoft’s own SDK’s for making a Ribbon.  What’s Microsoft’s position on other developer tools for making ribbon-like interfaces for Windows, Mac or even web pages?

Here is their response.  The links provided are updated from the ones on the ‘retired’ page.  The second question was ignored completely.

Windows 10 Creators from people 'in the know'

A detailed and independent look at Windows 10, especially written for the many people who use Microsoft Office.

Fully up-to-date with coverage of the Creators edition 2016 major update of Windows 10.

This 720 page book shows you important features and details for all serious Windows 10 users.

” Sharing the current developer frameworks that are licensed for creating a Ribbon UI, and they include:

• Introducing the Windows Ribbon Framework
• Ribbon (WPF)
• Ribbon XML
• Ribbon Class
• Windows 10 SDK “