CriticMarkup support?

[RMBLRX]

In regard to using imdone with prose, I was thinking that one thing missing from is a way to reference tasks inline within some text and perhaps in reference to a specific piece of text. Now before I get too carried away, I'd like to note that as it stands, imdone probably handles objects in too heavy a fashion (i.e., a kanban for every object, including the sort that would go under NOTE), at least to accomplish this in any straightforward fashion, as inline comments would be fairly abundant with no clear purpose for each having its own task (though possibly something like a subtask), at least not so much purpose as TODO tasks.

Nevertheless, I think there's some potential here:

CriticMarkup has a way to add comments inline with text (without breaking markdown), which can optionally even reference a piece of text or a specific proposed change to that text. It seems that this markup is slowly gaining some support, to include at least a couple of popular Mac text editors and Markua, as well as Pen-Paper-Coffee-Syntax and Markdown Preview Enhanced on Atom. Unfortunately there is a distinct lack of an Atom plugin to support it the way MMDC does.

What I propose is probably somewhat of a big ask, but basically I would like to be able to reference a task or a project in a critmark comment without any excess of markup (i.e., not having to mark up a new imdone object within each comment). So, for example:

{== some text ==}{>> some note +someProject id:# <<}

Ideally, I think it would be great if imdone would just track all such comments regardless of whether they reference a task ID or a project tag, perhaps as if they began with #COMMENT: or some user-designated object-type. However, that doesn't address the aforementioned issue of any such object being a bit too heavy to be practical. Incidentally, I also happen to feel this to be the case with other objects like those under NOTE, as I mostly either tie my notes to a TODO object by either nesting them under the TODO or giving them the same ID as the TODO object.

Anyway, I think this sort of support would be useful in imdone as it is, but I think the greater potential might lie in imdone enabling such support in the form of subtasks (which I understand would fundamentally change the structure of imdone). There's plenty more potential beyond that as far as I'm concerned, but whether any of what else I have in mind is within imdone's scope is probably unlikely.