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

The Beginning of CVOYA

There’s a unique energy that comes with starting something new — a blend of excitement,…

1 month ago

Enhancements in Graph Model: Dynamic Entities & Full-Text Search

As I continued work on BrainExpanded and its MCP service, I came to realize that…

4 months ago

GraphModel: A .NET Abstraction for Graphs

Just over a month ago, I published "Playing with graphs and Neo4j". Back then, it…

5 months ago

Playing with graphs and neo4j

After my initial implementation of some BrainExpanded-related ideas on top of dgraph using its GraphQL…

6 months ago

A Graph Model DSL

Say hello to the Graph Model Domain Specific Language (GMDSL), created with the help of…

7 months ago

BrainExpanded – Web app and Data Sources

As I wrote in previous posts, the manual recording of memories for BrainExpanded is just…

7 months ago