Pete,
I have no objections to the proposed changes - all of the "new" content is coming from an existing spec, and it makes sense to put it in MFD Model instead of duplicating it in all of the service specs.
On Feb 28, 2011, at 9:24 AM, Zehler, Peter wrote:
> All,
>>>> While updating the references in various tables I encountered some issues that led to the following comments.
>>>>>> 1) Remove MediaMaterial from MediaCol since it was somehow dropped between the original set 2 and 5100.11.
>>>> 2) Move DestinationURIs from FaxOut to Overall
>> This Job Processing element specifies destinations for the Job transmission (e.g., FaxOut). It is a sequence of DestinationURIsEntry each of which defines a single destination. The DestinationURI is an RFC3966 [RFC3966] compliant URI. Dial Strings were dropped when RFC3966 superseded RFC2806 [RFC2806], "Dial strings" are the actual numbers, symbols, and pauses entered by a user to place a phone call. We have added some elements to contain the Dial String information even though they could be encoded as RFC3966 compliant parameters.
>>> PreDialString
>> The PreDialString is the Dial string entered before the DestinationURI is applied. The data type for a dial string is a string. The ABNF for a Dial Sting that applies to a PreDialString is given below.
>>>> PostDialString
>> The PostDialString is the Dial string entered after the DestinationURI is applied. The data type for a dial string is a string. The ABNF for a Dial Sting that applies to a PostDialString is given below.
>>>>>> The ABNF for a Dial Sting that applies to a PreDialString and a PostDialString is given below.
>>>> DialString = 1*(phonedigit / dtmf-digit / pause-character)
>> pause-character = one-second-pause / wait-for-dial-tone
>> one-second-pause = "p"
>> wait-for-dial-tone = "w"
>> dtmf-digit = "*" / "A" | "B" / "C" / "D" / “#”
>> phonedigit = DIGIT / [ visual-separator ]
>> visual-separator = "-" / "." / "(" / ")" / "'" / "(" / ")"
>> T33Subaddress
>> The T33 subaddressing can be specified by the T33Subaddress element since a T33 subaddress can only contain digits [RFC3192], the data type for the T33Subaddress is an integer. Multiple T33 subaddresses are not supported in a single DestinationURIsEntry. If multiple mailboxes are to be addressed each one requires its own entry.
>>>> 3) Move ConfirmationSheetPrint from FaxOut to Overall
>> This element’s value indicates whether an confirmation sheet is to be printed when the job reaches a terminating state. The data type of this element is a Boolean. The format of the confirmation sheet is implementation specific.
>>>> 4) Move CoversheetInfo from FaxOut to Overall
>> This element specifies the information used to create a system generated coversheet transmitted before the documents(s) of the FaxOutJob.
>> CompanyName
>> This element contains the user supplied name of the company for the cover sheet. The data type of this element is a string.
>> DateTime
>> This element contains the user supplied date and time for the cover sheet. The data type of this element is a string.
>> From
>> This element contains the user supplied name of the person group or entity for the cover sheet. The data type of this element is a string.
>> Logo
>> This element contains the user supplied URL pointing to an image uses as the logo for the cover sheet. The data type of this element is a URI.
>> Message
>> This element contains the user supplied message for the cover sheet. The data type of this element is a string.
>> Subject
>> This element contains the user supplied subject for the cover sheet. The data type of this element is a string.
>> To
>> This element contains the user supplied name of the recipient for the cover sheet. The data type of this element is a string.
>> Any
>> This element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperability
>>>> 5) Move RetryInfo from FaxOut to Overall
>> This element specifies the information used to control document transmission timeouts.
>> NumberOfRetries
>> This element contains the number of attempts to retransmit the document in the event of a transmission failure before aborting the job. The data type of this element is an integer.
>> RetryInterval
>> This element contains the number of seconds between transmission attempts. The data type of this element is an integer.
>> RetryTimeout
>> This element contains the number of seconds before abandoning a transmission attempt when no document data is being sent. The data type of this element is an integer.
>> Any
>> This element provides an extension point for vendor differentiation and implementation specific extensions while maintaining interoperability
>>>> 6) Add missing OverridingElements to Overides sequence in <service>JobTicket & fix data type of Overrides in <service>JobTicketCapabilities (Align with PWG 5100.6 instead of obsolete PWG 5100.4.)
>> OverridingElements
>> This element contains the set of Job Ticket elements for the Override. The elements have the same meaning as in the <service> Job Ticket. The supported Job Ticket elements are listed in the <service>JobTicketCapabilities.Overrides.
>>>>>>>> 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
>>>>> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean. _______________________________________________
> mfd mailing list
>mfd at pwg.org>https://www.pwg.org/mailman/listinfo/mfd
__________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
--
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/20110228/e70e3bfc/attachment-0001.html>