The Avaya content model provides an organizational framework for categorizing and organizing Avaya product content so that it can be delivered and reused in a variety of ways.
The Avaya content model defines the types of content we develop and the structure of that content, and is based on the principles of topic-based authoring, information typing, structured authoring, content relevance, and semantic intent.
The content model includes a collection of standard information types and deliverable standards:
Each information type represents one type of content that we create, at a topic level, and has a specific intent.
Each information type is made up of a series of content elements, in a prescribed order.
Each deliverable standard is designed to meet a specific need of one or more of our defined user types. The typed content topics are “mapped” into the standard outline. The standards are available in Compas and the supporting files are in SDL repository.
The content model is independent of any particular technology or tools. The technology and the tools are enablers; the content is still the focus. We can apply our model to different technologies and authoring tools. The content model is the foundation of what we do and sets us up for the future.
The goal of developing the content model is to enable us to create relevant, consistent content that supports our users’ goals, and supports our goals for our outputs in the future.
Metadata can also be applied to content at the element, topic, or map level. Metadata is information about the content, like audience, product, platform, and version. This information describes the context in which the content should be used. Metadata can be used during processing to filter content for outputs, to customize navigation, or to prepare search indexes, to name a few.
