From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <glen.petrie@eitc.epson.com>
Message-ID: <2F7D63A21DB2C74EB8EB8C09AF667DB00559C9C3@eitc220.eitc.epson.com>
From: "Petrie, Glen" <glen.petrie@eitc.epson.com>
Date: Thu, 8 Feb 2007 15:47:34 -0800 
MIME-Version: 1.0
Content-Type: text/plain
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: printing-architecture@lists.freestandards.org

[snip...]

> (2) Establishing naming and documentation conventions for
>     new OP printing APIs
>     - possibly a small new OP specification
>   
It might be nice to have a guideline document that describes conventions 
to be used in OP specs.

[gwp] I would like to second this.  The document should include the memory
functions and other generalized items we uncover as time goes on.

glen