RE: [legalxml-courtfiling] ECF 4.0 reference implementation licensing

["Harris, Jim" <jharris@ncsc.org>]

There's a ECF TC call scheduled for next Tuesday at 1pm eastern.  We should use that call to regroup on tasks/next steps for the reference implementation.

-----Original Message-----
From: Cabral, James E. [mailto:JCabral@mtgmc.com] 
Sent: Thursday, November 05, 2009 9:35 AM
To: legalxml-courtfiling@lists.oasis-open.org; Price, Jim; Embley, Paul
Subject: RE: [legalxml-courtfiling] ECF 4.0 reference implementation licensing

Please use this version of the worksheet.  I reordered both the licenses and characteristics from the least restrictive (public domain) to the most restrictive (GPL v3).

BTW, I have not seen any communications about the reference implementation.  What are the next steps?

  Thanks,

Jim Cabral
MTG Management Consultants, L.L.C. 
www.mtgmc.com
(206) 442-5010 Phone
(502) 640-4970 Mobile 

Helping our clients make a difference in the lives of the people they serve.

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.  If you received this in error, please contact the sender and delete the material from any computer.


-----Original Message-----
From: Cabral, James E. [mailto:JCabral@mtgmc.com]
Sent: Wednesday, November 04, 2009 5:53 PM
To: legalxml-courtfiling@lists.oasis-open.org; Price, Jim; Embley, Paul
Subject: [legalxml-courtfiling] ECF 4.0 reference implementation licensing

ECF TC and friends:

As promised at CTC, I've attached a worksheet with my analysis of various licensing options for the ECF 4.0 reference implementation.  The first tab lists common open source licenses and the second tab defines various characteristics of those licenses.

I make the assumptions that the license for the ECF 4.0 reference implementation should have the following characteristics:

1. Approval by OSI as compatible with "open source"
2. Compatibility with other software licensed under the GNU Public License 3. Available for use as linked code/libraries in proprietary software 4. Preservation of any copyrights and disclaimers

Based on these assumptions, my (non-legal) opinion is I that the best options would be either the Apache Public License (APL) 2.0 or the GNU Lesser General Public License (LGPL) v3.  The decision between these licenses will come down to whether we want to include a "copyleft" that would prevent proprietary "derivative works".  If we want to prevent proprietary derivative works, then the LGPL would be the best choice.  If we want to allow proprietary derivative works, then the APL would be most appropriate.  The decision of whether something is a derivative work can be complex.  See http://en.wikipedia.org/wiki/Derivative_work for a definition.

Jim Cabral
MTG Management Consultants, L.L.C. 
www.mtgmc.com
(206) 442-5010 Phone
(502) 640-4970 Mobile 

Helping our clients make a difference in the lives of the people they serve.

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.  If you received this in error, please contact the sender and delete the material from any computer.

-----Original Message-----
From: Cabral, James E. 
Sent: Monday, September 21, 2009 1:18 PM
To: 'legalxml-courtfiling@lists.oasis-open.org'
Subject: OXCI Post-Implementation Review

ECF:

As we consider creating a reference implementation of ECF 4.0, there are some lessons learned from the OXCI implementation.  Many of these lessons were baked into ECF 3.0 but there are still some relevant findings related to open source licensing and the importance of software quality assurance.

James E. Cabral Jr., Senior Manager
MTG Management Consultants, L.L.C. 
1111 Third Avenue, Suite 3010
Seattle, Washington 98101-3292
www.mtgmc.com
(206) 442-5010 Phone
(502) 640-4970 Mobile
(206) 442-5011 Fax
jcabral@mtgmc.com

Helping our clients make a difference in the lives of the people they serve.

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material.  If you received this in error, please contact the sender and delete the material from any computer.