Glossary

Scripture Burrito Concepts

A burrito is a wrapper that contains content and metadata. That wrapper may be made available in various digital formats, such as a zip file, an Amazon S3 bucket or a series of API calls. The term “burrito” describes the wrapper, not the distribution mechanism.

The metadata describes the contents of the burrito, including directory structure and ingredients.

Burritos currently come in four flavors:

Any flavor can also be derived from another burrito — for example, a back-translation derived from a source text translation. See Derived Burritos Specification.

You can create your own nonstandard flavors using the x- prefix; see Custom Flavors Specification.

Flavors are distinguished by their flavor type and reference system.

A reference system identifies the way that a resource is referenced and navigated. For instance, a resource may use BCV (book, chapter, verse).

Burritos contain ingredients. An ingredient is a file-like resource with a mime-type and, optionally, a scope or role.

Flavors are typically quite broadly defined. Additional constraints may be added using conventions, which are expressed in the metadata using the schema. For example, an audio convention may specify that audio files represent whole chapters of Scripture, or that they are arranged according to a specific hierarchy. Burrito creators should respect any convention they include in the metadata. Burrito consumers may use conventions to decide how or whether to process a burrito. The semantics of no specified conventions is caveat emptor, i.e. nothing should be assumed about the content of the burrito beyond what is specified for the burrito flavor.

Other Terminology

USFM stands for Unified Standard Format Markers.

USX stands for Unified Scripture XML.