• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
IJIS - Registry driven SOA's for Justice Integration (San ...

IJIS - Registry driven SOA's for Justice Integration (San ...






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • Adobe is one of the largest global SW companies with annual revenues exceeding $1.2B, over 3500 employees and operations in 40 countries worldwide, We have a 20-year history of delivering category-leading products and technologies that contribute to more effective communications. Adobe's overall vision is to help people, enterprises, AND GOVERNMENTS communicate better. For our government and commercial customers, this means helping them communicate better (more effectively and efficiently) with constituents, other agencies and even other governments across agency, system and geographical boundaries.
  • The Dictionary Data Model shows how our less than 500 data elements are grouped into data entities and flexibly associated to meet the documentation requirements of any Justice Sector Case. The backbone of the case consists of Events, Processes, and Activities, following the concepts and vocabulary of the WfMC (Workflow Management Consortium) Objects can be multiply associated with those Events and Activities by assigning the Object an Object Role for each context, e.g. Person may have an Object Role of Defendant in this Charge same Person may have an Object Role of Suspect in this Event, etc Similarly Objects can be directly associated with one another, e.g. Person owns Property which was found at a Location an Organization has a Location which may be its Civic Address or Telephone Number of type Voice Growth in the number of Roles and Affiliations needed will undoubtedly mushroom over time but that will not require any change to the structure of the model.

