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

 


Help: OASIS Mailing Lists Help | MarkMail Help

legalxml-courtfiling-comment message

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


Subject: ECF 4.0 Citation Case Schema


While reviewing the ECF 4.0 Citation Schema (ECF-4.0-CitationCase.xsd) I noticed the following:

 

1.       The schema contains a complex type “VehicleType” which extends the NIEM “nc:VehicleType” to include “VehicleOwnerInsuranceCoverage” and “VehicleOperatorInsuranceCoverage” but I could not locate an element declared for the VehicleType and Vehicle is not referenced in the schema thus no vehicle data elements are available.

 

2.       The “CitationCase” complex type contains the “CaseDisposition” complex type which in turn contains the “nc:CaseDispositionDecision” complex type.  The actual NIEM data elements located in the nc:CaseDispositionDecision are not included in the niem-core subset thus in the schema it is an empty complex type.

 

3.       The “j:CaseCharge” complex type is included in 2 complex types, the NIEM  “j:CaseAugmentation” type and the extension “CitationCaseAugmentation” type.  This leads to ambiguity as to which schema location the charging information should be placed.

 

4.       The ECF Common Types schema (ECF-4.0-CommonTypes.xsd) includes a complex type called “OrganizationType” which extends the NIEM “nc:OrganizationType” to include 2 additional types "j:OrganizationAugmentation” and “OrganizationAugmentation”.  All of the entity types “CaseDefendantParty”, “CaseInitiatingParty” etc. contain 2 complex types called “EntityOrganization”.  This causes ambiguity for a potential adopter which can be removed by not including the NIEM “nc:OrganizationType” as a substitutable element for “nc:EntityRepresentation”.

 

5.       The ECF Common Types schema (ECF-4.0-CommonTypes.xsd) includes a complex type called “PersonType” which extends the NIEM “nc:PersonType” to include the additional type “PersonAugmentation”.  All of the entity types “CaseDefendantParty”, “CaseInitiatingParty” etc. contain 2 complex types called “EntityPerson”.  This causes ambiguity for a potential adopter which can be removed by not including the NIEM “nc:PersonType” as a substitutable element for “nc:EntityRepresentation”.

 

6.       Unclear where name information should be placed for a person receiving a citation.  Is the person in question a “Citation Subject” or a “Case Defendant Party”.  The “j:CaseDefendantParty” type contains the “EntityPerson” type which in turn contains the “nc:PersonName” type for inclusion of name data.  The “CitationCaseAugmentation” extension type contains the “CitationSubject” extension type which does not contain data elements for person name data.  The “CitationSubject” type contains the “PersonAugmentation” complex type while the “CaseDefendantParty” complex type contains “PersonName” which in turn contains the “PersonAugmentation” complex type.  It is also unclear when one path should be selected over the other for the data associated with the “PersonAugmentation” type.

 

 

Best Regards,

 

Edmund Herbert

 

 

Edmund Herbert
Information Services Division
Judicial Council of California - Administrative Office of the Courts

455 Golden Gate Avenue

San Francisco, CA 94102-3688

Office 415-865-5336, Cell 415-624-7652, Edmund.Herbert@jud.ca.gov

www.courts.ca.gov

 

"Serving the courts for the benefit of all Californians"

 

 

 



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