Chris,
Thank you for the list.
As Calin mentioned, I believe we should include augmentation / refinement in v1.3.
Also, to add to the list, I recall our discussions on Explicit substitutability topic on which we received consensus.
Regards,
Priya
From:
tosca@lists.oasis-open.org [mailto:
tosca@lists.oasis-open.org]
On Behalf Of Calin Curescu
Sent: Thursday, November 1, 2018 2:43 PM
To: Chris Lauwers <
lauwers@ubicity.com>;
tosca@lists.oasis-open.org Subject: Re: [tosca] finishing up 1.3
Hi,
I believe the refinements to be quite relevant so we should try to include it as well.
BR,
/Calin
From:
<
tosca@lists.oasis-open.org > on behalf of Chris Lauwers <
lauwers@ubicity.com >
Date: Wednesday, 31 October 2018 at 19:28
To: "
tosca@lists.oasis-open.org " <
tosca@lists.oasis-open.org >
Subject: [tosca] finishing up 1.3
During yesterday s YAML call, we discussed what items should be in scope for Version 1.3 of the spec. I believe we came up with the following remaining items:
-
Asynchronous notifications (based on Calin s latest document, which removes asynchronous operations)
-
Support for 3 rd -party workflows (based on Thinh s proposal, but with support added for outputs )
-
Artifact properties (based on Priya s contribution that clarifies where and how to use artifact properties)
-
Additional constraint logic (based on Anatoly s proposal).
One area we have worked on, but which hasn t been reflected yet in the spec, is the augmentation or refinement of definitions in derived types. Should we try to include this as well?
Did I miss anything else?
Thanks,
Chris
The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in
reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.