|Date||10 February 2019, 00:00 CET|
|Participants NB, PGL, TO, LF, JF, KP, PJ||Minutes by PJ.|
A list of actions can here found here
The following people were standing for election:
The LB is aiming for an odd number of members for votings reasons. As AH was willing to give up voting rights all eight members were accepted as Language Board members for 2019.
Some recent bug fixes (December 15).
A new version of ViennaTalk has been released.
Paul Chisholm (PC) is currently working on a feature that aims to reduce the efforts needed to document VDM specs. This is achieved by including the documentation in comments such that it can be used to auto-generate a set of HTML pages that act as the specification documentation. In addition to the documentation, a secondary goal is to provide a more convenient way to view specifications using the capabilities of HTML and a browser, avoiding the need for an IDE.
PC’s prototype is built on VDMJ4, but doesn’t adhere to the architecture NB introduced in VDMJ4. It covers all of the functional subset of VDM-SL, and a fairly large proportion of operations/statements as well. There are a number of issues that need resolved. The next step is to work on an update with the intent it will become part of the VDMJ baseline, adhering to the VDMJ4 architecture.
PC has only looked at HTML generation, but NB, LDC and LF have all proposed ideas that widen the scope (e.g. generation of makdown). Longer term, if we get a successful release of VDMJ it would be good to have something like this in Overture.
We’re currently working on implementing the annotations feature in Overture, but getting it to work with the IDE is causing a lot of problems that we’re currently looking into.
Release dates for 2019 can be found here.
See download stats on the downloads page
We need input from CG and LC. KP will follow up on this. The workshop page is available here.
We’re awaiting MV’s input on this.
See Planned Publications.