Re: [ws-caf] [Fwd: reference/addressing strawman]

[Greg Pavlik <greg.pavlik@oracle.com>]

yes, you are absolutely right. My intention was to include the element 
def., which would be as described in the first case.

Greg

Murray, Bryan P. wrote:

>Greg,
> 
>You propose a nice simple container type for reference information.
>However, I am not sure if you mean this type to have an associated
>element in which all references will be children, or if you mean this
>type to be used to refer to reference elements defined in other specs.
> 
>Your example actually confuses rather than clarifies the problem, as it
>is missing a reference-scheme attribute.
> 
> 
>If the proposed type is to have an associated element in which all
>references will be children, the element needs to be defined.
>    <xs:element name='ServiceRef' type='tns:ServiceRefType'/>
>and the example will be:
>    <ServiceRef
>reference-scheme="http://www.w3.org/2004/04/ws-messagedelivery";>
>      <wsdl11:service name="MyContextService"
>wsmd:portType="ctx:ContextManager">
>        <wsdl11:port name="myCtxPort" binding="ex:ctxServiceBinding">
>          <soapbind:address
>location="http://example.com/wsdl-example1/impl";
><http://example.com/wsdl-example1/impl> />
>        </wsdl11:port>
>      </wsdl11:service>
>    </ServiceRef>
> 
> 
>If the proposed type is to refer to elements already defined in other
>specs, an anyAttribute needs to be added to the type.
>    <xs:complexType name='ServiceRefType'>
>      <xs:sequence>
>        <xs:any namespace='##other' processing='lax' minOccurs='1'
>maxOccurs='1'/>
>      </xs:sequence>
>      <xs:attribute name='reference-scheme' type='xs:anyURI'
>use='required'/>
>      <xs:anyAttribute namespace='##other'/>
>    </xs:complexType>
>and the example will be:
>    <wsdl11:service name="MyContextService"
>wsmd:portType="ctx:ContextManager"
> 
>ws-caf:reference-scheme="http://www.w3.org/2004/04/ws-messagedelivery";>
>      <wsdl11:port name="myCtxPort" binding="ex:ctxServiceBinding">
>        <soapbind:address
>location="http://example.com/wsdl-example1/impl";
><http://example.com/wsdl-example1/impl> />
>      </wsdl11:port>
>    </wsdl11:service>
> 
> 
>Bryan
> 
>-----Original Message-----
>From: Greg Pavlik [mailto:greg.pavlik@oracle.com] 
>Sent: Monday, May 10, 2004 9:38 AM
>To: ws-caf
>Subject: [ws-caf] [Fwd: reference/addressing strawman]
>
>
>
>
>
>	-------- Original Message -------- 
>Subject: 	reference/addressing strawman	
>Date: 	Tue, 04 May 2004 16:24:06 -0400	
>From: 	Greg Pavlik <greg.pavlik@oracle.com>
><mailto:greg.pavlik@oracle.com> 	
>Organization: 	Oracle Corporation	
>To: 	ws-caf-editors <ws-caf-editors@lists.oasis-open.org>
><mailto:ws-caf-editors@lists.oasis-open.org> 	
>
>
>	Guys, trust you all made it home safely. Following my sign off
>is some proposed text for resolving the reference/addressing issue in
>the spec.
>	
>	Also, I'd like to move forward with work on the next draft.
>Mark, could you send me the latest Word doc and I'll try to hammer in
>some of the resolutions we arrived at in New Orleans -- unless someone
>else has a burning desire to do so -- over the next week or so.
>	
>	Greg
>	
>	
>
>	Web Service Referencing and Addressing
>
>	<!--[if !supportEmptyParas]--> <!--[endif]-->
>
>	There are multiple mechanisms for addressing messages and
>addressing web services in the web services environment. This
>specification defers the rules for addressing SOAP messages to existing
>specifications; the addressing information is assumed to be placed in
>SOAP headers and respect the normative rules required by existing
>specifications.
>	
>	However, the Context message set requires an interoperable
>mechanism for referencing web services. To support this model, WS-CAF
>provides the ServiceRefType:
>
>	<!--[if !supportEmptyParas]--><!--[endif]-->
>
>	<xs:complexType name="ServiceRefType">
>	  <xs:sequence>
>	    <xs:any namespace="##other" processContents="lax"
>minOccurs="1" maxOccurs="1"/>
>	  </xs:sequence>
>	   <xs:attribute name="reference-scheme" type="xs:anyURI"
>use="required"/>
>	</xs:complexType>
>
>	<!--[if !supportEmptyParas]--><!--[endif]-->
>
>	The ServiceRefType provides an open content model for service
>references.
>
>	The reference-scheme is the namespace URI for the referenced
>addressing specification. For example, the value for WSRef defined in
>the WS-MessageDelivery specification
>(http://www.w3.org/Submission/2004/SUBM-ws-messagedelivery-20040426)
>would be http://www.w3.org/2004/04/ws-messagedelivery.
>
>	The contents of the any element contain a service reference as
>defined by the referenced specfication. For example, a WSRef to a
>Context Manager service would appear as follows:
>
>	<wsdl11:service name="MyContextService"
>wsmd:portType="ctx:ContextManager"> <wsdl11:port name="myCtxPort"
>binding="ex:ctxServiceBinding"> <soapbind:address
>location="http://example.com/wsdl-example1/impl";
><http://example.com/wsdl-example1/impl> /> </wsdl11:port>
></wsdl11:service> 
>
>	Messages sent to referenced services must use the addressing
>scheme defined by the specification indicated by the value of the
>reference-scheme element.
>
>	To preserve interoperability in deployments that contain
>multiple addressing schemes, there are no restrictions on a system,
>beyond those of the composite services themselves. However, it is
>recommended where possible that composite applications confine
>themselves to a single addressing and reference scheme.
>	
>
>
>  
>