NO329750B1 - A server and a method for presenting and capturing data - Google Patents

Abstract

A server and method are described to add HTML functionality to XSL-FO standard document templates. Clients that support the extended XSL-FO standard can fill information interactively in documents produced from said templates, while other clients will process the documents as standard XSL-FO format documents.

Description

Field of the invention

The present invention relates to a server and a method for producing documents in a computer system, in particular for interactive presentation and capture of data from a user.

Background

Most computer systems need to present data as printouts (reports, certificates, receipts, etc.) and accept user input of data (form/GUI).

This task is solved by several different standards and programming languages. For example, J2EE/ASP/PHP and similar frameworks are often used to produce HTML interfaces in a Web application. Additionally, XSL-FO can be used to create printouts, as well as other proprietary systems such as JasperReports, QuickReport, ReportMill, etc.

HTML (HyperText Markup Language) can be used for printing, but lacks features such as accurate layout that spans multiple real pages. HTML is also not suitable for certificates as the format allows changes to the content of the text.

XSL-FO (Extendible Stylesheet Language Formatting Objects, a markup language for XML document formatting (XML = Extendible Markup Language) proposed by the W3C group, currently in version 1.1) has become a market standard for printing according to which this standard is particularly developed to solve printing problems. In its original form, however, this format will not allow data capture or user control as in HTML. XSL-FO only allows the production of PDF pages that can be locked for further changes. In other words, the original XSL-FO format does not support interactive documents that can receive information entered by the user for direct loading into e.g. a database, the user must instead enter their data in a form that is printed as a PDF document and mail the paper printout to the recipient.

This is a major shortcoming of XSL-FO and several proprietary extensions to the XSL-FO format have been presented to address this problem. However, such solutions will limit document production to a few proprietary products, as standard tools cannot understand the proprietary format code.

From US 2008/0017722 Al, a method is known for creating a summary of an electronic document in the form of barcodes.

US 2008/0010588 Al describes a method for updating electronic documents. The method allows client-based modification of the document.

US 7 036 072 B1 describes a method for processing a document, and in particular modifying a definition file.

Summary of the Invention

It is a purpose of the present invention to provide a solution for interactive capture of presentation of user-entered data in the XSL-FO data format which overcomes the problems mentioned above.

Specifically, the solution provides an extension of the XSL-FO format that takes advantage of HTML mechanisms to provide interactivity, while tools based on the current XSL-FO standard are allowed to produce documents as usual.

This is achieved in a server and a method as stated in the subsequent patent claims.

More specifically, according to a first aspect, the invention relates to a server for presenting and capturing data, including means for storing a document template, said document template being based on a layout definition for markup format, where the format is extended with interactive elements included in comment field in the template, the server being arranged to receive requests for said template and process the template to provide a presentation of the template with support for interactive elements, and means for collecting interactively captured information, according to claim 1.

According to another aspect, the invention relates to a method for presenting and capturing data, the method comprising the steps: storing at least one document template, said template being based on layout definition for markup format commands, providing at least one interactive element in a comment field in said template, processing of the template to provide a presentation of the template with support for interactive elements, and collection of interactively entered information, according to claim 6.

Several embodiments of the invention appear from the associated independent claims.

Brief description of the drawing

The invention will now be described in detail by reference to the attached drawing (only one) which schematically illustrates a system involving the present invention.

Detailed description

The drawing illustrates a situation where a number of users working on clients 1, 2, 3 access a commercial or public server 4, via a network 6 such as the Internet. The server 4 stores a number of documents, such as forms intended to be retrieved by clients 1, 2, 3 for completion and submission to those who operate the server 4. A client can request a specific form to read and fill in information.

The clients can be of different types, with different requirements and abilities. The server 4 must therefore be able to present information in several different formats that suit the individual client. As an example, client 1 can be a mobile phone that wants access to information from server 4 such as WAP pages. Client 2 can use a PC (personal computer) running a standard Web browser. Client 2 wants to receive information from server 4 in an interactive format. This means that any information entered by the user can be sent directly to a storage medium, such as a database in the server 4, without having to print the completed form and post it to the recipient. When the user has finished the form, the user will often need to print a receipt, and the server 4 must therefore also be able to produce the document in a standard PDF format. An example of the relevant document could be a tax return.

This document is stored as one of several templates in the server 4, typically stored in a database 5. The templates are produced using software that supports an XSL-FO format according to the present invention. The templates therefore include proprietary commands in addition to the standard XSL-FO format commands. The clients 1, 2 can access the server 4 and request a fill-in presentation of a particular template. The server 4 will then process the template, produce the fill-in presentation and return this to the client in a format that can be read by the client. During processing, the server 4 will come across extended XSL-FO format commands in the template. These commands will extend the XSL-FO presentation to include HTML-specific properties that bring interactivity to the document. Data filled into such a form is separated from the layout and can be collected to be sent to an external party or stored directly in the database. When the template is retrieved, the server 4 will typically also retrieve other information regarding the client, such as address information, from the database 5 or other sources 7 and include this information in the form that is presented to the client. The client may then be able to correct this information and complete the form with other information before it is entered into the database 8 (which may be local or remote from the server 4, e.g. located at an external party). This database 8 can be a separate database or identical to the database 5 which stores the templates. As mentioned above, the client can also request a receipt for the completed form, and the server will then use standard XSL-FO parsing to produce a PDF page.

