I propose that package-spec disallows dotted key names in the YAML used to define packages. Allowing dotted key names leads to ambiguous specifications. It also increases the complexity of properly parsing the specification because the parse needs to account for fields that maybe defined in more than one way. In the two ambiguous examples below the specification is clear in that both kibana and elasticsearch are to be objects. ^{1 2} But from a validation point of view these are accepted by elastic-package.

conditions:
  kibana.version: '^8.8.0'

  kibana:
    version: '^8.10.0'

elasticsearch.dynamic_dataset: true

elasticsearch:
  dynamic_dataset: false

There are many examples of this occurring in packages:

• https://github.com/elastic/integrations/blob/835c3c7cee4bef9aea55e831541d22803125f292/packages/system/data_stream/syslog/manifest.yml#L40-L42
• https://github.com/elastic/integrations/blob/835c3c7cee4bef9aea55e831541d22803125f292/packages/system/manifest.yml#L11-L12