# 🔪✅⬇️ (Annotations models) {% embed url="" %} ## Notes * Killing Markdown * GML (written in1969), an IBM project to write text into files for computers to display in a better formatted style * 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. * 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” --- # Agent Instructions: 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: ``` GET https://textav.gitbook.io/textav-event/problem-domains/d83d-dd2a-2705-2b07-fe0f-annotations-models.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.