Browse Prior Art Database

A Process and Tools for Multi-Modal Authoring of Web Content

IP.com Disclosure Number: IPCOM000123893D
Original Publication Date: 1999-Jun-01
Included in the Prior Art Database: 2005-Apr-05
Document File: 4 page(s) / 168K

Publishing Venue

IBM

Related People

Li, Y: AUTHOR [+4]

Abstract

HTML/XML based content authoring tools are becoming increasingly popular due to their ability to provide scaffolding support that eases the learning curve and development time required to create web pages and web sites. One problem that exists today with these tools, however, is that they focus on providing support for a single modality, that being the notion of hypertext and images. For example, when a user uses a content authoring tool to create a heading, he or she is usually given the option of six different headings to choose from. These six choices correspond to the six heading choices supported by HTML. As new devices with varying capabilities emerge, the user may desire that the heading be rendered in a different modality such as audio for devices like smart phones.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 39% of the total text.

A Process and Tools for Multi-Modal Authoring of Web Content

   HTML/XML based content authoring tools are becoming
increasingly popular due to their ability to provide scaffolding
support that eases the learning curve and development time required
to create web pages and web sites.  One problem that exists today
with these tools, however, is that they focus on providing support
for a single modality, that being the notion of hypertext and images.
For example, when a user uses a content authoring tool to create a
heading, he or she is usually given the option of six different
headings to choose from.  These six choices correspond to the six
heading choices supported by HTML.  As new devices with varying
capabilities emerge, the user may desire that the heading be rendered
in a different modality such as audio for devices like smart phones.
In a similar fashion, a user may have a video version of content, but
for some devices this content may need to be rendered as a static
jpeg image.  Moreover, on some devices with limited capabilities, an
audio description should be rendered in lieu of the video.  Thus, the
user would benefit from a content authoring tool that aids him or her
in the authoring of  content in multiple modalities.  In addition, it
should be possible for the content authoring tool to permit a user to
author content once, and to then automatically generate several
versions of content which, due to the modalities selected, are better
suited for various devices than what would have been normally created
by a single modal content authoring tool.  Moreover, the content
authoring tool should permit the user to preview what the variety of
generated content will look like on a particular device just like is
now possible when single modal content is generated.  In this
disclosure, we present a process and toolkit methodology which more
appropriately addresses the above requirements of multi-modal
content authoring.

   In this solution, we assume the content being authored is
XML.  Nonetheless, the solution presented herein could be used to
author well formed versions of HTML such as XHTML, an emerging W3C
standard.  Our solution enables multi-modal content authoring to be
supported through the use of a novel preprocessing mechanism for XSL
processing engines.  This mechanism permits multiple actions to be
associated with each pattern instead of only permitting just one
action associated with each pattern.  The preprocessing mechanism
selects a single action to be associated with each pattern.  The
action selected is based upon a lookup scheme which permits each
action to be associated with a presentation level.  Each presentation
level will typically correspond to a particular device or a string of
attributes which describes a particular device that is desired to be
supported.  For example, suppose we have the following XML content:
  <RECORD>
  <NAME>
  smith
  </NAME>
  <BALANCE>
  500
  </BALANCE>
  <ACCOU...