The LombardPress Schema

• Introduction to the LombardPress-Schema
• Statement on Versioning

We adopt the following standard https://tools.ietf.org/html/rfc2119 for key words and definitions indicating compliance to the LombardPress-Schema specifications.

Documentation

• current release
  • critical
  • diplomatic
• current release on github (master branch)
  • critical
  • diplomatic
• the bleeding edge (develop branch)
  • critical
  • diplomatic

ODD Files

• current release
  • critical
  • diplomatic
• current release on github (master branch)
  • critical
  • diplomatic
• the bleeding edge (develop branch)
  • critical
  • diplomatic

Schema Files

• current release
  • critical
  • diplomatic
• current release on github (master branch)
  • critical
  • diplomatic
• the bleeding edge (develop branch)
  • critical
  • diplomatic

To submit a bug report, ask a question about how to encode a particular text, or make a feature request, please submit an issue here: https://github.com/lombardpress/lombardpress-schema/issues

We follow the git-flow model to structure our branching workflow: http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/. Following this model, the best way to contribute a pull request is to fork the main develop branch, create a feature branch (e.g. feature/new-element-description) and then submit a pull request for your feature branch to be merged back into the main develop branch.