Name mappings PEP: General review

[jaimergp]

After a global pass at the full PEP as per https://github.com/rgommers/peps/tree/ac4400ea7e851e7e944118230189bc7034bb7a23:

• In motivation, “In the context of external dependencies, there are at least two key motivators:” is not necessary
• In “Governance and maintenance costs of name mappings”, simplify “Some ecosystems have such a name mapping already, because it’s required for tools like pyp2rpm and Grayskull to work. In those cases, the additional maintenance costs of connecting those mappings to a central registry are likely limited.”
• In “Generating package manager-specific install commands”, though -> through.
• Simplify and concretize open ended statements like “formats JSON, TOML, YAML”
• In “Registry design”, talk about it with the decisions we made, not the ones we need to make.
• Split top-level specification with more sub-headers.
• Move conda-forge example to Examples.
• Remove “Title” from tables.
• Examples: split urls in the sublist so they are items
• Consistency in quoting, list style, etc.
• ~/.config/pyproject-external/config.toml, add “or equivalent”
• “CLI also provides a simple way to perform [external] table validation:“, be more specific about validation type here (canonical).
• Move to “DepURL” terminology instead of dep: URL.
• Refine How to teach this, leaner
• Refine Reference Implementation
• Prettify long links
• Open Issues?

[rgommers]

@jaimergp does gh-56 close the last bits of this issue?

[jaimergp]

Yes, we can close!