Update/Reconcile NIEM Mappings with NIEM 3.0 Including

ECF 5.0 Core Specification Change Log:

IEPD Changes

-Update/reconcile NIEM mappings with NIEM 3.0 including:

Change data type of element j:Offense from nc:IncidentType to j:OffenseType in the NIEM 3.0 subset
Validate justice associations currently in ECF NIEM subset are still valid in NIEM 3.0
Add j:DrivingIncidentBloodAlcoholContentNumberText to j:DrivingIncidentType in the NIEM 3.0 subset and deprecate PersonBloodAlcoholNumber
Add new element j:JuvenileAsAdultIndicator to j:PersonChargeAssociationType in the NIEM 3.0 subset
Add support for new NIEM Children Youth and Family Services (CYFS) domain including:
Resolve overlap of new delinquency and dependency elements in ECF juvenile case type
Resolve overlap of new child support enforcement elements with ECF domestic case type
Align schemas with UML Profile for NIEM 3.0 (TBD)

-Update UBL 2.1 references to Committee Specification 1 (2013 June 29)

-Add new messages

ServeProcess - limited electronic service of process (electronic delivery to process servers and registered agents)
GetCourtSchedule – court scheduling
ReserveCourtDate – court scheduling
AllocatedCourtDate– court scheduling

-Fix cardinality issues including:

Make CaseCharge optional in some cases to allow criminal-related filings without charges (e.g. Probation reports)
Relax definitions to allow case-type extensions to be used in any filings
Make Document metadata and rendition in FilingLeadDocuments optional.
Make required elements explicitly "maxOccurs=1" and setting PersonLastName to "maxOccurs=1"?

-Add Affected PartyID and AdditionalData to DocumentMetadataType

-Add the following elements in nc:CaseDispositionDecision to the NIEM subset:

nc:CaseDispositionDecisionCategoryText - A kind of decision made in a case disposition.
nc:CaseDispositionDecisionText - The literal language of a decision.

-Eliminate j:CaseCharge from CitationCaseAugmentation

-Fix inconsistencies between ECF error codes and specification including:

Specification Changes

-Clarify scope

Clarify that the specification does not define how clerk review is completed (automated, manual, etc.). Manual clerk review is not required - auto-acceptance of filings is supported.
Clarify that filers may re-submit filings to correct minor errors. This should be a feature of the Filing Assembly MDE.

-Add new features

New Court Scheduling MDE including new machine-readable court policy, filing-preparation to docketing process, 3 new messages and business rules
Limited electronic service of process to process servers and registered agents
Optional expressions of Court Policy using Legal RuleML? Defer decision to early 2014, Michael Alexandrou will work with LegalRuleML/Monica Palmirani to provide examples of how LegalRuleML can satisfy our ECF 5.0 Court Policy Requirements
Security roles and groups (per McMillan paper)?
Better support for paper on demand and court forms?
Court Record MDE pull mode (per Mysko paper)?

-Update to latest version of NIEM (3.0)

Conform with NIEM Model Package Description (MPD) 1.1 (2012 Oct 1) guidelines.The ECF subset and extension schemas should be considered a NIEM BIE.
Align UML and mapping spreadsheet with UML Profile for NIEM 3.0 (TBD)

-Update to latest version of OASIS UBL (2.1 Committee Specification 1, 2013 June 29)

-Update ECF 5.0 Web Services SIP to conform with latest versions of Global Reference Architecture (GRA) specifications

GRA Web Service SIP v1.3 (May 2012)
GRA Execution Context 1.2 (Nov 2012)
GRA Service Specification Package (SSP) v1.0.0 (Aug 2012)

ECF 4.01 Core Specification Change Log:

IEPD Changes

-Address gaps in ECF-4.0-CitationCase.xsd identified by Doxpop including:

include a nc:Vehicle element in CitationCaseAugmentation
Add j:IncidentAugmentation to DrivingIncident
Add j:DrivingAccidentSeverityCode to the NIEM subset.

-Change the definition of FilingCompletionDate to “the date and time on which the Court Record MDE filing process was completed following the acceptance by the Filing Review MDE”

-Make the following elements optional in the schemas:

ProsecutionRecommendedBailText
FilingConfidentialityIndicator
ColorRelevantIndicator
RedactedIndicator

Specification Changes

-Clarify the UBL structures used by ECF 4.0

-Change references to separate ECF 3.x-style “messages” with ECF 4.0 “extensions”.

ECF 4.0 Core Specification Change Log:

IEPD Changes

Remap domain mode to conform to NIEM 2.0

»Map some elements in the ECF subset schemas to NIEM Core rather than Justice domain (e.g. Persons, Addresses, etc.)

