OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

legalxml-courtfiling message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: ECF 4.0 GetDocument specification/implementation


Shouldn’t we be using NIEM Core “DocumentIdentification” ?

 

http://apps.ncsc.org/niem/ShowElement.aspx?element=nc:DocumentIdentification

 

I agree with Brian that there in nearly all instances a document identification number being sent from a filer’s / EFSP system and in turn placed in the court’s document repository (even if it is linked documents in a CMS)

 

Jim M

 

From: legalxml-courtfiling@lists.oasis-open.org [mailto:legalxml-courtfiling@lists.oasis-open.org] On Behalf Of Bryant Austin
Sent: Tuesday, June 16, 2015 9:21 AM
To: legalxml-courtfiling@lists.oasis-open.org
Subject: [legalxml-courtfiling] ECF 4.0 GetDocument specification/implementation

 

I am hesitant to add more questions, but as I have been working through implementation of ECF 4.01 I have found the following and am not sure of the real intent.  The beginning definition of the GetDocument message in the ecf-4.01-spec states a case number and a document number, but the xsd files show a nc:CaseTrackingID and a nc:CaseDocketID (pertinent parts of the definitions are below for reference).  The niem definition seems to have a definite difference between a docket and a document.  I don’t understand how a document can be located with just the case tracking ID and the docket ID without a document number.  There can be many documents associated with a case and each document should have its own identifying number.

 

Thanks!

 

The ecf-4.01-spec document states the following, “3.2.13 GetDocument The Filing Assembly MDE MAY invoke the GetDocument query operation, including the case number and document number, on the Court Record MDE to retrieve a particular document from a case.  The Court Record MDE will respond synchronously with the requested document or instructions on how to access it.

 

The ECF-4.0-DocumentQueryMessage.xsd has the following:

“              <xsd:complexType name="DocumentQueryMessageType">

                                <xsd:annotation>

                                                <xsd:documentation>A request for an electronic document in the court's official record. </xsd:documentation>

                                </xsd:annotation>

                                <xsd:complexContent>

                                                <xsd:extension base="ecf:QueryMessageType">

                                                                <xsd:sequence>

                                                                                <xsd:element ref="nc:CaseTrackingID"/>

                                                                                <xsd:element ref="nc:CaseDocketID"/>

                                                                </xsd:sequence>

                                                </xsd:extension>

                                </xsd:complexContent>

                </xsd:complexType>”

 

The niem-core.xsd has the following, “

                <xsd:element name="CaseDocketID" type="niem-xsd:string" nillable="true">

                                <xsd:annotation>

                                                <xsd:documentation>An identifier used to reference a case docket.</xsd:documentation>”

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]