They could still use whatever config format they wanted - this would just be for providing their config schema. It also doesn’t need to be YAML, that’s just the easiest one for me to type on my phone. In fact, I think most schema validation programs rely on JSON as it is.

I also don’t think programs should be required to provide it. Many core programs and kernel modules would likely take years if they ever were able to add it just to avoid the risk of mistakes causing any major issues, especially if they haven’t needed an update in years. There are also many config files that use their own nonstandardized schema. A possibility is that they could be allowed to provide a CLI tool which could update the config or they could just ignore it entirely.

But creating a common schema for… well, the config schema would make it easier for systems to provide a frontend interface for updating your configs.

Seriously - Linux needs a standardized config schema spec. Something that programs should provide which an application can read and provide a frontend interface for the users to adjust config files.

Could be something like:

schema_version: 1.0
application:
  name: Poo Analyzer
  icon_path: /etc/pooanalyzer/images/icon.png
  description: Analyzes photos of poo
schema:
  - config_file:
      path: /etc/pooanalyzer/conf/poo.conf
      conf_type: ini
    configs:
      - field: poo_directory
        type: dir_path
        name: Poo Image Directory
        description: Directory of Poo Images
        icon_path: /etc/pooanalyzer/images/poo.png
      - field: poo_type
        type: list
        name: Poo Types
        description: Types of Poo to Analyze 
        values:
          - dog
          - cat
          - human
          - brown bear
        icon_path: /etc/pooanalyzer/images/animal.png
          ...

Any distro could then create any frontend they’d like to manage this - the user could even install their own.

Apparently it’s Athena Linux. At least, that’s what the hackable vacuums use.