Example of an interoperability profile: WS-I Basic Profile

[robert_weir@us.ibm.com]

WS-I Basic Profile 1.1:  
http://www.ws-i.org/Profiles/BasicProfile-1.1.html

This is a good example of the kind of thing I was hoping we'd do when I 
initially proposed the OIC TC.

From the introduction:

"This document defines the WS-I Basic Profile 1.1 (hereafter, "Profile"), 
consisting of a set of non-proprietary Web services specifications, along 
with clarifications, refinements, interpretations and amplifications of 
those specifications which promote interoperability."

"1.3 Guiding Principles" is also important, especially:

"Restriction vs. relaxation
When amplifying the requirements of referenced specifications, the Profile 
may restrict them, but does not relax them (e.g., change a MUST to a MAY). 
"

and

"Multiple mechanisms
    If a referenced specification allows multiple mechanisms to be used 
interchangeably, the Profile selects those that are well-understood, 
widely implemented and useful. Extraneous or underspecified mechanisms and 
extensions introduce complexity and therefore reduce interoperability."

And then you can read, starting in section 3 and following the set of 
numbered restrictions needed to conform to this profile. 

I'd told that the WS-I work is supported by IBM, Microsoft and Oracle.  So 
I'd like to think that the application of this successful, proven interop 
profile technique would be uncontroversial when applied to ODF.

-Rob