RE: DPS Disposition Exchange Schema mapping with ECF-4.0

["Cabral, James E." <JCabral@mtgmc.com>]

Ron,

Here are my responses to each of the mapping issues your programmer
found.  Many appear to be specific to disposition reporting or local
elements to Utah.  But he did identify several problems with the NIEM
subset and ECF schemas that I've now corrected. 

I've attached the list of issues with my responses as well as an updated
mapping spreadsheet.

Please let him know that I really appreciate the feedback.  

  Thanks,

Jim Cabral 
James E. Cabral Jr. 
MTG Management Consultants, L.L.C. 
(206) 442-5010 
www.mtgmc.com
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.



-----Original Message-----
From: Ron Bowmaster [mailto:ronb@email.utcourts.gov] 
Sent: Thursday, August 28, 2008 10:22 AM
To: Cabral, James E.
Subject: Fwd: DPS Disposition Exchange Schema mapping with ECF-4.0

Morning Jim,

I'm forwarding some comments on ECF 4 from the Public Safety programmer.
Granted, he's working on disposition reports, but we're trying to use
references in the standard.

Ron

>>> Ken So 8/27/2008 6:54 PM >>>
Ron,
I have attempted to map the current Disposition data items with ECF-4.0
schema. Please find the attached document: DPS Disposition Schema
Mapping with ECF 4.xls. Legends are as followed.

1. Under Notes column, I identified the issues/problems I found on your
document (ECF-4.0-NIEM2-mapping.xls) with RED font. Notes in BLACK font
is just comment for my information.

2. The column named "ECF-4.0 NIEM2-Mapping" is the element with path in
your document. "ECF-4.0 Source Line #" column specifies the row # in
your document. "ECF-4.0 Source Property" specifies the property of the
row in your document.

3. Rows that are highlighted in PINK color are the ones that I couldn't
find the matching element in ECF-4.0 schema.


For your convenience, I have re-listed the issues/problems that I found
in your document in the ascending order of the rows in your document. 

Row#3: The description in ECF4.0 seems to be correct but the actual
mapped NIEM element is not the right one.

Row#42: The abstract element nc:ActivityDateRepresentation should be
replaced by nc:ActivityDate.

Row#44: j:ArrestingAgency does not have the child element
j:OrganizationAugmentation. You can add j:OrganizationAugmentation to
your own substituted type of nc:OrganizationType but it is not currently
done that way. Please verify.

Row#85: In ECF-4.0-CoreFilingMessage-Appellate.xml sample xml file,
nc:DocumentPostDate doesn't go under nc:CaseFiling but rather under
CoreFilingMessage. What is the correct way to use nc:DocumentPostDate
element?

Row#108: nc:CaseTrackingID is already a string and therefore,
nc:IdentificationID is not required.

Row#153: On row 561, there is also another element for Judge. Which one
should I use for Disposition?

Row#227: The NIEM mapping column is not defined properly. It should be
j:Citation/nc:ActivityIdentification instead of
CourtEvent/CourtEventActor/nc:RoleOf

Row#238: There is no child j:IncidentViolatedStatuteAssociation element
under the type of j:CitationViolation. Please check. And there is also
spelling error in j:IncidentViolatedStatuteAssociation

Row#273: There is no CaseCourt under nc domain but there is one under j.

Row#274: Is j:CaseAugmentation a child element of j:Case by default?

Row#319: nc:EntityPerson does not have a child element called
j:PersonAugmentation. Should EntityPerson element be of an ECF type and
substitued for nc:EntityPerson? A type from niem-core namespace should
never contain an element from justice domain.

Row#420: I am so sure about this mapping. Targeted violence may not be
just limited to domestic.

Row#426: The NIEM mapping column shold read
"nc:DriverLicense/nc:DriverLicenseIdentification/nc:IdentificationJurisd
ictionNCICLISCode" (Spelling error and misuse of abstract element and
type). Please check.

Row#431: j:IncidentAugmentation is not the child element of
j:DrivingIncident by default.

Row#433: This is an abstract element substitutable by
j:DrivingIncidentHazMatCode or j:DrivingIncidentHazMatText but there is
no indicator substitution by default.

Row#434: j:DrivingAccidentSeverityCode is mispelled. Please check.

Row#442: Why does this property has the same name with the one above?
Typo? We use the same element but it is under different hierarchy.

Row#787: nc:IdentificationJurisdiction is abstract and therefore, a
substitution is needed. Should j:IdentificationJurisdictionNCICLISCode
be the right one to use?


According to the definition SentenceDescriptionText, all the sentence
components will be identified by SentenceDescriptionText. This can
create potential problem because if SentenceDescription is arbitrary
text, there is no way to parse if the sentence has components like
Probation, Suspended Time, Restitution, etc. 


I am open to a meeting in person and discuss these issues.

Regards,

Ken So
801-910-0040

DPS Disposition Schema Mapping with ECF 4.xls

ECF-4.0-NIEM2-mapping.xls