As Corinthia Hotels explored a new communication vehicle to launch their brand new luxury hotel in the heart of London, Nucleus valiantly managed the creation and implementation of an interactive video showcasing Hotel destination information. The interactive video showcases an engaging video tour throughout London and provides future Corinthia Hotel guests an opportunity to explore places of interest by London Taxi.  By creating an immersive experience with Clikthrough’s Theater, the Corinthia website will drive more engagement with visitors and offer a deeper brand interaction while showcasing the new hotel location and surrounding attractions.

In order to achieve these results, Clikthrough was able to evolve our technology and drive further innovation.  Notably, Clikthrough partnered with Nucleus to implement full API integration, an inquiry-based carousel, and fully externalized P3 panels. What does this mean? Put simply, Clikthrough empowered our partners to manage all of their own data and allow real time updates to be implemented by Nucleus and Corinthia directly.  This new functionality and innovation provides advanced levels of customization and skinning for all future partners. 

We are very pleased with the interactive experience and look forward to telling a story in a new innovative way. We hope you enjoy the experience and look forward to seeing you at the Corinthia Hotel nearest you.

This is an industry first to show all the great places in the heart of London!

Experience Luxury @ http://www.corinthialondon.com/Location/

·         mini GiRLS SPiRiT music video: 

·         Fuji “pro-mmercial”: 

·         Häagen-Dazs “pro-mmercial”: 

·         Recochoku “pro-mmercial”: 

A special thanks to Avex and their sponsors for having the thought leadership to commission these videos and bring the power of interactive video to the forefront once again.

http://clikthrough.avex.jp/

Clikthrough worked closely with Autobytel to create a custom interactive player to launch the first twenty-five automotive videos.   As you explore the player, you will notice the left and right panels were specially customized to display the rich content that was developed for the virtual test drive videos.  Additionally, Clikthrough addressed a unique challenge within interactive video.  As users are enjoying an automotive video, it may become difficult for a user to clik a on a vehicle traveling around a race track at over 100MPH.  Our solution was to build Freeze Frame functionality that allows viewers to have more control over their interactive video experience by allowing them to freeze the frame of the video every time a viewer mouse’s into the video they are watching.  This solution will allow users to easily “clik” on the highlighted features of the car in the video.

In addition to launching the new Freeze Frame functionality, Clikthrough explored new ways of improving Search Engine Optimization (SEO).  In order to help Autobytel achieve a higher SEO value, Clikthrough worked with Autobytel to implement media RSS (MRSS) feeds into the Autobytel homepage.  MRSS feeds provide search engines an immense amount of data regarding the content of the videos and in turn will allow the videos to become indexed and searchable.

As we continue our partnership with Autobytel, we are excited to provide new innovative solutions for the automotive industry and to create a unique engaging and interactive experience.  As with any new technology, innovation is driven by key individuals that are willing to push the limits to create a better experience.  Autobytel has several members of the team that accepted such a challenge and we are humbled to join them in the quest for automotive innovation!

Driving Innovation @ www.autobytel.com

For those not familiar with Clikthrough’s API (application programming interface), this REST based web service allows 3rd party partners to access, add and update videos, P3 details (products, people, places), and other extended video information in the Clikthrough Interactive Video Platform (IVP). 
 
Key features:
o Simplified object attribute names to create consistency and readability across the entire API
o Reduced each API response size by 20-45%
o Matched inputs and outputs allows for easy verification of uploaded data, and simpler 3rd party integration
   • Performance improvement of 10% across all data calls
   • Improved Security Policy – allows multiple companies to share the ownership of video and P3  details thus allowing multiple groups to edit/update the information associated with a video
   • Enhanced Meta-data – more attributes have been added to core P3 (products, people, places)
o Places – Geo positioning tags (latitude and longitude)
o People – Twitter Name
o Products – ISBN (for books and other media)

