The project status summary for each FSG/OP architecture component (completed, work-in-progress, or proposed) is summarized below, to capture the presentation made by Ira McDonald (High North, FSG/OP Steering Committee) to the PWG/FSG Joint Plenary at Lexington.

This summary is posted on the PWG FTP Server

in the directory:
  ftp://ftp.pwg.org/pub/pwg/fsg/Oct2006-Printing-Summit-Lexington-Slides
in the files:
  FSG-OpenPrinting-Project-Status-Summary-20061026.htm
  FSG-OpenPrinting-Project-Status-Summary-20061026.pdf

The FSG/OP Reference Model Diagram is posted on the PWG FTP Server

in the directory:
  ftp://ftp.pwg.org/pub/pwg/fsg/architecture/Reference-Model
in the file:
  FSG-OpenPrinting-Reference-Model-Diagram-20060410.pdf

FSG/OP DSH (Directory Structure and Hierarchy) - completed

• FSG/OP DSH standardizes locations of PPD files and print drivers
• FSG/OP DSH will be adopted into FHS (Filesystem Hierarchy Standard) and LSB/3.2

PAPI (Print API) - completed

• PAPI/1.0 formally released by FSG/OP in July 2005
• PAPI/1.0 currently shipping in Sun's Open Solaris
• PAPI/1.0 reference implementation posted on Source Forge
• PAPI/1.0 may be ported onto CUPS IPP API for LSB/4.0 inclusion
• PAPI/1.0 spec is posted on the PWG FTP Server

  in the directory:
    ftp://ftp.pwg.org/pub/pwg/fsg/spool
  in the file:
    papi-v1.0-2005-07-15.pdf
  

JTAPI (Job Ticket API) - completed

• JTAPI/1.0 formally released by FSG/OP in July 2005
• JTAPI/1.0 UML diagrams and C headers are stable and aligned with spec
• JTAPI/1.0 reference implementation has not been written
• JTAPI/1.0 may be contributed into CUPS for LSB/4.0 inclusion
• JTAPI/1.0 spec is posted on the PWG FTP Server

  in the directory:
    ftp://ftp.pwg.org/pub/pwg/fsg/jobticket/JTAPI_Spec
  in the file:
    fsg-openprinting-job-ticket-api-v0100-20050315.pdf
  

PDAPI (Print Driver API, aka OPVP) - work-in-progress

• PDAPI/0.2 implemented in Ghostscript in all Linux distributions with drivers for over 100 printer models from three manufacturers
• PDAPI/0.2 to be adopted into LSB/3.2 with PWG UPDF namespace required (used in all existing implementations) and partial Text/Font support excluded (will be added in the future when fully defined)
• PDAPI/1.0 now technically complete and scheduled for formal release by FSG/OP before end-of-2006
• PDAPI/1.0 makes support of PWG UPDF namespace for driver/printer properties mandatory for conformance (to ensure portability to any renderer)
• PDAPI spec is posted on the PWG FTP Server

  in the directory:
    ftp://ftp.pwg.org/pub/pwg/fsg/vector/work-in-progress
  in the file:
    pdapi-spec-1.0rc20061020.pdf
  

PCMAPI (Print Channel Manager API) - work-in-progress

• PCMAPI supports management of communications channels (USB, Parallel, etc.) to local or network printers
• PCMAPI design work continues with feedback from Printing Summit
• PCMAPI spec is posted on the PWG FTP Server

  in the directory:
    ftp://ftp.pwg.org/pub/pwg/fsg/pcm
  in the file:
    fsg-PCM-V008-060709E.pdf
  

SMAPI (Status Monitoring API) - work-in-progress

• SMAPI prototyped in 2004
• FSG/OP Steering Committee requested that communications channels be broken out separately (to PCMAPI)
• After PCMAPI is complete, SMAPI spec will be updated to use PCMAPI
• SMAPI spec is posted on PWG FTP Server

  in the directory:
    ftp://ftp.pwg.org/pub/pwg/fsg/status_monitoring
  in the file:
    SMAPI_draft_20040522.pdf
  

• PCAPI should support at least Adobe PPD and PWG UPDF property namespaces (in an abstract manner analogous to JTAPI)
• PCAPI is currently being designed by Wendy Phillips (Sun)

• DDAPI should support multiple discovery methods (SNMP, DNS-SD, LDAP, etc.)
• DDAPI design may be proposed by Ira McDonald (High North)

• TFMAPI should support format-neutral API for conversion of print document formats (source, intermediate, or print-ready) for use by PAPI implementations and applications
• TFMAPI design may be proposed by Ira McDonald (High North)