IJIS - Registry driven SOA's for Justice Integration (San ... IJIS - Registry driven SOA's for Justice Integration (San ... Presentation Transcript

  • Role of Registries in Service Oriented Architecture Jan 15, 2004 – San Diego Duane Nickull Senior Standards Strategist, Adobe Systems, Inc.
  • Introduction – Duane Nickull
    • Senior Standards Strategist, Adobe Systems Inc.
    • Team Lead (2001-2003) – United Nations/CEFACT eBusiness Architecture Group.
    • Chair (2002-2003) – UN eBusiness Working Group.
    • Former Co-lead /Chief Editor - ebXML Technical Architecture v 1.0
    • Worked on W3C Web Services Architecture, LE - XTract TM architecture & various Government Security/Justice initiatives.
    • Co-inventor of GoXML Search – Contextual XML Search engine
    • UN/CEFACT – OASIS Joint Coordination Committee Special Technical Liaison – W3C.
    • International SME – Registry/Repository
  • Integration: Problem area
    • Limited justice system integration (National)
    • Limited international sharing of intelligence information.
    • Information sharing is hindered at many levels (Zachman – Network, Motivation , Function, People and Data )
    • Einstein quote…integration?
    • Service Oriented Architecture (SOA) is an infrastructure to facilitate interoperability. Use 1..* Data models.
  • Service Oriented Architecture Overview
    • Modern Service Oriented Architectures (SOA’s) use registry systems (W3C Web Services Architecture, ebXML et al).
  • SOA Layer Decomposition SLA 1.. Supported Business Process <<References>> DTD’s Schemas? DTD’s Schemas? DTD’s Schemas? <<Constructed From>> 1.. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp. Core Comp Business Information Entities <<Constructed From>> <<Constructed From>> XML Representations XML Data Dictionaries context
  • What is a Registry/Repository?
    • A Registry is an infrastructure component that enables the registration and discovery of services, ontology's or other artifacts.
    • Neutral third party that facilitates interactions.
    • A shared resource, often in the form of a web-based service.
    • Can aid in solving many integration problems.
    Repository Registry Synchronization API I / O RIM
  • Relationship of Registry standards
  • Registry can provide registration Service interface Data Model Service choreography Physical network Intent/Policy Registry A G E N C y
    • Customer Services
    • Process Automation Services
    • Business Management Processes
    • Digital Asset Services
    • Business Analytical Services
    • Back Office Services
    • Support Services
    Other Agency … and subsequent discovery getServiceInterface() getDataModel() getSecurityRequirements() requestBinding() requestData() … JIEM et al
  • Justice Registry Prototype use case A Government of Canada pilot justice initiative. 9/25
  • Goals and Wish List.
    • Develop a library of re-useable data elements (similar to DoJ XML Justice Dictionary)
    • Share the Data Elements from a registry/repository.
    • Develop a methodology for process modelers to use the data elements to build transactions within their exchanges (Similar to JIEM).
    • Maintain and manage the library over time (Registry centric methodology).
    • Integrate with the international community (long term).
    • JIT privilege-based integration (long term).
  • Justice Data Dictionary goals RCMP Justice XML ON Courts NPB Customs 2000 2001 2002 2003 Existing Standards Harmonization! Corrections IJI v1.0 Data Dictionary
  • CPSIN IJI Logical Data Model
  • Object Role Object Object Affiliation Case Organization Property Person has Location found at owns responsible agency place of trial exhibit weapon suspect defendant Activity Event Process Charge Disposition CPSIN Data Model CPSIN = Canadian Public Safety Information Network
  • Registry expresses CPSIN Data Models
    • A Data Element has an Attribute.
    • What Agency asserts that information?
    • What Date was that information gathered?
    • How are instances of that information classified?
    • What amount of trust do I place on that information (Registry Audit Trail)?
    • What additional information MUST be associated with the assertion? Events MUST have an Agency who asserts them.
    • “ Context” can be asserted via Registry.
    • Roles and permission based access.
    • Complete Data Dictionary Management, versioning, event notifications, user defined ontology's and more.
    • Complexity of today’s data models REQUIRE Registry to manage them.
  • CPSIN IJI Data Elements (examples)…
    • Being
    • Being identifier
    • Event
    • Event type
    • Event date
    • Event identification code
    • Agency
    • Agency identifier
    • Agency case number
    • Etc…
  • Building Transactions with Data Elements JIEM Wrapper? Being Being.type Biometrics Identifier Description Description Identifier Biometrics Being.type Being Suspect Agency Case Links Event date Event
  • Information Sharing Use Case 1 US Law Enforcement Canadian Law Enforcement Web Service Interface Law Enforcement Registry All transactions assembled from Data dictionary in Registry. Request File For Suspect Response (XML) Who has details Of Being? What interface do I use? Justice Semantic Registry What does their Metadata mean in MY terms.
  • Event Notification - Use Case 2 US Law Enforcement Canadian Law Enforcement Canadian Registry Subscribe to any events (Event Profile) US workflow Registry Update my internal event workflow. Event notification Auditable Event Notification Support for: 1. Data Aggregation 2. Data mining 3. Event Probability Analysis 4. Pattern recognition 5. Audit Trails 6. Etc..
  • Registry eForms Architecture Registry enablement of Dynamic User interfaces and workflow.
  • Why Registry driven eForms?
    • ROI is very high.
    • Logical extension & next step to Data Dictionary.
    • eForms are common user interfaces to SOA’s.
    • Users familiar with many types of eForms (HTML, PDF etc) built on XML data models.
    • Abstracts “View” from Model and Control (MVC Philosophy).
    • Good data capture with integrity checks.
    • Justice/Law Enforcement depends on integrity of data captured. eForms facilitates.
  • Registry driven eForms – consumers of XML data dictionaries.
    • Life Management of eForms requires no further integration at client/user.
    • Changes published in to XML data model in Registry are reflected instantly to 1,000’s+ of forms/presentations. Real time system.
    • Instance data is data type consistent with applications. XML Data models use W3C Schema Data types.
    • Registry access control policy for instance data drives workflow based on model.
    • Flexible classification schemes and context mechanisms promote management of data models.
  • eForms Architecture
    • Receives data
    • Receives eForm template
    • Populates template
    • with data
    • Generates form
    • Signs form
    • Extracts content and metadata
    • Archives statements
    eForms Server Template/XML Data Model Registry and Repository eForms Design Tool uses XML Data Elements End user - eForms Presentation Archiving Registry and Repository Allows designers to quickly publish new eForms based on XML Data Models. Permissions based system – tight security.
  • Registry Driven eForms Sequence requests form template Process() Archive() Registry Registry Other Agencies N th Tier (UnKnown Users) Query for form structure Build Form Receive eForms data GUI Schema, DTD Registry UID Definitions Info Server Justice users ValidateForm() Convert2XML() ValidateForm() ErrorCheck() QueryRegistry() Applications ShareData() Semantic References QueryRegistry() Applications ?????()
  • Conclusions…
    • Registry Driven SOA’s, developed for eBusiness, work well for data integration.
    • Registry is the heart of modern SOA’s.
    • Registry agnostic to Objects. Any Object allowed. Supports new bread of “Smart” software.
    • Advanced, semantic content management helps facilitate complete integration.
    • Flexible, scalable taxonomy and ontology management.
    • Multi-layered security model compliant with many requirements.
  • Justice’s unique challenges…
    • Archive format – Registry + Archive format integrity and audit trail.
    • Security – Registry queries (USAF)
    • Legislative
    • Multi-lingual support (GoC – EN + FR)
    • Discussions?
  • Q & A
    • References:
    • CPSIN IJI - Canadian Government
      • [email_address]
      • (613) 957-2497
    • Registry Products - Duane Nickull
      • dnickull @adobe.com
      • (604) 738-1051
  • Supplemental Slides Data Harmonization
  • Data Model Harmonization
    • Harmonizing the Data model is a logical step.
    • Old models were driven by bottom up approach (take a common intersection of what all agencies have)
    • New models are driven by top-down approach (What do the stakeholders need to mine from the instance data)
    • Separating presentation of documents from structure and logic important (Think MVC)
    • Supported by Registry!
  • Examples of old data models
    • A relic of legacy data capture techniques.
    • Does not scale for aggregation models
    • Modern use cases for instance data never envisioned
  • Aggregation/Reconciliation Issues
    • How to rely on information that contradicts/conflicts?
    • Different masks
    • Different code sets
    • Assertion integrity
    • Dates of events
    • Data capture techniques
    • Agency audit trails
    • More…
  • New “Smart” Justice Object Model Process() Agency A Agency B Registry