- From: Mario Jeckle <mario@jeckle.de>
- Date: Fri, 09 Jan 2004 08:04:30 +0100
- To: Francis McCabe <frankmccabe@mac.com>
- Cc: www-ws-arch@w3.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 | 1. The relationship between a message and task is one of | choreography. The idea is that messages denote significant events in the | choreography of tasks. Anyone with a better suggestion would be welcomed. Perhaps, the following could work. Introduce a new node titled choreography. This node has a relationship to message named "orchestrates" (alternatively: "consists of", but I would prefer the first one). This will express that a cheoreography is a separate entity within the service model. Additionally, rename the relationship currently titled "cheoreography" to "codify" (sorry, cannot find a better name right now. I'm trying to state that a message is a concrete element which makes a task (from my point of view an abstract entity) available for technical use). Mario -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQE//lJ+46tt20EwGqwRAmCpAJ9keg1Ye/kAd95Cd0Mxu8BlbtpDCQCguTjV YmNVgsr48+CmTI2s4QQol80= =MXec -----END PGP SIGNATURE-----
Received on Friday, 9 January 2004 02:04:39 UTC