Machine readable encoding for configurations

For example, some vulnerabilities may only be relevant on certain operating systems / architectures. Are there other similar information that can be encoded in a machine readable and actionable way?

This issue tracks adding this as a potential new field to affected. e.g. something like:

{
	"affected": [ {
                 ....
		"configurations": [
                   {"os": "Windows"},
                   {"arch": "x86-64"},
                 ]
	} ]
}

This glosses over some additional detail (e.g. do we need to express specific versions of OSes?)

The issue names the affected field and proposes a JSON configurations field, but no files or tests. Start by reviewing the current affected schema and its examples; done means agreeing on how operating systems, architectures, and possible OS versions are represented and updating the schema accordingly.