These key improvements have also attracted two of our partners to build CMS plug-ins to support Clikthrough API integration directly into their existing CMS platforms.  This achievement has allowed our customers to update product information/availability, and specific events happening at local places seen in videos. We are very excited to offer the API integration to our partners and look forward to launching new features and additional support.

Below is a link to a video interview with Abe McCallum on the future of Interactive Video!

http://thetvoftomorrowshow.com/video/abe-mccallum-clikthrough-tvot-2010

Clikthrough has developed the oEmbed functionality within our website framework which allows consumers to post embedded interactive videos directly into a message or wall post on Facebook, WordPress, and other oEmbed enabled consumers.

Additionally, Clikthrough has partnered with and been approved by all major social network sites to embed Clikthrough interactive video’s directly on the 3rd party pages. Clikthrough is among an esteemed group approved for this technology and joins the ranks of YouTube, Vimeo, Hulu and Flickr. 

To give you a better idea of how this technology works, I have outlined a few screen shots below:
1.  User shares a video page found on Clikthrough.com (or any of our oEmbed enabled clients) to Facebook.

2.  The user writes a personalized message for their friends to see and at the same time, Facebook retrieves the video thumbnail and description from the Clikthrough page meta data.
3.  Once the user posts the message, Facebook will pull the information directly from the Clikthrough oEmbed API and will return a flash embed object of the interactive video. 
4.  When the user looks at the wall posting, there will be an interactive video thumbnail. Once clicked it will load the Clikthrough embed player inplace and allow for the consumer to engage with the interactive content directly within Facebook.  

For Clikthrough, the integration of the oEmbed technology represents a tremendous opportunity to help consumers more effectively share content and allow them to stay on their social network of choice. We are excited to continue pushing forward a deeply engaging and highly interactive video experience.

The A|X design team worked closely with Clikthrough to craft an exciting interactive multimedia presentation using the creative assets from the sultry Bodies of Summer advertising campaign. Throughout the experience, Clikthrough and A|X partnered to bring a new level of interactivity to traditional fashion advertisements.  In addition to viewing images, Clikthrough has enabled the consumer to go behind the scenes with the ad campaign’s models, hair stylists and make-up artists, listen to a custom A|X soundtrack, and get up to date information on how to purchase the featured fashions in the STYLEPAD.

Clikthrough is also very excited to announce the launch of a fashion first: Advertising Creation Tool (ACT), which allows site visitors to create their own advertising campaign images. These user-created ad images can then be shared via Facebook, MySpace, Orkut, Twitter and Digg. The ACT experience is a custom solution built for A|X to help facilitate a creative viral campaign element.  Clikthrough and Armani Exchange have continued to push the envelope of interactivity and will be launching additional emerging media projects this fall.

We are confident that our partnership and launch of the STYLEPAD and ACT will impact the fashion world and push the limits in interactive media.

You can see the STYLEPAD here:  http://www.armaniexchange.com/stylepad/summer2010.do

The NY Times did a special feature on the STYLEPAD.  http://mediadecoder.blogs.nytimes.com/2010/06/10/armanis-ax-brand-offers-quite-the-groovy-pad/

Along with this project, Clikthrough is proud to introduce a new social feature, Facebook Connect.  Facebook Connect allows viewers to use their Facebook account to login and make comments in the videos on Shops on Demand and add products to their personal wishlist. . With Elle Magazines help, we are one step closer to launching an interactive revolution across fashion, entertainment, and advertising. 

Stay tuned for additional partnership releases in the coming weeks. 

What is Internationalization?
Internationalization (shortened to 18n for most people that don’t want to type) is a work in progress for a lot of web technology companies.  Very few sites have a formal approach to supporting internationalization.

Key Terms:
I18n – internationalization – covers the changing of languages to match that of the user.  Keep in mind to overhaul an existing system you’ll need to replace navigation, error messages, tooltips or other helpers, and the big one… filter or translate all content.

L18n – localization – identifies the exact language and cultural settings for a user.  Each locale includes that region’s formatting of:
•    Dates
•    Times
•    Numbers
•    Currency (both value and representation/format)

