api on SWiK

Cairngorm - Adobe Labs

Thu, 07 Aug 2008 16:10:30 -0700

Lift WebKit 0.9 API : Overview

Thu, 07 Aug 2008 13:23:19 -0700

maemo.org - Python-maemo-3.x: LibOSSO API for Python

Thu, 07 Aug 2008 13:23:17 -0700

oEmbed API

Thu, 07 Aug 2008 13:22:58 -0700

delicious/help/feeds

Thu, 07 Aug 2008 13:22:57 -0700

Yahoo Boss Is So Open, It Runs on Google’s App Engine

Thu, 07 Aug 2008 13:20:48 -0700

The webapp Framework - Google App Engine - Google Code

Thu, 07 Aug 2008 13:20:48 -0700

Google Apps Videos (Python platform)

Thu, 07 Aug 2008 13:20:48 -0700

Yahoo Radically Opens Web Search With BOSS

Thu, 07 Aug 2008 13:20:47 -0700

Google Jumps Head First Into Web Services With Google App Engine

Thu, 07 Aug 2008 13:20:47 -0700

Yahoo SearchMonkey Launches Into Private Beta

Thu, 07 Aug 2008 13:20:46 -0700

Yahoo! Search Blog

Thu, 07 Aug 2008 13:20:46 -0700

RabbitMQ - API Guide

Thu, 07 Aug 2008 13:20:30 -0700

AWS Service Health Dashboard - Aug 7, 2008

Thu, 07 Aug 2008 13:17:54 -0700

Java BibTeX API

Thu, 07 Aug 2008 13:17:20 -0700

Home - OpenAL

Thu, 07 Aug 2008 13:15:38 -0700

OpenAL is a cross-platform 3D audio API appropriate for use with gaming applications and many other types of audio applications.

Ogre Forums :: View topic - wxOgreMVC open sourced

Thu, 07 Aug 2008 13:14:46 -0700

joshua's blog: beyond rest

Thu, 07 Aug 2008 13:14:10 -0700

Bill de hÓra: Patterns of Web Architecture

Thu, 07 Aug 2008 13:14:08 -0700

Nearly definitive survey

Welcome to Agavi!

Thu, 07 Aug 2008 13:12:03 -0700

Developer's Guide/Javascript API - FCKeditor Wiki

Thu, 06 Jul 2006 13:33:18 -0700

Streaming API for XML - Java API for XML Processing (JAXP) Tutorial

Thu, 07 Aug 2008 13:08:23 -0700

PHP Software Development | PHP Programming | Outsourcing PHP Development India, USA, UK, Canada

Sun, 18 May 2008 22:46:09 -0700

PHP Programming, PHP Development, Outsourced PHP Development, PHP Development Company, PHP Software Development, PHP Application Development, Outsourcing PHP Development Company India, USA, UK, Canada, PHP Programmers, PHP, Joomla, Opensource Development _ Qualsoft Services Offshore Software development Company

Google Translation Center: The World’s Largest Translation Memory

Mon, 04 Aug 2008 18:12:08 -0700

Disclosure: I am the founder of Der Mundo, a multilingual blogging service and translation community that combines human and machine translation (provided in part by Google), and I have researched translation technology for more than 10 years via the Worldwide Lexicon project.

Blogoscoped reports that Google is preparing to launch Google Translation Center, a new translation tool for freelance and professional translators. This is an interesting move, and it has broad implications for the translation industry, which up until now has been fragmented and somewhat behind the times, from a technology standpoint

Google has been investing significant resources in a multi-year effort to develop its statistical machine translation technology. Statistical MT works by comparing large numbers of parallel texts that have been translated between languages and from these learns which words and phrases usually map to others — similar to the way humans acquire language. The problem with statistical MT is that it requires a large number of directly translated sentences. These are hard to find, and because of this SMT systems use sources like the proceedings from the European Parliament, United Nations, etc. Which are fine if you’re writing in bureaucrat-speak, but aren’t so great for other texts. Google Translation Center is a straightforward and very clever way to gather a large corpus of parallel texts to train its machine translation systems.

Part machine translator and part translation memory (a sort of search engine for translation that helps translators to recall translations), GTC will help translators by providing a free, global translation memory, and in turn drive costs down by reducing the amount of work needed to complete a text. It will help Google by providing an excellent source of high quality parallel texts that can be fed back into the statistical translation systems.

If Google releases an API for the translation management system, it could establish a de facto standard for integrated machine translation and translation memory, creating a language platform around which projects like Der Mundo can build specialized applications and collect more training data.

