[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
protocol standards that use formal specification of behavior?
- To: occam-com@xxxxxxxxxx, java-threads@xxxxxxxxxx
- Subject: protocol standards that use formal specification of behavior?
- From: "Alan Grover" <alan.grover@xxxxxxxxx>
- Date: Mon, 22 Jan 2007 15:39:43 -0700
- Delivery-date: Mon, 22 Jan 2007 22:44:59 +0000
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=VMjWCJJsf2LKHcDRl2rnq2/X2LhdpfMFmL6dhNQyPwntZ2OZCo9CKnbJKojBOGp91SSu+OWtUGfCS5SzjF3YfOMn27qaZFreirMWf/iRc2IEURDJ6979O7IXjpRPK0Snxe+HL+lK1L97/89KIzTOnmqZ8D9oqf2bnIeyzkqmbQ0=
- Envelope-to: ats1@xxxxxxxxxxxxxxxx
- Sender: owner-java-threads@xxxxxxxxxx
I'm working on a SAE standards committee that is trying to add the specification of protocol behavior to their standard. There are camps of opinion that prefer RPCs, UMLish state machines, and IETF style descriptive-text-plus-illustrative diagrams approaches. I'm trying to move things in a CSP'ish direction, but it has been a hard sell so far.
Does anyone know of a published protocol standard that formally specifies behavior, including any that use something CSPish?