Content Transformation
- Content Transformation
- the
content management
task during which published
content
is transformed to the format specifically required for certain clients
As illustrated in the preceding figure, Content Transformation is part of the following inheritance hierarchy:
- Type: Concrete
- Superclass: Task
- Subclasses:
The typical responsibilities of Content Transformation are to:
- Transform HTML webpages to WML for transmission to
wireless clients (e.g., smart phones, PDAs) with limited
screen space, memory, and computational power.
- Transform content to XML for transmission to external
applications.
Content transformation typically can begin when the
following preconditions hold:
- The
construction phase has started.
- The initial conventions for content transformation (e.g.,
guidelines, standards) have been produced during the
process engineering activity.
- The following documents are largely complete and are
relatively stable:
- The
content management team has been adequately staffed and
trained in content transformation.
Content transformation is typically complete when the
following postconditions hold:
Content transformation typically involves the following
teams performing the following steps in an iterative,
incremental, parallel, and time-boxed manner:
-
Content Management Team:
- Determine the need for content transformation by
reading and understanding the associated:
- Informational (data) requirements in the:
- Information architecture:
- Content design:
- TBD
Content transformation typically can be performed using the
following techniques:
- Scripting
- Middleware technologies
Content transformation typically results in the production
of the following work products:
-
data components:
- Transformed Content:
- Textual content.
- Numerical content.
- Audio content.
- Graphical content.
- Video content.
- Content Metadata
- Content transformation should be performed iteratively,
incrementally, and in parallel with other content management
tasks.
- Content transformation occurs on an as needed basis.
- Content transformation is automated, typically by means
of scripts or middleware.
- The transformed content may be cached for future
use.
- Content transformation may not be necessary content is
only intended for a single client type.