Client 3 is a large company that runs an industrial computer system. They can retrieve a blank template from the server 4 to process in their own system. They will typically fill in relevant information for a number of customers or employees, and then produce PDF files that are printed and mailed to the recipients. The business client 3 uses software for document processing, such as Apache Fop, RenderX, Antenna XSL Format-ter, which supports standard XSL-FO, but not the extended version according to the present invention. When processing a template retrieved from the server 4, the client 3 will not understand the extended commands entered into the template. The client 3 will not actually notice the presence of said commands, but will process the template like any other XSL-FO based document. In this way, the extension of the XSL-FO format is transparent to software that does not support the Opflnerian extended format.

The transparent extension of the XML-FO standard can be realized in several ways:

1. XSLT comments extended with additional semantics

In XSL-FO, lines starting with an exclamation mark are interpreted as comments added for the benefit of the readers, i.e. to make the template easier to read. Such lines are skipped by the document processing programs as the content is of no use when processing the template. According to the present invention, a specific name field (xfo:) is added immediately after the exclamation point which tells the document processing program that the comment line should also be processed.

The following program listing shows an example of a user management/completion field realized as a comment line: <!-xfo:text-box id="id-0aa7396f-012ffad0" ref="firstname" expression="" taborder="0"-- >

<fo:block-container position="absolute" left="19.05mm" top="10.05mm" >

<fo:block text-align="start" font-family="Helvetica" font-size="10.00pt">

<xsl:value-of select="firstname"/>

</fo:block>

</fo:block-container>

The highlighted line is a comment line, indicated by the exclamation mark. In this case, however, the line includes extended format commands, which any document processing program that supports the extended format will understand, and which here defines a fill-in box where the user enters their first name. The following lines define the box in the standard way, which can also be interpreted by conventional programs (ie, the conventional programs will understand this as a definition of a box as such, but not assign any interactive or data-binding properties to the box).

As used in the present invention, the structure of the comment lines provides the possibility of: Classification of an element based on a collection of XSL-FO syntax (out sighted) which means that it can be interpreted to produce the corresponding HTML or corresponding protocol for GUI/user control. In the example, this element is described by xfo:text-box. This gives the opportunity to make the box interactive, i.e. the content entered by the user can be taken as input parameters.

To provide references to child data elements (XML) independent of the implementation in XSL-FO. In the example, this is described by ref= "first name". This means that the server 3 can omit reading FO syntax that describes the appearance of the box other than as a comment. This gives greater freedom for future changes in the implementation.

Giving the element specific identity/class that allows CSS control in HTML

(CSS = Cascading Style Sheet, a language used to define the appearance of files written in HTML or XML). In the example, this is described by id="id-0aa7396f-012ffad0". An alternative is to use the ID fields on the elements in the XSL-FO code. However, this means that the ID fields will not always be unique, and will produce unnecessarily long HTML documents. When listing elements, for example, an unambiguous classification of the ID for each element avoids to prevent several CSS elements that describe the same appearance, an appearance that is common to all the repeated elements.

Additional attributes in the comment field that cover other properties, such as

table rows, default values four padding fields, support for the blind, etc.

Using comments at different levels in the XSL-FO document as support

for page titles in HTML, support for translations (will be described later).

2. XSLT variables can be extended with additional functionality if necessary

An alternative technique for providing transparent extensions to the XSL-FO format can be realized using nested XSLT variables. These will normally be processed by the XSLT engine, but not produce output to PDF. (XSLT = Extendible Stylesheet Language Transformations is part of the XSL suite of tools defined by the W3C group, used to transform the XML elements in a document to HTML). The following example will user management with support for events and validation: <!-xfo:text-box id="id-0aa7396f-012ffad0" ref="firstname" expression="" taborder="0"">

<fo:block-container position="absolute" left="19.05mm" top="10.05mm" width="46.90mm" ...> <xsl:variable name="event">

<xsl:variable name="EventId"><![CDATA[OnClick]]x/xsl:variable>

<xsl:variable name="EventType"><![CDATA[Submit]]x/xsl:variable>

<xsl:variable name="EventHandler"><![CDATA[cmd_pdf]]></xsl:variable>

<xsl:variable name="EventParameter"><![CDATA[]]x/xsl:variable>

</xsl:variable>

<fo:block text-align="start" font-family="Helvetica" font-size="10.00pt">

< xsl: va lue-of select="forna vn"/>&# 160;

<xsl:variable name="validation">

<xsl:variable name="ErrorMessage"x![CDATA[Field must be completed!]]x/xsl:variable>

