Quite so. But I had not entered these questions as answered since the
responses did not appear to resolve my questions.
1. Since from your response, a document may contain zero or one document
ticket, and a job can contain zero or more documents, I do not see the error
in saying that a job can contain zero or more document tickets. At any rate,
for those who have not internalized the model, it does answer the question
of how the document tickets get into the service.
I may misunderstand, but I think it would be misleading to say in the
general document description that a document may contain zero or one
document ticket since documents can exist exclusive of jobs, but I assume
that it is only when a document is part of a job that it may contain a
2. Your response with regard to StorageMakeAndModel, although it appears
to confirm my observation, does not address the question of what the
reference should be. We originally had two separate elements but there
appeared to be consensus that a single MakeAndModel element was
reference-able. I do not recall who maintained that, but if that is so, I
would like the reference.
From: Ira McDonald [mailto:blueroofmusic at gmail.com]
Sent: Tuesday, January 05, 2010 3:01 PM
To: William Wagner; Ira McDonald
Cc: mfd at pwg.org
Subject: Re: [MFD] Dec. 8-9 Face-to-Face Meeting Minutes is now available
All of these questions have already been addressed earlier in
this thread (notes dated 18 through 23 December).
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - TCG Hardcopy WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
email: blueroofmusic at gmail.com
579 Park Place Saline, MI 48176
PO Box 221 Grand Marais, MI 49839
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...