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 1086 - Clarify which role ref/refs is/are valid in XML schema
Summary: Clarify which role ref/refs is/are valid in XML schema
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:
Blocks:
 
Reported: 2005-02-07 15:43 UTC by Greg Ritzinger
Modified: 2005-08-03 13:37 UTC (History)
0 users

See Also:


Attachments

Description Greg Ritzinger 2005-02-07 15:43:46 UTC
Clarify which role ref/refs is/are valid in XML schema in Section 12 and 
ensure consistency with Section 2.3.1 and other possible affected 
sections. In XML schema in Section 12, there are three tRoleRefxxx based 
on how they are used:

    * tRoleRef: tRelationshipType
    * tRoleRef2: tParticipantType
    * tRoleRef3: tChannelType

This could create some confusion with developer community where the role 
(reference) capabilities change given where used. If they are all valid, 
suggest we have clarifying text to state what they are and why we have 
defined them as they are.  This may also relate to the question about 
how we have chosen to name (and scope) RoleType.

  </complexType>
  <complexType name="tRelationshipType">
    <complexContent>
      <extension base="cdl:tExtensibleElements">
        <sequence>
          <element name="role" type="cdl:tRoleRef" minOccurs="2"
                  maxOccurs="2"/>
        </sequence>
        <attribute name="name" type="NCName" use="required"/>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="tRoleRef">
    <complexContent>
      <extension base="cdl:tExtensibleElements">
        <attribute name="type" type="QName" use="required"/>
        <attribute name="behavior" use="optional">
          <simpleType>
             <list itemType="NCName"/>
          </simpleType>
        </attribute>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="tParticipantType">
    <complexContent>
      <extension base="cdl:tExtensibleElements">
        <sequence>
          <element name="role" type="cdl:tRoleRef2" 
                  maxOccurs="unbounded"/>
        </sequence>
        <attribute name="name" type="NCName" use="required"/>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="tRoleRef2">
    <complexContent>
      <extension base="cdl:tExtensibleElements">
        <attribute name="type" type="QName" use="required"/>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="tChannelType">
    <complexContent>
      <extension base="cdl:tExtensibleElements">
        <sequence>
          <element name="passing" type="cdl:tPassing" minOccurs="0"
                  maxOccurs="unbounded"/>
          <element name="role" type="cdl:tRoleRef3"/>
          <element name="reference" type="cdl:tReference"/>
          <element name="identity" type="cdl:tIdentity" minOccurs="0" 
                  maxOccurs="1"/>
        </sequence>
        <attribute name="name" type="NCName" use="required"/>
        <attribute name="usage" type="cdl:tUsage" use="optional" 
                     default="unlimited"/>
        <attribute name="action" type="cdl:tAction" use="optional"
                     default="request"/>
      </extension>
    </complexContent>
  </complexType>
  <complexType name="tRoleRef3">
    <complexContent>
      <extension base="cdl:tExtensibleElements">
        <attribute name="type" type="QName" use="required"/>
        <attribute name="behavior" type="NCName" use="optional"/>
      </extension>
    </complexContent>
  </complexType>
Comment 1 Martin Chapman 2005-02-15 20:29:30 UTC
Agreed at meeting 15-feb-05

Editorial
Comment 2 Greg Ritzinger 2005-05-27 19:25:17 UTC
All the TypeRef complex type definitions are different and required.  They are
type definitions for different local elements even though they have the same tag
name. The text already describes the different attributes and child elements of
each.
Comment 3 Martin Chapman 2005-07-14 16:07:33 UTC
group notification of status change: http://lists.w3.org/Archives/Member/member-
ws-chor/2005Jul/0004.html
Comment 4 Martin Chapman 2005-07-20 14:50:59 UTC
reopened and marked as editorial from 19th jul 05.
text in the minutes:

http://lists.w3.org/Archives/Member/member-ws-chor/2005Jul/att-
0009/minutes_20050719_-_0.txt
Comment 5 Martin Chapman 2005-08-03 13:32:31 UTC
Completed and confirmed by members of the WG at the 2nd August 05 Con Call:

http://www.w3.org/2005/08/02-ws-chor-irc
Comment 6 Martin Chapman 2005-08-03 13:37:20 UTC
corrected resolution to closed