Port 25: The Open Source Community at Microsoft : Community, Standards

Roadmap Announced for Outlook Personal Folders Documentation

Peter Galli — Mon, 26 Oct 2009 23:20:00 GMT

Great news on the data portability front: today, Microsoft announced that it will be releasing documentation for the .pst file format - the format in which data is stored in Microsoft Outlook Personal Folders.

Even better is the fact that the documentation will be released under Microsoft's Open Specification Promise when complete. This lets anyone implement the .pst file format on any platform and in any tool, without concerns about patents, and without the need to contact Microsoft in any way.

But it is important for me to point out that this documentation is still in its early stages and the work is ongoing. However, Microsoft is also engaging directly with industry experts and interested customers to gather feedback on the quality of the .pst technical documentation to ensure that it is clear and useful.

As an increasing amount of information is stored and shared in digital formats, it is vital for people to be able to reuse their data across various applications and platforms. Giving access to the documentation will facilitate interoperability and let customers and vendors to access their data in .pst files across a variety of platforms.

This is also just another example of how Microsoft is listening to its customers and responding to their requests for greater interoperability, in this case around data portability.

Also, enabling customers and vendors to access the data in .pst files on a variety of platforms allows developers to read, create, and interoperate with the data in .pst files in server and client scenarios using the programming language and platform of their choice.

"We're excited about the possibilities created for our customers and partners by this kind of effort, and we look forward to continued collaboration with the industry in our pursuit of improved interoperability with Microsoft Office," said Paul Lorimer, the Group Manager for Office Interoperability at Microsoft, in a blog post.

New Bridge Broadens Java and .NET Interoperability

Peter Galli — Tue, 29 Sep 2009 15:31:00 GMT

Microsoft continues to deliver on its ongoing promise to build bridges between different technologies, and this week jointly announced with Noelios Technologies a new interoperability bridge between Java and .NET through REST.

The Microsoft Interoperability Technical Strategy team has been working with Noelios to build an extension to the Restlet Framework. As such, Noelios has released a new bridge for Java and .NET. It is shipping a new version of the Restlet open source project, a lightweight REST framework for Java.

This includes the Restlet Extension for ADO.NET Data Services, which makes it easier for Java developers to take advantage of ADO.NET Data Services, a set of recently added .NET Framework features that provides a simple way to expose a wide range of data sources, such as relational databases, XML files, and so on, through a RESTful service interface.

This announcement is yet another example of Microsoft's continued commitment to openness and interoperability, and demonstrates the ever increasing use of web standards in our technologies.

Formerly known as Project Astoria, the ADO.NET Data Services defines a flexible addressing and query interface using a URL convention, and supports the usual resource manipulation methods for data sources, including the full range of Create, Read, Update, and Delete operations.

Microsoft Visual Studio 2008 SP1 and the upcoming Visual Studio 2010 fully support ADO.NET Data Services, including the capability to create and consume data services directly from the development environment.

You can find all the technical details of this announcement on the Interoperability team blog here, as well as on the Noelis blog. You can also find a tutorial on this here.

Apache Qpid Moves Forward

Sandy Gupta — Tue, 29 Sep 2009 11:15:00 GMT

Microsoft recently made a significant code drop to the Apache Qpid project. For those of you who don't know, Qpid is Apache's implementation of the Advanced Message Queuing Protocol (aka AMQP), which is an exciting new reliable messaging protocol developed by some of the world's biggest messaging users (think names like JPMorgan Chase).

What we've done is a Windows Communication Foundation (WCF) Channel for AMQP. Our goal is to provide a first class AMQP experience for the .NET developer. And, since this is an Apache project we're talking about, all our code is obviously open source.

A couple of years ago the announcement of Microsoft making a major contribution to an open source project would have been sensational news, but things have moved on a little bit since then. Now it's just another day's work at Microsoft.

As the manager of this effort at Microsoft, I'd like to talk a little about what we bring to the open source table. We joined the Apache Qpid project, which was essentially focused on Linux, to help the community develop a port on Windows and integration with the .NET stack.

That was reflected both in the code itself and also in the build environment it used (autotools). One of the areas where we invested was the introduction of a cross-platform build and test environment (CMake), so as to smooth the way for cross-platform work.

We have continued to adopt our typical product development quality assurance mechanisms when working with open-source. These include team-based design and code reviews. We also use automated code-quality tools, such as StyleCop, to ensure consistent style and to detect common programming errors.

