Markdown-Annotations

An important aspect of markdown is hand authorship. Markdown Annotations are certainly interesting and I understand where the hash idea came from, but this requirement adds friction to hand authorship, and requires new custom parsing logic for markdown renderers. I would argue it should instead be: - file.md - .file.md.owners Where the owners file is generated / readable by a program supporting this behavior, along with a reference to the original file and its hash. This provides the same information and capabilities, while decoupling it from the source. It also means you can retroactively generate ownership without modifying original work. In reference to: https://github.com/iainc/Markdown-Annotations#hash-annotatio...

Good in principle, but bad in the implementation. From their Markdown Annotations specs [0], the authorship is recorded in a quasi-YAML block at the end of the file, e.g.,— Annotations: 0,95 SHA-256 1132bf5e376a605f5beed4b204456114 @Human: 0,20 33,4 45,6 62,4 &AI: 20,13 37,8 51,11 66,29 The format is bad for multiple reasons: 1. it doesn’t work with the existing de facto standard for markdown metadata, i.e., the YAML frontmatters; the markdown standard is already too fractured to have a new extension; 2. it messes with types by using YAML strings for arrays and integers; 3. it’s inefficient — any change in the file would demand iterating through all recorded ranges and updating the offsets. I’d prefer it to adopt the YAML frontmatters: authorship: authors: - {id: 0, name: Human, hash: xxxxxxxx} - {id: