Differentiating between Docker Compose and Open Compose

[cdrage]

There should be some form of meta-data in order to detect / differentiate whether or not this is an Open Compose format or Docker Compose due to the similarity of the projects.

For example, either a required parameter within meta-data or something that indicates it's a different format.

For example:

version: "0.1"
compose-name: "helloworld"
author:
  name: Uber Hacker
  email: developer@example.com

Or something ^^

[pradeepto]

@cdrage Good point.

[cdrage]

@pradeepto Yeah... the main problem is that when using a CLI tool, you'd have to explicitly supply that it's an opencompose format if the tool has multiple "compose-style" inputs

[dustymabe]

i'm +1 on adding something to the file/spec to be clear about what spec the file is conforming to.

In the past you could rely on the file extension (.jpeg, .txt, .md, etc) but since these are all yaml files I think coming up with a new extension for this would not be ideal.

[pradeepto]

@cdrage The sample spec (as it stands now), does have some metadata. You can see it in the example. Definitely needs from fine-tuning like everything else in this spec.

https://github.com/redhat-developer/opencompose/blob/master/opencompose-specification.asc

[cdrage]

@pradeepto which metadata? :) the labels? problem is that if the person doesn't choose to add labels / you can't detect it :(