SOAP 1.2 consolidated requirements

I took a todo to provide a consoladited list of SOAP 1.2
requirements. Well, here's the list!

I believe this discharges me of my action item.

Jean-Jacques.

SOAP 1.2 Messages
    
DR028

    [MUST] JJM: Describe SOAP 1.2 messages, including header, body, encoding, fault, RPC, actor (charter says: "must describe messages available via interface", "must describe error messages" and "make sure SOAP 1.2 extensibility mechanism can be expressed").
NR037

    JJM: Must describe SOAP 1.2 MEP (Message Exchange Pattern) (charter says: "must [...] describe [...] one-way messages, [...] request-response") (Last discussed 28 Feb 2002. Duplicate of R036.)
DR077

    [MUST] JS: Be able to describe SOAP 1.2 messages. (Duplicate DR028)
DR078

    [MUST] JS: Provide a normative description for SOAP 1.2 messages. (Duplicate DR028)
DR079

    [MUST] JS: Be able to describe SOAP 1.2 Header elements and Body elements. (Duplicate DR028)
DR080

    [MUST] JS: Be able to describe SOAP 1.2 Faults. (Duplicate DR028)    
DR029

    [MUST] JJM: Describe SOAP 1.2 header and body's content type (charter says: "must define [a mechanism for describing data types and structures] based on XML Schema" and "take into account encoding work going on in XML Protocol").



SOAP 1.2 Binding

DR061

    [MUST/SHOULD] Charter: It is expected that in the near-term future, Web services will be accessed largely through SOAP Version 1.2 (the XML-based protocol produced by the XML Protocol Working Group) carried over HTTP/1.1, or by means of simple HTTP/1.1 GET and POST requests. The Working Group will describe the following bindings:

       1.

          [MUST] SOAP Version 1.2; SOAP can be used over a variety of underlying protocols; the Working Group will provide a concrete SOAP Version 1.2 over HTTP binding.
       2.

          [SHOULD] HTTP/1.1 GET and POST requests.
DR062

    [MUST] Charter: The Working Group will also ensure that other SOAP bindings can be described.
DR063

    [MUST] JJM: Ensure that SOAP 1.2 bindings to SMTP or BEEP (for example) can be described (charter says: "ensure that other SOAP bindings can be described"). (Duplicate DR062 ?)
DR065

    [MUST] JS: Provide a normative description of the binding for SOAP 1.2. (Duplicate DR061)



SOAP 1.2 RPC

DR030

    [SHOULD] JJM: Describe SOAP 1.2 RPC parameters types (ibid.).



SOAP 1.2 Intermediaries
DR031

    [SHOULD] JJM: Support SOAP 1.2 intermediaries (charter says: "make sure SOAP 1.2 extensibility mechanism can be expressed")



SOAP 1.2 Extensibility Mechanism

DR025

    [MUST] Charter: The Working Group will make sure that SOAP Version 1.2's extensibility mechanism can be expressed.