On the other hand, GTC could be bad news for translation service bureaus — especially those that use proprietary translation management systems as a way to hold customers and translators hostage. Most translation bureaus aren’t really technology companies and aren’t very competent at building quality software. Google Translation Center fills a void in the translation tools market that was created when the few independent companies, such as Trados, were acquired.

For freelancers, GTC could be very good news; they could work directly with clients and have access to high quality productivity tools. Overall this is a welcome move that will force service providers to focus on quality, while Google, which is competent at software, can focus on building tools. Google has a pretty mixed track record with consumer-facing services outside its core search business. But if it positions itself as a neutral service provider, it could enable projects like Der Mundo and others to create powerful and easy-to-use translation services for a broad range of industries.

Translation management is more complex than it appears, with different practices in different industries. If you’re translating a news story, you want minimal cost and fast turnaround time (publish early, correct often). If you’re translating a product spec sheet, you’re willing to spend more to have it done right before it goes to press. Google would be smart to position GTC as a utility for translators and to encourage service bureaus to standardize around it, much as it did around earlier tools like Trados, and much as it has done with their keyword ad business. That strategy would also eliminate a potential conflict of interest, as translation professionals are understandably wary of contributing to something that could put them out of work, as well as avoid channel conflicts with partners who will be their best advocates in selling to various clients.

While it’s my guess that Google has no intention of directly monetizing the service (charging a commission on transactions it brokers would expose Google to a billing and payment disbursal nightmare), the R&D value of collecting millions of parallel sentences in every language pair imaginable is indisputable, and it will pay off in unforeseen ways. So, my guess is Google will make this a free tool for the translation industry to use, and it will figure the money part out later. It can afford to be patient.

Translation is a very difficult problem. If it weren’t, it would have been solved a long time ago. I remain convinced that a multilingual web will be a reality in a short time, and that a menagerie of tools and services will emerge over the next few years — some geared toward helping translators, some toward building translation communities, and others that make publishing multilingual sites and blogs easy and intuitive.

As these emerge, the web will begin translating itself, and within a short time, we’ll be able to read content from sources worldwide just as we currently explore the web in our own language today.

Upcoming Reports Changes: August 19

Thu, 31 Jul 2008 15:05:51 -0700

We want to give developers a heads-up about an upcoming change affecting AdWords reports. If you retrieve reports via the AdWords API's getReportDownloadUrl() or getGzipReportDownloadUrl() method then these changes may potentially affect the data in your reports. These changes impact a small number of columns and should not fundamentally change the way you parse report data.

We plan on rolling out these changes on Tuesday, August 19.

The values returned by the following columns will be changing. Please note that some of these columns are only available for reports scheduled via the AdWords web interface, not the AdWords API, but we're listing them here in case you use the AdWords API to retrieve and process such reports.

CustomerTimeZone: the time zone information will be returned as, e.g., the previous "America/New_York" will change to "(GMT-05:00) Eastern Time".
Time aggregation columns: the columns representing the aggregation time period (e.g. weekStart) will represent date ranges in a different format. E.g. the previous "2008-06-01-2008-06-01" will now be returned as "6/1/08 - 6/1/08".
Keyword: values for category-based website criteria will change from, e.g., "docvertical::3" to "Animals >> Endangered Species". Values returned for keyword or non-category-based website criteria should not change.
Interactions: the name of reported interactions will change from, e.g., "VideoPlayTime25" to "Video Play Reached 25%."

There are also fixes to edge cases in which values for the impressions and the position preferences columns that were previously returned as invalid values should be more accurate.

If you would like to test your application against these changes ahead of time, please visit the AdWords web interface and log in as an account in which you normally would run reports. Visit the "Reports" or "Client Reports" tab, select an existing report from the list, and when viewing the report, use the "Export Report" button to download the report as a .xml file. This XML should match the report XML that you will retrieve via the AdWords API after the changes are put in place.

apiviz - Google Code

Sat, 26 Jul 2008 19:50:04 -0700

APIviz is a JavaDoc doclet which extends the Java standard doclet. It generates comprehensive UML-like class and package diagrams for quick understanding of the overall API structure

Open Source Hardware Presentation.pdf (application/pdf Object)

Sat, 26 Jul 2008 18:51:23 -0700

Scala Library

Sat, 26 Jul 2008 11:03:02 -0700

oEmbed

Sat, 26 Jul 2008 11:03:02 -0700

Xaj: Simple XQuery API for Java

Sat, 26 Jul 2008 11:00:43 -0700