Uploaded image for project: 'PrintTalk'
  1. PrintTalk
  2. PTK-66

update intro

    XMLWordPrintable

    Details

      Description

      need to mention cip4

        Draft

        1 Introduction
        PrintTalk is an XML standard that is maintained by CIP4 and provides a single format for Print Providers to collaboratively communicate Business
        Transactions and specifications of Print Product both with their Print Buyers and among themselves. Print industry professionals from a wide range of organizations contributed to the design of PrintTalk. Such organizations include eCommerce companies, print business management systems, print providers, and print equipment manufactures.

        The PrintTalk standard embraces [XJDF 2.0] and [cXML 1.2]. These bracketed references are defined in Appendix
        D References. By incorporating PrintTalk XJDF has been enhanced to provide a richer descriptive capability. While XJDF
        describes the piece to be produced, PrintTalk specifies the external communication of business processes between Print
        Provider and Print Buyer.
        With the extensions made for PrintTalk 1.3, it may also be used for subcontracting. For details about XJDF, see [XJDF
        2.0] .
        The PrintTalk interface specification is distributed free of any license fees or royalties in order to address the need for
        end-to-end connectivity in the printing industry.
        The following pages describe the Business Objects that make up PrintTalk. See Section 2.8 Business Objects for a complete
        list of Business Objects and a description of each.

         

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                prosi Rainer Prosi
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: