No information is available needs IDs and a review

[GeorgeKerscher]

In Pr 535, I mention that the last statement in examples is "No information is available" and this needs to be reviewed. I wanted to capture this issue instead of having get lost when that PR is merged.

In many places there was a variable and a ID string that matched well. However, in other places the logic in the techniques do not lead to that statement; I would call this a fall through statement, i.e., the condition where everything fails because there is no metadata present.

There are also the markup of the ID that should be placed in the guidelines.

I think the guidelines should be updated after the techniques are revised.

[mattgarrish]

The recent removal of the headings makes these fall-through statements confusing. There's now nothing in the techniques about how to add headings, presumably forcing implementers to read the json file to figure out what to do, although even that is not made clear.

But if the headings are now at the discretion of implementers, it means you could get multiple "no information available" statements with no context. It's also not clear how the statements would be modified depending on whether the implementer uses the predefined headings from the guidelines or whether they come up with some new heading group of their own.