Definitely needed. Thanks to Joe for finding that. – Jim M
From: legalxml-courtfiling@lists.oasis-open.org [mailto:legalxml-courtfiling@lists.oasis-open.org]
On Behalf Of James E Cabral
Sent: Wednesday, May 30, 2012 8:42 AM
To: legalxml-courtfiling@lists.oasis-open.org
Cc: Joe.Mierwa@urlintegration.com
Subject: [legalxml-courtfiling] FW: ECF schema question
ECF TC:
Joe Mierwa has pointed out an issue with the ECF 4.01’s handling of multiple service recipients by the same service MDE:
The Service Message is a CoreFilingMessage which is based on ElectronicFilingMessageType which can include multiple occurrences of ElectronicServiceInformation (one for each recipient). From ECF-4.0-CommonTypes.xsd:
<xsd:complexType
name="ElectronicFilingMessageType"
abstract="true">
<xsd:annotation>
<xsd:documentation>The
base message for an electronic filing using ECF 4.0.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension
base="CaseFilingType">
<xsd:sequence>
<xsd:element
ref="ElectronicServiceInformation"
minOccurs="0"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType
name="ElectronicServiceInformationType">
<xsd:annotation>
<xsd:documentation>The
structure for the information needed to electronically serve other parties to the case.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension
base="s:ComplexObjectType">
<xsd:sequence>
<xsd:element
ref="ServiceRecipientID"/>
<xsd:element
ref="ReceivingMDELocationID"/>
<xsd:element
ref="ReceivingMDEProfileCode"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
The ServiceReceiptMessage, however, includes only 1 ServiceRecipientStatus which refers to only 1 recipient. Since ServiceReceiptMessage is a synchronous response, therefore, there is currently no way for a
Service MDE to acknowledge synchronously that it has received service for multiple recipients.
<xsd:complexType
name="ServiceReceiptMessageType">
<xsd:annotation>
<xsd:documentation>A
synchronous response by a Filing Assembly MDE acknowledging receipt of a service message for one of its clients.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension
base="receipt:MessageReceiptMessageType">
<xsd:sequence>
<xsd:element
ref="ServiceRecipientStatus"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType
name="ServiceRecipientStatusType">
<xsd:annotation>
<xsd:documentation>A
value describing the status of electronic service on a particular recipient.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension
base="nc:StatusType">
<xsd:sequence>
<xsd:element
ref="ecf:ServiceRecipientID"/>
<xsd:element
ref="ServiceStatusCode"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
To address this issue, I recommend changing the description and cardinality of ServiceRecipientMessageType to allow for multiple occurrences of ServiceRecipientStatus, ala:
<xsd:complexType
name="ServiceReceiptMessageType">
<xsd:annotation>
<xsd:documentation>A
synchronous response by a Filing Assembly MDE acknowledging receipt of a service message for one or more of its clients.</xsd:documentation>
</xsd:annotation>
<xsd:complexContent>
<xsd:extension
base="receipt:MessageReceiptMessageType">
<xsd:sequence>
<xsd:element
ref="ServiceRecipientStatus"
maxOccurs="unbounded"/
>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Jim Cabral
MTG Management Consultants, L.L.C.
www.mtgmc.com
(206) 442-5010
Phone
(502) 509-4532
Mobile
Helping our clients make a difference in the lives of the people they serve.
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you
received this in error, please contact the sender and delete the material from any computer.
From: Joe Mierwa [mailto:Joe.Mierwa@urlintegration.com]
Sent: Friday, May 25, 2012 12:04 PM
To: James E Cabral
Subject: ECF schema question
Hi Jim,
Looking at legal service, the core filing message allows for 0 to many ElectronicServiceInformation elements each containing 1 ServiceRecipientID. The serviceReceipt message only supports 1 and only 1 of the service status ID, which contains
1 Service Recipient ID. This seems like an error because the service receipt message is a synchronous message so if there were 10 service recipients on the request, wouldn’t you want 10 status elements in the receipt?
|
Joe Mierwa |
|
|
|
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in
error, please contact the sender and delete the e-mail and its attachments from all computers.