[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [legalxml-courtfiling] Proper Use of SendingLocationMDE
|
Gary, The definitions of message:SendingMDEProfileCode and message:ReceivingMDEProfileCode
still referred to “message profiles” which were renamed “service
interaction profiles” in ECF 3.01 to bring us into conformance with the
OASIS SOA Reference Model. I have now updated the definitions. The profile
codes are defined ECF 3.0 Service Interaction Profiles, e.g. the ECF 3.0 Web
Services Service Interaction Profile uses the following code: urn:oasis:names:tc:legalxml-courtfiling:schema:xsd:WebServicesMessaging-1.0. Regarding the SendingMDELocationID, the complete definition is “Location
for the MDE to which asynchronous and service messages can be sent. This unique
location is self-assigned by the MDE.” This definition is
consistent with its use. In short, the MDE receiving a message already
knows its own ID – it just needs to receive the ID of the sending MDE. In your example: FilingReview operation 1.
FilingAssemblyMDE sends a CoreFilingMessage with
SendingMDELocationID set to the FilingAssemblyMDE’s ID. 2.
FilingReviewMDE sends a MessageReceiptMessage (synchronous
response) with SendingMDELocaitonID set to the FilingReviewMDE’s ID. NotifyFilingReviewComplete operation (after review and docketing
is complete): 3.
FilingReviewMDE sends a ReviewFilingCallbackMessage (asynchronous
response) with SendingMDELocaitonID set to the FilingReviewMDE’s ID. Does this clarify? Jim Cabral James
E. Cabral Jr. 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: Graham, Gary
[mailto:GGraham@courts.az.gov] I’m
having some trouble trying to determine the proper use of the elements <message:SendingMDELocationID> and <message:SendingMDEProfileCode>, specifically in the
CourtPolicyResponseMessage, but generally, in any message. From
the XSD, you can find the following definitions: <message:SendingMDELocationID> - Location
for the MDE to which asynchronous and service messages can be sent. This unique
location is self-assigned by the MDE. <message:SendingMDEProfileCode> - Code
identifying the message profile being used by the sending filing assembly MDE.
This list should be extensible to accommodate future messaging profiles. Each
code value is specified within the message profile approved for use with ECF. The
Sample XML simply shows ‘MDEID’
as the example for Location, and ‘MESSAGINGPROFILEID’ for the Profile. So
here’s my question: In the CourtPolicyResponseMessage which is being
returned to the Filing Assembly MDE from the Filing Review MDE, should the <message:SendingMDELocationID>
identify
the Filing Assembly MDE and not the Filing Review MDE? On
the Sequence Diagram from the specification document (i.e.
ecf-v3.01-spec-wd02.doc, page 23) the response is shown as a dashed line which
indicates a synchronous response. However, the definition of <message:SendingMDELocationID> addresses
‘asynchronous and service messages’; it is neither. Is this just an
error in the definition or am I missing something? The
definition for <message:SendingMDEProfileCode> talks about a
“message profile”. What is a “message profile”, and
where is this defined? It also mentions a “list”. Where is this
list of message profiles? How are practitioners using this element? Also,
it says it’s the profile “used by the sending filing assembly
MDE”; so if the answer to the first Location question is Filing Review
MDE and not Filing Assembly MDE as I suggest, then please explain. Thank
you in advance for your considered response, Gary
Graham Arizona
Supreme Court |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]