From: William A Wagner (email@example.com)
Date: Mon Dec 17 2007 - 17:41:06 EST
I agree with Pete's distinction between configuration and settings. Although
I have heard "configuration" used to identify a set of settings, using
"settings" to identify a physical configuration seems quite inappropriate.
Coming from a hardware background, I regard "component" at a much lower
level than "subunit", although technically the word is correct at any
level... that is, anything may be considered a component of something.
"Subunit" retains a physical connotation while component can apply to
anything. Although it might be a bit muddy as to what a unit is, in this
context a unit would tend to refer to a physical entity performing a primary
function. A sub-unit would be one step down. So the term would imply some
physical component performing a relatively high level function. Component
would have no physical or functional connotation; it is just, in some way, a
part of something.
Clear physical terms are often use for "logical" entities, so things get
pretty foggy. Although the terms must be defined in the document, it would
better to follow general usage in of the intended audience. So I guess that
is the answer and the question.
From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of
Sent: Monday, December 17, 2007 12:38 PM
To: Ira McDonald
Cc: Ira McDonald; firstname.lastname@example.org; email@example.com; firstname.lastname@example.org; Zehler,
Subject: Re: MFD> Dec 11 PWG MFD face-to-face meeting minutes available
I, too, hate our use of the term "subunit" and support the change to
I also strongly agree with Pete that I don't want the proposed change.
Components are constituent elements. Configuration is the relative
disposition or arrangement of elements. Therefore, the Configuration is
made up of Components.
Capabilities depend on the available Components, or the Configuration.
Settings is a collection of Capabilities and their current state. (We'll
ignore Heisenberg's uncertainty principle)
Sent by: "Zehler, Peter"
email@example.com <Peter.Zehler@xerox.com>, "Ira
12/17/2007 11:42 firstname.lastname@example.org, email@example.com
Re: MFD> Dec 11 PWG MFD
face-to-face meeting minutes
I see you what you mean, but...
Be aware that DMTF CIM Core WG hates our term "subunits" and has made
us completely replace it with their term "components".
"Configuration is" just too inherently ambiguous. "Xxx" is just as
if the intent is to imply components.
On Dec 17, 2007 6:38 AM, Zehler, Peter <Peter.Zehler@xerox.com> wrote:
> I do not want to see that change. When I talk to our driver people
> "settings" is more closely aligned with the default ticket and
> capabilities. Settings can be changed by an administrator or End User
> (often remotely). A configuration can not be as easily changed and
> involves the addition or removal of hardware. There are other mappings
> <http://msdn2.microsoft.com/en-us/library/aa507422.aspx>) that are very
> closely aligned with the PWG Semantic model. Their Defaults & Allowed
> Values map to Settings. Their Configuration maps to Subunits (i.e.
> In the PWG Semantic Model the configuration element is the installed
> hardware for the system or the effective hardware configuration for the
> service (i.e. the service specific view for the subunits used).
> Peter Zehler
> Xerox Research Center Webster
> Email: Peter.Zehler@Xerox.com
> Voice: (585) 265-8755
> FAX: (585) 265-7441
> US Mail: Peter Zehler
> Xerox Corp.
> 800 Phillips Rd.
> M/S 128-25E
> Webster NY, 14580-9701
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com] On Behalf Of Ira
> Sent: Saturday, December 15, 2007 1:40 PM
> To: firstname.lastname@example.org; Ira McDonald
> Cc: email@example.com
> Subject: Re: MFD> Dec 11 PWG MFD face-to-face meeting minutes available
> Hi Nancy,
> Thanks for these excellent and detailed minutes.
> A comment on element group naming. What Pete (and minutes) referred
> to as a new group parallel to Capabilities and DefaultJobTicket is
> called Settings throughout the classes in the CIM model.
> We will have to add a PrintServiceSettings and PrintServiceCapabilities
> classes in our 2008 WIMS-CIM modelling work.
> I suggest changing Configuration to Settings.
> - Ira
> On Dec 15, 2007 2:54 AM, <firstname.lastname@example.org> wrote:
> > Dear All,
> > The meeting minutes is now available as:
> > ftp://ftp.pwg.org/pub/pwg/mfd/minutes/PWG_MFD_minutes_20071211.pdf
> > and
> > ftp://ftp.pwg.org/pub/pwg/mfd/minutes/PWG_MFD_minutes_20071211.doc
> > Thanks very much for your participations. We had very fun, witty, and
> > fruitful discussions in the meeting.
> > -Nancy
> > Nancy Chen
> > Solutions and Technology
> > Oki Data
> > 2000 Bishops Gate Blvd.
> > Mt. Laurel, NJ 08054
> > Phone: (856) 222-7006 (desk)
> > (856) 222-5148 (lab)
> > Email: email@example.com
> Ira McDonald (Musician / Software Architect)
> Chair - Linux Foundation Open Printing WG
> Blue Roof Music / High North Inc
> PO Box 221 Grand Marais, MI 49839
> work: +1-906-494-2434
> home: +1-906-494-2697
> email: firstname.lastname@example.org
-- Ira McDonald (Musician / Software Architect) Chair - Linux Foundation Open Printing WG Blue Roof Music / High North Inc PO Box 221 Grand Marais, MI 49839 work: +1-906-494-2434 home: +1-906-494-2697 email: email@example.com
This archive was generated by hypermail 2.1.4 : Mon Dec 17 2007 - 17:44:14 EST