In MissionKit Version 2010 Revision 3, new features include support for industry standards iXBRL and National Information Exchange Model (NIEM), and support for mapping data based on SAP’s IDoc EDI format. Altova has also added in some integration with Microsoft Visual Studio 2010.

Some highlights to the individual tools include:

• XMLSpy – can now validate internal naming and coding conventions outside of the XML Schema standard and integrates with VS2010.
• MapForce – C++ code generation has been updated to MSXML6. This data mapping tool can now generate C++ for 64-bit applications and perform mapping based on SAP’s IDoc EDI format.
• UModel  – can now generate code in C# 4.0 and reverse engineer C# code to create UML models.
• StyleVision – now supports Inline XBRL (iXBRL) in visual stylesheet and electronic forms design. The iXBRL standard embeds XBRL fragments into an HTML document so that the same source can be used for both human and machine processing.

For more information, check out Altova.com.

Writes Ford:

UML is a failure. It failed for several reasons. Mainly, it failed because it falls into the cracks between technical people (developers, architects) and non-technical people (business analysts, project managers, etc). UML is too technical for non-technical people, and not technical enough for technical people. By this, I mean that it isn’t really technical enough to do serious work on design by techies. At the same time, it’s obscure enough to be mostly incomprehensible to non-techies.

Maybe the fact that Microsoft finally came around to UML was the signal for a pile on. Fact is, UML’s major failing is that it exists, flaws and all. Things in the imagination tend to work way better, you know.

Related software modeling information
Arbitrary Markup Language - Meme Agora

SoaML’s goal is to provide SOA modeling of services within UML, without making changes to UML. As part of that, the spec seeks to support services architectures where different parties use multiple services and where services can be defined to contain other services. Mappings to business process specs are also in store, notably BPDM and BPMN.

Anyone concerned about an over-bearing top-down modeling regimen in SoaML can take heart in its claimed adherence to either top-down, bottom up or meet-in-the-middle modeling.

The SoaML has been percolating for awhile, with more details due in 2009. Just recently, a wiki of sorts has been formed for all things SoaML. A complete working doc is available as a PDF from OMG. And for the over-the-top would-be SoaML enthusiast there is a background feature on the making of the SoaML logo on the Yaya-Colour blog.

At the TechEd conference in Orlando, Fla. he announced Oslo, Microsoft’s SOA modeling project, will incorporate UML. It was also revealed that Visual Studio 10 will feature UML support. At first blush that may not sound like a big deal. After all, it’s just Microsoft embracing a popular standard modeling language.

Yet Oslo is Microsoft’s Hail Mary pass over the rest of the SOA market and apparently the company has decided to end its religious differences with UML for the sake of giving Oslo mass appeal. Previously Microsoft had been pushing domain specific languages (DSLs) as an alternative to the general purpose format of UML. Unfortunately for the folks in Redmond, DSLs have failed to gain much traction. Part of the problem is getting the people who form a domain to agree upon a standard syntax. Another part is having that DSL interact with anything outside of its domain. Those things surely will come with the march of time, but the uptake has been painfully slow.

SOA demands some commonality, that everyone stop trying to be so special and idiosyncratic. Microsoft has always understood that on some levels, but it’s got skin in the proprietary software business (actually it’s got skin, blood, muscle, bone, you name it). Its maverick tendencies have often led to it offering users products that do SOA the Microsoft way. That is in stark contrasts to the company’s Web services tooling, which has for the most part embraced open standards and heterogeneous systems (most notably Windows Communication Foundation). This is where I remind some readers out there that, yes, there truly is a difference between SOA and Web services.

In fact, one way to look at Oslo, which supposedly will offer a Community Technical Preview in September, is that this is Microsoft’s flag in the ground for SOA. It emphasizes the importance of modeling, attempting to bring the technology as close as possible to the business. As such, UML represents an excellent choice. It should create interoperability between Oslo projects and those built with rival modeling tools (e.g. IBM Rational). And Eclipse’s Modeling Development Tools Project will have a UML2 component ready by the end of the month.

UML gives Oslo a reach it never would have had if it were based on a proprietary modeling language. The UML foundation means Oslo stands a chance of being truly universal, which is as SOA a concept as you can get. It also puts pressure on the vendors backing Service Component Architecture. Has Microsoft managed to leapfrog them in terms of offering a general purpose SOA modeling platform? Or perhaps could this lead to Microsoft embracing SCA at some level, perhaps via Apache Tuscany?

With this UML announcement, Oslo suddenly ranks as a potentially powerful new addition to the SOA space. Nice to see that Bill Gates can still shake things up, even as he prepares to step down as full-time chairman of Microsoft.