We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Developing a Schematron-Owning Your Content Markup

Formal Metadata

Title
Developing a Schematron-Owning Your Content Markup
Subtitle
A Case Study
Title of Series
Part Number
15
Number of Parts
16
Author
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2012
Production PlaceWashington, D.C.

Content Metadata

Subject Area
Genre
Abstract
This paper will detail an organization's development and implementation of Schematron in its workflow process to cut down on errors as well as develop consistent markup across articles and journals. The process for developing the Schematron will be explored. This consisted of compiling error reports from 8 months of data as the basis for writing rules.The paper will examine how the Schematron was implemented into a Content Management System and broken up into Phases for the varied workflows of the organization. Upon content ingestion, files are validated against a specific Phase in the Schematron, based on the workflow, and reports are generated if any rules throw an error or warning.The results of the implementation of the Schematron will be summarized. A decline in errors was realized which reduced the average number of deliveries prior to online approval. The case study demonstrates how introducing Schematron into an XML workflow can help a publisher drive their content markup while reducing publishing delays and cost of corrections.