W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2002

RE: Wire Trace approach to MEP/Binding descriptions.

From: Eamon O'Tuathail <eamon.otuathail@clipcode.com>
Date: Thu, 10 Jan 2002 10:21:19 -0000
To: <xml-dist-app@w3.org>
Cc: "'Williams, Stuart'" <skw@hplb.hpl.hp.com>
Message-ID: <000001c199c0$8d0cc740$56c8fea9@central>
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 05:24:18 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:05 GMT