<xsl:variable name="Required"x![CDATA[true]]x/xsl:variable>

<xsl:variable name="ValidationType"x![CDATA[none]]x/xsl:variable>

<xsl:variable name="NumberOfCharacters"x![CDATA[0,0]]x/xsl:variable>

<xsl:variable name="CompareWith"x![CDATA[]]x/xsl:variable>

</xsl:variable>

</fo:block>

</fo:block-container>

Nested variables provide the opportunity to:

to produce several levels as is usual in XML. This is done by placing variables inside other variables. In the example above, a superordinate level is created for an event, and all specific attributes/characteristics of the event are defined in additional variables. The outer level is in bold in the example.

Using multiple level/nested elements gives the opportunity to expand the format on

an easy way in the future.

To separate information from the general format. Then standard tools will

for DF/print skip this information.

To allow the information to be read in logical levels.

Easy addition of new commands and functions.

Support for translation into different languages

The extensions to the XSL-FO format are based on assigning identities to different elements (id). This gives the opportunity to retrieve translations of the elements if needed.

Software tools that support the extended format can easily extract translatable information based on the structure of the format. This information can then be translated using a standard text editor.

An example of exporting translatable information for user management:

<?xml version="1.0" encoding="ISO-8859-l"?>

<digiforms_locale documentld="id-0a6c8386-013cle00" language="no_NO" ..>

<element id="id-0aa7396f-012ffad0" type="xfo:text-box">

<default>

<fieldvalidate>

<errorx![CDATA[The field must be filled in!]]x/error>

</fieldvalidate>

</default>

<translation>

<fieldvalidate>

<errorx![CDATA[Field must be filled in!]]x/error>

</fieldvalidate>

</translation>

</element>

</digiforms_locale>

Note that this listing continues from the previous examples. The example shows that the element (user acid) defined in a child comment (extension) in the original format, <!— xfo:text-box id="id-0aa7396f-012ffad0", can export information that is considered translatable.

The elements are organized with a section showing the original information in its original language and providing a simple starting point for the translation. The ID of the element allows translated information to be relocated into the document when it is displayed or produced in the desired language. This is done by setting a parameter in the processing software that indicates which language fields are to be retrieved from the support server.

The structure prevents the person doing the translation from changing the original format, appearance or functions of the document.

The translator can use any available editor or word processing software.

The inventive use of XSLT variables allows a template to be used both for interactive form filling and document production, in different languages. These functions require the availability of a support server. However, the format can also be used by clients to produce output based on the original format and which is not dependent on said support server.

Although the invention has been described in a particular embodiment that uses HTML elements to produce interactivity, those skilled in the art will recognize that there are several alternatives for this purpose available from other markup languages such as XHTML; WML etc.

An embodiment of the invention provides interactivity by using or unused comment fields in the template. When the template is processed, the server is informed of the presence of an interactive command by a specific name field that follows the comment declaration mark (exclamation mark). However, any pattern that can be recognized by the server can be used for this purpose.

Another implementation is to use nested XSLT variables to provide interactivity. The term "variable" is intended to cover any command to any party involved and in the present description of the invention the term "command is used in a broad sense. A command can e.g. be an "event handler" that starts a handler if the user places the cursor in a specific field (or when he/she removes the cursor from said field) such as providing a comment/explanation to users or an instruction to the server to read information entered in a field, to modify the content of the field or to open another page, etc.

Claims (12)

1. Server (4) for presenting and capturing information, including means (5) for storing at least one document template, said document template being based on a layout definition for markup format, characterized in that the layout definition for markup format is extended with interactive elements, where said interactive elements are included in comment fields in said template, the server (4) is arranged to receive requests for said template and process the template to provide a presentation of the template with support for interactive elements, and means (8) for collecting interactive captured information. 2. Server according to claim 1, where said layout definition for markup format is XSL-FO and said interactive elements are HTML elements. 3. Server according to claim 1, where said storage means (5) and/or said means (8) for collecting information include one or more databases. 4. Server according to claim 1, where said means (8) for collecting information are arranged to forward collected information to t external system or service. 5. Server according to claim 1, in that the server is further arranged to incorporate information from other sources in said presentation. 6. Procedure for presenting and capturing data, characterized in that the five-step method includes the steps: storing at least one document template, said document template being based on layout definition for markup format commands, providing at least one interactive element in a comment field in said template, processing the template to provide a presentation of the template with support for said at least one interactive element, and collection of interactively entered information. 7. Method according to claim 6, where said layout definition for markup format is XSL-FO and said interactive elements are HTML, XHTML or WML elements. 8. Method according to claim 6, further comprising incorporating information from other sources in said presentation. 9. Method according to claim 6, comprising providing a pattern or name field that identifies that the comment field includes one or more interactive elements. 10. Method according to claim 6, comprising inserting said interactive element into a command, as a variable inside another variable. 11. Method according to one of claims 6 - 10, comprising providing each of said interactive elements with a specific identity. 12. Method according to claim 11, comprising the step of including language-specific information in said presentation.