Add an entry to the Security Considerations section that highlights the danger of peers sharing lists among each other without proper vetting.

It has been suggested that hierarchical/chained lists would be more beneficial if there are ecosystems that have millions of issuers that change hourly.

The size of the list was raised as a concern in the weekly W3C presentation. I think combining this issue with chain lists can help to sort this problem.

As Steve notes here:

https://lists.w3.org/Archives/Public/public-credentials/2023Mar/0039.html

It's important for the specification to draw a clear line wrt. what's in scope (the format and semantics of the list and items in the list) and what's out of scope (APIs for managing the list, governance models for managing the list, etc.).

We should add a section to the introduction of the specification that highlights what the spec does and does not address.

Add an entry to the Security Considerations section that highlights inadvertent "first mover" advantages of one party's trust anchors overwhelming others because they published first. What happens when an actor publishes a useful list and then gets most of the ecosystem to use that list and then uses their control over the list to block new entrants into the market?