Language Selection

English French German Italian Portuguese Spanish

IBM and Microsoft face WS-critics

Filed under
Misc

The title of the five-person panel debate at the Digital ID World conference was "Federated Standards: The State of Convergence". The answer, if there was one, was that there will be no broad convergence. Not any time soon, anyway.

The debate, which got quite heated, boiled down to people asking Microsoft and IBM to develop their WS- specs in the open, where any interested vendor can contribute, and Microsoft and IBM declining, saying such processes are not suitable.

"It's not necessarily the optimal process for everything," said John Shewchuk, chief technology officer of Microsoft's Distributed Systems Group. "What comes out at the end may not meet our technical objectives as a vendor."

For several years, Microsoft and IBM have been working on WS- specs, such as WS-Security and WS-Trust, to enable interoperable web services. While some other vendors help out, the process is strictly invitation-only.

When a spec is mostly finished, it is submitted to OASIS, Organization for the Advancement of Structured Information Standards, but sometimes it will conflict with work already done by others, and differences need to be ironed out.

Recently, for example, there was a clash within OASIS between the Oracle-Hitachi- Fujitsu WS-Reliability and the Microsoft-IBM-BEA-Tibco WS-Reliable Exchange. The two groups will reportedly work to converge them.

It gets more confusing in the digital identity space, where there's also the Liberty Alliance, which works on standard specifications for federating identities between domains, enabling single sign-on.

"Everybody has enough invested now that they can't just get up and walk away from it," said Intel's George Goodman, on the panel in his capacity as Liberty president. "It's hard to see convergence... at this point we have to focus on interoperability."

Developers expressed frustration that the companies creating the specs cannot come to an agreement on converging them, and are basically leaving it up to buyers to decide whether to implement one, the other, or both.

Full Story.

More in Tux Machines

Servers: Docker, Red Hat and InfluxData

Laptops: Chrome OS and System76

  • Chrome OS Gets Material Design for "Do Not Disturb," Android-Like Screenshots
    Chromium evangelist François Beaufort is sharing today information on a new Material Design refresh for Google's Chrome OS' "Do Not Disturb" mode, which landed in the latest Chrome Canary channel. According to the developer, the Material Design refresh for the "Do Not Disturb" mode will make the Notification Center look nicer, but also consistent with the Android user experience. Those using the Chrome Canary experimental channel can give it a try right now.
  • System76 'Lemur' and 'Galago Pro' Ubuntu Linux laptops get 8th gen Intel Core CPUs
    The famed Linux-laptop seller also says, "The Lemur you know and love is now even better with the Intel 8th Gen Coffee Lake CPU with 4 cores and 8 threads, allowing you to multitask up to 40-percent faster. The slim, 3.6 lb laptop with impressive 14.1-inch 1080p IPS display is still your perfect travel companion; easy to carry from meeting to meeting or across campus." New processors aside, these laptops should be pretty much identical to prior generations -- which is a very good thing. If you want to configure a Lemur with a Coffee Lake chip, you can build your own here. A Galago Pro with an 8th Gen Intel Core processor can be configured here.

Events: Open Source Summit Europe, LibrePlanet 2018

Licences: Eclipse Public Licence 2.0, GPL Copyright Troll, Fiduciary License Agreement 2.0

  • Eclipse Public License version 2.0 added to license list
    We recently updated our list of various licenses and comments about them to include the Eclipse Public License version 2.0 (EPL). In terms of GPL compatibility, the Eclipse Public License version 2.0 is essentially equivalent to version 1.0. The only change is that it explicitly offers the option of designating the GNU GPL version 2 or later as a "secondary license" for a certain piece of code.
  • Linux kernel community tries to castrate GPL copyright troll
    Linux kernel maintainer Greg Kroah-Hartman and several other senior Linux figures have published a “Linux Kernel Community Enforcement Statement” to be included in future Linux documentation, in order to ensure contributions to the kernel don't fall foul of copyright claims that have already seen a single developer win "at least a few million Euros.” In a post released on Monday, October 16th, Kroah-Hartman explained the Statement's needed because not everyone who contributes to the kernel understands the obligations the GNU Public Licence 2.0 (GPL 2.0), and the licence has “ambiguities … that no one in our community has ever considered part of compliance.”
  • Fiduciary License Agreement 2.0
    After many years of working on it, it is with immense pleasure to see the FLA-2.0 – the full rewrite of the Fiduciary License Agreement – officially launch.