While at the Microsoft MVP Conference this week, I’ve added “modeling in ‘M'” to my “to do” list. While I’ve kept only a peripheral view on “M” to date, the sessions here on “M” modeling have really gotten my mind working. There seem to be plenty of opportunities to build both practical data sets and actionable content through textual DSLs.
One great example of applying “M” to existing products/technologies is this great post by Dana Kaufman entitled A BizTalk DSL using “Oslo” which shows how one could write a simple textual language that gets converted to an ODX file. It’ll be fun watching folks figure out cool ways to take existing data and tasks and make them easier to understand by abstracting them into a easily maintained textual representation.
Update: Yossi Dahan has also posted details about his current side project of creating an “M” representation of a BizTalk deployment process. He’s done a good job on this, and may have come up with a very clean way of packaging up BizTalk solutions. Keep it coming.
Richard Seroter's Architecture Musings 
Wow, I was thinking of this last week and exchanged a couple of emails with Mick (Badran) about it – in my mind you could write in M an entire BizTalk solution split into two parts:
– ‘Visual studio’ parts: Orchestrations, pipelines, maps, schemas
– ‘Admin console’parts: Ports, adapters, bindings
Put this through an interpreter and magically your whole solution is built, requiring only some fine tuning.
And the other way around as well, get the interpreter to look at a BizTalk environment and generate the M schema and instances for it.
Good to know my thinking is in the right track!