Jun, et al:
I have no problem including other ways to include in-line image data using the
object and/or img elements. The issue the group needs to decide on is what is
the compliance answer? Are all the possible methods acceptable? Should we
identify one and only one that is required for compliance? Any discussion from
others?
I'll add a reference to RFC2397.
**********************************************
Don Wright don at lexmark.com
Member, IEEE SA Standards Board
Member, IEEE-ISTO Board of Directors
f.wright at ieee.org / f.wright at computer.org
Director, Alliances & Standards
Lexmark International
740 New Circle Rd
Lexington, Ky 40550
859-825-4808 (phone) 603-963-8352 (fax)
**********************************************
Jun Fujisawa <fujisawa.jun%canon.co.jp at interlock.lexmark.com> on 03/08/2002
02:11:37 AM
To: PWG XHTML-Print <xp%pwg.org at interlock.lexmark.com>
cc: (bcc: Don Wright/Lex/Lexmark)
Subject: XP> Inline image data
The description of an alternate method to include inline image
by using 'declare' attribute of 'object' element has been added
to Appendix B of XHTML-Print 0.951 specification.
I don't think this particular method is the only "conditionally
mandatory" method to include inline image in XHTML-Print.
What's wrong with the following methods?
- 'object' element without 'declare' attribute
<object width="20 mm" height="20 mm" type="image/jpeg"
data="data:image/jpeg;base64,aGh67Fghsapa0Hji7dfGSweTa..."
- 'img' element
<img width="20 mm" height="20 mm"
src="data:image/jpeg;base64,aGh67Fghsapa0Hji7dfGSweTa..."
Also, I'd like to suggest to add a reference to RFC2397.
"RFC2397 - The "data" URL scheme", L. Masinter.
It is available from http://www.ietf.org/rfc/rfc2397.txt.
--
Jun Fujisawa
<mailto:fujisawa.jun at canon.co.jp>