All,
There will be an MFD conference call at 3:00 PM EST (12:00 PM PST)
Thursday July 22. Below is the proposed agenda and meeting logistics.
The meeting is held in accord with the PWG Intellectual Property Policy.
Agenda:
1. Identify Minute Taker
2. Approval of minutes from last meeting
<ftp://ftp.pwg.org/pub/pwg/mfd/minutes/pwg-mfd-minutes-20100715.pdf>
3. Agenda bashing
4. Plan agenda for upcoming Face to Face
5. Discuss MFD Requirements document Last Call Comments (including
Internationalization and Security)
<ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100720.pdf>
6. Discuss Copy Service Last Call Comments
<ftp://ftp.pwg.org/pub/pwg/mfd/wd/lcrc-mfdreq10-20100720.pdf>
Comments are included below
7. Next steps
Audio Information
Call-in toll-free number (US/Canada): 1-866-469-3239
Call-in toll number (US/Canada): 1-650-429-3300
Call-in toll number (US/Canada): 1-408-856-9570
Attendee access code: (by request only, please contact me if you do not
have it).
LiveMeeting URL:
Join the meeting.
<https://www.livemeeting.com/cc/xerox/join?id=PWG-MFD&role=attend&pw=Let
MeIn>
LiveMeeting First Time Users:
To save time before the meeting, check your system
<http://go.microsoft.com/fwlink/?LinkId=90703> to make sure it is ready
to use Microsoft Office Live Meeting.
LiveMeeting Troubleshooting
Unable to join the meeting? Follow these steps:
1. Copy this address and paste it into your web browser:
https://www.livemeeting.com/cc/xerox/join
2. Copy and paste the required information:
Meeting ID: PWG-MFD
Entry Code: LetMeIn
Location: https://www.livemeeting.com/cc/xerox
If you still cannot enter the meeting, contact support
<http://www.mymeetings.com/xerox>
Notice
Microsoft Office Live Meeting can be used to record meetings. By
participating in this meeting, you agree that your communications may be
monitored or recorded at any time during the meeting.
Peter Zehler
Xerox Research Center Webster
Email: Peter.Zehler at 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
1. Terminology
(1) Add <service> to the list of terms defined in the "Overall" document
Terminology section.
(2) Remove all XML element names - they are not terminologies.
(3) Some terms listed in Terminology are never used in the spec, should
be removed. Some are listed as being defined in the "Overall" document,
but never be capitalized in the spec. Please fix.
CopyDevice, Attributes, CrossFeed direction, Element, Feed
direction, Group Element, Hardcopy Document, Job Ticket, Local Client,
PhysicalCopyJobTicket, Remote Client, Scan Device, Scan Region,
Sequence, Slow Scan Direction, Template, Users, X, Y.
Section 6,
Line 263 -
"The PWG Semantic Model" mentioned here is very confusing. If it's PWG
Semantic Model v1.0 which only has semantics for Print Service, it does
not have semantics for Copy Service. Currently there is no newer PWG
Semantic Model spec that covers all MFD services yet. I think it's
better to replace it with "MFD System".
Line 269 - "printoing" should be "printing", a typo
Line 289 - "Copy" : should be "copy job"
Line 290 - remove a duplicated "that" from "that that"
Line 294 - "Each job has exactly zero document." : please provide the
rationale for this statement, or reference the section where the
rationale is provided.
Section 6.1
Line 308 - "CopyServer" : should be "CopyService"
Section 7.2
Line 422 - "provide" should be "provides"
Section 7.3.1
Line 449 - "set" should be "sets"
Section 7.3.3
Line 488-489 - Elements of CopyJobProcessing that are outside the yellow
box are said taken from PrintJobProcessing and are described in the MFD
Overall document, but such descriptions do not exist in the Overall
document yet.
Section 9
Line 511 - "ar" should be "are"
Section 10.2.1
Line 540 - "Conforming implementations MUST implement "all" of the model
objects as defined in this specification in the indicated sections" :
but not all are MANDATORY according to the Schema!!!
Security Consideration Section
I have recommended some general security considerations for all services
in MFD Requirements document. Please reference that document for common
security considerations.
Section 13.1
Depending on MFD's local security site policy, encryption of the
internal digital document might not be required. For example, for
copying a section of book or magzine in a public library, does a public
library normally require the internal digital doument be encrypted?
Section 13.2
I suggest to add at the beginning: "The design of Copy Service should
include access control to Copy Service operations in accordance with the
local site security policy."
--
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...
URL: <http://www.pwg.org/pipermail/mfd/attachments/20100721/26b89849/attachment-0001.html>