W3C home > Mailing lists > Public > public-ws-chor@w3.org > February 2006

Re: Latest primer

From: Gary Brown <gary@pi4tech.com>
Date: Tue, 7 Feb 2006 17:44:00 -0000
Message-ID: <01ef01c62c0e$1691dc60$0200a8c0@GPB1>
To: "'WS-Choreography List'" <public-ws-chor@w3.org>, "Monica J Martin" <monica.martin@sun.com>, "Steve Ross-Talbot" <steve@pi4tech.com>

Section 3 comments:

1st para:
From:
" In order to understand WS-CDL is best to illustrate it through the use of 
an example "
To:
" In order to understand WS-CDL it is best to illustrate it through the use 
of an example "


3.3.1

5th para:
From:
" which occurs over a channel variables "
To:
" which occurs over a channel variable "

6th para:
From:
" for the variables , and respectively "
To:
" for the variables , respectively "


3.3.2 role types

The role type definition is not valid - the <description> node does not have 
a closing >


3.3.3

1st para:
From:
" implemented by the same logical entity beit a organisation or line of 
business within an organisation "
To:
" implemented by the same logical entity, albeit an organisation or line of 
business within an organisation "

2nd para:
" In the case of a "Participant" the information within a "Participant" may 
be shared in the same sense of information existing in some shared memory 
between different threads in a process. "
- possibly need to link back to roles - i.e. all of the roles within a 
participant can share information???

3.3.4

2nd para:
" A relationship comprises a name and two role types. We use the convention 
in this document that the first role type defines the "from" role and the 
second the "to" role and connect them with the number 2, thus all of our 
relationships are of the form from2to, though WS-CDL does not require this 
directionality to be declared in the name of a relationship. "

- this paragraph implies directionality in the relationship, although its 
only talking about naming, but the implication is there


3.3.6

1st Para:
From:
" The tokens and their locators are used later on to define the identity 
attributes that ensure channel communication can be correlated. "
To:
" The tokens and their locators are used later on to define the identity 
attributes that ensure messages can be correlated to their appropriate 
channel instance and therefore choreography session. "

2nd para:
From:
" reference, that is a url, t for a web service "
To:
" reference, that is a url, for a web service "

- actually the main reason for having the channel type reference token is 
for channel passing purposes - we need to understand what data type will be 
used to transfer the endpoint reference between services

4th para:
From:
" We define the tokens id which represents the information type IdentityType 
and URI "
To:
" We define the tokens id, which represents the information type 
IdentityType, and URI "

- not sure about the second and third sentences of this para - need to 
simplify the explanation (e.g. we define locators for these types that will 
cause the identity information, associated with token 'id', to be obtained 
from the contents of these messages when exchanged on the channel).


3.3.7

1st para:
From:
" Finally, having defined our roles, information types, tokens and 
locatorswe are "
To:
" Finally, having defined our roles, information types, tokens and locators 
we are "

2nd para:
From:
" we have a channel variables called "
To:
" we have a channel variable called "


3.3.8

1st para:
From:
" declaring the relationships that wil be leveraged in the choreography "
To:
" declaring the relationships that will be leveraged in the choreography "

5th para:
From:
" If you don't an explicit sequence it is implied "
To:
" If you don't have an explicit sequence then it is implied "

7th para:
From:
" is called QuoteRequest is is based on a "
To:
" is called QuoteRequest and is based on a "




----- Original Message ----- 
From: "Steve Ross-Talbot" <steve@pi4tech.com>
To: "'WS-Choreography List'" <public-ws-chor@w3.org>; "Monica J Martin" 
<monica.martin@sun.com>
Sent: Tuesday, January 31, 2006 10:45 PM
Subject: Fwd: Latest primer



Primer up to and including section 3 for review, comments and
suggestions as to how to make it read better.

If anyone needs the XML instead of the html Yves can supply it.


Cheers

Steve T

Begin forwarded message:

> From: Yves Lafon <ylafon@w3.org>
> Date: 31 January 2006 21:58:35 GMT
> To: Steve Ross-Talbot <steve@pi4tech.com>
> Subject: Re: Latest primer
>
> On Tue, 31 Jan 2006, Steve Ross-Talbot wrote:
>
>> Including a png diagram.
>
> Online right now at
> http://www.w3.org/2002/ws/chor/edcopies/primer/primer.html
>
>>
>> Cheers
>>
>> Steve T
>>
>>
>
> -- 
> Yves Lafon - W3C
> "Baroula que barouleras, au tiéu toujou t'entourneras."
>
>
Received on Tuesday, 7 February 2006 17:44:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 18 December 2010 01:01:44 GMT