Re: [legalxml-courtfiling] Re: WS SIP SOAP samples

Eric,

The latest version of the SIP is the zip file attached to action item 60.

https://www.oasis-open.org/apps/org/workgroup/legalxml-courtfiling/members/action_item.php?action_item_id=3449

The document we are referencing is the original SIP document included in the SSP zip at the following location:

artifacts\various artifacts\ecf-v4.0-webservice=v2.01-csprd03

__
Jim Cabral
502 509-4532

From: Eric Eastman
Sent: ‎Wednesday‎, ‎June‎ ‎10‎, ‎2015 ‎3‎:‎19‎ ‎PM
To: James E Cabral
Cc: Gary Graham, legalxml-courtfiling@lists.oasis-open.org

Gary, Jim,

I downloaded ECF_SSP_v_4.01.1.zip from the OASIS website. That contains the WSDL and XSD, samples and more but it doesn't seem to contain the Document where you are quoting Section 2.5. Should it? Exactly which version of which document are we talking about?

Comparing the WSDL & schema from the SSP to the contents of this email, the sample XML conforms to the WSDL (visual comparison, I may have missed something)

This section of the WSDL:

</message>

specifies that the "GetCaseRequest" message (the input parameter to the GetCase operation) is implemented by the "CaseQueryMessage" xml element.

Section 7.1 of SOAP1.1 does seem to back up the wording of Section 2.5 quoted above. However it would be a major undertaking and a disruptive change to bring our WSDL into compliance with 2.5. I don't think any of our operations currently follow that convention.
http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383533

Here are a couple tiny (by SOAP/WSDL standards) examples.
http://www.w3.org/2001/03/14-annotated-WSDL-examples.html

My suggestion: Delete section 2.5 in it's entirety. It's better to say nothing than to say wrong things. Create an action item for 5.0 to make some intentional choices in this area.

Eric

On Wed, Jun 10, 2015 at 12:16 PM, James E Cabral <jec@mtgmc.com> wrote:

Appendix C and the samples are non-normative.

I think the fix is probably to relax the wording of Section 2.5 itself since there is no schema that defines an element called “GetCase”. The alternative would be to update the schemas in the Core Specification. Do you agree?

__
Jim Cabral
502 509-4532

From: Gary Graham
Sent: ‎Tuesday‎, ‎June‎ ‎9‎, ‎2015 ‎7‎:‎20‎ ‎PM
To: James E Cabral
Cc: legalxml-courtfiling@lists.oasis-open.org

See below

From: legalxml-courtfiling@lists.oasis-open.org [mailto:legalxml-courtfiling@lists.oasis-open.org] On Behalf Of James E Cabral
Sent: Tuesday, June 09, 2015 2:54 PM
To: Graham, Gary
Cc: legalxml-courtfiling@lists.oasis-open.org
Subject: [legalxml-courtfiling] WS SIP SOAP samples

Gary,

On the TC call today, you reported an incompatibility between Section 2.5 of the WS SIP specification and at least some of the SOAP samples, including GetCaseRequest.soap. I’m hoping you elaborate more on what you see as the incompatibility. The relevant snippets are included below.   Are you saying that you would expect to see “GetCaseRequest” instead of “CaseQueryMessage” inside of the soapenv:Body? No, there are no ECF operations named GetCaseRequest or CaseQueryMessage. However there is an operation named GetCase that takes CaseQueryMessage as a parameter (see C.3.1 of the ECF specification). Hence, the first child element of <soapenv:Body> MUST be GetCase since ‘GetCase’ is the operation name.

-------------------------------

WS SIP Section 2.5:

Each message transmission MUST identify the operation being invoked within the SOAP Body only; the (qualified) operation name MUST be the qualified name of the first child element of the SOAP body element, as called for in section 7.1 of the [SOAP 1.1] specification.

An MDE implementation MAY allow message transmissions that include a SOAPAction HTTP header.

In compliance with the [WSI-I BP 1.1] specification, a receiving MDE MAY NOT rely on the value of the SOAPAction HTTP header in processing the message.

-----------------------------

GetCaseRequest.soap:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

<soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing">

<wsse:Security soapenv:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

         …

</wsse:Security>

<wsa:Action>urn:oasis:names:tc:legalxml-courtfiling:wsdl:WebServicesProfile-Definitions-4.0\CourtRecordMDEPort\GetCase</wsa:Action>

<wsa:ReplyTo>

<wsa:Address>https://JEC-SURFACEPRO2:8080/mockFilingAssemblyMDEPortSOAPBinding</wsa:Address>

</wsa:ReplyTo>

<wsa:MessageID>uuid:48a86134-9712-451b-a4ee-036d408b4f07</wsa:MessageID>

<wsa:To>https://JEC-SURFACEPRO2/mockCourtRecordMDEPortSOAPBinding</wsa:To>

</soapenv:Header>

<soapenv:Body wsu:Id="id-53204E93D7C96443EC141342618529211" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

<CaseQueryMessage xsi:schemaLocation="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseQueryMessage-4.0 ../../schemas/information/message/ECF-4.0-CaseQueryMessage.xsd" xmlns="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CaseQueryMessage-4.0" xmlns:ecf="urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:CommonTypes-4.0" xmlns:j="http://niem.gov/niem/domains/jxdm/4.0" xmlns:nc="http://niem.gov/niem/niem-core/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

         …

</CaseQueryMessage>

</soapenv:Body>

</soapenv:Envelope>

__
Jim Cabral
502 509-4532

Eric Dimick Eastman
Green Filing, LLC

Web: www.greenfiling.com

Phone: (801) 448-7268

Cell: (765) 277-4158

legalxml-courtfiling message