Patent Grant
8307045
1. Field of the Invention
The invention relates generally to methods for communicating data and more particularly to methods for generating templates for the conversion of XML and other non-display-formatted data to formats which are suitable for presentation on specific devices or classes of devices which utilize corresponding mark-up languages.
2. Background of the Invention
The Internet has become a powerful tool for disseminating information. Although the Internet was originally used to communicate scientific and technical data, increased numbers of service providers, improved applications for retrieving data and user-friendly interfaces have made it a useful tool for millions upon millions of users. It is commonly used by people of all ages for transmitting and receiving messages, for research, for shopping and for surfing (browsing) the Internet.
The increased popularity of the Internet is due in part to the amount of information which is available, and in part to the convenience with which people can access this information. Generally speaking, the information is accessed with browsers of various types. Traditionally, browsers have been computer-based applications which provide user interfaces to the Internet. These browsers are configured to request information from servers which are also connected to the Internet. The browsers typically communicate with the servers using a protocol known as hypertext transfer protocol, or HTTP. The servers, in turn, provided their information to the browsers via text and data which is marked or tagged so that the browser can format it for display to the user. This formatting information is typically provided through the use of hypertext markup language (HTML) tags that indicate which pieces of information should be formatted in a given manner.
The use of HTML to provide formatting information to the browsers allows the same information to be transmitted to different types of browsers which have different capabilities, yet still be presented to the user in a readable/viewable fashion, adapted to the capabilities of the respective browsers. As a result, information providers do not have to tailor the format of their information to a particular type of browser and thereby limit the dissemination of the information. Instead, they can provide information in a single format which is accessible by a much greater user population.
The accessibility of Internet-based information has increased further with recent developments in browser technology. Browsers can be incorporated into portable, wireless devices so that users can access the Internet without being tied to a PC. For example, some cellular phones and personal digital assistants (PDAs) incorporate Web browsers. Information which is transmitted to these browsers typically incorporates wireless markup language (WML), rather than HTML tags.
One of the difficulties in accommodating all of these different types of client devices is that each of them may use a different markup language which is specifically adapted to the capabilities of the corresponding device. A mechanism must therefore be provided to enable the conversion of generic data to the appropriate markup language for each of the devices. Typically, this mechanism is provided through a set of templates, wherein each of the templates is configured to convert the generic data into a corresponding markup language.
There are several drawbacks to the use of these templates. One of these drawbacks relates to the fact that each of the templates is configured to convert data corresponding to one particular service into a markup language corresponding to one particular client device. Whenever it is desired to enable the transfer of data to a new client device, or to transfer data corresponding to a new service to the existing client, it is necessary to generate a new set of templates which is configured to make the required content transformations. It should be noted that, to support a single new client device, a set of templates corresponding to each of the available services is necessary. Likewise, in order to support a single new data service, a set of templates corresponding to each supported client device is necessary. Because the creation of new templates (typically using JSP or ASP technology) is difficult, the need to create a new set of templates for each new client device or service presents a daunting task.
One or more of the problems outlined above may be solved by the various embodiments of the invention. Broadly speaking, the invention comprises systems and methods for enabling the automatic creation of templates which are then used to convert service data from a non-displayable generic format to alternate formats which are suited to be displayed on various client devices. In a preferred embodiment, a master template corresponding to a set of devices is generated. The master template contains information relating to these devices which enable it to generate individual templates corresponding to specific service data and specific devices (or device classes). When it is desired to provide data corresponding to a new service to the client devices, the data corresponding to the new service is examined to identify its structure, specifically name-value pairs. A user is prompted to accept a default label (the name from the name-value pair) or provide a new label corresponding to each pair. The user may select all or part of the service data to be used with the individual templates that will be generated. Based upon the service data and the information provided by the user, the master template is used to generate a service-specific template for each specific device class, wherein each template is configured to convert the service data into markup language data suitable for display on a corresponding device. The method thereby enables the automatic generation of templates for the conversion of the service data to markup language files that can be displayed on different client devices.
In one embodiment, a method comprises examining service data and using a master template to generate service-specific templates for each of a plurality of devices or device classes. A master template is constructed to define a style for presentation of data on the devices. Service data such as XML data is examined to identify name-value pairs (XML tags and the information enclosed by the tags). The user is queried for labels that will be associated with these pairs. The XML tag corresponding to each pair may be used as a default label if no alternative is provided by the user. Based upon this information and the information contained in the master template, a plurality of device templates, each of which is associated with a specific type or class of devices, are generated. Each device template is configured to receive the service data and convert this data into a markup language format which is suitable for display on the associated device type. The method thereby eliminates the need to manually construct an individual device template for each device type whenever it is desired to provide a new data service.
Another embodiment of the invention comprises a software application. The software application is embodied in a computer-readable medium such as a floppy disk, CD-ROM, DVD-ROM, RAM, ROM, database schemas and the like. The computer readable medium contains instructions which are configured to cause a computer to execute a method which is generally as described above. It should be noted that the computer readable medium may comprise a RAM or other memory which forms part of a computer system. The computer system would thereby be enabled to perform a method in accordance with the present disclosure and is believed to be within the scope of the appended claims.
Numerous additional embodiments are also possible.
Other objects and advantages of the invention may become apparent upon reading the following detailed description and upon reference to the accompanying drawings.
While the invention is subject to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and the accompanying detailed description. It should be understood, however, that the drawings and detailed description are not intended to limit the invention to the particular embodiment which is described. This disclosure is instead intended to cover all modifications, equivalents and alternatives falling within the scope of the present invention as defined by the appended claims.
A preferred embodiment of the invention is described below. It should be noted that this and any other embodiments described below are exemplary and are intended to be illustrative of the invention rather than limiting.
Broadly speaking, the invention comprises systems and methods for facilitating the communication of data which must be converted into a markup language in order to make it suitable for display on a receiving device. The present techniques allow templates to be quickly created for the conversion of data such as XML-formatted data into markup languages which are suitable for use with one or more corresponding devices. For example, information which is formatted as XML data may need to be converted to HTML before it can be viewed on a full-size browser such as Netscape. If, on the other hand, the data is to be transmitted to a wireless device, the data may need to be converted to a particular form of WML in order to be properly displayed on that device.
Instead of manually generating individual templates to convert generic data for each service into each markup language which may need to be provided to a client device, a master template can be used to generate an individual template for each group of similar devices requiring a specific markup language and relying on a specific user interface pattern. Each individual template corresponds to a particular device type and a particular service. Individual templates corresponding to new data services can therefore be automatically generated.
Raw data may be delimited in a way that it is not easily human-readable. For example, a series of values may be separated by semicolons or some other delimiter (e.g., “first name; last name; . . . ”). When a database engine reads this data, it is aware based upon the database schema that the first value corresponds to a first variable, the second value corresponds to a second variable, and so on (e.g., the first value is a first name, the second value is a last name, . . . ).
In XML, the values are delimited by text tags which identify the corresponding variables. The tags have the form “<tag_name>” and “</tag_name>”, where the former delimits the beginning of the value and the latter delimits the end of the value. For example, if the variable “first_name” has the value “John”, this would typically appear in XML as <first_name>John</first_name>”.
XML differs from earlier in data formats in that it is easily human-readable, and that it is easy to program an application that understands the XML data and does something with it. An application could, for example, read data formatted as described above and identify the first_name and last_name values, handling each one in a manner which is appropriate for the application. This may consist of re-ordering the names, presenting them in a particular font, or using or manipulating the values in any other way. The application simply has to look for the appropriate tags and read the information which is enclosed by them. There is no need for special database drivers or software which allow the data to be read.
The use of tags in XML is very similar to the use of tags in HTML. In XML, however, the tags are used only for the purposes of delimiting and identifying data. The tags do not define presentation information, such as font, color, position on a page, etc. In other words, the tags do not serve a markup purpose as they do in HTML and other markup languages. Below is an example of XML data for a weather reporting service.
<weather_report>
<day_of_week>Monday</day_of_week>
<temperature>75</temperature>
<wind_speed>10</wind_speed>
</weather_report>
This data corresponds to a service which provides data relating to particular weather conditions. The data for a given report is preceded by the opening tag <weather_report> and is followed by the </weather_report> tag. The individual pieces of data within the report are each enclosed by tags identifying the data.
It should be noted that, for the purposes of this disclosure, the term “unformatted data” will be used to refer to XML or similar data despite the use of identifying tags. (This data could alternately be referred to as “non-display-formatted” data.) This data is referred to as unformatted because it does not contain information relating to the manner in which the data should be formatted for the purposes of presentation. For example, it does not have tags identifying tables, cells within tables, fonts, colors, or other information that would be used to control the presentation of the data to a user.
Referring to
As indicated above, the server must be capable of providing data to a variety of different types of clients. For example, the client may be a PC running a full-scale Internet browser such as Netscape, or it may be a cellular phone which has a browser with limited screen area and features. The client device may even be a two-way pager which can only display one or two lines of text at a time. A separate XSL template is needed for each of these devices. This is illustrated in
One embodiment of the present intention involves the use of a master template from which individual templates can be generated. These individual templates can then be used to convert unformatted (e.g., XML) data into a format which is suitable for presentation via a corresponding client device. This is illustrated in
It should be noted that, for the purposes of this disclosure, identical items in the figures may be indicated by identical reference numerals followed by a lowercase letter, e.g., 22a, 22b, and so on. The items may be collectively referred to herein simply by the reference numeral.
Master template 43 contains information that defines the manner in which data for the selected service is presented, as well as information on the presentation capabilities of the client devices. Master template 43 is not intended to be used to directly convert unformatted data to a particular markup language. It is instead intended to provide building blocks from which the individual templates (which are intended to convert the unformatted data into formatted data) can be constructed. The master template is used in conjunction with a software application (a “wizard”) which identifies the name-value pairs in the service data and selects the building blocks from the master template which are necessary to generate the formatting for these name-value pairs.
“Name value pairs is used here to refer generally to the generic format of the service data. It should be noted that the data may be in a more sophisticated format in some instances. For example, wind data could be presented in XML as
<WindSpeed>5</WindSpeed>
<WindDirestion>NW</WindDirection>
or
<Wind>
<Speed>5</Speed><Direction>NW</Direction></Wind>
The template wizard can be configured to handle either format.
It should also be noted that the XML data may contain pictures or other multimedia content. For instance, the weather conditions “Sunny” and “Cloudy” could be represented by sunshine or cloud icons, respectively. The wizard can be configured to display the icons on devices which have the appropriate graphics capabilities, while the words (e.g., “Sunny” or “Cloudy” could be displayed on devices which don't have the capability to display icons.
The master template follows a predetermined style. When the master template is written, the author chopses the manner in which data will be displayed. For example, it may be written to display name-value pairs as rows in a table. Different types of data may be handled differently. For instance, report headings may be displayed in a larger font than other data. The style may be adapted to each of the devices for which the master template will be used to create individual templates since the formatting for each type of data is defined in a separate building block.
Referring to
Referring to
In the preferred embodiment, there is a single master template. The master template defines a single style (which may vary somewhat from device to device) which is embodied in the individual, service/device-specific templates. When it is desired to support a new type of client device, the master template must be updated (or a new one written) to include building blocks corresponding to that device. These building blocks can then be used to define a service-specific template for the new device. It is contemplated that, in an alternate embodiment, several master templates may be provided, wherein each defines a different style for the presentation of service data. A user could then be prompted by the wizard application to select a style (master template) according to which the individual templates will be generated.
The present invention may provide a number of advantages over prior art methods. For example, although XML provides a mechanism for enabling the definition, transmission, interpretation, etc. of data between disparate applications and thereby simplify the interfaces between such applications, XML is widely regarded as a very unforgiving language. Consequently, it is typically very tedious and time consuming to manually construct the templates necessary for the generation of markup-language data which is suitable for display on the different client devices to which a server may provide data. The time and cost associated with the generation of these templates can make XML-based server solutions unattractive to users in spite of other advantages they might provide. By providing a means for the automatic generation of templates to accommodate new data services, the present methods may eliminate this disadvantage.
The benefits and advantages which may be provided by the present invention have been described above with regard to specific embodiments. These benefits and advantages, and any elements or limitations that may cause them to occur or to become more pronounced are not to be construed as a critical, required, or essential features of any or all of the claims. As used herein, the terms “comprises,” “comprising,” or any other variations thereof, are intended to be interpreted as non-exclusively including the elements or limitations which follow those terms. Accordingly, a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to the claimed process, method, article, or apparatus.
While the present invention has been described with reference to particular embodiments, it should be understood that the embodiments are illustrative and that the scope of the invention is not limited to these embodiments. Many variations, modifications, additions and improvements to the embodiments described above are possible. Particularly, these variations may include computers or other data processing devices, computer readable media (such as floppy disks, CD-ROMs, DVD-ROMs, etc.,) storage devices, computer memories and the like which contain software, firmware or other programming embodying the foregoing methods. It is contemplated that these variations, modifications, additions and improvements fall within the scope of the invention as detailed within the following claims.
This application claims the benefit of U.S.C. §119(e) of U.S. provisional application Ser. No. 60/314,514, filed on Aug. 22, 2001 entitled “Method for Creating Templates to Convert Data into Target Markup Languages”, which is hereby incorporated by reference as if set forth herein in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4754428 | Schultz et al. | Jun 1988 | A |
| 4811207 | Hikita et al. | Mar 1989 | A |
| 5210824 | Putz et al. | May 1993 | A |
| 5212787 | Baker et al. | May 1993 | A |
| 5226161 | Khoyi et al. | Jul 1993 | A |
| 5257369 | Skeen et al. | Oct 1993 | A |
| 5331673 | Elko et al. | Jul 1994 | A |
| 5339392 | Risberg et al. | Aug 1994 | A |
| 5421015 | Khoyi et al. | May 1995 | A |
| 5572643 | Judson | Nov 1996 | A |
| 5704017 | Heckerman et al. | Dec 1997 | A |
| 5727129 | Barrett et al. | Mar 1998 | A |
| 5732218 | Bland et al. | Mar 1998 | A |
| 5740430 | Rosenberg et al. | Apr 1998 | A |
| 5761416 | Mandal et al. | Jun 1998 | A |
| 5774660 | Brendel et al. | Jun 1998 | A |
| 5790426 | Robinson | Aug 1998 | A |
| 5790790 | Smith et al. | Aug 1998 | A |
| 5796952 | Davis et al. | Aug 1998 | A |
| 5870559 | Leshem et al. | Feb 1999 | A |
| 5878223 | Becker et al. | Mar 1999 | A |
| 5884282 | Robinson | Mar 1999 | A |
| 5918014 | Robinson | Jun 1999 | A |
| 5958008 | Pogrebisky et al. | Sep 1999 | A |
| 6012052 | Altschuler et al. | Jan 2000 | A |
| 6041311 | Chislenko et al. | Mar 2000 | A |
| 6049777 | Sheena et al. | Apr 2000 | A |
| 6067565 | Horvitz | May 2000 | A |
| 6085226 | Horvitz | Jul 2000 | A |
| 6092049 | Chislenko et al. | Jul 2000 | A |
| 6094662 | Hawes | Jul 2000 | A |
| 6112279 | Wang | Aug 2000 | A |
| 6128655 | Fields et al. | Oct 2000 | A |
| 6138141 | DeSimone et al. | Oct 2000 | A |
| 6141737 | Krantz et al. | Oct 2000 | A |
| 6151624 | Teare et al. | Nov 2000 | A |
| 6182136 | Ramanathan et al. | Jan 2001 | B1 |
| 6185586 | Judson | Feb 2001 | B1 |
| 6185608 | Hon et al. | Feb 2001 | B1 |
| 6192415 | Haverstock et al. | Feb 2001 | B1 |
| 6198824 | Shambroom | Mar 2001 | B1 |
| 6272492 | Kay et al. | Aug 2001 | B1 |
| 6374247 | Gebauer | Apr 2002 | B1 |
| 6408360 | Chamberlain et al. | Jun 2002 | B1 |
| 6571246 | Anderson et al. | May 2003 | B1 |
| 6578000 | Dodrill et al. | Jun 2003 | B1 |
| 6651217 | Kennedy et al. | Nov 2003 | B1 |
| 6671746 | Northrup | Dec 2003 | B1 |
| 6697844 | Chan et al. | Feb 2004 | B1 |
| 6701428 | Harvey, III et al. | Mar 2004 | B1 |
| 6754621 | Cunningham et al. | Jun 2004 | B1 |
| 6850941 | White et al. | Feb 2005 | B1 |
| 7051316 | Charisius et al. | May 2006 | B2 |
| 7530016 | Sahota et al. | May 2009 | B2 |
| 7756727 | Greenspan et al. | Jul 2010 | B1 |
| 20010032254 | Hawkins | Oct 2001 | A1 |
| 20010034771 | Hutsch et al. | Oct 2001 | A1 |
| 20020049833 | Kikinis | Apr 2002 | A1 |
| 20020065109 | Mansikkaniemi et al. | May 2002 | A1 |
| 20020065912 | Catchpole et al. | May 2002 | A1 |
| 20020073119 | Richard | Jun 2002 | A1 |
| 20020078168 | Christfort et al. | Jun 2002 | A1 |
| 20020138582 | Chandra et al. | Sep 2002 | A1 |
| 20020165877 | Malcolm et al. | Nov 2002 | A1 |
| 20020178187 | Rasmussen et al. | Nov 2002 | A1 |
| 20020184610 | Chong et al. | Dec 2002 | A1 |
| 20030033377 | Chatterjee et al. | Feb 2003 | A1 |
| 20030060896 | Hulai et al. | Mar 2003 | A9 |
| 20030217117 | Dan et al. | Nov 2003 | A1 |
| 20040030697 | Cochran et al. | Feb 2004 | A1 |
| 20040205452 | Fitzsimons et al. | Oct 2004 | A1 |
| 20060010373 | Burns | Jan 2006 | A1 |
| 20060074944 | Stark et al. | Apr 2006 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| 60314514 | Aug 2001 | US |
