Orange Activity in Content Adaptation

1
Orange ActivityinContent Adaptation

• Barry Haynes / Matthew Clough Orange UK
• Presentation for W3C DIWG Workshop - October 12th
  2004

2
Activity

• Orange have an in-house Orange Mark-up Language
  OML.
• Evolved to its current state as a result of
  collaboration between Orange in the UK, Orange in
  France and France Telecom.
• Orange ML has to support content adaptation
  across multiple platforms.
• At the same time we have to provide an avenue for
  migration to industry standards as they emerge.

3
section twoRequirements
4
Key Requirements (1)

• Orange key requirements are
• A device agnostic mark-up language for use
  across all Orange multimedia channels including
  Portal, SMS/MMS/Email Messaging, IVR services
• Applicable to any branded, co-branded or third
  party branded service.
• Provide multi-device facilities including
  content selection filtering and scoping, and
  multimedia adaptation images etc.
• Supported across all Oranges device-specific
  content platform(s) - for service development

5
Key Requirements (2)

• Orange graphical guidelines define many of the
  core elements within our portal.
• As such we need to
• Be able to support and render all the components
  described within these guidelines for all devices
• Provide support for the adaptation engine to
  control the quality of the rendering implicitly
  or explicitly
• Provide mechanisms to allow evolution of
  graphical components without impacting the code
  of the our partners

6
Key Requirements (3)

• Additionally we require the mark-up to
• Be easy to use AND straightforward transcode
  make adding the metadata worthwhile
• Provides XML combinations that
• Support rich conditional logic for content
  selection
• Support theming
• Support internationalisation, locales -
  country/language pairs.
• Support versioning etc.
• Also, ideally provide XML combinations that
• Supports structural growth of the schema
• Allows structural validation of page components
  if desired
• Help developers - avoid too many ways to do the
  same thing

7
section twoCapability
8
Current Capability Orange Mark-up Language

• Orange ML currently uses XHTML schema with
  modularisation to provide
• Document level metadata
• Document and element level theming
• Element level content selection based on context
  including
• Delivery channel
• Device Group Targeting
• Dynamic Targeting
• Bespoke Orange elements

9
Example Content Selection by Device Capability
  xmlns"http//orange.com/oml/3.0/oml"
xmlnsxsi"http//www.w3.org/2001/XMLSchema-instan
ce" xsischemaLocation"http//orange.com/om
l/3.0/oml ../schema/orange.com/oml/3.0/oml.xsd"
The ltblockgt
element xsitype"generic.type" Your
Games arget namejava typefeature namecol typefeature hrefgame.jadDownload
 
10
Example Themes at Document or Element Level
  xmlns"http//orange.com/oml/3.0/oml"
xmlnsxsi"http//www.w3.org/2001/XMLSchema-instan
ce" xsischemaLocation"http//orange.com/om
l/3.0/oml ../schema/orange.com/oml/3.0/oml.xsd"
themeorangeworld3 bannerid""The ltblockgt element readcrumbs Samples
ltblockgt element crumbs xsitype"generic.type" themesome_other_theme
  ... ... ...  
11
Current Capability - Platforms

• Comment Content adaptation platforms have
  evolved to support different approaches and
  different levels of adaptation.
• Specifically
• Authoring low, often element level, adaptation
  that optimises the device rendering
• Semantic high, often component level, adaptation
  that can provide rendering simplicity but can be
  restrictive.
• Orange have experience in both approaches

12
section twoFuture Evolutions
13
Future Evolution

• Orange evolution / roadmap
• More transparent meta-data to express semantics
• XHTML Version 2.0 ?
• Content selection via DIselect ?
• W3C standards alignment to assist our service
  development

14
thanks