This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1022 - Point of clarity - Section 2.3.3, 3rd paragraph, 2nd sentence
Summary: Point of clarity - Section 2.3.3, 3rd paragraph, 2nd sentence
Status: CLOSED FIXED
Alias: None
Product: WS Choreography
Classification: Unclassified
Component: Last Call Comment: Confirmed Closed (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: --
Assignee: Martin Chapman
QA Contact: Martin Chapman
URL: http://lists.w3.org/Archives/Public/p...
Whiteboard:
Keywords:
Depends on: 1018
Blocks:
  Show dependency treegraph
 
Reported: 2005-01-20 20:13 UTC by Greg Ritzinger
Modified: 2005-07-18 18:45 UTC (History)
0 users

See Also:


Attachments

Description Greg Ritzinger 2005-01-20 20:13:15 UTC
Section 2.3.3, 3rd paragraph, 2nd sentence.   
     Point of clarity   
   <role type="qname" />+   
   "Each Role Type is specified by the type attribute of the role element"   
   What is the relationship between the type attribute of this <role> element,
and the name attribute of <roleType> of section 2.3.1?   
   Need a statement clarifying the relationship explicitly rather than just by
example.
Comment 1 Martin Chapman 2005-01-25 20:36:38 UTC
editorial
Comment 2 Martin Chapman 2005-02-14 21:00:30 UTC
From meeting on 25-jan-05:
http://lists.w3.org/Archives/Member/member-ws-chor/2005Jan/att-0010/2005-01-
25_WS-Chor_Notes.txt

Depends on the 1018 ? editorial.
Comment 3 Greg Ritzinger 2005-03-11 18:07:34 UTC
Add: "This type attribute points to the name of a role element."

same applies for 2.3.2
Comment 4 Greg Ritzinger 2005-05-25 20:42:10 UTC
In section 2.3.3, 3rd paragraph, 2nd added sentence:  The "qname"
value of the <z>type</z> attribute of the <z>role</z> element MUST reference
the name of a roleType. 
 
Also added same sentence to penultimate paragraph of section 2.3.2
 
 Question: in section 2.3.3 

<roleType name="Buyer">

   . . .

</roleType>

<roleType name="SellerForBuyer">

    <behavior name="sellerForBuyer" interface="rns:sellerForBuyerPT"/>

</roleType>

<roleType name="SellerForShipper">

    <behavior name="sellerForShipper" interface="rns:sellerForShipperPT"/>

</roleType>

<roleType name="Shipper">

   . . .

</roleType>

<relationshipType name="Buyer-Seller">

    <role type="tns:Buyer" />

    <role type="tns:SellerForBuyer" />

</relationshipType>

<relationshipType name="Seller-Shipper">

    <role type="tns:SellerForShipper" />

    <role type="tns:Shipper" />

</relationshipType>

 

<participantType name="Broker">

   <role type="tns:SellerForBuyer" />

   <role type="tns:SellerForShipper" />

</participantType>

 
should the two rns: name prefixes be tns: or are they deliberately
different?
Comment 5 Martin Chapman 2005-07-14 15:23:59 UTC
Yin-Leng has been informed of the group's resolution to this issue [1].
changed to closed, and awaiting confirmation.

[1] http://lists.w3.org/Archives/Public/public-ws-chor-
comments/2005Jul/0002.html
Comment 6 Martin Chapman 2005-07-18 18:45:45 UTC
Yin Leng has confirmed the resolution:

http://lists.w3.org/Archives/Public/public-ws-chor-comments/2005Jul/0010.html