# Standoff Markup
Draft article I'm writing: [Standoff Markup](https://standoff.jessmart.in/article)
## Exampls of Standoff in the wild
- [Attributed Text](https://github.com/superlistapp/super_editor/blob/main/attributed_text/README.md) from Superlist
- [BlueSky Facets](https://www.pfrazee.com/blog/why-facets)
See the [[Standoff Properties Working Group]]
As opposed to procedural markup.
It's not hierarchical, so you can overlap annotations easily.
You can _ignore_ annotations as well!
Benefits
- One data, many views
- Security: you don't have to _parse_ the text,
- Enables multiplayer
Challenges:
- How to use structure?
# Standoff Explainer
```
--- HTML
<h1>Some header</h1>
<p>Some <b>te<i>xt</i></b><i> and italic</i></p>
^ Overlapping markup is hard!
--- Heirarchy
h1. Some header
p. Some
b. te
i. xt
i. and italic
--- Raw text
Some header\n
\n
Some text and italic
Standoff properties:
[
{
markType: 'heading',
startOffset: 0,
endOffset: 10,
author: 'jess'
},
{
markType: 'bold',
startOffset: 17,
endOffset: 20,
author: 'john'
},
{
markType: 'italic',
startOffset: 19,
endOffset: 27
},
{
markType: 'comment',
startOffset: 15,
endOffset: 19,
commentText: 'This word "some" at the beginning of the line is silly'
}
]
Separation of semantics from content!
Many different layers of semantic meaning.
Enables multiple authors to overlay their semantics
```