- From: Jean-Jacques Moreau <moreau@crf.canon.fr>
- Date: Thu, 10 Jan 2002 15:29:29 +0100
- To: "Eamon O'Tuathail" <eamon.otuathail@clipcode.com>
- CC: xml-dist-app@w3.org, "'Williams Stuart'" <skw@hplb.hpl.hp.com>
+1 IMHO, the current tables are not accurate enough (compared to this other approach) and consumme too much space (I hate to say this now that I have done the HTML to XML conversion, but...). Jean-Jacques. Eamon O'Tuathail wrote: > Stuart, > > I would certainly be in favour of having this incorporated into the WD. > > It is clear and succinct, yet accurate - properties which are needed > (but, alas, often missing) in technical specs. > > Eamon O'Tuathail > > ======================== > > Events: > SOReq Start-of-Request > EOReq End-of-Request > SOResp Start-of-Response > EOResp End-of-Response > fail Some abnormal termination. > > Process: > srr-exchange = SOReq.( EOReq.(SOResp.(EOResp | fail) | fail) > | SOResp.( EOReq.(EOResp | fail) > | EOResp.(EOReq | fail) > | fail) ) > | fail ).stop > > Can be rearranged as: > > srr-exchange = SOReq.S1 > S1 = EOReq.S2 | SOResp.S3 | (fail.stop) > S2 = SOResp.S4 | (fail.stop) > S3 = EOReq.S4 | EOResp.S5 | (fail.stop) > S4 = EOResp.stop | (fail.stop) > S5 = EOReq.stop | (fail.stop) > > Each line effectively repesents a state.
Received on Thursday, 10 January 2002 09:30:57 UTC