> For the complete documentation index, see [llms.txt](https://bcds.gitbook.io/handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bcds.gitbook.io/handbook/digital-scholarship-methods/overview/tei.md).

# ¶ Textual Encoding Initiative

Textual Encoding Initiative (TEI) is a [consortium](https://tei-c.org/) and an [XML standardized markup language](https://www.w3schools.com/xml/xml_whatis.asp) used for encoding literary texts, historical documents, and the like. During the process, scholars use TEI to "markup" texts to indicate different aspects such as titles, chapter headings, line breaks, and handwritten marginalia, as well as to note significance and inscribe interpretation. Most commonly TEI is used to create critical editions and facsimiles. 

**Related terms:**

* **Markup languages** use tags to define elements within a digital document. XML (Extensible Markup Language) is used for encoding texts and employs a number of different standards and schemas.
* **Markup tags** are in and out marks that “wrap” a text element, e.g., a title, header, single word, paragraph, etc. Below is a simple example using the more commonly known markup language, HTML (Hypertext Markup Language):

```
<h2>Their Eyes are Watching God</h2>
<p><em>Their Eyes are Watching God</em> was written by Zora Neale Hurston in 1937.
</p>
```

In a web browse the above looks like:

### &#x20;    Their Eyes are Watching God

&#x20;    *Their Eyes are Watching God* was written by Zora Neale Hurston in 1937.&#x20;

The \<h2> tag marks the title as a header and determines the specific size of the header. The \<p> tag marks the sentence as a paragraph or a general body of text and the \<em> tag marks the title as emphasized (italicized).&#x20;

##


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://bcds.gitbook.io/handbook/digital-scholarship-methods/overview/tei.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.