Don,
I was wondering why not publish xhtml-print as an IEEE-ISTO standard with a
PWG standard number, say, 5103.1? (The PWG agreed to allocate IEEE-ISTO 5102
series to IPPFAX this week for the IFX (5102.1) and UIF (5102.2) documents).
xhtml-print can still have its own web site as you have done and be
available at something like (when approved):
ftp://ftp.xhtml-print.org/pub/pwg/xhtml-print/standards/xhtml-print-v1.0.pdf
but it could also be published on the PWG site as well when approved (there
is no problem with double posting, I would think):
ftp://ftp.pwg.org/pub/pwg/standards/pwg5103.1.pdf
A separate, but related question would be about
application/vnd.pwg-multiplexed?
Since we agreed to make application/vnd.pwg-multiplexed a PWG standard this
week (but try first to get the IETF to publish the PWG standard as an
informational RFC), we could also publish application/vnd.pwg-multiplexed on
the xhtml-print.org web site as well as the pwg web site.
Should application/vnd.pwg-multiplexed be in the same IEEE-ISTO series as
xhtml-print, i.e., 5103.2? or its own number: 5104.1?
Thanks,
Tom
-----Original Message-----
From: don@lexmark.com [mailto:don@lexmark.com]
Sent: Friday, September 14, 2001 12:32
To: Hastings, Tom N
Cc: IMAGING@forum.upnp.org
Subject: Re: Updated PrintBasic:0.90 Template [xhtml-print has new URL
an d new MIME type]
All:
Application/vnd.pwg-xhtml-print+xml has been registered with IANA. That is
all
I plan to register at this time.
**********************************************
* Don Wright don@lexmark.com *
* *
* Chair, IEEE MSC *
* Member, IEEE SA Board of Governors *
* Member, IEEE-ISTO Board of Directors *
* *
* Director, Alliances & Standards *
* Lexmark International *
* 740 New Circle Rd *
* Lexington, Ky 40550 *
* 859-825-4808 (phone) 603-963-8352 (fax) *
**********************************************
"Hastings, Tom N" <hastings%CP10.ES.XEROX.COM@interlock.lexmark.com> on
09/14/2001 03:26:37 PM
Please respond to "Hastings, Tom N"
<hastings%CP10.ES.XEROX.COM@interlock.lexmark.com>
To: IMAGING%FORUM.UPNP.ORG@interlock.lexmark.com
cc: (bcc: Don Wright/Lex/Lexmark)
Subject: Re: Updated PrintBasic:0.90 Template [xhtml-print has new URL an
d new MIME type]
Don Wright has published a new version of the xhtml-print spec.
Changes which need to be made to the UPnP PrintBasic template 90 spec as a
result include:
1. The URL to the document is now a new web site
(http://www.xhtml-print.org):
In section 2.3 References, change:
[XHTML-PRINT] - "XHTML (tm) - Print", version 0.60, May 11, 2001, <work in
progress>, Available at: ftp://ftp.lexmark.com/pub/standards/xhtml-print.pdf
to:
[XHTML-PRINT] - "XHTML (tm) - Print", version 0.9, August 30, 2001, <work in
progress>, Available at:
ftp://ftp.xhtml-print.org/pub/pwg/xhtml-print/drafts/xhtml-print-draft-090.p
df
2. The MIME Media type has changed to application/vnd.pwg-xhtml-print+xml
2a. In section 2.6.16 DocumentFormat, change:
If the UCP (client) does not know the document format, it SHOULD supply the
'application/octet-stream' value and let the Printer determine the format,
unless the Printer doesn't support the 'application/octet-stream' value, in
which case the UCP's only recourse is to supply the special 'unknown' value.
All UPnP printers MUST support at least the 'text/xhtml-print+xml' document
format[XHTML-PRINT] and the 'unknown' value.
to:
If the UCP (client) does not know the document format, it SHOULD supply the
'application/octet-stream' value and let the Printer determine the format,
unless the Printer doesn't support the 'application/octet-stream' value, in
which case the UCP's only recourse is to supply the special 'unknown' value.
All UPnP printers MUST support at least the
'application/vnd.pwg-xhtml-print+xml' document format[XHTML-PRINT] and the
'unknown' value.
2b. Change:
The vendors MAY extend the allowed values for this attribute, but MUST NOT
support the 'device-setting' Distinguished Value. The vendor MAY subset the
allowed values as long as 'text/xhtml-print+xml' and 'unknown' remain as
supported values.
to:
The vendors MAY extend the allowed values for this attribute, but MUST NOT
support the 'device-setting' Distinguished Value. The vendor MAY subset the
allowed values as long as 'application/vnd.pwg-xhtml-print+xml' and
'unknown' remain as supported values.
2c. Change:
Note: 'text/xhtml-print+xml' needs to be registered as a MIME Media Type
with IANA.
to:
Note: 'application/vnd.pwg-xhtml-print+xml' needs to be registered as a
MIME Media Type with IANA.
ISSUE: Has it been registered with IANA?
2d. In Table 2.5, change:
text/xhtml-print+xml
to:
application/vnd.pwg-xhtml-print+xml
2e. Change section 3 ML Service Description from:
<allowedValue>text/xhtml-print+xml</allowedValue>
to:
<allowedValue>application/vnd.pwg-xhtml-print+xml</allowedValue>
Thanks,
Tom
-----Original Message-----
From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com]
Sent: Thursday, August 16, 2001 11:57
To: IMAGING@forum.upnp.org
Subject: Re: Updated PrintBasic:0.90 Template - "Design Complete" for
Plug -Fest [version number 0.90 vs. 90]
Just to clarify. I wasn't at the meeting in Toronto, so I didn't realize
that you had agreed to change the version number to be integer 90, not 0.90,
(at least just for the Plug Fest. Here is from the minutes just published:
Because UPnP requires integer values for the version number, devices will
advertise "PrintBasic:90" for the PlugFest.
So you'll have to make this minor edit to the template for the plug fest to
change 0.90 to 90.
Sorry for the confusion,
Tom
-----Original Message-----
From: Hastings, Tom N [mailto:hastings@cp10.es.xerox.com]
Sent: Monday, August 13, 2001 10:08
To: IMAGING@forum.upnp.org
Subject: Updated PrintBasic:0.90 Template - "Design Complete" for
Plug-Fes t
Gerry and I have updated the PrintBasic Template as agreed at the Toronto
meeting starting with the version that Shivaun edited at the meeting. This
template is the one for the Plug-Fest and is "Design Complete". Therefore,
we changed the version number from 0.84 to 0.90. Here is the Change
History:
Version .84 to .90
Incorporated the following changes from our July 31st meeting in Toronto:
1) Changed the name of the service template to
PrintBasic from BasicPrint. This enables the ability to search for all
Print service templates by specifying the service name as "Print". This
search request would retrieve responses from PrintBasic:1, PrintBasic:2,
PrintEnhanced:1, PrintEnhanced:2, etc.
2) Move the version to .90 to indicate Design
Complete.
3) Modified error 765 to be a generic temporary
error instead of specifying a "memory overflow" or "disk full" condition,
since the Technical Committee has come up with 6xx series errors that
overlap with our errors. If a printer encounters a memory overflow error,
the printer should report the 603 "Memory Overflow" error to the client. If
the printer encounters any other error that is considered a temporary
condition, then the printer should report the 765 error.
4) Removed the Conformance Requirements section
since there was concern about redundancy and we didn't see the value in
having this section. Device vendors are required to implement everything
specified in this document.
5) Rewrote the section on Synchronization of
Evented Variables for clarity.
Other editorial things we fixed, but don't need mention in the Change
History:
Added zero and decimal point before the 90 in the name, sub-title, Section
2.1 Service Type, and page headings, since I assume that it is 0.90, not
version 90, correct? We had done it that way for most of our previous
versions.
Changed the reference to Enhanced Template to PrintEnhancedLayout and so
made those changes to the references, and put TBD for the date for version
0.10.
Added a proper reference in the References Section [MULTIPLEXED] to Bob
Herriot's paper (two r and one t) and referred to it from the
XHTMLImageSupported section.
Added text to the Temporary Error to refer to the 6xx errors, if they were
more specific (as already indicated in the Change History).
Did a spell check.
I've attached a .zip with both the version with revisions (-rev in the file
name) and a clean version. I also changed the file name to today date
010810 which is the date that I put in the document header as well.
Thanks,
Tom
<<Service_printer_v90_010810.zip>>
This archive was generated by hypermail 2b29 : Fri Oct 26 2001 - 13:46:34 EDT