DHQauthor Schema

This document provides information and resources for authors on using the DHQ authoring schema to tag their own articles. Here's what you'll find on this page:

• Documentation at the Tag Library
• Schemas and other materials for download at Download Central
• How to get started with DHQ markup

Tools, samples, and other support

Elements and attributes supported by DHQauthor are documented in the Tag Library.

Sample encoded files are available at Download Central.

You can find tools for editing, file conversion, and other functions at the Tools page.

Information on how to get started

Other Useful Links

• Coordinate changes on DHQschemaDevelopment
• Read Getting Started with DHQauthor for step-by-step help
• Track Issues and Suggestions for DHQauthor
• Workspace: TEI Variances - which we will eventually refine into:
  • A list of changes to DHQ
  • An ODD "shell" for DHQ (TEI compliance!)
• Big picture stuff (for developers): start with Schema Requirements
• SkunkWorks for discussion of technical tasks and ideas for development

Design of the schema

The schema has a modular design intended to facilitate development by making maintenance and reuse easy.

The complete schema has two separable main modules, which can be graphed as follows:

1. DHQauthor.rng - the DHQauthor schema main module, which calls in
   • DHQauthor-header.rng - module for the header, which calls in
     • cc-license.rng - module for the Creative Commons license component of the header
2. DHQauthor-ready.sch - Schematron assertion set for additional validation

For convenience and to ensure all modules are successfully included when processing, all the files should be stored in the same subdirectory.

The main DHQauthor.rng module provides for structural validation of DHQauthor documents. Ordinarily, users should not have to be concerned with its submodules as long as they are present (though they may also be used separately).

The DHQauthor-ready.sch Schematron provides for validation of additional constraints, by providing warnings when certain conditions (either strict or loose) are not met over and above the basic DHQauthor tagging constructs. For example, if a cross-reference does not link correctly to a target, a document may still be formally valid to the DHQauthor RNG schema, but the lapse will be reported by the Schematron.

This design enables files to be valid to the Relax NG schema well before completion (and indeed, from the first moments of drafting). An author may find it useful, therefore, to validate to DHQauthor.rng while composing, and add validation to DHQauthor-ready.sch only when nearing completion to perform final checks.

Validating to both components warrants that a document has no "loose ends". ''Depending on editorial requirements, however, validation to every constraint expressed in the Schematron may not be demanded.'' (It will report warnings for certain conditions that are discouraged but not actually disallowed.) ''Validation against the Relax NG schema is, however, mandatory.''

How to help

• Making sample documents
• Contributing to discussions on dhq-tech (where you will probably be listened to) or dhq-publish (where actual decisions are more likely to emerge)
• Contributing to Issues and Suggestions
• Contributing documentation (help with this FAQ etc.)

Modifications log

for Release 2 [to be listed when 2 is released]

-- WendellPiez - 10 Sep 2006