Hilton Portland, Portland, Oregon
June 24, 2002
I. Introductions II. Review and Approve minutes from April III. Review status of open issues and action items from minutes i) CSS Attributes Proposal from Melinda and Elliot IV. Review of xhtml version of the document V. Discussion on Canon's request to reorganize the specification see: http://www.pwg.org/hypermail/xp/0036.html http://www.pwg.org/hypermail/xp/0038.html http://www.pwg.org/hypermail/xp/att-0036/01-xhtml-print-CanonDraftProposal-020529.pdf VI. W3C Device Independent Working Group and its effect of XHTML-Print (http://www.w3.org/2002/06/w3c-di-wg-charter-20020612.html note: section5.2.5) VII. New Issues i) Using Multiple Style Sheets (http://www.pwg.org/hypermail/xp/att-0040/01-One_or_more_style_sheets_can_be_used_in_a_document.doc) VIII. Adjourn
Jim Bigelow agreed to be the minute taker for the meeting.
Accepted as distributed
Melinda Grant and Elliot Bradshaw examined each of the relevant XHTML attributes and categorized them into:
Note: a revised version of the attribute-spread sheet was distributed the Friday before the meeting so participants had not had time to review it. A discussion of some of the attributes marked "optional" occurred with the understanding that the committee would discuss and decide how all the attributes should be handled in subsequent meetings:
|action, cols, enctype, method, rows, tabindex, <select size>||
Consideration of this attribute and others directly related to
supporting the Basic Forms module showed some difficulties
with printing a representation of a form. Printing a blank
form or a form containing the default values is not difficult.
The problem comes up when considering a use case where
users would like to fill out a form and print it, as filled out, for
a record or confirmation of a transaction. XHTML-Print
support for this use case is not possible within the
specification of XHTML-Print constructs since the data
entered into the form by the user is not part of the language,
rather it is a separate data stream. |
The entity presenting the form can avoid the problem by presenting an information page integrating the user's data and the form.
Melinda Grant suggested that only minimal support for printing a blank form be mandated in the language since there is no method within the language to merge the user data and the form.
Jacob Refstrup suggested that the user data and form could be transmitted to the printer in a multi-part/multiplexed data stream in a manner similar to the transmission of inline data.
|Charset||The suggestion is this attribute is optional since UTF-8 handles character set specification. The manner that a conforming printer handles this attribute is implementation dependent.|
|Classid & codetype||The suggestion is one attribute is supported they must both be supported.|
|Declare||Support for this attribute is optional since low memory device any not be able to honor the intent of attribute – to store the image for later reference.|
|Src||Make jpeg baseline the minimum requirement|
|Valign||The rationale for suggesting this be optional was not available during the discussion, in its absence the suggestion is to make it required.|
Action Item: Jacob Refstrup will locate and make available a version of a tool to find and mark differences between two html documents.
Action Item: Don Wright is to decide where in the specification the attributes will be discussed.
Action Item: Don Wright will replace the character reference with an entity reference.
There were two parts to the proposal to restructure the specification:
The discussion of how to organize the specification can be summarized as follows:
The discussion of how to specify an image's orientation can be paraphrased as follows:
Action Item: Canon will bring up the issue of image rotation with the w3c so that a w3c approved method can created and used in the XHTML-Print specification. In the interim the processing of EXIF marker will be optional.
Action Item: post the issue for discussion of the PWG XP mailing list for 2 weeks.
The mission of the W3C Device Independent Working Group is to study issues related to authoring, adaptation and presentation of Web content and applications that can be delivered effectively through different access mechanisms. The group's charter (Section 5.2.5 Printer related groups) names the PWG XHTML-Print committee as the body responsible for the definition of print markup (XHTML-Print) and printer capability descriptions.
The link element can be used to include one or more style sheets in a document. Depending on the attributes within the link element the style sheet:
The consensus is that:
Action Item: Jim Bigelow will write a paragraph for the XHTML-Print specification dealing with multiple style sheets in a document.
Jacob Refstrup is attending CSS meetings and reports that:
XSL (eXtensible Stylesheet Language) is a markup language for formatting material to media such as a page. XSL contains 51 formatting objects and 231 properties for configuring the formatting objects.
Harry Lewis called for a consideration of the relationship of XSL formatting objects and XHTML-Print. The consensus was that XSL is too complex for low cost printers to implement.
Melinda Grant called for a consideration of how to deal with the CSS material now in the XHTML-Print specification since it is not complete. The discussion evolved into a consideration of the structure of the XHTML-Print specification and ended with the proposal that the specification be broken into the following separate documents:
Action Item: Jacob Refstrup will write the first draft of "CSS Print Profile." Don Wright will write drafts of the other two documents: "XHTML Print" and "XHTML + CSS: A Profile for Printing"
Work is continuing with the conversion w3c documents to an XML schema. When the conversion is complete, the DTD can also be easily converted.
|August 26-30,||Santa Fe, NM.|
|November 4-8,||New Orleans, LA|