[FEATURE] Consider score-spec a superset of compose-spec (or potentially merge with compose)

[steren]

Detailed description

Score would likely be more successful if it could leverage all the compose files that exist out there.

Context

Compose spec is everywhere, but mainly used for development.

Possible implementation

This could be achieved in two ways:

• make the score spec a superset of compose spec, so that any compose file would "just work" with score-* CLIs
• merge score spec into compose spec. It seems that the main difference is the ability to define resources without specifying implementation. This could be added to compose spec (and is already what compose spec does for the newly introduced model attribute)

Additional information

No response

[astromechza]

Unfortunately, score-spec cannot be a super set of compose spec, as it is, by design, intended to be simpler than docker compose.

You're right that the main difference is primarily the ability to define resources associated with workloads and to then inject results of those resources into the resulting workloads. It would be an interesting project to see if you can extend the compose spec to handle resources too, but this is not the concern of the Score project itself. The bulk of the Score spec is around the definition of the workload containers, and resource behaviour is not strictly defined.