[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [tosca-comment] RE: Wording of operation outputs description
Chris, The most well known example of syntax or railroad diagrams (https://en.wikipedia.org/wiki/Syntax_diagram) is the one at
json.org. When I was learning TOSCA I created for my own use what I called a skeleton file. It contained a cut and paste of each possible clause of the syntax in its recommended order and to several levels of depth â so for example property definition
appeared more than once â once in each place where that clause can be used. Iâve been wondering about creating a set of syntax diagrams for TOSCA as an educational aid. From: Chris Lauwers <lauwers@ubicity.com>
Hi Paul, pardon my ignorance but Iâm not sure what you mean by ârailroad diagramsâ. Would you mind expanding a bit? Thanks, Chris From:
paul.m.jordan@bt.com <paul.m.jordan@bt.com>
I would also be interested on working on a formal statement of the syntax â not that I have much experience in doing it. There is much more tool support JSON schema and so I agree that it would be more useful in the long term that BNF. I suspect that there is much in the current draft of v2 which would be difficult to describe in JSON schema today and definitive
schema will probably mean having to make changes to the spec. So a definitive schema can probably only be a long term goal. In the nearer term creating a ârailroad diagramâ would, I think, be helpful for tutorials and to highlight areas of the syntax which need attention. These diagrams can be drawn manually or from EBNF.
I would have expected that moving from EBNF to JSON schema would be a mechanical process but a brief search has no turned up any references to a suitable technique or tool.
Paul Jordan This email contains information from BT that might be privileged or confidential. And it's
only meant for the person above. If that's not you, we're sorry - we must have sent it to you by mistake. Please email us to let us know, and don't copy or forward it to anyone else. Thanks. We monitor our email systems and may record all our emails. From: adam souzis <adam@onecommons.org>
I think developing a JSON schema is a great idea and something I would volunteer to help with. It would make it much easier for tools to syntactically validate TOSCA templates and help us remove ambiguity from the spec. As a side note,
OpenAPI also uses json schema so this might help interoperability with interface definitions. I think a BNF-like definition would be more work and considerably less useful. Thanks, Adam On Thu, Dec 3, 2020 at 9:00 PM Chris Lauwers <lauwers@ubicity.com> wrote:
á |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]