> For the complete documentation index, see [llms.txt](https://textav.gitbook.io/textav-event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://textav.gitbook.io/textav-event/problem-domains/d83d-dd2a-2705-2b07-fe0f-annotations-models.md).

# 🔪✅⬇️ (Annotations models)

{% embed url="<https://www.youtube.com/embed/Cd56vF3lZ_Q>" %}

## Notes

* Killing Markdown
* GML (written in1969), an IBM project to write text into files for computers to display in a better formatted style&#x20;
* GML gave birth to SGML, which gave birth to HTML and XML
* “Our tools were based on presumptions that simply were not true anymore”
* "Content is not hierarchical"
* Can we come up with a better mental model for thinking about content?
* We can write code that does this but it's not reproducible.
* Example of manually edited document: The "content" is the printed material and the notes taken over in pen fit in … where?
* JSON, content, annotations: “Contents” distinct from “annotations” in JSON format.&#x20;
  * Here’s a simplified version:

```javascript
{
    contents: “Main text document goes here etc etc etc”,
    annotations: [
        { position: 4, text: “Change this” }
        { position: 12, text: “I like this” }
    ]
}
```

* Theoretically possible for transcript/audio data too.

  Not a standard format – ”I’m allergic to standards”

  Even the format Blaine showed on screen is “massively simplified”