Edits for this document.
Page 6, "Document Data" has an extra comma
Page 6, "<service>" is duplicated here (see Page 8 for desired entry)
Page 7, "Job Ticket" is entered twice.
Page 9, should the abbreviation for PSTN be added (which is done on page
11)
Page 16, There is no sentence under item 10.
Page 17, There is no sentence under item 5. It looks like item 4 was
spread over item 5 and 6.
Page 18, This is the only use-case that does not have a subsection
header called "Processing Steps". I do not think it is critical, I
just wanted to note it.
Glen
> -----Original Message-----
> From: pwg-announce-bounces at pwg.org[mailto:pwg-announce-bounces at pwg.org]
> On Behalf Of Michael Sweet
> Sent: Monday, August 09, 2010 2:00 PM
> To: pwg-announce at pwg.org> Subject: [Pwg-Announce] PWG MFD Requirements Formal Vote (9-31 August
> 2010)
>> Greetings:
>> This email initiates the Formal Approval vote by the PWG membership on
the
> PWG MFD Requirements, which is located at:
>>ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdreq10-20100722.pdf>> The complete list of PWG Last Call issues and resolutions is located
at:
>>ftp://ftp.pwg.org/pub/pwg/mfd/wd/mfdreq10-last-call-comment-> resolution-20100722.txt
>> The voting period will open today on Monday 9 August 2010 and will
close
> at 10pm (US Pacific Time) on Tuesday 31 August 2010.
>> Valid votes are: Yes, No, No (with Strong Objection), Abstain.
>> Representatives from PWG member companies are strongly encouraged to
> exercise their right to vote.
>> PWG Privacy Policy: Your vote is confidential and will not be
disclosed
> by PWG officers or document editors.
>> To vote, send an email with *exactly* the following subject line
format:
>> MFD Requirements Formal Vote-<company name>-<voter's last name>-
> <Yes/No/Abstain>
>> Example: MFD Requirements Formal Vote-Acme-McGee-Yes
>> Any "No" vote MUST state the reason for the "No" vote and MUST contain
a
> description of the *technical* changes required to turn the "No" vote
into
> a "Yes" vote - otherwise such a "No" vote will NOT be counted. Any
"No"
> vote MUST NOT contain *editorial* comments, per the PWG Process/3.0.
>> Any "Yes" vote MAY contain "editorial" comments but MUST NOT contain
any
> *technical* comments, per the PWG Process/3.0.
>> Please send your vote to all of the following email addresses
(replacing
> "dot" with '.' and "at" with '@'):
>> msweet"at"apple"dot"com (PWG Chair)
>> ptykodi"at"tykodi"dot"com (PWG Secretary)
>> Peter"dot"Zehler"at"xerox"dot"com (MFD WG Chair)
>> wamwagner"at"comcast"dot"net (MFD Requirements Editor)
>> Please do NOT simply reply to this note on PWG-Announce (to preserve
the
> confidentiality of your vote).
>> Note:
> (1) This Formal Vote is being conducted under the rules of the PWG
> Process/3.0 and the current PWG Policy on Intellectual Property and
> Confidentiality agreement. The 2010 PWG Membership Agreement calls out
> both of these documents and the links are provided below.
>> (2) To be eligible to vote the member MUST have submitted a signed
copy of
> the 2010 PWG Membership Agreement and paid their dues.
>> The PWG Definition of the Standards Development Process Version 3.0 is
> located at:
>>http://www.pwg.org/chair/membership_docs/pwg-process30.pdf>> The PWG Policy on Intellectual Property and Confidentiality is located
at:
>>http://www.pwg.org/chair/membership_docs/pwg-ip-policy.pdf>> Regards,
> Michael Sweet (PWG Chair)
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>> _______________________________________________
> pwg-announce mailing list
>pwg-announce at pwg.org>https://www.pwg.org/mailman/listinfo/pwg-announce
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.