We developed the initial version of the WCF Channel on a private Subversion repository and used a private bug database for logging issues and work items. Now we have made the initial drop to the community, we intend to do all revisions in the Apache repository and switch to using the community Jira-based bug tracking system.

Today we have a group of 5 engineers working with Qpid, both vendors and full-time Microsoft employees. Over time, it's our goal for many of these folks to achieve committer status on the project.To date, we've worked on the following work items:

The port of the C++ broker and client library to Windows
Introduction of the CMake-based cross-platform build and test environment
Windows Communication Foundation (WCF) Channel to provide a first class AMQP experience for the .NET developer
Improved packaging for Windows, including adding DLL support and a Windows installer
In progress: Persistence provider for Windows leveraging SQL Server and the Common Log File System (CLFS)

Starting soon:

SSL support on for the Windows client library and broker

For me, leading AMQP initiative at Microsoft has been quite a learning experience. Our collaboration with the community has been strong and we have received full support from our executives.

Here at Microsoft we understand that AMQP can become the SMTP for Messaging. This means AMQP is going to have a huge beneficial impact on all kinds of users in the years to come, and we want to help make that happen.

Helping develop the open source AMQP reference implementation at Apache Qpid as part of a broad community effort is our way of moving the AMQP ball forward. I'll have a lot more news to report about our efforts in the months to come.

Zend Launches Open Source Initiative to Drive Cloud Application Development

Peter Galli — Tue, 22 Sep 2009 14:00:00 GMT

Today, Zend Technologies announced the Simple API for Cloud Application Services project, which is a new open source initiative that allows developers to use common application services in the cloud, while enabling them to unlock value-added features available from individual providers.

This new project is designed to encourage widespread participation and contributions from the open source community, resulting in the availability of Simple Cloud API adapters for virtually all major cloud providers.

Zend, Microsoft, IBM, Nirvanix, Rackspace and GoGrid are all co-founding contributors to this community project, which aims to facilitate the development of cloud applications that can access services on all major cloud platforms and whose initial goal is to provide a set of programming interfaces for PHP developers to facilitate the development of applications that have basic cloud storage needs.

The first deliverables will include interfaces for file storage, document database, and simple queue services from platforms like Amazon Web Services, Windows Azure, Nirvanix Storage Delivery Network and Rackspace Cloud Files, allowing developers to deploy software applications to access services in these environments without making time consuming and expensive changes to their source code.

As Andi Gutmans, the CEO at Zend Technologies, notes in the press release announcing the project, "cloud computing offers irresistible value to enterprises of all sizes, but the lack of portability across cloud application services for even the most basic operations has been an impediment to broader adoption of cloud services."

An initial Simple Cloud API proposal and reference implementation is already available now for community review and participation, while a technology preview of the PHP client libraries for Windows Azure can be found here.

Microsoft is also contributing Simple Cloud API adapters, along with the official PHP client libraries for Windows Azure storage, to future versions of Zend Framework. These adapters will allow applications to take advantage of many Windows Azure features through the Simple Cloud API interface, while Microsoft's client libraries will put Windows Azure innovations, such as transaction and partial upload support, at the fingertips of cloud application developers.

"The Simple Cloud API is an example of Microsoft's continued investment in the openness and interoperability of its platform. We're excited to see how this project will foster adoption of cloud computing platforms by PHP developers and hope that many of these developers are encouraged to use Windows Azure," Doug Hauger, the General Manager for Windows Azure, notes in the press release.

Microsoft's involvement started a few months ago, through our work with Real Dolmen on a Windows Azure SDK for PHP developers. This SDK has been submitted to the Zend Framework, and it now forms the basis of Microsoft's contribution to the Simple Cloud API project.

As Vijay Rajagopalan, a Principal Architect at Microsoft, notes in his blog, the Zend Adapter for Windows Azure will leverage Microsoft's contribution. PHP developers will now be able to program against Windows Azure - in a way that is consistent with other cloud platforms - by tapping into the main features of Window Azure Storage.

Those PHP developers who need to use specific Windows Azure features not included in the scope of the Simple Cloup API (like transaction), will be able to combine the Zend Cloud Adapter with the dedicated Windows Azure SDK for PHP.

"This will allow developers to use common application services in the cloud, while enabling them to unlock value-added features available from individual providers. Simple API for Cloud also gives PHP developers more choices, and this is a great opportunity for them to think about using Windows Azure," he says.

