4 ms·
iA Writer 7
- jasonjmcghee 3y agoAn 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-annotation https://github.com/iainc/Markdown-Annotations#hash-annotatio...
- sillywalk 3y agoI think that keeping the two files in sync would be an issue. It looks like under this system, all the annotations are stored at the end of the file, so can just sort of be ignored.
- kemayo 3y agoIgnoring them would result in breaking them with any hand edits, I think. This spec seems to create chunks of markdown documents that (almost) cannot be edited by hand -- any change you make that affects the offsets in the `Annotations` range requires you to update all the references character-offsets. (And any changes made within the annotation range itself require recomputing the hash as well as updating the ranges.) The only change you can make to one of these documents by hand is to add further content after the annotated ranges.