These two syntaxes should express the exact same set of Bikeshed anchors. The first is simple JSON, the second is a custom nesting syntax.
Some notes on the second:
- Anchors are defined by the leaf nodes, accumulating values from the path down. You can express any anchor purely through nesting, but when the nesting doesn't add anything, you can collapse values into a single line with a semicolon separating them.
- The
urlPrefix
key is accumulative; if multiple are encountered as you descend the nesting, they concatenate. The finalurl
key is then concatenated to the accumulatedurlPrefix
. - If there is no
url
key, one is generated from thetext
key by doing standard IDification. If theurlPrefix
doesn't contain a#
character, one is inserted between the prefix and the generated ID. - Each anchor must contain a
type
, atext
, and one or both ofurlPrefix
andurl
. It may contain afor
.