Semantic Model Face-to-Face Minutes
December 7, 2011

Meeting was called to order at approximately 1:00pm local on December 7, 2011.

Attendees

	Jacob Brown (Dell)
	Nancy Chen (Oki Data - call in)
	Tim McCann (Konica Minolta)
	Ira McDonald (High North/Samsung - call in)
	Joe Murdock (Sharp)
	Glen Petrie (Epson - call in)
	Michael Sweet (Apple)
	Jerry Thrasher (Lexmark)
	Bill Wagner (TIC)
	Rick Yardumian (Canon)
	Pete Zehler (Xerox - call in)

Agenda Items

	1.	IP Policy and Minute Taker
	a.	Policy accepted with Mike taking the minutes
	2.	Review comments on MFD System Control Service
	a.	ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdsystemcontrolservicemodel10-20111102.pdf
	b.	Section 6.3: Update roll-up state to use table or decision tree
	⁃	If any service is processing, report processing, else
	⁃	If any service is idle, report idle, else
	⁃	If any service is ..., report ..., else
	⁃	else if all services are stopped, report stopped
	⁃	Also update system state reasons roll-up
	⁃	Maybe use subsection - 6.3.1 Optimistic State Rollup
	c.	Global: Remove all usage of NEED NOT
	d.	Bad reference to conformance terminology
	3.	Review Dublin Core metadata additions
	a.	Action: Mike to rename document-dc-metadata to document-metadata in JPS3
	4.	Transform Service
	a.	Transform services provide a namespace-based transform list
	b.	Many-to-many mapping of documents
	c.	Variable data printing
	⁃	Do we pass data and "control file" or "form" as documents, or pass the data as a document and the "control file" or "form" as a URI/reference in the job ticket?
	⁃	Both possible, defined by transform
	d.	Document/JobDescription elements provide input document ticket
	e.	Document/JobProcessing elements provide output document ticket
	f.	Do we have standard transforms?
	⁃	We should in order to test interoperability and avoid proliferation of different versions of common transforms
	⁃	Also necessary to validate design of service
	g.	Come up with a list of potential transforms and verify that the transform service, as defined, can support those transforms
	h.	Validation of output is important for implementation; all we care about for interop testing is that some output was produced for the transform job (i.e. if the transform converts an input document to PDF, we just care that a PDF file was produced)
	i.	Potential transform services (for use cases, out-of-scope, design requirements, etc.):
	⁃	File conversion
	⁃	Remove printer drivers (very similar to file conversion)
	⁃	Imposition/scaling
	⁃	Color manipulation/red-eye removal
	⁃	Encryption/Decryption
	⁃	OCR/making a searchable PDF
	⁃	Variable data printing
	⁃	Watermarking, Bates Stamp (simple variable data printing)
	⁃	Mail merge (another simple variable data printing)
	j.	Make specific implementation recommendations for specific services
	5.	FaxIn Service
	a.	ftp://ftp.pwg.org/pub/pwg/mfd/wd/wd-mfdfaxinmodel10-20111130-rev.pdf
	b.	Section 6.5: Missing period, clarify that "figure N shows all possible subunits, but only the following subunits are applicable to the FaxInService: ..."
	c.	Action: Pete to add ServiceChargeInfo to SM; ServiceChargeInfo, ServiceChargeInfoUri, and ServiceOrganizations should be optional part of base class
	d.	Action: Ira to check LDAP schema for printer-charge-info/printer-charge-info-uri
	e.	Table 2: Add ServiceChargeInfo
	f.	Need JobRecievingUri for durable log
	g.	Action: Pete to add JobReceivingUri to FaxInJobStatus
	h.	FaxInJob Lifecycle:
	⁃	Pretty up...
	⁃	Rewrite to "FaxInService creates FaxInJob on behalf of System etc."
	⁃	What about logging of failed fax-in jobs during negotiation?
	⁃	Job is only created once a successful connection is negotiated
	⁃	Must be logged as a service event with one of the reason keywords a la MFD Alerts (make sure to cover this in step 0)
	⁃	Missing use of FaxInMetrics to get default job ticket as part of job creation
	⁃	Use named properties (e.g. FaxLogUri)
	⁃	Break up step 5 into successful/failed job
	⁃	Break up step 2 into successful/failed receipt
	⁃	Need to describe spooled vs. streamed fax jobs and when job enters the processing state
	⁃	Action: Mike to make some diagrams for the lifecycle of a spooled and streamed job
	i.	Lines 528/529: multidocument should be multiple document or multi-document; check throughout the document
	j.	Global: Remove all usage of NEED NOT

Next Steps / Open Actions

	•	Next conference call January 12, 2011 at 3pm (EDT)
	•	Print Job Ticket update and WG last call
	•	System Object and System Control Service PWG Formal Vote
	•	Work on preliminary draft of Transform Service
	•	Action: Mike to rename document-dc-metadata to document-metadata in JPS3
	•	Action: Mike to make some diagrams for the lifecycle of a spooled and streamed job
	•	Action: Pete to add ServiceChargeInfo to SM; ServiceChargeInfo, ServiceChargeInfoUri, and ServiceOrganizations should be optional part of base class
	•	Action: Pete to add JobReceivingUri to FaxInJobStatus
	•	Action: Ira to check LDAP schema for printer-charge-info/printer-charge-info-uri