Windows Live Embraces the Activity Streams Open Standard

Peter Galli — Fri, 04 Sep 2009 16:52:00 GMT

More good news with regard to Microsoft's embrace of open standards, this time out of the Windows Live group.

The Windows Live team is using a developing open standard called Activity Streams - an extension to the Atom feed format - which kicks in when users add Web Activity for Facebook and bring their status, photos, shared links, and more from Facebook into Windows Live to share in Messenger, Hotmail, and on their Windows Live Profile.

As Windows Live Program Manager Rob Dolin notes in a post on the team blog, what you may not know is that when you add the Facebook Web activity, the data is passed from Facebook to Windows Live using the developing Activity Streams open standard.

"With hundreds of thousands of users since release a few months ago, the Windows Live web activity for Facebook might be the largest implementation of Activity Streams today ... Just as many of our other web activities leverage community standards like RSS 2.0, Atom 1.0, and MediaRSS, I'm hopeful that Activity Streams will be a powerful enabling technology so users can bring their activities like status updates, posted photos, or shared links, from one service to another. We look forward to working with other partners to enable our mutual users to share their activities between services," Dolin says.

You can add the Web Activity for Facebook application here.

Tuxera Signs File System IP Agreement with Microsoft

Peter Galli — Wed, 26 Aug 2009 12:21:00 GMT

Tuxera, a Finnish company that develops NTFS drivers, has entered into a file system IP agreement with Microsoft in the area of data portability for devices

The agreement gives Tuxera access to the exFAT specifications and source code, as well as testing and verification tools, and the company will develop exFAT drivers for host device manufacturers. The company will also join the Interoperability Vendor Alliance.

While this is also the first-ever file system IP agreement that Microsoft has signed with an independent software vendor, Tuxera joins a growing number of companies entering into the exFAT Program.

The Extended File Allocation Table (exFAT) is a new file system that is better adapted to the growing needs of mobile personal storage. It allows a common file system to be used across all platform and devices that implement exFAT, which allows for data portability.

It also handles not only large files, such as those used for media storage, but also enables seamless interoperability between desktop PCs and devices like portable media devices, cameras or even kitchen devices so that files can easily be copied between desktop and device.

"Adding exFAT into our product portfolio is the logical step to help our customers to solve their interoperable file systems needs. Microsoft supports exFAT as the first-choice for many Windows interoperability needs including flash memories in consumer devices. exFAT is for example an integral part of SDXC formats, and the driver is good for flash drives, including devices that use SDXC cards," says Tuxera CTO Szabolcs Szakacsits

For his part, Mikko Välimäki, the company's CEO, believes that his company's ongoing collaboration with Microsoft ensures seamless file system interoperability into the future.

"We were the first to offer exFAT drivers based on our first-hand access to specifications and source code.We are also licensing exFAT drivers to device manufacturers, we are joining Microsoft's partner program, and have also announced a new product: Tuxera exFAT for Embedded Systems, which will be first available for Linux, but we can also port the product to proprietary platforms," he says.

The IP agreement the company has signed with Microsoft is consistent with Tuxera's business model, which is to integrate and license commercial, high-performance versions of its file system drivers to customers, as well as to provide support, maintenance, and product updates, Välimäki says.

The PHP Toolkit for ADO.NET Data Services

Peter Galli — Fri, 21 Aug 2009 11:00:00 GMT

Today, the DPE Interop team at Microsoft released a new open source project that bridges PHP and .NET using REST.

Specifically, the PHP Toolkit for ADO.NET Data Services was made available, which makes it easier for PHP developers to take advantage of the ADO.NET Data Services, a set of features recently added to the .NET Framework.

The PHP Toolkit for ADO.NET Data Services is an open source project funded by Microsoft and developed by Persistent Systems. It is available on CodePlex today.

These services, which were previously referred to by the codename Project Astoria, expose a wide range of data sources through a RESTful service interface.

There is full support for ADO.NET Data Services in Visual Studio 2008 SP1 as well as in the upcoming Visual Studio 2010, which includes direct support for both creating and consuming data services directly from the development environment.

Read more about all this on the Interoperability blog, and watch the Channel 9 video interview with Claudio Caldato, Senior Program Manager in the Interoperability Technical Strategy team, and Pablo Castro, software architect of ADO.NET Data Services.