»Remap some ECF extensions to new and updated codelists and content in new domains (e.g. new drug category codes, updated language codes, new FBI namespace, new immigration domain)

»Change all ECF 3.1 extensions based on SuperType to either be based on s:ComplexObjectType or include s:SimpleObjectAttributeGroup

»Replace some inheritance and references with associations and roles (e.g. Pro se defendants would be mapped as persons with both defendant and defense attorney roles)

»Add support for type substitution (e.g. enable local courts to override ECF code lists)

»Perform mapping and subset schema generation using new NIEM 2.0 tools

»Add support for alternate contact information through NIEM contact information model.

»Update party attorney relationships to use NIEM 2.0 improved support for roles and associations

»Combine core, casetype-specific and court-specific messages to support NIEM extension mechanisms.

Add support for appellate courts case types including:

»Add a new case-type-specific message based on the new appellate domain model

»Change case lineage to support a hierarchy of multiple-levels of case lineage

»Add the required elements and identifiers to support the ordering of trial court transcripts.

Add better support for traffic, ordinance violations and parking cases including:

»Create a new citation case type message for traffic, ordinance violation and parking case types in jurisdictions that handle these matters as civil rather than criminal cases.

»Include the element for the name of a code in the message.

»Add lot or facility and meter number or space number for ordinance and parking cases.

»Implement significant changes to our approach to the traffic and ordinance case structure.

»Replicate both the traffic and ordinance structure within the criminal case type message to support those jurisdictions in which traffic and ordinance violations are filed as counts in a criminal complaint, information or indictment.

»Add a “red light camera case” indicator to both the criminal and civil traffic case type messages.

Add support for genericode in code tables including defining the columns and keys for existing code tables defined in the ECF specification.

Add new default genericode codelists where appropriate.

Align our current case types with the NCSC case types.

Include additional core judgment elements.

Remap Payments and Receipts to UBL 2.0

Allow more than one document type to be submitted for a filing. The specification will alert courts to the danger of accepting more than one document type for a single filing and how to constrain a court’s implementation so as not to allow multiple document types to be submitted.

Add metadata for multiple renditions (e.g. redacted, multiple language, sealed status) of documents.

Regenerate the constraint schemas

»Change the cardinality of CourtEvent to support multiple documents

Regenerate sample instance for each message

Review compliance with NIEM User’s Guide and NIEM Naming and Design Rules (NDRs)

Specification Changes

Add chunking as an optional feature of SIPs.

Include Brian Hickman’s suggested changes to the text of the specification concerning service.

Add edits of the ECF 3.1 specification to improve readability that were deferred to ECF 4.0 including:

»In section 1.3, replace “leverages” with something more clear.

»In section 1.3.1, note that the use of GJXDM/NIEM element names does not require any change in local legal terminology. XML tag names are invisible to the user of an application employing them.

»In section 1.7, use a publicly accessible URL for the reference to the committee charter.

»In section 2, add words to indicate “recording a filing” involves adding documents that constitute the “filing” into the “court document management system” to resolve the ambiguous language.

»In section 2.2, use the term “legal service” when referring to the business process. Thus, the Service MDE will be renamed the Legal Service MDE.

»In section 2.3.3, substitute “supporting document” for the business context and “message attachment” for the technical context.

»In section 3.2.8, change the reference to the SHA algorithm to “SHA 256”.

»In section 3.3.3.3, use “retain” rather than “archive”.

Add explanatory language on options for using the MDEs in the specification and the requirement to support all messages when implementations do not include all MDEs.

Add support for appellate courts case types including:

»Support a record on appeal as an index document with attachments.

»Support additions to a record on appeal as a new index document with only the new documents attached.

»Support deletions from a record on appeal as a new index document with an attached document that indicates the DocumentDocketIDs of the documents to be deleted.

»Explain the problem with an appellate court rejecting a subsequent message modifying the record on appeal if a previous such message is still pending. The issue is that the trial court’s further corrected index will have to assume that the previous corrected index was accepted by the appellate court.

»Consider the use of the trial court case number for the record on appeal since the appellate court case number doesn’t exist yet.

Update OASIS Notices (IPR statement)

Complete OASIS Specification Checklist

Update acknowledgements

ECF 4.0 Web Services SIP Specification Change Log:

Improve MTOM support when next version of WS-I Basic Profile is released

Add support for bulk filings

Add support for chunking using Web Services Reliable Messaging (WSRM) features to track sequential messages.

Validate WSDL with Eclipse

ECF 4.0 Email SIP Specification Change Log:

Develop email SIP

Clarify that the email SIP is only approved use is for the transmission of courtesy notices, not for official information exchanges.

Future:

Provide a non-normative guidance document suggesting alternative methods (best practices) for courts and vendors to implement service, including a multi-vendor environment model.