All of lore.kernel.org
 help / color / mirror / Atom feed
From: Norm Jacobs <Norm.Jacobs@Sun.COM>
To: printing-architecture <printing-architecture@freestandards.org>,
	"Printing-Sc (E-mail)" <printing-sc@freestandards.org>,
	printing-japan@freestandards.org
Subject: [Printing-architecture] OPVP specification and use of UPDF
Date: Wed, 04 Oct 2006 15:28:00 -0500	[thread overview]
Message-ID: <45241950.4070208@Sun.COM> (raw)


At today's architecture meeting, we discussed the proposed OPVP 
specification in it's current form.  We discussed the issue with the 
method of describing properties that was brought up at the last 
OpenPrinting SC meeting.  The issue is that the specification does not 
require a conforming implementation to support a specific scheme, but 
instead simply states that the implementation can support any scheme it 
likes.  The specification goes on to use UPDF as an example.

What we are looking for is a statement in the specification that selects 
a required scheme to facilitate standard
description of properties so that there is a known method of specifying 
properties.  Without this, it becomes less likely that renderers and 
drivers will be able to be used outside of the specific renderer or 
driver that they were designed to be used with.

We would appreciate it if someone would come to the OpenPrinting 
Steering Committee meeting next week prepared to respond to this.  Once 
this is addressed, we can move forward with the process.

       -Norm


             reply	other threads:[~2006-10-04 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-04 20:28 Norm Jacobs [this message]
2006-10-05  2:43 ` [Printing-architecture] [Printing-sc] OPVP specification and use of UPDF Takaaki Higuchi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45241950.4070208@Sun.COM \
    --to=norm.jacobs@sun.com \
    --cc=printing-architecture@freestandards.org \
    --cc=printing-japan@freestandards.org \
    --cc=printing-sc@freestandards.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.