This is yet another example of Microsoft's continued commitment to openness and interoperability as well as of its embrace of Web standards in its technologies.

The ECMA C# and CLI Standards

Peter Galli — Mon, 06 Jul 2009 17:27:00 GMT

I have some good news to announce: Microsoft will be applying the Community Promise to the ECMA 334 and ECMA 335 specs.

ECMA 334 specifies the form and establishes the interpretation of programs written in the C# programming language, while the ECMA 335 standard defines the Common Language Infrastructure (CLI) in which applications written in multiple high-level languages can be executed in different system environments without the need to rewrite those applications to take into consideration the unique characteristics of those environments.

"The Community Promise is an excellent vehicle and, in this situation, ensures the best balance of interoperability and flexibility for developers," Scott Guthrie, the Corporate Vice President for the .Net Developer Platform, told me July 6.

It is important to note that, under the Community Promise, anyone can freely implement these specifications with their technology, code, and solutions.

You do not need to sign a license agreement, or otherwise communicate to Microsoft how you will implement the specifications.

The Promise applies to developers, distributors, and users of Covered Implementations without regard to the development model that created the implementations, the type of copyright licenses under which it is distributed, or the associated business model.

Under the Community Promise, Microsoft provides assurance that it will not assert its Necessary Claims against anyone who makes, uses, sells, offers for sale, imports, or distributes any Covered Implementation under any type of development or distribution model, including open-source licensing models such as the LGPL or GPL.

You can find the terms of the Microsoft Community Promise here.

I told you this was good news!

Microsoft, NASA and Open Source

Peter Galli — Tue, 02 Jun 2009 15:05:00 GMT

There has been some renewed media interest in the NASA Space Act Agreement with Microsoft, which was signed earlier this year.

Microsoft signed that agreement so as to provide an umbrella framework of contractual terms that allows for a variety of cooperative projects. At the same time, we also entered into a project agreement that had an initial project to write code that would allow for the conversion of a lot of data about the planets (the planetary data system) and Martian survey information (LROC) into the World Wide Telescope (WWT) format.

WWT is an online program that pulls together images from across space and which lets users use their computer screens to traverse the universe.

Conversion of the information into the WWT format Tessellated Octahedral Adaptive Subdivision Transform (TOAST), allows the data to be viewed in both the WWT client and a newly developed Silverlight version of the client that supports multiple platforms, while other clients can also implement TOAST. The WWT is a freely downloadable Windows client application.

TOAST displays flat images, like those from telescopes,on representations of spherical objects like planets and moons, on a computer screen. One of the primary reasons for adapting the TOAST format for WWT was that it can accurately render the celestial poles with little distortion.

The traditional Mercator projection that is used by Google Earth and Sky in Google Earth cannot accurately render terrain or the sky within 15 degrees of the poles. TOAST is able to accurately render the sky and polar regions of the sky, Earth and planets with little distortion, which was important to both WWT and NASA.

The intent all along was also to make the conversion utilities that were developed for this initial project available under an open source licensed distribution. This is part of Microsoft's Open Edge strategy, which allows for the extension of the platforms that we provide to the community, by the community, in cooperation with the leading domain authorities - in this case NASA.

The WWT platform is the best astronomical data visualization technology available, and it makes sense that the most knowledgeable members of the community should be able to extend the platform with a variety of components under a mixture of licensing models.

As Alyssa Goodman, a Professor of Astronomy at Harvard University, says: "If only we could travel faster than the speed of light, we could leave our solar system, go past the nearby stars of our galaxy, leave the Milky Way and visit the many galaxies beyond. Until then more and more incredible telescopes, including this WorldWide Telescope, will continue to let us marvel at the wonders of the Universe."

Helping Facilitate Open Government

Peter Galli — Wed, 06 May 2009 19:03:00 GMT

Microsoft will announce on May 7 an initiative to help government agencies and developers publish and interact with their data in Windows Azure, the company's cloud computing platform.

One of these is the Open Government Data Initiative (OGDI), a cloud-based approach to housing public government data in Windows Azure, making it accessible in a programmatic manner via open standard protocols and application programming interfaces.

The source code for OGDI is being made publicly available through CodePlex, Microsoft's open source hosting site, so that developers may reuse it and provide feedback. Sample code is also being provided for technologies widely used on the Web, including PHP, Python, Flash, JavaScript, and Silverlight.

