DMware is the working name for the open-source distribution and development of document-management software carried out with the institutional sponsorship of AIIM International.
The subject matter of the DMware clearinghouse is public, openly-contributed document-management software, documentation, and metadata definitions.
The DMware clearinghouse accepts all open-source contributions that further the coherent, interoperable usage of standards-based document-management technology.
This is a draft 0.04 of an in-progress work. For access to the latest version, visit the DMware Development Site Model Section.
web page last updated 2002-09-03-22:02 -0700 (pdt)
, 1999 Technical Committee Chairman, AIIM Document Management Alliance
This is draft 0.04 of 2000-09-02.
1. Introduction
2. DMware Clearinghouse
3. Open-Source Licensing
4. Contribution Procedures
5. Open-Source DMware Availability and Accountability
6. Open-Source Project Management
7. Specifications, Definitions, and Metadata Clearinghouse
8. Existing Specifications and Software
9. Implementation and Transition
10. References and Resources
Contributors
Change History
DMware is the name for clearinghouse and open-source development activities to be carried out with the institutional sponsorship of AIIM International. The DMware clearinghouse provides an archive of the document-management technical specifications and sample software developed under auspices of AIIM International. This includes the work of the AIIM Document Management Alliance (DMA) and the AIIM Open Document Management API (ODMA). The DMware clearinghouse provides an open, public forum for access to, discussion of, application of, and contribution to this body of work Open-source projects in other areas of standards-based document-management interoperability are also welcome as part of DMware.
This approach is being undertaken for the following purposes:
- Make the efforts of the AIIM DMA and ODMA coalitions and other contributors to document-management interoperability as widely-accessible and usable as possible
- Foster the open contribution of participants in businesses, institutions, and government in the review and improvement of this technical work
- Promote achievement of interoperability in document management applications through the application of common software architectures, integration frameworks, interchange techniques, and protocol agreements
- Cultivate the creation of community-owned software components that are primarily valuable only when commonly used and openly shared among a diverse community of interests and application
- Establish a high level of quality and accountability for critical interoperable elements through their full disclosure, peer inspection, carefully-managed maintenance, extensive usage, and widespread community adoption
- Encourage the contribution of scientists, scholars, and artisans to the ongoing exploration, development, and refinement of interoperability techniques in document management, providing an avenue for placing new ideas and innovations into practice
The heart of the DMware clearinghouse is a World-Wide Web site, operated as part of the AIIM Web site (at http://www.aiim.org), that provides access to all information and participants of the DMware community.
- Archives of information that is available for reference and for use
- Status information on completed work and any comments, experiences, and defects that have been reported
- Distribution lists for discussions among DMware users, contributors, and developers
The DMware clearinghouse provides three levels of material:
- Specifications, standards, and documentation that offer models, frameworks, interfaces, and procedures of value in the achievement of document-management interoperability
- Computer software that supports document-management system interoperability along with technical materials and documentation related to the application of that software
- User experiences and common definitions for user-meaningful information (e.g., metadata) that enhances the interoperability of systems as well as the interchange and reusability of managed materials
Although initial material for the DMware clearinghouse is related to technical integration methodologies and software interfaces for interoperable access to document collections, coverage will expand to areas of usage and practice as establishment of technical interoperability proceeds.
To ensure that DMware software and related works are freely available for continuing community development, improvement, and refinement, open-source licensing practices are adopted.
Rather than require a unique open-source license, the license-definition efforts of the open-source community are utilized. The Open Source Initiative [OSI] provides definitions [OSD] and a certification mark [OSImark] that will be relied upon for DMAware.
Copyright to all copyrighted subject matter contributed to DMware will generally be held by AIIM International. Where copyright is retained by the contributing party, the contribution must be Open-Source Certified such that AIIM International and recipients of the contributed material may freely copy, distribute, and modify the work in accord with the license that is employed.
Submitters of new contributions must provide a transfer agreement affirming the contributor's authority and right to make the contribution under the covering copyright and license (section 4.1)
All license statements employed for DMware will conform to the Open-Source Definition [OSD] and be approved by the Open Source Initiative [OSI]. Contributors may use any OSI-approved license. There are nine qualities that version OSD 1.7 stipulates as characteristics of open-source licenses. Here is the recommended application to DMware practice:
- Free Redistribution
DMware: Place no restriction on the redistribution of the work in complete form, separately or as part of a compilation, so long as the work is not modified and the work is provided under cover of exactly the same license(s) as its original distribution. Permit, but do not require, redistribution of copies at no charge. Make the same redistribution rights available to all recipients of distributions, without any requirement that recipients enter into any additional license. (See 7, below.)
- Source Code
DMware: Accompany distributions in a form that omit source code with a clear notification and description of a means for obtaining the source code without difficulty and at nominal cost, if any. Source code deposited in the DMware clearinghouse may be used for this purpose (see 3, below).
DMware: The easiest way to ensure availability of the source code is to include it. Permit redistribution in source code form with or without distribution in compiled or object-code form.
- Derived Works
"The license must allow modifications and derived works, and must allow them to be distributed under the same terms as the license of the original software."
DMware: Source code of DMware-based open-source works can be deposited in the DMware clearinghouse. Deposited source code may be used to satisfy availability of omitted source code in satisfaction of item (2), above.
DMware - Provenance Accountability Condition: When a derivative work is produced and distributed, the recipient of the derivative work is notified of the open-source work on which the derivative is based and offered unrestricted access to that complete open-source work (e.g., in the DMware clearinghouse).
DMware - Substitution Interoperability Condition: For derived works that are intended to be substitutable for use of the original work in operation on the same computer systems, provide any additional installation and configuration requirements so that conditions of substitutability and interoperability are perpetuated. (See section 8.2.)
DMware - Simplicity Condition: Avoid confusion, ambiguity, and uncertainty around potential infringement of copyright by granting complete license for creation of derivative works without requiring (but allowing) distribution "under the same terms as the license of the original software." (See section 3.3.1.)
- Integrity of the Author's Source Code
"The license may restrict source-code from being distributed in modified form only if the license allows the distribution of 'patch files' with the source code for the purpose of modifying the program at build time. The license must explicitly permit distribution of software built from modified source code. The license may require derived works to carry a different name or version number from the original software."
DMware - Source Integrity and Separability Condition: Derived works are distinctly identified, avoiding confusion with the original work or subsequent versions of the original work. If the source-code of the derived work is distributed, the original source-code is clearly identified and kept intact in a separable form together with its covering licenses.
- No Discrimination Against Persons or Groups
"The license must not discriminate against any person or group of persons."
DMware: Omit any identification of persons and groups of persons in any fashion.
- No Discrimination Against Fields of Endeavor
"The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research."
DMware: Make no statements limiting use.
- Distribution of License
"The rights attached to the program must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties."
DMware: (See 1, above.)
- License Must Not Be Specific to a Product
"The rights attached to the program must not depend on the program's being part of a particular software distribution. If the program is extracted from that distribution and used or distributed within the terms of the program's license, all parties to whom the program is redistributed should have the same rights as those that are granted in conjunction with the original software distribution."
DMware: Maintain separability when works and derivatives are combined and/or incorporated in larger works. The original work can be extracted and distributed with its covering license. (See 4, above.)
- License Must Not Contaminate Other Software
"The license must not place restrictions on other software that is distributed along with the licensed software. For example, the license must not insist that all other programs distributed on the same medium must be open-source software."
Up to three specific OSI-approved license statements will be recommended (after development, if needed) for application to DMware. This is to provide for differentiation among
- simple licenses which do not limit derivative works,
- general open-source licensing that requires derivatives to be covered under the same license, and
- open-source libraries/components that may be used freely in construction of and/or co-operated with other software provided that derivatives of the library/component itself are covered under the same license.
Existing OSI-approved licenses will be usable. It is intended that contributors may make use of any OSI-approved licenses, whether or not DMware-specific licenses are also established. DMware licenses will not be introduced where there is an available OSI-approved license that serves the requirements.
Important Note: The key differentiation among the following cases involves what is viewed as a derivative of the original work when derivatives are required to be available as open-source contributions under the same license conditions as the original.
3.3.1 Simple Open-Source Licensing
Simple open-source licenses can be applied to any variety of software. The basic characteristic is that derivative works of any kind are permitted and no further license is required. Permitted derivative works are not required to be distributed as open-source software under the same conditions and license as the original work. Possible models for a simple open-source license are the BSD License [*BSD], the MIT License [MITlicense], and other licenses such as the one provided by Henry Spencer on some widely-used library software [SpencerRegex]
The key advantage of simple open-source licensing is that an user of the work is not at risk of copyright infringement or license breach as a consequence of making a derivative of the work, provided that other, easily-honored conditions of the license are satisfied. This removes technical uncertainties around being able to determine when a work constitutes a derivative of the licensed work.
For the author of the licensed work, there is no loss of copyright, since no derivative work can pre-empt the copyright of the original, nor of portions of the original retained in the derivative. For users of the licensed work, the creation of derivative works by themselves or others can in no way impede the continued use of the licensed work.
The key difference over stricter open-source licenses is that derivative works are not assured to be made available to the contributing community on the same conditions that the licensed work is. Contributors will determine for themselves whether they are willing to contribute open-source software under those conditions.
Simple open-source licensing is preferred for DMware as a means of encouraging use and reuse of the contributed software and simplifying compliance with the open-source license. Creators of derivative works are encouraged to recognize their self-interest in contributing repairs and improvements of the original work back to the community for establishing a new level of common usage and confirmed quality.
3.3.2 General Open-Source Licensing
There are a variety of OSI-approved general open-source licenses, the most well-known one being the GNU GPL. It is probably unnecessary to craft an additional license for this purpose.
A general open-source license, comparable in strength to the GNU General Public License [GPL] requires that any derivative works under copyright law be distributed as open-source software under the same conditions and license as the original work.
General open-source licensing is most clear cut when applied to
- fully-implemented client programs,
- reference implementations of document spaces and other services,
- standalone tools for installation, operation, administration, testing, and verification of document systems
and when the contributor is unwilling to allow derivatives under a simple open-source license. For other kinds of works, especially libraries and components that are useful in the creation or operation of other works, it is recommended that library / component licensing be considered first.
3.3.3 Open-Source Library/Component Licensing
The purpose of a library/component-level license is to encourage the separable distribution of library and component software. There is unrestricted use of the library/component in building larger programs and components (dependent works) that incorporate or operate with the unaltered library/component software. The open-source library/component license releases the dependent work from restrictions placed on derivative works. Derivatives that involve alteration of the material of the licensed work, including additions and deletions, must be redistributed under the same open-source license.
This form of license encourages interoperability, reduces redundancy of useful library implementations, and expands the community of application for the library, contributing to its achievement of high reliability and utility. It also provides an avenue for developers of close-source software to contribute useful libraries/components to the open-source community and retain full rights to application of the library/component (and open-source improvements of it) in their closed-source applications.
Components are relatively-new kinds of software artifact, having qualities of complete software elements and also of libraries. They are not independently operable but are employed in conjunction with other software system elements and libraries. Open-source components are similar to open-source libraries except that combination with other elements occurs only in the course of processing operations and is entirely ephemeral. The combination need never occur as a complete work fixed in a tangible medium in any way.
Examples of components in DMware include plug-in DMA service elements for converting URLs in different character-set encodings, for comparing texts in different collation sequences, for providing error message translations in different user languages, and for creating cross-repository searches (merging scopes). Other DMware components are reference or test implementations of DMA system objects and ODMA DMS drivers. In the reference implementation of DMA 1.0, the DMA System Manager is accessed and operated as a shared component by any DMA application that requires access to DMA services (delivered in turn by further components). In the ODMA integration model, the ODMA Connection Manager is accessed and operated as a shared component by any ODMA-aware client.
Open-source implementations of Java classes, of ActiveX components, DMA service elements, and similar packaged components benefit from this form of licensing. The objective is to permit, at the option of the contributor, free commingling of closed-source and open-source components in operations of open-source and closed-source systems while requiring direct derivatives to be redistributed under the same license.
A library / component open-source license, comparable in strength to the GNU Lesser General Public License [LGPL] is recommended for open-source distribution of libraries/components, such that
- Employment of the library/component in construction of other software (the dependent work) are permitted without requiring the resulting combination to be distributed under the same license as the library.
- Modifications of the open-source library/component might still be required to be distributed under the same license as the library.
- Independently-developed substitutions that provide the same interfaces and functions as the open-source library/component are permitted (see 3.2(3))
- There may be conditions on the identification of dependencies on the library/component, and on notification of the availability of the library/component, in material that accompanies the dependent work.
- The library/component is completely separable and distributable separately even when redistributed with other software and installed in conjunction with the installation of other software.
- Dependent works must be reintegratable with newer versions of the component by any recipient of an allowed dependent work.
The open-source nature of contributions will be clearly specified and be authoritative.
4.1.1 New contributions must be clearly packaged with appropriate open-source license statements.
4.1.2 New contributions must be accompanied by a formal release statement that attests to the authority of the contributor to make the contribution, that transfers copyright to AIIM International if appropriate, and that asserts the absence of any encumbrance to the license. The material will be distributed as open-source certified software.
4.1.3 The DMware clearinghouse will maintain records of the history of new contributions and modifications to contributions so that the origin of all material is readily auditable and confirmable.
So that users of DMware material are always clear on the usability of software obtained from the DMware clearinghouse, only open-source and public-domain software will be provided on the clearinghouse site.
4.2.1 Contributions of software that are not made under an OSI-approved open-source license appropriate to the software will be rejected. The clearinghouse materials will not be commingled with non-open-source software. People who access software provided through the DMware clearinghouse will have the reasonable expectation that all materials will be either OSI-certified or public-domain material. Public-domain materials will be clearly identified.
4.2.2 The DMware clearinghouse will allow announcements and posting of information for locating other materials, proprietary and otherwise, that may be of interest and value to the DMware user community. However, only open-source and public-domain materials, as already described, will be directly available via the DMware clearinghouse.
It is important that a recipient of the contribution have sufficient information to be able to reproduce the construction of operational forms of the software elements. There will be packaging requirements for ensuring that contributions provide that information, including the following:
4.3.1 Contributions must provide sufficient dependency and construction information such that any compiled or derived software elements can be reconstructed and the reconstruction confirmed (i.e, the elements when recompiled and rebuilt or rederived are reproduced exactly in every material respect).
4.3.2 Any dependency of the open-source software portions on non-redistributable materials that must be obtained elsewhere are clearly identified along with information on where to obtain the necessary materials. Such materials include non-redistributable debugging versions of run-time libraries, non-redistributable include files that are packaged with proprietary compilers and proprietary library systems, and run-time libraries and subsystems that are restricted from redistribution.
4.3.3 All dependency of the contributed software on tools, generic or specific, that are not included as part of the contribution must be clearly identified and the actual versions of tools used in construction and confirmation of the element must be identified so that all tool operations can be reproduced. (This includes parameters and option settings that must be provided for proper tool operation.)
4.3.4 Any dependency of the open-source software on redistributable materials and tools that are included under separate license conditions must be clearly identified, the redistributed material must be clearly identified, the applicable license statement must identify the material to which it applies and the license must be included. The separate license for redistributable materials must permit continued redistribution as part of redistribution of the open-source material and of any derivative open-source works of that material. (An example of this case is the library file dmacom.h that is subject to redistribution as part of DMA 1.0 DMware under terms and conditions established by Microsoft Corporation.)
The status of all available and under-development DMware will be fully reported on the DMware clearinghouse site. Reports of difficulties, suspected defects, and proposed remedies will be openly available. The DMware site will maintain an account of the history, provenance, and known status of all DMware open-source releases. Users of DMware or of products that depend upon open-source DMware are able to confirm the condition and history of the specific versions involved.
Availability of open-source releases of DMware software will be announced on appropriate archive news groups and other avenues. The DMware clearinghouse site will provide a catalog of the current status of all open-source releases, including providing means for downloading the material from the DMware clearinghouse site. Other sites can redistribute and make available open-source DMware materials as provided for in the applicable open-source licenses.
Users who wish to download open-source DMware materials may be required to register prior to being given download privileges. The registration process is used to ensure that the requester is informed of the license conditions that apply to the material and knowingly consents to those conditions. Registration also provides a contact mechanism if there is need to follow-up or communicate with the requester at a later time. It is the policy of the DMware site that the identity of requesters who have accessed DMware materials not be disclosed and not be used for any other purpose.
Distribution lists will be available for discussion of DMware, provision of trouble-shooting information and problem reports, and other discussions related to the use and any difficulties with the open-source DMware software.
Defect reports, proposed patches, and change suggestions will be announced and posted on the DMware clearinghouse site.
Users of software systems that include open-source DMware programs, libraries, or components will be able to confirm, from information that accompanies those software elements, the history and current status of the specific DMware software versions that are employed. License materials supplied to those users will include instructions on how to identify the versions and confirm their status.
There will be reliable procedures for the consistent maintenance of those open-source contributions for which the DMware clearinghouse serves as the primary development, distribution, and archive point. These procedures and guidelines will establish how open-source DMware projects are constituted and the leadership roles and accountabilities that govern management of contributions and development of revisions.
In general, there is no particular procedure for developing a contribution and submitting it along the lines proposed in Section 4, Contribution Procedures. The need for open-source project management arises when maintenance and further development of an existing contribution is carried out by an informal open-source team. In many ways, the project management requirement is similar to the rules that a club might have to reach agreement on direction and tasks. There becomes a need to establish how disagreements are to be resolved and who is allowed to participate in those decisions.
It is expected that there will be very few specific procedures initially, and that more-detailed project management agreements will be introduced as the first projects are carried forward.
Contributions of open-source DMware software will be maintained and updated using agreed software project and configuration management practices. The project management approach of the Apache Project [Apache][JakartaProj] will serve as the model for DMAware project management. As DMware open-source development projects are undertaken, there will be identification of
- roles and responsibilities - defining the recognized roles in the project
- participating users
- contributing developers
- development team
- managing body
- communication structure - defining how users and developers communicate with regard to the project
- user lists
- contributor lists
- development team lists
- announcement lists
- decision making - defining how action items are proposed and agreement reached
- classification of action items
- consensus process
- non-consensus resolution process
- standing of participants in decision making
- configuration management - defining how the project's source code and other materials are organized and developed
- definitive repository location and structure
- requirements for license on submissions
- access rights to repository
- maintaining and reporting accurate status of configuration elements in the repository
- distinguishing categories of development: branches, changes, and patches
- formats for submissions to and distributions from the repository
- project management - defining the roles and responsibility of any management oversight for the project
- eligibility to participate in management process
- relationship of project management and the institutional sponsor (AIIM International)
The AIIM DMware clearinghouse will be employed as an archive and connection point. On-going open-source development projects for DMware can be carried out using separate Web facilities that are freely available for this purpose (e.g., [SourceForge]), with the major results archived/mirrored on the DMware clearinghouse site.
The AIIM DMware clearinghouse will be the primary site for archival retention of specifications, definitions, and shared metadata definitions.
Documentation and specifications will be available via the DMware clearinghouse, both for download and on-line viewing. Redistribution and creation of derivative works of these materials will be governed by notices provided in the documentation itself.
An important contribution of the DMware clearinghouse is providing a place for users of DMware to publish and exchange application-valuable information. There will be an electronic clearinghouse for users to publish class and property definitions and property identifications that are valuable for use between organizations and individuals in achieving interoperability and interchange of managed-document information. This includes ODMA DMS identifications as well as format identifications and their definitions.
The DMware clearinghouse will provide a registry in which users can publish useful properties and class definitions and also publish descriptions of those items in any number of languages. Material publicized and described in the registry will be freely usable in other usages of DMware and in interoperable use of document-management systems.
The intention is to employ registry-information data formats that are easily interchanged and employed in conjunction with standards-based metadata repository systems.
The specifications and software produced by AIIM document-management coalitions (ODMA and DMA) will be available for distribution via the DMware clearinghouse.
8.1.1 Existing software and documents that have been contributed without restriction to the AIIM Document Management Alliance will be maintained under copyright of AIIM International. This software and its source code will be segregated in the DMware clearinghouse as DMA 1.0 material. This material has no additional license conditions on its downloading or usage (except for restrictions on any redistributed elements that might apply: see section 4.3.4). This material includes the DMA 1.0 samples and the source code employed in the creation of the DMA System Manager for Win32, file dma10.dll.
8.1.2 Electronic versions of the DMA 1.0 specifications, the accompanying code samples and supporting documentation -- primarily the final proposals that were adopted as part of formulating DMA 1.0 -- will be segregated as part of the DMA 1.0 material of the DMware clearinghouse. This material will be maintained under copyright of AIIM International. There is no limitation on the downloading and redistribution of this material in unchanged form. All other rights, including the creation of derivative works, are strictly reserved in accordance with the Document Management Alliance participation agreement under which the DMA 1.0 specification was produced and made available.
8.1.3 All DMA enhancement proposals that have been put forward for trial-use in the DMA Technical Committee will be made available as supplemental material of the DMA 1.0 DMware collection. Usage of this material is limited in exactly the same manner as the DMA 1.0 specification itself.
8.1.4 Certain supplemental data files constitute a database by which portions of the DMA 1.0 specification and interface libraries are produced. The data files applicable to creation of the DMA 1.0 specification will be preserved in conjunction with the electronic versions of the specification. This data is usable to recreate the DMA 1.0 specification or an authorized derivative work based on that specification.
8.1.5 Apart from other work informally preserved under the DMware clearinghouse, such as presentations and training materials, no other materials from the development of the DMA 1.0 specifications and related materials will be preserved as part of DMware.
8.2.1 The interface library that is maintained as part of DMA 1.0 support will be kept as part of the electronic DMA 1.0 specification (8.1.2). A derivative of this library will be updated and packaged as an open-source software library under a simple open-source license (section 3.3.1). This library consists entirely of definitions of interfaces and supporting data-element values. The appropriate license statements will be included in the updated package, satisfying the requirements of an open-source DMware contribution (section 4).
8.2.2 The DMA System Manager will also be repackaged and recreated as an open-source DMware contribution. The appropriate license statements will be included in the updated package. All further work on the System Manager, including maintenance of this code base, will be carried out as an open-source development project. There are to be special license provisions to ensure coordinated maintenance of a single implementation for each hardware-software platform on which the System Manager is made available. The objective is to provide installation practices and a consistent progressions of versions so that there can always be a single implementation operating on a given computer, shared by all applications and all installed DMA components. System Managers will be upgradeable in a way that preserves the operation of already-installed components that depend on it or integrate under it.
8.2.3 Introduction of derivatives any other DMA 1.0 materials as open-source DMware contributions will depend upon voluntary contributions by individuals and organizations having the authority to contribute, as specified in section 4. Samples already available for further development as open-source DMware include the sample System Object included as part of the Amigo System Manager contirbution, the ODMA-DMA Translator contributed by Eastman Software, and the Eastman Software ActiveX component used to provide access to DMA-managed documents from workflow applications.
The DMware clearinghouse will be populated in accordance with the following provisional task definitions.
The DMA 1.0 specifications and existing reference software, along with other contributions made during the operation of the Document Management Alliance are reusable by members of the Alliance in accordance with the participation agreement that all DMA members have accepted. This reuse corresponds to the rights granted under a simple open-source license. To provide a clear division between pre-open-source and post-open-source activities, the DMA 1.0 specifications, interface definitions, and contributed software are kept segregated within the clearinghouse. These materials are available as part of the foundation for DMware.
- Inventory DMA materials on ftp.aiim.org site.
- Identify all DMA 1.0 and trial-use material to be preserved.
- Organize materials on a working web site for review and verification. Include historical copies of the participation agreement and identification of the DMA members that have use of the DMA 1.0 DMware under the terms of that agreement.
- Bring up provisional DMware web on http://www.aiim.org
- Make DMA 1.0 specifications and background proposal information available via DMware web as the official base definitions.
- Archive all interface definitions (header files), interface and documentation maintenance tools, and contributed software for reference under the DMA participation agreement.
- Make all DMA extension proposals available via the DMware web site for information and voluntary trial use application.
The DMA 1.0 specification, proposed extensions, and reference software are fixed and represent the DMware base level. Any derivatives made as part of the open-source activity are separated as supplements or replacements, archived in a distinct way and identified to avoid any confusion between further open-source development and the DMA 1.0 base.
- Collect DMA 1.0 interface definitions for use as baseline open-source library / component interfaces using the latest published DMA header files and interface databases.
- Add all DMA 1.0 trial-use definitions for companion use as open-source library / component interface definitions
- Provide a clearinghouse for additional library and component interfaces defined by open-source contributors of further libraries and components.
- Archive the DMA 1.0 System Manager (Amigo B0.03) reference implementation for reuse as the common Win32 implementation and as the base for porting and further development.
- Collect all known problem reports and fixes made to the System Manager by users.
- Organize for further continuation as an open-source development.
As contributions become available, extend the clearinghouse to provide for archiving and dissemination of
- further DMware interface definitions, protocol proposals, API extensions and alternatives: developed, contributed, and discussed on DMware distribution lists and submitted in an agreed proposal format (e.g., using IETF-draft format as a model)
- open-source client, service-element, and middleware software
- related open-source libraries and components
- related-open source utilities, tools, and databases for support of document-management systems and their interoperability
- registration of definitions and description translations of useful document classes, properties, interfaces and other metadata that contributes to interoperability by being reused in document-system applications of others
- appropriate tracking, change-control, and problem reporting/resolution support for maintenance and continuing development of the open-source software and the metadata clearinghouse
Upon dissolution of the Document Management Alliance, materials not captured and supported under the DMware clearinghouse are no long assured to be available.
- [Apache]
- About the Apache HTTP Server Project. published on the web at http://www.apache.org/ABOUT_APACHE.html. Apache Software Foundation (Forest Hill, MD: February, 1999).
- [Bazaar]
- Raymond, Eric S. The Cathedral and the Bazaar. O'Reilley (Sebastopol, CA :1999). 288pp. ISBN 1-56592-724-9.
- [*BSD]
- The BSD License. Template. An OSI approved license published on the web at http://www.opensource.org/licenses/bsd-license.html. University of California (Berkeley: 1998).
- [DMA]
- Document Management Alliance. AIIM International. Coalition created in 1995 to produce a single document-management interoperability interface specification based on the work of the Document Enabled Networking initiative and the Shamrock Coalition.
- [DocBook]
- Walsh, Norman., Muellner, Leonard. DocBook: The Definitive Guide. O'Reilly (Sebastopol, CA: 1999). ISBN 1-56592-580-7. xiii + 613pp + index + CD-ROM.
- [FogelCVS]
- Fogel, Karl. Open Source Development with CVS. A Guide to Using CVS in the Free Software World. Coriolis (Scottsdale, AZ: 1999). 300pp + appendices + index. ISBN 1-57610-490-7 pbk.
- [GNU Software]
- Software. 1999 November 6 update published on the web at http://www.gnu.ai.mit.edu/software/software.html. Free Software Foundation (Boston, MA: 1996, 1997, 1998, 1999). This useful catalog of GNU and related software, some under GPL, some available under other terms, provides an useful sketch of the reach of the GNU effort. It shows the kinds of information that a clearinghouse can provide around a focused open-source effort.
- [GPL]
- The GNU General Public License. version 2, June 1991. An OSI approved license published on the web at http://www.opensource.org/licenses/gpl-license.html. Free Software Foundation (Boston, MA: 1989, 1991).
- [JakartaProj]
- The Jakarta Project Guidelines. Published on the web at http://jakarta.apache.org/guidelines/.
- [LGPL]
- The GNU Lesser General Public License. version 2.1, January 1999. An OSI approved license published on the web at www.opensource.org/licenses/lgpl-license.html. Free Software Foundation (Boston, MA: 1991, 1999).
- [LinuxDoc]
- , Ferguson, Greg., . The Linux Documentation Project (LDP) Manifesto. published on the web at http://www.linuxdoc.org/manifesto.html.
- [OSWGpolicy]
- . Open Source Writers Group: Document Licensing Policy. published on the web at http://ww.oswg.org/oswg-nightly/en_US.ISO_8859-1/articles/OSWG-Licensing-Policy/.
- [MITlicense]
- MIT License. Template. AN OSI approved license published on the web at http://www.opensource.org/licenses/mit-license.html. Open Source Initiative (California: 1999).
- [OSD]
- The Open Source Definition. Version 1.7 published on the web at http://www.opensource.org/osd.html. Open Source Initiative. A key definition of the qualities of an open-source license and the terms and conditions that apply to software that is approved as open-source certified.
- [OSI]
- Open Source Initiative. web site at http://www.opensource.org. Open Source Initiative (California: 1999).
- [OSImark]
- The OSI Certification Mark and Program. published on the web at http://www.opensource.org/certification-mark.html. Open Source Initiative (California: 1999). OSI has developed a two-step certification process. A license is reviewed for conforming to the Open Source Definition and then approved. Distributions of software under that approved license may be identified as OSI Certified Open Source, using the OSI Certification Mark. A number of open-source licenses are already OSI approved, including the GPL and LGPL.
- [OSWGpolicy]
- . Open Source Writers Group: Document Licensing Policy. published on the web at http://ww.oswg.org/oswg-nightly/en_US.ISO_8859-1/articles/OSWG-Licensing-Policy/.
- [ProCon]
- Harvey, Joan (ed.). Open Source: An Introduction to the new programming paradigm. TechRepublic White Paper. TechRepublic (Louisville, KY: October, 1999). published on the web at http://www.techrepublic.com/download_item.jhtml?id=dr00519991004jon99.htm. This is a comprehensive survey of the open-source movement, with analysis of the importance for information technology organizations. Pros and cons on the use of open-source development within an enterprise are presented.
- [SpencerRegex]
- . untitled. License Statement. provided with some library software that is commonly incorporated in open-source works. This version, dated 1996-07-23, was extracted from an open-source software package that redistributed the regex library as part of its implementation.
- [SourceForge]
- SourceForge. Web site. VA LiNUX Systems (Sunnyvale, CA: 1999-2000). A free service that provides a clearinghouse for open-source projects along with a logistics support for conducting open-source development projects over the Internet.
The following people contributed to the development of this document:
- , Director, Standards Program, AIIM International
- reviewer; contributed leads to additional references and sources
- , 1997-1998 DMA Technical Committee Chair, FileNET Corporation
- reviewer, proposed clear-cut simplification by having initial DMAware place no constraint on derivative works
- , 1999 DMA Technical Committee Chair, NuovoDoc
- editor; principal author
- , 1998-1999 DMA Advisory Council Chair, Xerox Corporation
- reviewer, clarifications for sections 8 and 9
- , 1999 DMA TC Asia-Japan Vice-Chair, Ricoh Company, Ltd.
- reviewer, discussion of derivative-work constraints in section 3.2
- , 1998-1999 DMA TC North American Vice-Chair, Xerox Corporation
- reviewer, clarification of difference between DMA 1.0 and open-source DMAware, clarifying whether the DMA 1.0 specifications can be changed or revised (sections 8 and 9), examples for components, keeping project management light-weight, clarification of introductory paragraph
- , DMA developer, FileNET Corporation
- reviewer, clarification of System Manager support requirements and tightening of nomenclature around "middleware." Suggestion of follow-on activities and other open-source components that can be continued.
- draft 0.04 2000-01-05 Major Revision to Reflect DMware orientation and Simple-License focus (orcmid)
- 1. Changed the [FreeBSD] reference to [*BSD], reflecting the variety of open-source versions of Unix under the BSD license.
2. Corrected the damaged internal linkage to the [SpencerRegexp] citation from section 3.3.1. (Richard Sauvain)
3. Corrected section 4.3.2 to apply to non-redistributable run-time libraries and subsystems.
4. Eliminated a dangling use of "reference middleware" in section 8.2.2, consistently using DMA System Manager instead. (Mike Seaman)
5. Extended section 8.2.3 to include three specific examples of other projects suggested by Michael Seaman.
6. In section 3.3.3, Added and discussed an overlooked proviso of [LGPL] to the effect that dependent programs must have some way of being recombined with updates to the library by users of the dependent work, whether or not the dependent work is distributed under the same license. We are going to finesse the library/component case at this time, focusing on the Simple DMware (SDM) for now.
7. Expanded the references to included [FogelCVS]. Found and included the link to the on-line version of the book.
8. Changed the name to DMware and reflected that change everywhere in the document.
9. Explicitly included ODMA as eligible DMware and adjusted examples to reflect ODMA support by the DMware clearinghouse and open-source projects.
10. Added reference to the Jakarta Project as a better example of Apache-style project management. Updated references about this in Section 6, Open-Source Project Management.
11. Added references to the Linux Documentation Project and the Open Source Writer's Group.
12. Added [SourceForge] as soon as I found out about it. Reflected that in the section on project management.
13. Closed off this version for posting to the site, with need for a draft 0.05 as soon as a better license draft is available.- draft 0.03 1999-11-29-16:25 pst (-0800) by dh
- 1. General editorial tweaking, including pointing out that there is other material on the DMware Development Site related to open-source software.
2. Incorporated Chuck Fay's suggestion that the header files and existing samples plus reference work be unrestricted with regard to derivative works in a way that leaves their usage clear for commercial developers, so these sources are freely usable by anyone to the same degree available to DMA members.
3. Numbered Change History items so that they are clearly separated.
4. In section 3.2, added recommended practices around use of OSI-approved DMAware licenses in satisfying the Open Source Definition..
5. Restructured section 3 to favor a simple license that does not hamper the creation of derivatives, so long as the origin and provenance of the original work is preserved. The two additional flavors are now a General License and a Library/Component License, and they are only important when stricter conditions apply to derivative works.
6. Added references to the FreeBSD, MIT, and Spencer licenses.
7. Added reference to AIIM site and resources.- draft 0.02 1999-11-23-14:42 pst (-0800) by dh
- "Change History" section added.
references "to Top of Document" corrected to be internal shortcuts and not web site references.
Section 3.2 (3) updated to include requirement for deposit of derivative works and section 3.2 (2) revised to allow access to source code to be satisfied by reference to the deposited copy.
Remembered to run the FrontPage 98 spelling checker.
"Contributors" section added.
Changed titles in the References sections to also be hyperlinks to the sources, even though these may not be presented correctly on conversion to versions of Microsoft Word older than Word 97. The references were revised to provide hyperlinks for all web-published materials and sources.
Removed dates from section 9 and replaced section with a simple road map. Clarified the separation between DMA 1.0 material and subsequent open-source materials.
Copyright retention by AIIM is relaxed for material which is contributed under existing copyright, so long as the material is OSI-certified.
Added more examples and cases for libraries and components in section 3.
Affirmed that project management is intended to be light-weight, applies beyond initial contribution, and is more like having bylaws for a club
Left open determination of whether or not derivative works must be redistributed under the same conditions (section 3.2 (3)).
Provided more motivation for the purpose of library and component licenses separate from a general software license.
Emphasized the special status of the DMA System Manager and the importance of having all applications and components installed on a computer be able to rely on a single, shared system-manager copy.
Completed sections 1 and 2.
Minor adjustments between the Word and HTML versions.- draft 0.01 1999-11-10-12:00 pst (-0800) by dh
- Initial Microsoft Word draft circulated for review and comment among DMA officers and key contributors
created 2000-01-05 by orcmid
$$Author: Orcmid $
$$Date: 02-09-03 22:07 $
$$Revision: 29 $
HomeEnd of Document