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.

REST, Silverlight, and the New York Times

Posted by Jonathan Allen on May 12, 2009

Sections
Architecture & Design,
Development,
Enterprise Architecture
Topics
REST ,
Rich Internet Apps ,
Silverlight ,
SOA ,
.NET
Tags
JSON

In a effort to remain relevant in the increasingly difficult news industry, the New York Times has built a REST-based API through the Times Developer Network. Though still in public beta, there is already a rather extensive list of available APIs. Most APIs return both XML and JSON and are very well documented. Other REST providers would do well to emulate their standards.

  • Article Search API: Search Times articles from 1981 to today, retrieving headlines, abstracts and links to associated multimedia.
  • Best Sellers API: Get data from all New York Times best-seller lists, including rank history for specific best sellers.
  • Campaign Finance API: Get presidential campaign contribution and expenditure data based on United States Federal Election Commission filings.
  • Community API: Get comments by NYTimes.com users.
  • Congress API: Get U.S. Congressional vote data, including information about specific House and Senate members.
  • Movie Reviews API: Get links to reviews and NYT Critics' Picks, and search movie reviews by keyword.
  • New York State Legislature API: Get member and committee information for the New York State Senate and Assembly.
  • Real Estate API: Get aggregate data for real estate listings and sales in New York City.
  • Times Newswire API: Get links and metadata for Times articles in an up-to-the-minute stream.
  • TimesPeople API: Get TimesPeople profile and activity data.
  • TimesTags API: Get standardized terms that match your search query, and filter by Times dictionaries.

Currently the APIs are free, but there are numerous restrictions on the APIs. For example, only the Campaign Finance, Congress, and NY State Legislature APIs are licensed for commercial use. All other APIs are strictly limited to non-commercial, non-competing use. And of course there is no guarantee that fees won’t be charged in the future, presumably once they figure out how to make money off the thing.

In order to make it easier for developers to use these APIs, Microsoft and the New York Times are jointly offering the New York Times Silverlight Kit. As the name implies, this toolkit is heavily focused on promoting Silverlight and other Microsoft technologies. This are reflected in the project goals.

  • Make it easy for designers and developers to use the APIs with little to no coding: all XAML
  • Include Design-Time sample data to facilitate crafting experiences in Expression Blend and Visual Studio
  • Use the MVVM Design Pattern to separate components for test-ability and data binding.

Despite being tagged with the Microsoft Permissive License, the source code isn’t actually available at this time. Only the DLL and related debug symbols are in the 1.0.1 release.

  • This article is part of a featured topic series on SOA
New York Times Silverlight Kit Now Open Source by Michael Scherotter Posted
Re: New York Times Silverlight Kit Now Open Source by Paul Hunter Posted
  1. Back to top

    New York Times Silverlight Kit Now Open Source

    by Michael Scherotter

    We just published the New York Times Silverlight Kit with source code, unit tests, and demo code under the MS-PL license. It just took a while to get everything wrapped up and ready.

  2. Back to top

    Re: New York Times Silverlight Kit Now Open Source

    by Paul Hunter

    If the NY Times want's "to remain relevant in the increasingly difficult news industry" they should climb out of the ditch on the left-side of the political road and move to the center (is that to much to ask?) or maybe just the the left shoulder.

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.