Another approach might be to represent the fix description as a note:
This has some real advantages.
- You can describe the fix in as much detail as you need.
- You can link to and from the fix. For example, the last time I actually used a tensor myself was in undergraduate General Relativity, and I don’t recall just what reshaping a tensor would be.
- Agents can search for bug fixes than mention tensors.
- Bugfixes could then have attributes,
That said, Tianrui Niu raises a discussion I’ve been having with Rosemary Simpson (designer of Lisp Machine’s pioneering hypertext system Gateway) for decades. Simpson believes that links should be first class objects — in essence, a kind of note. That was actually the key behind Halasz and Marshall’s Aquanet, a system to which Tinderbox today acknowledges many debts.
Tinderbox’s immediate inspiration, VIKI, was designed in reaction against Aquanet and its formalisms, and Tinderbox was originally conceived as a tiny VIKI that could escape the laboratory. So, negotiating these two irreconcilable visions is a tricky negotiation.
At the extreme pragmatic end of the spectrum, too, things aren’t easy. Once maps become moderately complex, it becomes tricky to find ways to place the labels so they’re legible. Tinderbox today is quite naive in its efforts at label placement; we’ve actually invested quite a bit of work in that area, and it’s always been a pain in the neck. (The underlying layout problem is NP-hard for most plausible measures of label placement. That means it’s one of the large class of problems that are computationally intractable if you really want the right answer.)
So, that’s the story of the current status quo. Stay tuned! Always happy to learn of new references (I know the literature fairly well but there’s always new stuff and there’s always a dusty corner to revisit) and new approaches.