RE: [tosca] Re: Clarification required for "!!timestamp" type in YAML

Thatâs a good idea, but this raises the following question: many of the âsnippetsâ in the spec are just that: snippets (or code segments) that wouldnât be parsable without being contained in a valid service template. We could make sure all snippets are âcompleteâ TOSCA, but that would make examples much more verbose.

Chris

From: Tal Liron [mailto:tliron@redhat.com]
Sent: Tuesday, October 01, 2019 11:27 AM
To: Chris Lauwers
Cc: tosca@lists.oasis-open.org
Subject: Re: [tosca] Re: Clarification required for "!!timestamp" type in YAML

On Mon, Sep 30, 2019 at 11:17 PM Chris Lauwers <lauwers@ubicity.com> wrote:

Please keep mentioning them 😊 Iâll try to fix them as we find them.

Here's a suggestion:

Let's create a git repository with all the YAML snippets from the spec. This would allow each of us to run them through our parsers and see if they are valid examples. We would then require that any new examples in the spec be committed to this repo. We can even do auto-testing (Travis?) to ensure this, even if it's just at the YAML level.

It's very embarrassing to have bad YAML in the spec, let alone bad TOSCA...

tosca message