From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <Norm.Jacobs@Sun.COM>
Message-ID: <45CD24BF.4080606@Sun.COM>
Date: Fri, 09 Feb 2007 19:49:51 -0600
From: Norm Jacobs <Norm.Jacobs@Sun.COM>
MIME-Version: 1.0
References: <789E617C880666438EDEE30C2A3E8D100105A5E3@mailsrvnt05.enet.sharplabs.com>
In-Reply-To: <789E617C880666438EDEE30C2A3E8D100105A5E3@mailsrvnt05.enet.sharplabs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Printing-architecture] Activity Plan for OP Architecture WG
List-Id: Printing architecture under linux
	<printing-architecture.lists.freestandards.org>
List-Unsubscribe: <http://lists.freestandards.org/mailman/listinfo/printing-architecture>,
	<mailto:printing-architecture-request@lists.freestandards.org?subject=unsubscribe>
List-Archive: <http://lists.freestandards.org/pipermail/printing-architecture>
List-Post: <mailto:printing-architecture@lists.freestandards.org>
List-Help: <mailto:printing-architecture-request@lists.freestandards.org?subject=help>
List-Subscribe: <http://lists.freestandards.org/mailman/listinfo/printing-architecture>,
	<mailto:printing-architecture-request@lists.freestandards.org?subject=subscribe>
To: "McDonald, Ira" <imcdonald@sharplabs.com>
Cc: printing-architecture@lists.freestandards.org


I could see that curtailing involvement from a set of producers and 
consumers of the the interfaces.  If the specs don't contain any viral 
or restrictive licensing, a compliant header file generated from a 
reading of the specs can use whatever licensing the header file author 
desires.

       -Norm

McDonald, Ira wrote:
> About licenses - the context was an expressed concern
> that Linux Foundation policy might (for example) require
> that OP API headers carry a GPL licenses - which would be
> a disaster for participation by many companies.
>