Open Specification Promise: What. How. Why.

This is great for those building protocol-based integration solutions.

?Recently, Microsoft announced a new type of licensing model aimed at making it much easier, therefore safer from a legal point of view, for developers to implement specs without having to spend a lot of time understanding complex license agreements and obscure legalese, then signing and faxing Microsoft legal documents in order to leverage a specification. This new breed of simple licensing model is called the Open Specification Promise (OSP).

Here, we chat with the minds behind OSP: Jean Paoli, co-creator of XML and General Manager of Interoperability XML Architecture, Tom Robertson, General Manager of IP and Corportate Standards Strategy, and Amy Marasco, General Manager of Standards Strategy. Want to to understand what OSP is and why we created it? Tune in and let the the folks who thought it up explain it to you.

Link to Open Specification Promise: What. How. Why.

Recent Posts

CVOYA Graph v1.0 is out

Last week, I wrote about the evolution of the CVOYA Graph. After a lot of…

3 weeks ago

CVOYA Graph – Evolution

Last year, I released the "Graph Model" library for .NET as an open source project. It…

4 weeks ago

The boat is in the water: Spring Voyage is open source

Today I'm pushing Spring Voyage out of the harbor. You can track its journey on…

2 months ago

My Coding Agent Needed Its Own GitHub Identity

In my last post, I wrote that "the typing of code was parallelized and delegated.…

4 months ago

Rebuilding My AI Team in Twelve Days — And Why

In February, I wrote about the small team I'd stood up instead of hiring humans:…

4 months ago

How I Built My Own Team of AI Developers

Assembling a dream team without a single hire I've been making great progress on CVOYA's…

6 months ago