From: Hellwig Geisse <hellwig.geisse@mni.thm.de>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] TUHS Digest, Vol 33, Issue 5
Date: Mon, 06 Aug 2018 18:30:30 +0200 [thread overview]
Message-ID: <1533573030.3671.98.camel@mni.thm.de> (raw)
In-Reply-To: <2EDF09AC-F35B-461A-AB53-9DEB29D9AE25@bitblocks.com>
On Mo, 2018-08-06 at 08:52 -0700, Bakul Shah wrote:
>
> What counts as a "formal spec"? Is it like Justice Potter Stewart's
> "I know it when I see it" definition or something better?
>
For me, a "formal spec" should serve two goals:
1) You can reason about the thing that is specified.
2) The spec can be "executed" (i.e., there is an
interpreting mechanism, which lets the spec behave
like the real thing).
Hellwig
next prev parent reply other threads:[~2018-08-06 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-06 13:06 Noel Chiappa
2018-08-06 15:52 ` Bakul Shah
2018-08-06 16:30 ` Hellwig Geisse [this message]
2018-08-06 21:19 ` Steve Johnson
2018-08-18 19:57 ` [TUHS] Formal Specification and Verification (was Re: TUHS Digest, Vol 33, Issue 5) Perry E. Metzger
2018-08-19 23:47 ` George Michaelson
2018-08-20 0:57 ` Perry E. Metzger
2018-08-20 3:29 ` [TUHS] Formal Specification and Verification Warren Toomey
2018-08-20 18:48 ` [TUHS] Formal Specification and Verification (was Re: TUHS Digest, Vol 33, Issue 5) Tony Finch
-- strict thread matches above, loose matches on Subject: below --
2018-08-06 17:26 [TUHS] TUHS Digest, Vol 33, Issue 5 Noel Chiappa
2018-08-06 17:22 Noel Chiappa
[not found] <mailman.1.1533520802.6258.tuhs@minnie.tuhs.org>
2018-08-06 10:50 ` Steve Simon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1533573030.3671.98.camel@mni.thm.de \
--to=hellwig.geisse@mni.thm.de \
--cc=tuhs@minnie.tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).