This initiative helps to provide government with tools focused on increasing responsiveness and access to critical services, streamlined processes and services.

For their part, Microsoft and its partners have developed a robust enterprise architecture approach that enables agencies to meet the technology requirements of government mandates with a familiar set of tools - built on an enterprise-ready, scalable, and easily-managed software-powered architecture.

So, in short, the goal of ODGI is to reduce the cost of publishing government data, and simplifying data access by leveraging cloud computing and open standards.

More information on Microsoft's Open Government Data Initiative can be found here.

To see an implementation of a data service in Windows Azure, using a sample of publicly available government data, visit this reference beta site.

These moves are part of Microsoft's ongoing open government efforts aimed at helping government organizations meet goals of transparency, participation and collaboration, particularly as an ever increasing amount of data becomes necessary and available.

As such, new methods need to be opened up to allow interaction with that data, and Microsoft's OGDI is designed to help public sector entities meet these goals.

This software, which underscores the importance of programmatic access to government data rather than having to download it, will give developers the ability to write programs that access data via Web-friendly programming methods without having to download or host the data; and let them write applications using any technology via open standards.

It also provides easier access to a broad array of government datasets, enabling the building of new and unique applications, while governments will be able to automatically refresh data without having to buy and maintain servers.

Cloud computing is the ideal platform for government data, and the technology is finally available to make it happen, says John Miri, Senior Fellow at the Center for Digital Government.

"The qualities that government looks for in an information management platform - things like flexibility, scalability, security, performance, and cost efficiency - are all better in a cloud model. As we see demands for government to become more transparent, collaborative, and interactive, a shift like this in technology architecture just has to happen, " he says.

For governments to become truly open, citizen access to public data in standards-based and interoperable ways is essential at all levels of government.

Given that most federal, state, local and education entities implement the American Recovery and Reinvestment Act (ARRA), they can meet open government goals of oversight, transparency and accountability through cloud and on-premises solutions such as Microsoft Stimulus360, which helps public sector agencies track, measure, and share information about federal stimulus programs through graphical dashboards and maps.

ECMAScript Candidate Specification Published

Peter Galli — Fri, 10 Apr 2009 19:50:00 GMT

The candidate specification of the ECMAScript language standard - known as ECMA-262, was published on April 9.

ECMAScript is the scripting language used to create web pages with dynamic behavior, and is more commonly known as JavaScript. It is a component of every web browser and is an essential aspect of interoperability.

The ECMAScript standard is "one of the core standards that enable the existence of interoperable web applications on the World Wide Web," Ecma International, which develops standards for Information and Communication Technology, said in a media release.

This candidate specification, the PDF of which is available here, will now undergo interoperability and web compatibility testing, and will likely be submitted to the Ecma General Assembly for ratification as an Ecma standard before the end of 2009.

ECMA is inviting technical experts to review this candidate specification and submit feedback here by July 15, 2009.

This latest revision of ECMA-262 will now be known as ECMAScript, Fifth Edition and not under the previous working name ECMAScript 3.1.

The Fifth Edition codifies de facto interpretations of the language specification that have become common among browser implementations and adds support for new features, ECMA said.

The ECMAScript, Fifth Edition candidate specification has been developed by Ecma TC39, whose membership includes all major browser vendors.

These members will now create and test implementations of the candidate specification to verify its correctness and the feasibility of creating interoperable implementations and for web compatibility testing to ensure that the revised specification remains compatible with existing web applications.

TC39 members Opera, Mozilla, and Microsoft have each committed to participating in this testing process, which should be finished by the middle of July, and that a final draft of the specification can be agreed upon in September for submission to the Ecma General Assembly for final approval in December 2009.

ECMA also expects this to result in a fast-track submission to ISO/IEC JTC 1 for revision of ISO/IEC 16262.

"We expect the Fifth Edition to benefit all web developers by helping improve browser interoperability and making enhanced scripting features broadly available," said Allen Wirfs-Brock, Microsoft's ECMAScript architect. Read more about all this on Microsoft's JScript team blog.

The last major revision of the ECMAScript standard was the Third Edition, published in 1999 and work on future ECMAScript editions continues as part of the ECMAScript Harmony project.

Integrate Your IT Environment

Peter Galli — Thu, 02 Apr 2009 21:41:00 GMT

Microsoft is embarking on a 15-city road show to help customers learn more about available solutions that may address their unique interoperability needs.

