1. Introduction1.3.4 OASIS Reference Model for Service

Oriented Architecture2. ECF 4.0 Architecture

2.1 Core vs. Profiles

2.2 Major Design Elements

2.3 Information Model2.3.1 Messages2.3.2 Attachment2.3.3 Sample Message Streams

3. ECF 4.0 Process Model3.1 Filing-Preparation-to-Docketing PM3.2 Business Rules3.3 Message Business Rules3.4 Filing the Record on Appeal

4. ECF 4.0 Schemas

5. Service Interaction Profiles6. Document Signature Profiles7. ConformanceAppendix A. (Informative) Release NotesAppendix B. (Informative) ECF 4.0 Development Appendix C. (Informative) MDE OperationsAppendix D. (Informative) Example InstancesAppendix E. (Informative) OngoingAppendix F. (Informative) AcknowledgmentsAppendix G. (Informative) Revision History

Document IntroductionService Overview

Purpose*Scope*Capabilities*Real-World Effects*SummaryDescriptionSecurity Classification*Service Specification Package Version*

Business ScenariosBusiness Scenario

Primary FlowAlternative Flows*

Service Interoperability RequirementsService Assumptions*Service DependenciesExecution Context*Policies and Contracts*Security*Privacy*Other Requirements

Additional InformationService Model

Information ModelIEPD Reference

Data Inputs*Data Outputs*Data Provenance*

Behavior ModelAction Model*Process Model*

Appendix A - ReferencesAppendix B - GlossaryAppendix C - Document History

Color denotes details for an SSP that are not expressly identifiable or contained as part of the ECF content.

ECF/SSP Layout Comparison

Assessment• ECF perspective is a top down perspective

– focused on the larger business process and architecture referred to as court filing

– Contains 4 independent services that interact with one another– Court Record and Filing Review each consolidate operations related to

• Court Filing• Query Services in support of out-of-scope local business processes

– Only really focuses on services as part of informative Appendix– All ECF services share common process model, information models

and service profiles• SSP perspective is bottom up

– Focuses on a services location in a larger business model– Tendency to focus on parts of a potentially larger process model that

is associated with an architecture

Alignment Recommendation• Keep high level focus of ECF specification

– Do not refactor into separate SSPs• Keep shared information and behavioral models as common

sections• Augment common sections with missing common service

interoperability information• Add MDE Service (SSP) Normative sections for each Service

either:– Between sections 4 and 5, or– As Normative Appendixes– Replaces Appendix C– Add normative appendix mapping of ECF to SSP v0.9.7 – Define service specific artifacts (catalog, metadata, etc) for each

service