OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-caf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [ws-caf] AssertionType


Dear John and others,

As I said on the phone, as far as I can see at present,
AssertionWithProtocolURIType only adds a protocol-uri element which is of
anyURI type.  Again the purpose and use of this parameter is not described
in the WS-Context specification, so the first obvious thought is to drop it
too.  If this parameter is really required it can be added to each protocol
message (which would now not be an extension of anything) as easily as each
protocol message extending this base type.  In this case the purpose and use
of this parameter should be clearly described in the WS-Context
specification.


 Best Regards     Tony
A M Fletcher
 
Cohesions  (TM)
 
Business transaction management software for application coordination
www.choreology.com
 
Choreology Ltd., 68 Lombard Street, London EC3V 9LJ     UK
Tel: +44 (0) 1473 729537   Mobile: +44 (0) 7801 948219
tony.fletcher@choreology.com     (Home: amfletcher@iee.org)

-----Original Message-----
From: John Fuller [mailto:jfuller@wernervas.com] 
Sent: 17 January 2005 21:12
To: WS-CAF
Subject: [ws-caf] AssertionType



If we get rid of AssertionType, what happens to 
AssertionWithProtocolURIType?



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]