This is just another of the many ways Microsoft continues to respond to customers working in heterogeneous environments, a mission that was enhanced by the announcement of our Interoperability Principles last year.

The road show is being organized by Microsoft TechNet, and will stop in cities from Mountain View on the West coast to Denver, Atlanta and Chicago as well as Philadelphia, Boston and New York on the East Coast.

The rationale behind these events is simple: many customers work in heterogeneous environments that include Microsoft technologies as well as those from MySQL, Apple and Linux. As such, integration becomes vital in order for their core business applications to maintain business flow and efficiency.

Each event will last four hours, during which three sessions will be offered: Windows Server 2008 Active Directory Interop with Linux and OS X; running Open Source Software on Window Server 2008; and SQL Server 2008 and PHP Web Application Infrastructure.

This program aims to increase understanding of the heterogeneous IT landscape and discuss practical interoperability solutions.

It also complements Microsoft's existing engagement in interoperability at many levels - through its ongoing participation in industry and internal development projects and standards bodies, as well as its publication of technologies under open licenses and strong collaboration with customers, governments and partners.

We hope you'll join us at one of these events!

Brazilian Students Set Their Own Course

Mark Stone — Mon, 16 Mar 2009 19:05:00 GMT

I’m going to tell a story that starts in Indiana, but really it’s about Brazil.

Once upon a time “scientific computing” was nearly synonymous with “Fortran”. Today, though, just about any high level language can be used to write High Performance Computing (HPC) applications. These days that language choice also includes C#.

At Indiana University, the Open Systems Lab has pioneered work to implement Message Passing Interface (MPI) support for .Net, so that MPI applications can be written in C#. The project is MPI.Net, and you can find it on Codeplex. It is open source, about three years old, has reached a 1.0 release, and is compatible with two other important open source projects, OpenMPI and Mono. The principle developers behind the project are Andrew Lumsdaine at Indiana University and his former student, Douglas Gregor, who is now on the faculty of Rensselear Polytechnic Institute.

This is the kind of open source work that’s really exciting to see because of the way it expands choices for the developer and the end user. A C# developer should not be closed off from writing HPC applications if that’s what they want to do. And a research scientist should not have to think about whether their lab is running Linux or Windows Server. Both of these individuals are working enough layers above the operating system that somebody else’s operating system choice should not be a constraint.

So I was very excited to learn that students in Brazil at Federal University of Rio Grande do Sul were doing work on MPI, and excited to talk with them about their work. One of their projects is MPI#, also open source and also hosted on Codeplex.

MPI# builds on top of the work of MPI.Net, adding some functionality not yet present in MPI.Net. Specifically, quoting from the project description:

The goals of this project would be to build upon MPI.NET in order to complement it with the features that are missing, mainly regarding collective communication. Either they could benefit from C# native support for such communication, either they could be programmed on top of the provided MPISend/MPIRecv encapsulations. C# and .NET features such as fault tolerance or dynamicity support would be studied, in other to turn the MPI# implementation robust in large, dynamic and heterogeneous platforms.

Two of the students working on MPI# are Ismael Stangherlini and Fernando Afonso. They are graduate students in computer science, working on projects affiliated with the Brazilian Interoperability and Open Source Software Development Nucleous. When I talked to them about their work on MPI# I was curious what their communication with Indiana University had been like. Their response: they had never been in contact with Indiana University; they simply downloaded the code for MPI.Net and started working on their own.

That’s the magic of open source: that they can, in fact, just download the code on their own and start coding against it. They may make an important contribution to MPI.Net. Or their code may be entirely disregarded. Or they may move on to other projects and somebody else may or may not pick up where they left off. At this stage it’s too early to tell. But the fact that all of these scenarios are possible demonstrates why, as a methodology, open source is so nimble and adaptive. A top-down product development process, or a top-down standards development process can only execute on the innovations envisioned by the few at the top, and at the speed of the slowest decision-makers in the process. But a bottom-up open source process enables every innovation that anyone at the grass roots level can see.

OASIS Members Approve Nine Web Services Standards

Peter Galli — Thu, 05 Feb 2009 01:13:00 GMT

Members of OASIS, the international open standards consortium, have approved nine Web services specifications as OASIS Standards.

The WS Reliable Exchange (WS-RX), WS Transactions (WS-TX), and WS Secure Exchange (WS-SX) standards support reliable message exchange, coordinate the outcome of distributed application actions, and enable trusted relationships.

