Use Cases

  1. Scripture Burrito is designed first and foremost for data interchange between ecosystems, although creators and consumers may also choose to use some or all of the format internally.
  2. Scripture Burrito is a Bible-lifespan format. In other words, it is intended to be used from the start of the translation, through checking and community testing, into publication via multiple toolchains, and then through revision processes.
  3. Scripture Burrito supports non-text formats as first-class content. In other words, the model is not “text plus multimedia”. In some cases text may play a secondary role or even be absent (eg in the case of oral translation or sign-language projects).
  4. Scripture Burrito assumes the existence of ecosystem servers that provide ids for users, organizations and projects, and stores information to enable that server-hosted context to be discovered.
  5. Scripture Burrito is intended to allow lossless roundtripping of projects between ecosystems. This depends to some extent on references to ecosystem servers that enable reconnection with different ecosystem-specific contexts.
  6. Scripture Burrito supports Scripture content, but also Scriptural content (eg glosses) and Scripture-related content (eg commentaries, translation manuals).