InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Microsoft is to Release Open-Source Compatible XAML/WPF Specs

Posted by Jonathan Allen on Apr 03, 2008

Sections
Development
Topics
.NET ,
Rich Client / Desktop
Tags
XAML ,
WPF

Microsoft has released an early draft of the specifications for XAML and WPF under the Microsoft Open Specification Promise. This offers patent protection for implementers against claims by Microsoft, allowing open source projects to use the specifications.

The Microsoft Open Specification Promise essentially says that if Microsoft has a patent on a covered specification, then the patent will never be enforced against any implementation of said specification. They do not however promise to indemnify implementers against non-Microsoft patents.

Microsoft irrevocably promises not to assert any Microsoft Necessary Claims against you for making, using, selling, offering for sale, importing or distributing any implementation to the extent it conforms to a Covered Specification (“Covered Implementation”), subject to the following. This is a personal promise directly from Microsoft to you, and you acknowledge as a condition of benefiting from it that no Microsoft rights are received from suppliers, distributors, or otherwise in connection with this promise. If you file, maintain or voluntarily participate in a patent infringement lawsuit against a Microsoft implementation of such Covered Specification, then this personal promise does not apply with respect to any Covered Implementation of the same Covered Specification made or used by you. To clarify, “Microsoft Necessary Claims” are those claims of Microsoft-owned or Microsoft-controlled patents that are necessary to implement only the required portions of the Covered Specification that are described in detail and not merely referenced in such Specification. “Covered Specifications” are listed below.

This promise is not an assurance either (i) that any of Microsoft’s issued patent claims covers a Covered Implementation or are enforceable or (ii) that a Covered Implementation would not infringe patents or other intellectual property rights of any third party. No other rights except those expressly stated in this promise shall be deemed granted, waived or received by implication, exhaustion, estoppel, or otherwise.

The XAML specifications are divided into two parts. First is the Xaml Object Mapping Specification. This defines the XAML language itself and focuses heavily on parsing. The second specification is the WPF Xaml Vocabulary Specification. This covers the objects found in the Windows Presentation Foundation. Unlike the Object Mapping specification, the Vocabulary specification is more of an outline that a true specification at this stage.

RE: more outline than specification by Rob Relyea Posted
  1. Back to top

    RE: more outline than specification

    by Rob Relyea

    Yes, the Vocabulary specification is not yet totally complete...we want feedback on our first published version. It is missing several TextSyntax descriptions. Beyond that, we'd love to understand what else you think is lacking that makes it more of an "outline". Please do understand, it is meant to describe WPF's file format, not WPF in its entirety.



    Please feel free to give any details via comments on this blog post:

    InfoQ: Post about Xaml/WPF Xaml Vocab Specs



    Thanks, Rob Relyea

    Architect, Microsoft, WPF/Xaml Team

    robrelyea.com
    | /blog | /wpf
    | /xaml

Educational Content

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.

Beauty Is in the Eye of the Beholder

Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.

Architecting Visa for Massive Scale and Continuous Innovation

John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.

Max Protect: Scalability and Caching at ESPN.com

Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.

The Seven Deadly Sins of Enterprise Agile Adoption

Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.

Questions for an Enterprise Architect

Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?

Wrap Your SQL Head Around Riak MapReduce

Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.