The three WS-RX standards - WS ReliableMessaging 1.2, WS ReliableMessaging Policy 1.2, and WS MakeConnection 1.1 - allow messages to be transferred reliably despite failures in software components, systems, or networks. They enable a broad range of features, including ordered delivery, duplicate elimination, and guaranteed receipt.

The three WS-TX standards - WS-Coordination 1.2, WS-AtomicTransaction 1.2, and WSBusinessActivity1.2 - describe an extensible framework for coordinating transactions across a mixed vendor environment, while the three WS-SX standards - WS-Trust 1.4, WS-SecureConversation 1.4, and WS-SecurityPolicy 1.3 - provide methods for issuing security tokens, establishing trust relationships, and allowing key material to be exchanged more efficiently.

All nine standards were developed under the Royalty-Free on RAND mode of the OASIS Intellectual Property Rights Policy, and participation in the WS-RX, WS-TX, and WS-SX Technical Committees remain open to all interested parties. You can read more in this OASIS release.

OASIS members include, among others, Microsoft, Oracle, Sun Microsystems, and Novell. Paul Cotton, the Partner Group Manager in Microsoft's Connected Systems Division, says that the standardization of these versions of the WS-SX, WS-RX and WS-TX specifications is a major step that finalizes the core Web services standards.

"The Web services standards offer mature support for critical customer enterprise scenarios, whether the protocols are used alone or in combination, thereby scaling from simple to complex scenarios," Cotton says.

In its drive for interoperability between different implementations on various platforms, Microsoft'sInteroperability Technical Strategy Team is already participating as a code contributor to an Apache project: the Stonehenge incubator project, which has been approved as an incubator project within Apache Software Foundation.

The WSO2 and Microsoft have already contributed code for a web-services based sample application, known as StockTrader, to this effort.

StockTrader is also just the starting point for the broader goals of Stonehenge, which aims to develop a set of sample applications to demonstrate seamless interoperability across multiple underlying platform technologies by using currently defined W3C and OASIS standard protocols.

Web Sandbox Source Now Available Under Apache License 2.0

Peter Galli — Tue, 27 Jan 2009 02:48:00 GMT

Microsoft has released more source code under an OSI-approved license: this time it has made the source code for the Web Sandbox runtime available under the Apache 2.0 open source license.

The Web Sandbox project explores how to advance the web platform to improve security, isolation, quality of service and extensibility capabilities for web developers and website users.

More information on the licensing details, as well as comprehensive documentation for experimenting and integrating with the Web Sandbox, can be found here.

But, while developers are being encouraged to help define and refine the Web Sandbox, it is not recommended for those developers creating production sites as it is still under development.

The Web Sandbox was created in response to limitations found in the current web platform, and is designed to explore potential solutions. Having a more secure and robust architecture as a foundational building block will help drive the next wave of Web innovation.

The Sandbox is a framework that works on most modern browsers that support the"ECMA-262, 3^rd Edition" (JavaScript) standard, and provides the same features in all modern web browsers. No browser add-ons or changes are required to leverage this technology. Beyond security, the Web Sandbox normalizes the different browsers and provides consistent W3C DOM support.

Since the initial release of Web Sandbox at PDC 2008, the team has received a lot of useful feedback from the web security community, and has also been collaborating with a number of customers, partners and the standards communities, all of whom want to adopt the technology when it is ready.

The goal? An open and interoperable standard that will help foster interoperability with complementary technologies like script frameworks and drive widespread adoption of the Web Sandbox.

This move is good news for Microsoft and the open source communities. But, it is important to note that while an Apache license is being used, the Web Sandbox project is not an Apache Software Foundation project and is not sponsored or endorsed by the ASF.

Microsoft does, however, already have an active relationship with the ASF. In fact, last year the company announced it had become a sponsor of the ASF so as to help enable the Foundation pay administrators and other support staff so that its developers can focus on writing great software.

Sam Ramji, the senior Director of Platform Strategy at Microsoft, also delivered a keynote address at ApacheCon in New Orleans last November.

Microsoft's Interoperability Technical Strategy Team already participates as a code contributor to the Apache Stonehenge incubator project; the company has also contributed a patch to ADOdb, a popular data access layer for PHP used by many applications and which is licensed under the LGPL and BSD; while Microsoft's Powerset team contributes to HBase, an open-source, column-oriented, distributed database written in Java.