Should the namespace of `customizations` be more standardized?

[avidal]

Currently, customizations are namespaced by arbitrary product names. The only two I've seen in wide-use are vscode and codespaces, which makes sense as those are the only two widely used implementations of devcontainers.

As the spec is picking up steam, it may be worth considering changing these keys to use reverse domain name notation. Implementing tools would continue to support the original names for the foreseeable future, but could map the legacy name to the proper name and potentially print a warning at build time at some point in the future if the customization namespace does not look like a reverse domain, with extra flavor for well-known names.

Thoughts? If there's interest I could write it up as an actual proposal.

[bamurtaugh]

Hi @avidal, thanks for opening this issue! I agree this is a great topic to revisit.

I think there are a couple steps here:

• Formalize the request process for a namespace in customizations
• For namespaces that may not be registered in the official schema, use a method like reverse dns (this proposal you describe)

Opening a proposal on the second bullet sounds good to me, thank you for offering! cc @jkeech @Chuxel as we discussed this