Accessibility

Sample files — TSP301

Download these sample files (ZIP: 127k) to demonstrate functionality. The following files are included in the download:

  • PDF form (tsp301.pdf)
  • XML form data file (tsp301.xml)
  • XML form data package file (tsp301.xdp)
  • PDF form, rights-enabled for Adobe® Reader® software (tsp301b1.pdf)
  •  

    tsp301.pdf

    This sample file should be opened using Adobe Acrobat® 6.0 software. This is a typical form used by employees to allocate retirement savings across several different investment funds. This particular sample illustrates a government agency example, but it is equally applicable to private industry.

    Traditionally, an employee would open the PDF file, print it, fill in the information, and send the paper form for processing, where the data would then be keyed into an enterprise system. This paper-based process may take days, if not weeks, to complete and risks introducing data entry errors and delays.

    Delays, expense, and effort can be eliminated using new Adobe technology for Portable Document Format (PDF) and XML that allows the data to be entered directly into the form, where it can then be integrated with enterprise systems without human intervention.

    When the form is opened in Acrobat 6.0, the user can enter the information directly into the form.

    Note: When the form is first opened in Acrobat 6.0, a dialog box appears that tells the user that the total of all fund percentages must equal 100. This is an example of simple business logic that can be embedded in a PDF/XML form. The business logic can be as simple or as complex as desired or required by the business process of which the form is a part. For example, the business logic could connect to a database or a Web service. Click OK to dismiss the dialog box.

    tsp301.xml

    Now it is time to see the XML form data representation that is produced by the form. To export the XML form data yourself, follow these instructions:

    The schema representation for the form data is a simple one that was developed to show the XML output from Adobe PDF/XML forms. The schema to which the data conforms could come from a database, a Web service, or an external industry-standard vocabulary such as ACORD (insurance), eGrants (government grants), HL7 (health care), RosettaNet/OASIS EPS (manufacturing), HR-XML (human resources), TaxML (financial services), XBRL (financial statement reporting), UBL (e-commerce), or any other. Adobe's technology for XML supports arbitrary, customer-defined XML data sources. Using the Adobe design tool, the form designer imports the XML schema and binds the elements of the schema to the form fields. The form can even be created automatically by dragging the XML from the schema onto the form design canvas.

    By combining XML with PDF in this manner, PDF/XML documents become the vehicle for integrating human interaction into enterprise data systems. Furthermore, PDF/XML documents can be used to both collect and distribute data.

    The next step is to import the XML data into a PDF template. However, let's modify the data first.

    This illustrates the ability to use PDF/XML documents for round-tripping data or for one-way distribution of data from an enterprise system. The PDF/XML document can act as a presentation template, which is then merged with the XML instance data to make a complete document. Furthermore, the XML data continues to move with the PDF/XML document and can be exported later if needed. PDF/XML documents can also contain XML data that is not part of the form but is used for other aspects of the business process of which the form is a part. Consequently, the PDF document can act as a data container.

    tsp301.xdp

    As part of the new Adobe XML architecture, Adobe is also introducing an XML packaging mechanism for PDF called XML Data Package (XDP). This sample (tsp301.xdp) is an example of the XDP file for the tsp301.pdf sample file. To create an XDP from the PDF file:

    The XDP specification is a way to save a PDF file in XML format where a number of PDF subassemblies are exposed in the XML file. Some of these subassemblies include the XML form template definition and the XML form data schema, among others. The PDF file itself is also Base-64 encoded in the XDP. As a result, PDF files can participate in XML workflows where an enterprise has existing infrastructure, applications, and tooling for processing XML. Then when the user needs to interact with the XML data, the XDP file can also be opened in Acrobat or Adobe Reader .

    tsp301b1.pdf

    This is an example of a PDF/XML document that has also been rights enabled with Adobe LiveCycle™ Reader Extensions software, providing users of the free Adobe Reader 6.0 with the ability to save forms and data locally, fill them out online, distribute to others for review and commenting, add digital signatures, and submit them via e-mail or the Web directly from within Adobe Reader.

    Most organizations want to accrue the benefits of using PDF/XML forms, but don't want to impose any cost or technology constraints on their users or customers. Adobe solutions allow organizations to accomplish both of these goals because the Adobe Reader is free and is available on most major technology platforms.

    To see how the XML capabilities are enabled in this sample: