[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Bug 224] Mandate WSDL and SOAP?
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=224 mark.little@arjuna.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |LATER ------- Additional Comments From mark.little@arjuna.com 2005-02-17 11:18 ------- Related to conformance. Mark motioned to say that if an implementation supports context / one ways then it must do according to the specification. Kevin seconded (i.e. optional to implement, but specification is normative if you do implement). Amendment from Doug: a conformant implementation must implement one ways according to the specification. Tony suggested putting conformance for the CAF stack in the highest level referencing specification in the CAF family. Eric said no as will not always have a referencing specification. Greg: there are different conformance points in the specification. For instance may just comply with the context structure only, or with the structure and by the reference mechanism. Greg suggested a functional unit approach. Martin agreed with Tony that high-level specifications can/should add conformance statements for what they used, but also felt each should be usable stand-alone as Eric said. Doug suggested having a consistent statement on WSDL in all the CAF specifications. Tony said that he supported what Greg said as well as what he had expressed. Motion: if you use the facility then must do according to WSDL and text in the specification. Agreed unanimously. It was agreed that people can and should review the resulting text in WS-Context and raise new specific issues if necessary. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]