Notes
Slide Show
Outline
1

XML for Legislatures: A Case Study on the Automation of Law


  • http://XMLPlanning.com/XDNCD
2
XML Planning Group…
  • A consortium of existing organizations
  • Technology and product neutral
  • Focused on the intelligence stored in data
  • Experienced in legislative document
    and process environments
    • Ohio
    • Minnesota
    • Idaho
  • General consulting and education
    in a variety of State and Federal agencies
    • California
    • Colorado
    • New York
    • Ohio Supreme Court
    • Texas
3
Our perspective
  • Real world XML solutions “immortalize” the intelligence in data
    • We believe that real world solutions only work when
      • the client IT community
        is involved
      • the end user is involved
      • change is managed effectively
      • expectations are managed
    • We are committed to
      education and knowledge
      transfer
4
Consulting to States
5
XML de-mystified…
  • XML is
    • A family of international standards at the heart & soul of all new technological developments
    • A meta-language for
      identifying and marking
      structured data
    • Based on tags delimiting
      elements and attributes
      (similar to HTML)
    • Verbose, but that’s OK
    • Both machine readable
      and human intelligible
6
Legislative Data
7
MN - XTEND Summary
  • XML-Based Text Editor New Development
    • 70 users in Legislature
  • Phase I:
    • Legislative Documents
    • Senate Documents
    • Doc Repositories
    • Search capabilities
    • Security Model
8
What should a new solution do?
  • Streamline the processes of authoring, manipulation and publication
  • Provide a series of applications that meet the users’ needs while providing each user access to a central set of structured data
  • Facilitate enhancements and ongoing process changes with minimal impact on the core functionality
9
What should a new solution do?
  • Mitigate the risks associated with the use of proprietary technologies and products
  • Promote the adoption of open industry standards
  • Allow the legislative IT community to perform its primary function – support of the legislative process – with a minimum of the traditional IT headaches
10
Project Timeline
11
Programmer’s Work Area
12
Technology – Inventory
  • Hardware
    • HP Proliant DL380 G3
      • Intel Xeon 2.80 GHz
      • 2GB RAM
      • 2 x 36 HDD
    • HP EVA3000 (SAN)
      • 550 GB now
      • > 1TB total capacity

  • Operating System
    • MS Windows 2003 Server
    • Citrix MetaFrame Presentation Server 3.0


    • Red Hat Linux
      • Advanced Server 3.0
13
Technology – Inventory  (cont.)
  • Commercial Apps
    • Arbortext
      • Epic • E3
      • Styler • Architect
      • Print Composer
    • Oracle 10g
      • JDeveloper
      • App Server
      • Database with RAC
    • Open Source
      • CVS, Ant, CruiseControl
    • Sparx
      • Enterprise Architect
    • Elementool
  • Custom Apps in
    • Sun J2EE
    • Arbortext ACL
    • Perl
    • PHP


14
Service-Oriented Architecture (SOA)
  • Corner-stone design principle in XTEND
  • Simple (and compelling) business drivers:
    • Reduce costs by adopting standards-based software built on commodity hardware, widely-supported development languages, and operating systems
    • Increase business responsiveness, preserve high-quality performance, and ensure reliability by focusing software development and integration on re-usable services rather than redevelopment efforts
15
XTEND – Logical Architecture
16
XTEND – Physical Architecture
17
3 Environments
18
Modular Legislative Schemata
  • <!ENTITY % statute_structure SYSTEM "statute_structure.dtd“ >
  • %statute_structure;
  • <!ENTITY % volume_info SYSTEM "volume_info.dtd" >
  • %volume_info;
  • <!ENTITY % volume_analysis SYSTEM "volume_analysis.dtd" >
  • %volume_analysis;
  • <!ENTITY % title_info          SYSTEM "title_info.dtd" >
  • %title_info;
  • <!ENTITY % title_analysis      SYSTEM "title_analysis.dtd" >
  • %title_analysis;
  • <!ENTITY % part_info           SYSTEM "part_info.dtd"      >
  • %part_info;
  • <!ENTITY % part_analysis       SYSTEM "part_analysis.dtd"   >
  • %part_analysis;
  • <!ENTITY % chapter_info        SYSTEM "chapter_info.dtd"  >
  • %chapter_info;
  • <!ENTITY % chapter_analysis    SYSTEM "chapter_analysis.dtd" >
  • %chapter_analysis;
  • <!ENTITY % stat_sect_text      SYSTEM "stat_sect_text.dtd" >
  • %stat_sect_text;
  • <!ENTITY % stat_sect_hist      SYSTEM "stat_sect_hist.dtd"  >
  • %stat_sect_hist;
  • <!ENTITY % table_structure     SYSTEM "table_module.dtd"   >
  • %table_structure;
  • <!ENTITY % common_vocab        SYSTEM "common_vocab.dtd"   >
  • %common_vocab;
19
Complex Legislative Processing
  • The legal requirements for immortalized line numbers add complexities to legislative documents


  • Not typically supported by products out of the box
20
Arbortext for Bill Drafting in MN

  • Epic XML editor
  • Enterprise E-Content Engine (E3)
  • Arbortext Architect
  • Arbortext Styler
  • Arbortext Repository Adapter for Oracle


  • Goals for the use of Epic Suite:
  • Improve authoring productivity and time-to-publication
  • Provide legacy “look-alike” capabilities where desired
  • Ensure tight and seamless integration with other parts of the technology stack
  • Facilitate “touch once, use often” data modularity
  • Standardize all published versions of documents (print, Web, local online, PDF, etc.)


21
XML Curriculum
22
Web Development
23
Java Curriculum
24
.NET Curriculum