ODMA Support
Year 2000
Statement of Work

Last updated 2006-01-11 18:50 -0700 (pdt)

Performance against the Year 2000 Statement of Work is an accountability of the AIIM DMware Technical Coordinator.  Six elements apply to the support of ODMA.

The statement of work was reviewed and approved on March 15, 2000.  This material is updated and accounted for as DMware Clearinghouse organization continues over the course of the year.


Statement of Work: January 1 - December 31, 2000

1. Organize Existing Material

Organize existing materials for access and utilization under open-source license agreements.

2. Define and Document Procedures

Define and document additional procedures, in conjunction with AIIM staff, for any collaborative open-source projects and their project management.

3. Review Submissions

Review new submissions and updates for appropriate license and technical compliance.

4. Provide Timely Response

Provide timely response to questions from users and developers on technical matters until peer-support structure is operating successfully.

5. Establish Metadata Clearinghouse

Establish metadata clearinghouse with initial content based on DMA 1.0, ODMA 2.0, and existing trial-use proposals; define clearinghouse and promote its technical use by users and vendors through the Web-DM Interoperability Forum and other venues.

6. Evangelize DMware

Evangelize DMware in the open-source community: contribute links, white papers and supporting information for the DMware clearinghouse at AIIM to increase visibility and utility to the AIIM information-management community.


1. Organize Existing Material

Organize existing materials for access and utilization under open-source license agreements.

1.1 Make Current Materials Available On-Line

2000-05-30: The HTML version of the ODMA 2.0 Specification is provided on-line for downloading, direct review, and use in cross-references from annotations, supplements, and technical discussions.

2000-05-17: The ODMA Downloads Area is created and all ODMA 2.0 materials are posted for direct download from the Web.  The ODMA 2.0 Connection Manager source code is included, for inspection and use in confirmation of operation, trouble-shooting, and later updating.

1.2 Archive Historical Materials and Make Available On-Line

2000-06-19: All materials have been collected and archived, except the ODMA List Server materials.  Putting the material on-line has secondary priority to completion of immediately-required structures for support of ODMA 2.0.

2000-04-08: All known ODMA materials are captured from other on-line sources and retained for review and reposting to the DMware ODMA site.  This includes earlier versions of the specification, earlier versions of the ODMA SDK, and other materials compiled about ODMA, including the tutorials and overviews carried on Colin O'Brien's activedoc.com site.

2000-02-16: In preparation for the DMware setup, Bob St. Jean contributes all historical information that he retained, including a draft time-line of the historical development of ODMA.

1.3 Update Materials for Open-Source Licensing

2000-06-19: Materials are currently covered by AIIM copyright notices.  These notices are valid and the material can be used subject to those copyrights.  When the DMware simple license is completed and approved for use, the relevant materials are to be updated so that the license is incorporated in and provided along with the material.  It will then be unnecessary to contact AIIM for specific rights and permissions that are explicitly granted under the open-source license.

2. Define and Document Procedures

Define and document additional procedures, in conjunction with AIIM staff, for any collaborative open-source projects and their project management.

2.1 Formalize Support Activities

Before new projects are created, support for existing ODMA 2.0 specifications and software is formalized.  In addition to providing on-line access to materials, an on-line support area is created.  The support area is used to formalize 

2000-05-17: Experimental incident report structure adopted and applied to an initial critical problem.

3. Review Submissions

Review new submissions and updates for appropriate license and technical compliance.

2000-06-19: There are no new submissions to process at this point.  As any major maintenance is performed, enough submission machinery will be put in place to apply it to the maintenance activities.  Arrival of new contributions will also be used as occasions for raising the level of submission support.

4. Provide Timely Response

Provide timely response to questions from users and developers on technical matters until peer-support structure is operating successfully.

4.1 Create On-Line Support Area

2000-06-19: Support area reorganized and expanded to include additional material, especially trouble-shooting tips for isolating problems where ODMA connections and operations are suspected to be operating improperly.  The statement of work is published, and an initial statement of approach is developed.  There is a 24-hour response time, with tracking and of actual response performance.

2000-05-17: On-line ODMA Support section (originally called status) added to the trial DMware site.  This responds to an urgent problem occurring in some ODMA configurations on Windows 2000.  

4.2 Establish and Measure Response Performance

2000-06-19: Formal response requirements are introduced in the statement of approach.

2000-03-07: Informal response practices are instituted.  The Technical Coordinator makes sure that no enquiry on ODMA Tech goes unanswered.  Tracking is informal.

5. Establish Metadata Clearinghouse

Establish metadata clearinghouse with initial content based on DMA 1.0, ODMA 2.0, and existing trial-use proposals; define clearinghouse and promote its technical use by users and vendors through the Web-DM Interoperability Forum and other venues.

5.1 Identify ODMA Metadata for Clearinghouse

There are 5 kinds of metadata introduced with ODMA:

  1. Identification of DMS providers
  2. Identifications of applications and their document formats
  3. Identification of standard document attributes for coordination between applications and DMS providers
  4. Identification of vendor-specific attributes and elements that are maintained by agreement, outside of the ODMA specification
  5. Additional elements that are employed in the coordinated operation of ODMA-compliant software and that are maintained as standard elements: COM Interfaces, result codes in operations, and any specialized data elements that are part of ODMA integration.

Standard metadata management techniques are extended over those elements for which public accountability and visibility is important.

2000-06-19: There are presently no registries or other metadata directories separately maintained for ODMA.

6. Evangelize DMware

Evangelize DMware in the open-source community: contribute links, white papers and supporting information for the DMware clearinghouse at AIIM to increase visibility and utility to the AIIM information-management community.

2000-04-10: The AIIM 2000 Standards at Work area is supported with local and on-line versions of the DMware test site.  Most questions at the booth are about ODMA and where it is going, how it fits in a world with WebDAV, etc.  Questions are captured and used to create a FAQ that is used on-line at the conference.

2000-04-07: DMware linkage is added to the AIIM Standards Web page.  The linkage is to the test DMware site on InfoNuovo.com.


created 2000-06-19-08:51 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 10-08-29 20:15 $
$$Revision: 15 $