1. Imaging Status
Shivaun Albright
Imaging Committee Chair HP

2. Agenda UPnP v1 Imaging Update – Where are we? UPnP v1 Deficiencies
UPnP v2 Requirements
UPnP v2 Use Scenarios
Why Web Services?
Schedule for UPnP v2 Imaging
Future Meetings

3. Scan Subcommittee Status – UPnP V1
Scanner Service Definitions Complete
Scanner Device
Scanner Service
ExternalActivity Service
Feeder Service
Minimal Data Format – XHTML-Print
Required Image Format
JPEG (JFIF) Support
Sample Implementers: Canon, Ricoh, HP
Scanner Specifications published as Approved Standards

4. Print Subcommittee Status - UPnP v1
Printer Service Specifications Approved
Printer:1 Device
PrintBasic:1 Service
Optional Printer Service
PrintEnhancedLayout:80 shelved for now
Targeted at Photo Printing
Minimal Data Format – XHTML-Print
Planned PWG submittal of XHTML-Print
Required Embedded Image Format
JPEG (JFIF) – PrintBasic
Sample Implementers
HP, Oak Technologies, Canon

5. UPnP Version 1 Deficiencies
Data types
Missing arrays and structures
Action Extensibility
Need to be able to specify whether arguments are optional/required or whether it should just use device settings (defaults)
Security – e.g., Access control
Service Inheritance
Data inheritance may work here
Eventing
Prefer SOAP-based eventing instead of GENA
Event filtering and grouping at the device level

6. Imaging WC Architecture Requirements
Utilize existing toolsets – generic web services
Utilize standard web services to develop a standard service for:
Eventing
Security
AllowedValueList
Vendors must be able to extend and subset the AllowedValueList for Printer and Job attributes
Ability to extend Actions/Operations
Wild carding on the M-Search in SSDP
Scalability of discovery for enterprise support
Simple way to designate “Default” values

7. Use Scenarios (Printer)
Location-based Printing – “print to the near-by printer” (hotel, home, airport, etc.)
Microsoft desktop printing for the mobile client
Driver-centric model using a PDL
PDA, cell phone (e.g., XHTML-Print) printing
Job Ticket Model + XHTML-Print
“Client operates the same—regardless of the location”
Print-by-URL (Printer http Gets file)
Secure Printing

8. Use Scenarios (Scan) Scan
Scan to a service (e.g., storage, application)
Scan to a fax
Scan to
Scan to Print (copy function)
Scan with user intervention

9. Why Web Services? Offloads printing functions:
Job control and workflow
Content rendering
Billing and accounting
Security and authentication
Uses latest standards in the industry (e.g., XML, SOAP, WSDL)

10. UPnP v2 Imaging Schedule
Complete Use cases
Prioritize
Identify Requirements
Complete Device Model (MFD vs. Print & Scan)
Provide Architecture input
Complete Detailed service interfaces
Design Complete – March 2003
Complete Prototypes
PlugFests (minimum of 2) – May, July 2003,
Possible Hosts: Lexmark, Oak Tech., MS, HP
Incorporate feedback from Plugfests
Technical review, forum review, SC review
“Approved” specification (Sept 2003)

11. Next Steps Future Meetings Imaging Committee w/ 2 subcommittees:
Nov 4th – 7th – PWG in New Orleans
Nov 4th UPnP Print and Scan
January – Hawaii Meeting
Imaging Committee w/ 2 subcommittees:
Printing Subcommittee
Scanning Subcommittee

12. For the interconnected lifestyle