Locale – A locale is best thought of as a region (usually within a country).  For instance, in Switzerland there are different regions within the country where German, French and Italian are the commonly spoken “local” languages.

ISO – The ISO (International Organization for Standards) is the world’s largest developer and publisher of International Standards.  Throughout this blog, we make heavy reference to the ISO and the standards that it has put out there regarding internationalization.

Confusion in the Implementation of ISO Codes:
As web user’s we see many internationalized websites with language/locale codes in their urls.  In some cases they’re added to the urls (url path or sub domain), and in other cases stored in session.  Some examples are:
-http://translate.google.com/translate_t?ie=UTF-8&text=test&sl=en&tl=zh-TW – uses correct ISO code format w/ a dash
-http://www.mag.com/ja_JP/mag.html - correct capitalization, using _ (underscore)
-http://de.wikipedia.org/ - they’ve included language code as a sub domain (de – Deutsch, German)
-http://zh.wikipedia.org/wiki/ this is actually wrong as it should be ch-ZH (Chinese – Simplified)

Confusion in the Definition of ISO Codes:
Wikipedia (http://en.wikipedia.org/wiki/Locale) defines the correct format as [language[_territory][.codeset][@modifier]].  For example, Australian English using the UTF-8 encoding is en_AU.UTF-8.

IBM (http://publib.boulder.ibm.com/infocenter/zos/v1r9/index.jsp?topic=/com.ibm.zos.r9.cbcpx01/locnamc.htm) defines convention as “<Language>-<Territory>.<Codeset>” yet the language/territory separator in all examples is an underscore (_).  Also, it lists language codes with the first character capitalized (which is against standards) and there is also an error in the documentation in the language_territory separator, they list it as  “Li-LT” (using a dash).

W3C  (http://www.w3.org/TR/REC-html40/struct/dirlang.html#langcodes) states that the language attribute’s value is a language code that identifies a natural language spoken, written, or otherwise used for the communication of information among people. Computer languages are explicitly excluded from language codes.  RFC1766 (published in March 1995) defines and explains the language codes that must be used in HTML documents.  Briefly, language codes consist of a primary code and a possibly empty series of sub codes.  For example:
language-code = primary-code ( “-” subcode )*

Here are some sample language codes: “en”is English and “en-US”: the U.S. version of English.

The Actual ISO/RFC Standards:
The original language code standard was RFC 1766.  That standard was superseded in January 2001 by RFC 3066 (http://tools.ietf.org/html/rfc3066).  RFC 3066 was superseded in September 2006 by RFC 4646 & 4647.

Popular vs Standards-Based Implementations:
Here in 2010, you would think that this issue would be resolved given the standards have been in place for over 10 years. Yet, there still seems to be confusion over the standard of coding localization/language codes.  In all the ISO specs dating from the 1990’s, everything was done with a “-“ (dash) separating the language and the territory (country) code.  However, in many modern implementations seen on the web, people are using a “_” (underscore) to separate the language and country codes.  The simple fix for us was to accept either separator in all externally facing interfaces/API’s (Application Protocol Interface).

Setting Things Straight:
Written in ISO code RFC1766, and subsequent amendments 4646& 4647 define the ISO code as follows:

[language[-territory][.codeset][@modifiers]]

In this example above, the language is in two lowercase characters as described in ISO639.  For example, en for English, ja for Japanese, and zh for Chinese.

Further, territory (country) is two uppercase characters as described in ISO3166.  For example, GB for United Kingdom (Great Britain), KR for Republic of Korea (South Korea), CN for China.

As you can see, there are a lot of ways to go wrong with internationalization and the language and locales are just the first part.  Stay tuned for more posts on internationalization here in the future.  To see an example of the internationalization work we have done, check out the Clikthrough player deployed on the www.MAG.com site.  Clikthrough is the only interactive video player in the market that supports over 20 languages.

http://www.youtube.com/watch?v=W_DExL3UBrQ