Also the "optional" word at https://pagure.io/modulemd/blob/master/f/spec.yaml#_50 can be misleading.

@psabata, the modulemd spec is your bailiwick, can you clarify what is meant with "optional" there?

well, you might have module which doesn't depend on any other ;) in practice it is impossible, but in theory why not :P

spec.yaml is the format specification, not packaging guidelines, even though it includes some packaging recommendations.

Optional fields mean the field may be omitted and the modulemd file is still valid. No more, no less. Modules with no dependencies whatsoever might seem a little obscure and perhaps they are but they're still allowed.

modulemd doesn't deal with component level dependencies. Require modules that provide your dependency or include the component in your module.

@jvymazal Hmm, seems I've sent you to the wrong repo re: the documentation (and noticed it just now). I've fixed it for the docs web site in this PR: https://pagure.io/modularity/pull-request/37

@psabata Hmm, seems I can't close it again. Sorry for the hassle.