Skip to main content
photo
 
Workflow Impact

The separation of content from style enabled us to effectively separate the functions associated with content and style. Now the content owners (subject matter experts, project managers, communications staff) could work on their content without the intermediary of a Webmaster or HTML coder. In other words, content would not be developed once in a word processing format and then redeveloped again in an HTML format and then likely redeveloped again and again for various HTML pages or browsers.

The content could now reside in one place only: the XML file. The XSL stylesheets determine how the content is presented in the various Web pages and browsers on which the content will be displayed. And the presentation is not restricted to Web pages. The XSL stylesheets can transform the XML file into HTML, PDF, RTF, WML - a variety of options - all working from a single XML file.

Figures 4 and 5 illustrate the workflow impacts in moving from an HTML-based Web architecture to an XML-based architecture. One of the advantages of using XML, as seen in these diagrams, is that it eliminates many dependencies and redundancies in the workflow, allows teams to work independently, and maintains a single source document (XML) with multiple deliveries (HTML, RTF, PDF, etc.).

Figure 4. Workflow (Simplified) in HTML-based Web Site Management

Figure 4. Workflow (Simplified) in HTML-based Web Site Management

Figure 5. Workflow (Simplified) in XML-based Web Site Management

Figure 5. Workflow (Simplified) in XML-based Web Site Management