How is the BNML Schema different?

Many general purpose DTDs or schema contain a vast number of elements in an attempt to provide a smorgasbord of elements for different types of content. It is also common for these schema to provide multiple ways to markup the same content, even down to the paragraph and list level. This approach makes it very difficult to train authors to use the schema and XML editing tools. It leads to very inconsistent markup usage by different authors and between documents by the same author. This causes problems for content re-use and automated rendering processes. It also makes rendering applications expensive to develop and difficult to maintain.

Using just a few elements, the Elkera BNML Schema defines a few simple patterns that can provide a generic representation of almost any narrative content of the kind found in technical, legal and business documents. The Elkera BNML Schema uses a recursive hierarchical model for the main narrative structure and is particularly suited to documents with numbered provisions, such as clauses in contracts and technical documents.

The simple, re-usable patterns defined by the Elkera BNML Schema mean that there is really only one way to markup most narrative content. This promotes much more consistent markup than is achievable with many other general purpose schema and it reduces the training and support needs of authors.