EP1155373A1 - Creation d'un contenu hypermedia pour site web - Google Patents

Creation d'un contenu hypermedia pour site web

Info

Publication number
EP1155373A1
EP1155373A1 EP00903859A EP00903859A EP1155373A1 EP 1155373 A1 EP1155373 A1 EP 1155373A1 EP 00903859 A EP00903859 A EP 00903859A EP 00903859 A EP00903859 A EP 00903859A EP 1155373 A1 EP1155373 A1 EP 1155373A1
Authority
EP
European Patent Office
Prior art keywords
file
web site
folder
files
template
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Withdrawn
Application number
EP00903859A
Other languages
German (de)
English (en)
Inventor
Martin Russ
Ben Willis
Ian Christopher Kegel
Mark Bagley
Rachel Berry
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
British Telecommunications PLC
Original Assignee
British Telecommunications PLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from GBGB9903641.0A external-priority patent/GB9903641D0/en
Application filed by British Telecommunications PLC filed Critical British Telecommunications PLC
Priority to EP00903859A priority Critical patent/EP1155373A1/fr
Publication of EP1155373A1 publication Critical patent/EP1155373A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/12—Use of codes for handling textual entities
    • G06F40/131—Fragmentation of text files, e.g. creating reusable text-blocks; Linking to fragments, e.g. using XInclude; Namespaces
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/103—Formatting, i.e. changing of presentation of documents
    • G06F40/117—Tagging; Marking up; Designating a block; Setting of attributes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • G06F40/186—Templates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/197—Version control

Definitions

  • This invention relates to creating hypermedia content for a web site.
  • hypermedia such as hypertext
  • HTML hypertext language
  • the client may comprise a personal computer or other processing device capable of presenting the data retrieved from the server to a user.
  • the network may comprise a local area network (LAN), a wide area network (WAN) or may comprise the Internet.
  • LAN local area network
  • WAN wide area network
  • the World Wide Web comprises many servers connected over the Internet in a web, which have addresses in the form of universal resource locators (URL).
  • URL universal resource locators
  • the hypertext information is arranged in web pages which include hyperlinks to allow the user to establish a link to another web page, which may be located on the same or a different server, the routing to the document being achieved by use of a URL in the web page at the hyperlink.
  • Web clients typically access the hypermedia information using a browser.
  • An overview of the World Wide Web and HTML is given in Chapter 1 of "HTML 3.2 and CGI Unleashed” J. December and M. Ginsberg 1996 (ISBN 1-57521-177-7) .
  • HTML is usually used to prepare web pages, they can also be created in other markup languages.
  • Web pages can display text, graphics and files of other descriptions such as video images, animated graphics and audio samples.
  • Hypermedia have the significant advantage that the client can rapidly transfer viewing from one document to another by using a mouse to click on hyperlinks in the document, permitting the user to transfer from one web site to another, which may be at different physical locations.
  • markup languages such as HTML define the location and format of hypermedia included in the web page.
  • the page may include text in a particular font and at a particular location defined by.HTML markers on the page.
  • HTML HyperText Markup Language
  • individual web pages may be written by a programmer in HTML but this is a time consuming exercise and a number of alternative approaches have been implemented hitherto.
  • HTML converter programs are available which translate documents into HTML. For example, a document prepared in the wordprocessor format can be converted into HTML by the use of such a conversion program. Sometimes, templates are used which define the layout of a page in HTML, into which the user can insert text or other data such as images, in order to create a web page with a particular look and feel.
  • HTML editors are used to create and edit hypertext. Many editors provide a what-you-see-is-what-you-get (WYSIWYG) way to create and edit HTML files, without actually having to type the individual HTML marker tags which define the position and style of item in each web page. Such HTML editors comprise an application program software package which needs to be loaded onto the computer. The editor establishes a database of HTML files that can be edited and amended using a viewer. The relationship between the individual pages of the web can be displayed graphically.
  • WYSIWYG what-you-see-is-what-you-get
  • HTML editor is FrontPage by Microsoft Corporation. This provides a viewer which allows features such as hyperlinks and graphics to be dropped onto a web page without having to write lines of code in HTML.
  • the editor is provided with a database for storing the web pages and the links between them produced when using the viewer.
  • the resulting HTML code can be uploaded to a server from the editor's database.
  • Other HTML editors include PageMill by Adobe Corporation, for use with Macintosh hardware and Webmaster Pro from HeyerTech Inc.
  • HTML editors such as FrontPage
  • HTML editors enable high quality web sites to be produced in HTML
  • the use of the editor requires a certain amount of training and the editor needs to be purchased as an additional package which is loaded onto the computer as an application program, to provide the viewer, the database and other functionality.
  • Such editors enable relatively large web sites to ' be created and maintained effectively but they are not particularly suited to creating and editing relatively small web sites, making them unattractive for example, to users who wish to establish a personal web site or small business users who wish to establish a relatively small web site.
  • a method of creating hypermedia content for a web site making use of a computer configuration that has an operating system wherein files are configurable in a hierarchical structure and the operating system is provided with a viewer that provides a visual display of the hierarchical structure and an indication of the file content, the method being characterised by using the viewer of the operating system to establish a hierarchical structure of files corresponding to content for the web site, and running a conversion program module to convert the file contents into hypermedia for the web site with hyperlinks therein corresponding to the file structure.
  • the hierarchical file structure may include file folders and at least one of the folders may contain a template file defining a predetermined configuration for hypermedia at a node in the web site corresponding to the folder, and the conversion program module produces a web page corresponding to the template for the node.
  • the template may be selected from a library thereof, for example by using the file viewer, to place the selected template in a selected folder.
  • the invention instead of using a bespoke viewer and associated database in an application program overlying the operating system, the invention makes use of the viewer provided with the operating system and a conversion program module converts the file content into corresponding hypermedia. Accordingly, a person with limited knowledge of HTML, and with no knowledge of specialised HTML editors, can produce a web site by establishing a hierarchical file structure using the operating system viewer and the program module automatically converts the files into corresponding, linked web pages.
  • the invention also includes a conversion program module operable to create hypermedia content for a web site, by running on a computer configuration that has an operating system wherein files are selectively configurable in a hierarchical structure and the operating system is provided with a viewer that provides a visual display of the hierarchical structure and an indication of the file content, characterised by the module being operable to convert a hierarchical configuration of files corresponding to content for the web site previously assembled in the operating system using the viewer, into hypermedia for the web site with hyperlinks therein corresponding to the file structure.
  • a conversion program module operable to create hypermedia content for a web site, by running on a computer configuration that has an operating system wherein files are selectively configurable in a hierarchical structure and the operating system is provided with a viewer that provides a visual display of the hierarchical structure and an indication of the file content, characterised by the module being operable to convert a hierarchical configuration of files corresponding to content for the web site previously assembled in the operating system using the viewer, into hypermedia for the web site
  • the invention further includes a library of templates for use in the aforesaid method
  • Figure 1 is a schematic illustration of client and server workstations connected in a network
  • FIG. 2 is a schematic illustration of the software running on workstation PC la of Figure 1;
  • Figure 3 is a schematic illustration of a hierarchical file structure provided by the operating system shown in Figure 2;
  • Figure 4 is a schematic flow diagram of the steps involved in generating hyperme ' dia for a web site on PC la, in accordance with the invention
  • Figure 5 is a screen shot of the hierarchical file structure for the web site when viewed with a file viewer;
  • Figure 6 is a schematic illustration of a node page of the web site and viewed in a browser, together with a corresponding partial view of the file structure when viewed in the file viewer as per Figure 5;
  • Figure 7 is a schematic illustration of the home page of the web site when viewed in the web browser;
  • Figure 8 is a schematic illustration of a file classification process which occurs at a node when producing hypermedia for the web site from the file structure
  • Figure 9 is a schematic illustration of the process carried out to apply a node template to a folder of the file structure
  • Figure 10 illustrates how a text document template is applied to individual files in the folder
  • Figure 11 illustrates how a plugin in the template is processed in order to create a HTML corresponding to the template
  • Figure 12 illustrates how a graphics file is located and inserted
  • Figure 13 illustrates in more detail how a plugin for a document file is processed
  • Figure 14 is a process diagram for link templates
  • Figure 15 is a schematic flow diagram for uploading the hypermedia produced by the conversion program to a specified site in the network.
  • FIG 1 illustrates a conventional network in which a plurality of client workstations in the form of personal computers (PCs) la, lb, lc are connected by means of a network 2 to a server 3 which may also be a PC or a dedicated server, as well known in the art.
  • the network 2 may comprise the world-wide web (WWW) a LAN or a WAN.
  • WWW world-wide web
  • PC la comprises a screen 4 such as a cathode ray tube or plasma display, keyboard 5, mouse 6, a storage device 7, typically a floppy disc drive 7a, a hard disc 7b, a CD or DVD ROM drive 7c, processor 8, RAM 9, ROM 10 and network connections 11 such as a modem or ISDN interface or, if the network is a local network a suitable network card.
  • a common bus 12 as well known in the art.
  • FIG. 2 A schematic illustration of the software running on the PC is shown in Figure 2.
  • BIOS basic input output system
  • An operating system 14 controls operation of the BIOS 13.
  • the operating system includes a file handling system 15 and a graphical user interface (GUI) 16.
  • GUI graphical user interface
  • An example of such an operating system is MicrosoftTM Windows e.g. Windows 98TM .
  • programs and data are arranged in files, which are grouped in directories referred to herein as folders.
  • the file handling system 15 of the operating system 14 allows files to be organised in a hierarchical structure. This structure can be viewed using a file viewer 17 associated with the operating system 14.
  • the file viewer 17 in one example comprises Microsoft Windows Explorer that is supplied with the Windows 98TM operating system.
  • the operating system 14 allows application programs 18 to be run on the computer.
  • the application programs can take a multiplicity of different forms.
  • the application programs may include a wordprocessor such as Microsoft WordTM or programs written by other software suppliers.
  • spreadsheet programs such as Microsoft Excel TM and presentation programs such as Microsoft PowerpointTM can be run as application programs 18.
  • the application programs can also include a web browser such as Microsoft Internet Explorer 5 or Netscape Navigator. As known in the art, these browsers are used to display hypertext media derived from web sites e.g. from web sites at the server 3 shown in Figure 1.
  • a web browser such as Microsoft Internet Explorer 5 or Netscape Navigator.
  • these browsers are used to display hypertext media derived from web sites e.g. from web sites at the server 3 shown in Figure 1.
  • FIG. 3 A schematic illustration of a hierarchical folder and file structure for PC la is shown in Figure 3. At the top of the hierarchical structure is a folder 20 labelled
  • Folder 21 is referenced “My Computer” and contains all of the files held locally on the PC la.
  • Folder 22 includes details of the folders available through the network 2 shown in Figure 1.
  • the next lower level in the hierarchical structure comprises subfolders 23, 24 and 25.
  • the folder 23 comprises files held on a floppy disk when inserted into the floppy disk drive 7a of Figure 1.
  • Folder 24 is a repository for files held on the hard disk 7b shown in Figure 1 and folder 25 is a repository for files available through the CD/DVD ROM drive 7c of Figure 1.
  • the next lower level comprises folders 26, 27 and 28 which respectively contain program files, documents and programs for running Microsoft WindowsTM .
  • Each of the folders 26, 27 and 28 itself contains subfolders and each of the subfolders contains individual files which may comprise programs or documents or other data.
  • Program file folder 26 is shown to have a subfolder 29 which contains files for a web site conversion program module according to the invention, and an associated template library as explained in more detail hereinafter.
  • FIG. 3 This general, hierarchical structure of folders is well known in the art and the configuration shown in Figure 3 comprises a typical example of the format used in Microsoft WindowsTM .
  • the usual file viewer 17 of Figure 2 enables a display such as shown in Figure 3 to be produced of the folders and file structure.
  • file viewers such as Microsoft WindowsTM Explorer allow file management to be achieved, by permitting files to be dragged and dropped into the folders shown in Figure 3.
  • the file viewer also allows folders to be opened and named, and provided with subfolders according to a desired hierarchical structure, as well known in the art.
  • the file viewer 17 is used to establish an hierarchical file structure corresponding to web pages for a web site such that the file content can be converted into hypermedia for the web site with hyperlinks corresponding to the file structure.
  • An overview of the web creation process is given in Figure 4.
  • the hierarchical file structure is set up using the viewer 17.
  • a conversion program module is run, which converts the file structure established in step SI into hypermedia, with web pages corresponding to the files of the file structure and links between them corresponding to the hierarchy of the file structure.
  • the hypermedia produced by step S2 is uploaded to a server to provide a web site.
  • the hypermedia is uploaded to server 3 shown in Figure 1 although it will be appreciated that the web site can be established at any convenient server location including PC la itself. Once uploaded, the web site can be viewed using a web browser as previously described.
  • FIG. 5 the file structure for the Lemon Catering web site is set up using the file viewer 17, in this example Microsoft WindowsTM Explorer.
  • the Windows Explorer viewer 17 includes a left hand window 30 that shows the hierarchical folder structure, and a right hand window 31 that shows the individual files included within a particular folder.
  • the hierarchical folder structure for the "Lemon catering” web site comprises a root folder 33 named “Lemon Source” with the following sub-folders on the next lower level of the hierarchy: “About Us” 34, “Contacts” 35, “Products” 36 and “Services” 37.
  • the folder “Products” 36 has associated sub-folders “Meals” 38 and “Snacks” 39.
  • the folder “Meals” 38 has associated sub-folders "Breakfast” 40, "Evening Meal” 41 and "Lunch” 42.
  • Each folder constitutes a node in the web site and as will be explained in detail hereinafter, gives rise to an HTML web page corresponding to the node, with links to other ones (HTML web pages) of the nodes corresponding to the file hierarchy.
  • the top level folder referred to herein as the 'root' folder "Lemon Source" 33 corresponds to the Home Page of the web site, and has hyperlinks to node pages corresponding to folders 35 - 39, which in turn have hyperlinks to node pages corresponding to the sub-folders according to the hierarchy shown in Figure 5.
  • One or more of the folders may contain text files which each provide an HTML web page that has a hyperlink to the node page corresponding to the folder containing the text file.
  • the folder "Meals" 38 in Figure 5 is shown open and its contents are shown in the right hand window 31.
  • the folder contents include a word processor text file 43 "Booking Form for all Menus.doc, and text files 44, 45 and 46 corresponding to the text of individual menus.
  • the folder 38 also includes a text file 47 referred to as a comment file with a file suffix ".cmt" with text for inclusion on the node page, and a graphics file 48 for inclusion on the node page, as will be explained later.
  • Figure 6 is a view of the node web page 49 that is produced from the "Meals" folder 38 when viewed with a web browser.
  • Microsoft Internet ExplorerTM web browser is utilised although others may be used such as the
  • Netscape NavigatorTM As will be explained in more detail hereinafter, an HTML template is applied to the contents of folder 38 so as to produce a corresponding node web page.
  • the browser has a viewing window 50 which displays the web page corresponding to folder 38.
  • the web page 49 includes hyperlinks hi corresponding to the hierarchical folder structure.
  • the folder 38 contains files 43-46 ( Figure 5) and, in the node web page 49 of Figure 6, hyperlinks b/43-b/46 are provided to web pages corresponding to the document files 43-46.
  • the hyperlinks b/43-b/46 can be considered as document links.
  • the web page 49 also includes hyperlinks which permit the user to move through the hierarchical folder structure.
  • Hyperlink hi 33 labelled "Home” provides access to the Home Page of the web site, which in this example corresponds to root folder 33 "Lemon Source” shown in the window 30 of the file viewer 17.
  • the web page 49 further includes hyperlink b/36 labelled "Back" which provides access to the web page corresponding to the next node up in the hierarchical file structure, corresponding to the "Products" folder 36 shown in Figure 5.
  • the "Products" folder 36 can be considered as a parent for the "Meals” folder 38 and so the hyperlink b/36 can be considered as a parent link.
  • the "Meals" folder 38 is at one level up in the hierarchical folder structure from the folders 40, 41 and 42, entitled “Breakfast”, “Evening Meal” and “Lunch” . These folders can be considered in terms of the hierarchy as children in relation to the "Meals" folder 38.
  • hyperlinks b/40, b/41 and b/42 are provided to web pages corresponding to the folders 41, 42 and 43 and can be considered as child links.
  • a hyperlink b/51 which enables the user to e-mail comments in respect of the web page, is provided.
  • the operation of this hyperlink is conventional and will not be described further herein.
  • the user can navigate through the hierarchical structure of the web site by using the links displayed on each web page, the links being set up in accordance with the hierarchical file structure established using the file viewer 17 associated with the operating system which, in this example, comprises Microsoft Windows Explorer.
  • the "look and feel" of the web pages that make up the web site is determined by template files placed in the file structure.
  • the template files are designed to provide a quick and easy way of applying a uniform look to pages of the web site and template files may be provided in a library so that the user can select a particular
  • the web site is arranged with the links corresponding to the hierarchical structure of the files, but the look of the pages corresponds to the templates placed in the file structure.
  • the content of the pages is thus separate from the look of the pages, and the links are also separate, being derived from the file structure.
  • the folders in the hierarchical file structure can be considered as nodes and a template is provided to give each node a particular layout and appearance. Furthermore, a template is provided for document files so that these can be given an individual, common appearance different from the node.
  • the template files comprise a template for the Home Page of the web site, a node template that can be used for each folder shown in the window 30 of Figure 5 and a document template for individual document files corresponding to files 43-46 in window 31 of Figure 5.
  • the template files are pre-written in HTML and make use of plugins, as will be described in detail later.
  • the user can choose a particular template file configuration from the library and the template files are dragged and dropped using viewer 17 into the Home Page folder namely "Lemon Source” folder 33 shown in Figure 5.
  • the template files have a suffix " .tpl" and an example of
  • an image file Logo.gif is included.
  • the convention adopted is that the file contains a non-meaningful object and that the templates are configured so that the user can replace the files by bespoke files, for example a company logo or other image information pertinent to the web site concerned.
  • the user has replaced the original non-meaningful Logo.gif file by a bespoke lemon logo image file.
  • HTML corresponding to a template node.tpl which is applied to the node pages, is as follows:
  • the look and feel of a web page produced using the document template document.tpl is consistent with that of the Home page and node pages produced by the templates lemon.tpl and node.tpl.
  • the aforementioned three template files are provided in the root "Lemon Source” folder 33 and act to provide a default look for the entire web site but can be selectively overridden by the user if it is desired to give web pages corresponding to individual nodes or files a different appearance. If a further template is placed in one of the folders, then the further template will then be used to provide the default look for that folder and folders or documents below it in the file structure. This can be achieved, for example for a node, by including an individual node template in the corresponding folder, which will override the hierarchy provided by the node template in the Home Page "Lemon Source” folder 33.
  • templates from the template library in folder 29 - provide a quick and easy way of applying a common style to a web site, with the template being selected by the user from the library and dragged and dropped into the root folder of the web site - folder 33 in this example.
  • more sophisticated users can adapt and modify individual parts of the web site as desired e.g. by placing different template files in individual folders of the file structure.
  • the template may be individually written in HTML, selected by the user from a library, or downloaded from a remote server, depending on the skill level of the user. Conversion program module
  • the conversion program module which converts the various files and folders shown in window 30 into hypermedia, resides in program subf older 29 shown in Figure 3.
  • the program module includes a conventional tree creeper which moves hierarchically downwardly through the file structure, folder by folder, converting the folder contents into corresponding hypermedia, making use of the previously described templates.
  • An example of a suitable tree creeper is given in computer programming algorithm literature, for example: [http://www.cs.hope.edu/ ⁇ alganim/ccaa/tree.html] .
  • Other examples of searching routines which can be used for this purpose are described in "Handbook of
  • step S2.1 all the files of the folder are identified and at step S2.2, classified according to their file suffixes.
  • Files with the " .tpl" suffix are identified as templates for use in producing the individual web pages. These are shown schematically as block 51.
  • Files which are to be uploaded without conversion to the web site are identified as block 52.
  • files which are in the Microsoft Powerpoint format or other application software files such as spreadsheets can be loaded to the web site for use as subsequent downloads by users running local copies of the application program rather than browsing by means of a web browser.
  • Text files with the .txt, .htm or .doc suffix are identified in block 53.
  • HTML for the node web page is produced using an aforementioned node template.
  • the node template can be placed in the relevant folder by the user in order to achieve a particular look for the node concerned.
  • the node template for the next highest level is used, which can be considered as an "inheritance" of the template, and, if there is no template specified for the next higher level, the routine moves up the file structure so that if necessary, the node template held in the Home Page "Lemon Source” file 33 ( Figure 6) is used.
  • a search for the node template file in the node concerned is carried out and, if it does not exist, at step S2.4 the search is carried out at a higher level in the file structure and the process is repeated if necessary at higher levels until a suitable node template is found.
  • the node template is found, it is then used to create HTML as shown at step S2.5.
  • the HTML comprises in effect the menu page associated with the node or folder, of the type shown and described in relation to Figure 6, with a set of hyperlinks to child topics, its parent node and the Home Page, as specified by the template.
  • Figure 10 illustrates the process carried out to convert document text files (block 53 of Figure 8) into corresponding HTML for inclusion as web pages in the web site.
  • step S2.6 an individual file is reviewed from the list of files obtained at S2.1 ( Figure 8).
  • step S2.7 the file is reviewed to determine whether it is a text document i.e. with a suffix .txt. If not, the next file is obtained at step S2.6.
  • a corresponding document template is sought at step S2.8.
  • document templates document.tpl can be placed in a particular node (folder).
  • the process goes back up one level of the hierarchical file structure at step S2.10 to seek a corresponding document template and the process is repeated until an appropriate template is found.
  • This provides a default template at a higher level in the file structure, which can be selectively overridden by the user in the event that a particular template is required at a particular node, or for a particular document.
  • the overriding is achieved by the user placing a bespoke document template in the folder containing the document concerned.
  • the corresponding HTML is then created using the template, ' at step S2.9.
  • the creation of HTML is achieved by applying HTML tags from the template document to the text of the file obtained at step S2.6. Thus, the text is marked up so as to take up the attributes prescribed by the HTML tags.
  • corresponding routines for different text file types can be used.
  • a corresponding routine can be run for text documents produced in Microsoft WordTM with step S2.7 checking to see if the documents have a file suffix .doc signifying a Word text file.
  • Plugins can be used in the HTML of each of the different types of templates in order to insert particular information into the corresponding web page.
  • the plugins are identified in the HTML code by ⁇ xxx ⁇ .
  • the instruction given within the exclamation marks causes data to be fetched and inserted in the relevant place in the web page produced by the template. Examples of plugins are set out in Table 1 below and examples of the use of such plugins is given hereinbefore in the HTML snippets corresponding to the templates lemon. tpl, node.tpl and document.tpl.
  • FIG. 11 A process for creating HTML from a template containing plugins is illustrated in Figure 11.
  • a template is being parsed at step S2.ll and found to contain a plugin, at step S2.12, then the entire reference to the plugin is replaced, including the exclamation marks, by new HTML that corresponds to the function defined by the plugin, at step S2.13, according to the rules set out in Table 1.
  • step S2.14 A process for handling graphical file references will now be described with - reference to Figure 12.
  • the template contains graphic file references, i.e. references to files with the suffix .gif or the like
  • a search is carried out for them at step S2.14.
  • the search is initially carried out in the current folder and if not located, the search moves up one level in the hierarchical folder structure. This search process is repeatedly carried out at higher levels until the corresponding file is found, as illustrated by step S2.15.
  • step S2.16 the graphic is inserted, into the web page.
  • the HTML template lemon. tpl given above includes reference to "Logo.gif" .
  • the plugin ⁇ Documentlmage ⁇ can be used to import a graphical file into HTML produced by a template. When used in a within a node template, this plugin will insert a reference to an image which has the same name as the current folder.
  • the plugin ⁇ Documentlmage ⁇ is used in the template node.tpl with the result that the file "meals.gif" 48 which has the same name as the folder Meals 36 produces a corresponding image 48 in the displayed web page 49 shown in Figure 6.
  • the plugin ⁇ Documentlmagel! will insert a reference to an image which has the same name as the current document.
  • step S2.9.1 where a document template is located that contains the plugin UDocumentFile(parameterlist)!, a corresponding document text file is fetched at step S2.9.2.
  • the document is checked at step S2.9.3 to see whether it contains HTML tags already. If so, the file is inserted together with its HTML tags in its entirety in the location of the plugin in the template, at step S2.9.4. However, if the document file contains text which has not already been marked up e.g. a .txt file, suitable HTML paragraph formatting is inserted at step S2.9.5.
  • some plugins are capable of creating the HTML representing a list of items such as hyperlinks to documents (in the case of UDocumentLinks(parameterlist)U).
  • the parameter ⁇ link> is used in a number of the plugins.
  • This enables hyperlinks to be set up between the web pages according to the hierarchical file structure, by using appropriate plugins as per Table 1 in the aforementioned templates.
  • the plugins HHomelink!, ⁇ CousinLinks ⁇ , ⁇ Parentlink ⁇ and ⁇ Childlinks ⁇ as shown in Table 1 can be used for example as shown in the HTML for the templates lemon. tpl and node.tpl described above to provide corresponding hyperlinks between pages of the web site in accordance with the hierarchical file and folder structure.
  • fragments of HTML referred to herein as "link templates" can be used to extensibly format the specific information provided by the plugins.
  • a plugin which defines a hyperlink such as the plugin !!Childlinks ⁇ link> ⁇ dir> ⁇ shown in Table 1
  • the link parameter ⁇ Erik > allows particular text or and/or an image to be associated with the link as displayed in the resulting web page.
  • the link templates are stored as files containing HTML fragments, with the suffix .lpl and contain instructions that insert the specific information within the fragment, which is then inserted in the web page by the plugin.
  • Table 1 shows that the link parameter can be in a number of standard forms - the link template allows further flexibility, as described above.
  • Figure 14 illustrates how the link templates are used to generate HTML.
  • the link parameter is checked at step S2.17 to determine whether it is in one of the standard forms specified in Table 1. If so, HTML corresponding to the link is formatted according to the standard formats listed in Table 1, e.g. plain, image, table or table with images. This is shown at step S2.18.
  • the corresponding HTML code is outputted at step S2.19.
  • a search is made in the corresponding folder of the hierarchical file structure for the link template at step S2.20. If the link template is not found, the search is carried out at the next level up in the hierarchical folder structure at step S2.21 and the process is repeated at successive higher levels of the structure until the relevant link template is found.
  • step S2.22 the link template is examined to determine the specified URL text and image to be associated therewith.
  • step S2.23 the specific information such as URL, image and appropriate text are inserted into the link template, which in turn is inserted into the relevant plugin so as to produce HTML code as shown at step S2.24.
  • the templates may include a plugin entitled ⁇ Comment ⁇ which is used to insert text into the web pages.
  • the plugin is used to incorporate text from files with a suffix .cmt.
  • the plugin has a different effect for node templates and document templates.
  • the plugin inserts the contents of all files with the suffix .cmt which do not have the same names as document files in the relevant folder.
  • the open "Meals" folder 38 includes a comment file entitled Meals. cmt 47. The name of this file is thus different from the names of the other text files in the folder, namely files 43 - 46.
  • the plugin ⁇ Comment ⁇ in the template file node.tpl given above is operative to take the text from the file Meals. cmt and insert it at a predetermined location in the HTML corresponding to the node page for the folder Meals 38. This is shown in Figure 6 and the text from the file Meals. cmt 47 is shown at location 47 in Figure 6.
  • the plugin ⁇ Comment!! is used in a different way in document templates.
  • the plugin When used in a document template, the plugin will insert the contents of a single .cmt file with the same name as the document. This enables comment files to add text to a document in a web page corresponding to the document file.
  • Running conversion program - step S2 Figure 15 shows the process of running the conversion program in more detail.
  • the source folder for the hierarchical folder structure is specified.
  • the source folder comprises root folder 33 "Lemon Source” shown in Figure 5.
  • the destination folder for the web site is specified. As previously explained, this can be at any suitable location either on the same computer or at a different location in the network. For example, the destination may be a folder at the server 3 shown in Figure 1.
  • the user has the option of producing a local preview of the web site or uploading HTML for the web site to the specified server.
  • the local preview option allows the user to check the web site before recompiling it for uploading to the specified server.
  • step S2.28 the system checks to see which option was selected. If the local preview option is selected, the conversion program module is run at S.2.29 and HTML web pages and other associated hypermedia are produced corresponding to the hierarchical folder structure of Figure 5, as previously described, with the hyperlinks pointing to a predetermined local destination folder on the computer that allows a local preview with a web browser. If the user is not satisfied with the web pages, the configuration of the folder structure can readily be amended with the viewer 17 and the preview process repeated until the desired result is achieved.
  • the hypermedia can be produced in a form that is suitable for uploading to the destination folder of the server.
  • the option to upload to the server is then selected at S2.27, so that at step S2.30, the conversion program is run and the resulting HTML web pages and other associated hypermedia are produced corresponding to the hierarchical folder structure of Figure 5, with the hyperlinks pointing to the destination folder specified at step S2.26.
  • the hypermedia is then uploaded to the server at step S3.1.
  • the file viewer 17 can be re-opened and the files or their links can be easily edited. It will be appreciated that the hierarchy of the files can easily be changed using the standard editing functions provided with the file viewer 17. When the user is satisfied with the amendments made, the process of Figure 15 can be run again so that the changes can quickly and easily be incorporated into the HTML code for the web site.
  • the resulting web pages include hyperlinks, graphics and other information according to the files and templates included in the folder structure of Figure 5.
  • Some may contain spreadsheet and presentation files as may be created by Microsoft Excel and Powerpoint. These files need not necessarily be converted into HTML but may be uploaded in a link-only format so that the user can access them by way of downloading the relevant files to a locally held copy of the application program so that the presentation program files or spreadsheets can be run locally as a download.
  • the majority of web pages can be displayed using a conventional web browser 50 in the manner previously described.
  • the file viewer comprises Microsoft Windows Explorer
  • many different versions of file viewer could be used.
  • File Manager may be used.
  • the programs are handled in later versions of DOS, the well known DOSSHELL file viewer can be used.
  • operating systems other than Windows have their own proprietary file viewer systems, which can be similarly used in accordance with the invention.
  • the conversion program module can be supplied to users on conventional storage media such as a floppy disc or CD ROM and also can be provided to customers as a download from a server e.g. through the Internet.
  • the invention is not restricted to wired network systems but can be used also with wireless, mobile networks, and run on mobile telephones and other mobile web hardware.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Health & Medical Sciences (AREA)
  • Computational Linguistics (AREA)
  • General Health & Medical Sciences (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Artificial Intelligence (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)
  • Document Processing Apparatus (AREA)

Abstract

L'invention concerne un procédé permettant de créer un contenu hypermédia pour un site Web à l'aide d'une configuration machine telle qu'un ordinateur personnel (PC1a) qui comprend un système (14) d'exploitation dans lequel les fichiers peuvent être configurés selon une structure hiérarchique. Le système d'exploitation comporte en outre une fonction aperçu (17) qui permet de visualiser la structure hiérarchique ainsi qu'une indication du contenu du fichier. On utilise cette fonction aperçu (17) du système d'exploitation (étape S1) pour établir une structure hiérarchique des fichiers (Fig. 5) correspondant au contenu du site Web, puis on lance un module (29) de programme de conversion (étape S2) afin de convertir les contenus des fichiers en hypermédia pour le site Web, les hyperliens du contenu hypermédia correspondant à la structure des fichiers. Après une prévisualisation locale du contenu hypermédia à l'aide d'un explorateur (50) le contenu est téléchargé (étape S3) vers un serveur afin de créer le site Web.
EP00903859A 1999-02-17 2000-02-16 Creation d'un contenu hypermedia pour site web Withdrawn EP1155373A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP00903859A EP1155373A1 (fr) 1999-02-17 2000-02-16 Creation d'un contenu hypermedia pour site web

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
GBGB9903641.0A GB9903641D0 (en) 1999-02-17 1999-02-17 Document management method and tool
GB9903641 1999-02-17
EP99304800 1999-06-18
EP99304800 1999-06-18
PCT/GB2000/000548 WO2000049520A1 (fr) 1999-02-17 2000-02-16 Creation d'un contenu hypermedia pour site web
EP00903859A EP1155373A1 (fr) 1999-02-17 2000-02-16 Creation d'un contenu hypermedia pour site web

Publications (1)

Publication Number Publication Date
EP1155373A1 true EP1155373A1 (fr) 2001-11-21

Family

ID=26153502

Family Applications (2)

Application Number Title Priority Date Filing Date
EP00903863A Ceased EP1161730A1 (fr) 1999-02-17 2000-02-16 Procede et gestion de documents
EP00903859A Withdrawn EP1155373A1 (fr) 1999-02-17 2000-02-16 Creation d'un contenu hypermedia pour site web

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP00903863A Ceased EP1161730A1 (fr) 1999-02-17 2000-02-16 Procede et gestion de documents

Country Status (6)

Country Link
EP (2) EP1161730A1 (fr)
JP (2) JP2002537603A (fr)
AU (2) AU771925B2 (fr)
CA (2) CA2363006C (fr)
HK (1) HK1043841A1 (fr)
WO (2) WO2000049519A1 (fr)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU8668001A (en) 2000-08-21 2002-03-04 Intellocity Usa Inc System and method for television enhancement
US6760043B2 (en) * 2000-08-21 2004-07-06 Intellocity Usa, Inc. System and method for web based enhanced interactive television content page layout
KR20020034672A (ko) * 2000-11-03 2002-05-09 김상수 홈페이지 관리 장치 및 방법
SE0100191L (sv) * 2001-01-24 2002-07-25 Ericsson Telefon Ab L M En anordning och ett förfarande relaterande till access av applikationer/tjänster
SE0100190L (sv) * 2001-01-24 2002-07-25 Ericsson Telefon Ab L M En anordning och ett förfarande för presentationskundanpassning i en portalstruktur.
DE10125110A1 (de) * 2001-05-23 2002-12-12 Building Systems Ges Fuer Syst Datenverarbeitungseinrichtung
US6910049B2 (en) * 2001-06-15 2005-06-21 Sony Corporation System and process of managing media content
AU2002950134A0 (en) * 2002-07-11 2002-09-12 Youramigo Pty Ltd A link generation system
EP1671240A1 (fr) * 2003-09-18 2006-06-21 80-20 Software Pty. Limited Logiciel de dossier intelligent
JP4438542B2 (ja) * 2004-07-12 2010-03-24 ブラザー工業株式会社 レイアウト編集装置、レイアウト編集プログラム、及びレイアウト編集プログラムを記録したコンピュータ読み取り可能な記録媒体
US8554599B2 (en) 2005-03-25 2013-10-08 Microsoft Corporation Work item rules for a work item tracking system
US10733223B2 (en) 2008-01-08 2020-08-04 International Business Machines Corporation Term-driven records file plan and thesaurus design
CN101911004B (zh) * 2008-01-09 2013-10-30 惠普开发有限公司 提供均匀观感的bios图形引擎
US9699503B2 (en) 2010-09-07 2017-07-04 Opentv, Inc. Smart playlist
US10210160B2 (en) 2010-09-07 2019-02-19 Opentv, Inc. Collecting data from different sources
US8949871B2 (en) 2010-09-08 2015-02-03 Opentv, Inc. Smart media selection based on viewer user presence
EA201591779A1 (ru) * 2013-03-14 2016-03-31 Викс.Ком Лтд. Система и способ персонализации диалогов
JP7464351B2 (ja) * 2014-08-27 2024-04-09 マシューズ インターナショナル コーポレイション メディア生成システムおよびそのシステムを実行する方法
JP7106177B1 (ja) * 2021-05-12 2022-07-26 弁理士法人Ipx 情報処理システム、情報処理方法及びプログラム

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5313394A (en) * 1990-12-11 1994-05-17 Barbara Clapp Document assembly customization system for modifying a source instrument including text and decisional commands
US5384911A (en) * 1992-12-23 1995-01-24 International Business Machines Corporation Method of transferring programs from action oriented GUI paradigm to object oriented GUI paradigm
JP4138011B2 (ja) * 1996-09-09 2008-08-20 マイクロソフト コーポレーション 媒体でデザインするためのコンテンツの自動的なレイアウトおよび書式設定
US5956736A (en) * 1996-09-27 1999-09-21 Apple Computer, Inc. Object-oriented editor for creating world wide web documents
US6239802B1 (en) * 1997-09-15 2001-05-29 International Business Machines Corporation File menu option for making file templates from pre-existing files
JPH11144027A (ja) * 1997-11-04 1999-05-28 Canon Inc ファイル管理システム、方法および記録媒体

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0049520A1 *

Also Published As

Publication number Publication date
AU771925B2 (en) 2004-04-08
CA2363135A1 (fr) 2000-08-24
EP1161730A1 (fr) 2001-12-12
JP2002537603A (ja) 2002-11-05
WO2000049520A1 (fr) 2000-08-24
AU2561600A (en) 2000-09-04
JP2002537602A (ja) 2002-11-05
CA2363006C (fr) 2008-01-29
AU777775B2 (en) 2004-10-28
CA2363006A1 (fr) 2000-08-24
AU2561300A (en) 2000-09-04
WO2000049519A1 (fr) 2000-08-24
JP4481507B2 (ja) 2010-06-16
HK1043841A1 (zh) 2002-09-27

Similar Documents

Publication Publication Date Title
CA2405995C (fr) Changement du contenu hypermedia d'un site web
AU777775B2 (en) Creating hypermedia content for a web site
US10254925B2 (en) GUI document management system
US20180293307A1 (en) User driven computerized selection, categorization, and layout of live content components
EP1218843B1 (fr) Procede et systeme pour publier et reviser des ensembles hierarchiquement organises de pages web intranet et internet statiques
US7392466B2 (en) Method and system of annotation for electronic documents
US20100251143A1 (en) Method, system and computer program for creating and editing a website
US7958445B1 (en) System and method for storing data associated with a file
US8387055B1 (en) System and method for providing information and associating information
US20050166141A1 (en) Method and apparatus for providing a graphical user interface for creating and editing a mapping of a first structural description to a second structural description
US20050028081A1 (en) System and method for facilitating the design of a website
Nadkarni et al. WebEAV: automatic metadata-driven generation of web interfaces to entity-attribute-value databases
US20040117732A1 (en) Method of and apparatus for creating a computer document
EP1816586A1 (fr) Système de traitement de données, méthode de traitement de données et serveur de gestion
US20090021767A1 (en) Document processing device
US20060069986A1 (en) Technical specification editor
US7827195B2 (en) Document management device and document management method
EP1821220A1 (fr) Dispositif de traitement de donnees, dispositif de traitement d'un document, et procede de traitement de document
KR100261265B1 (ko) 웹 문서 저작을 위한 장치 및 그 운용 방법
US20050039122A1 (en) Methodology and system for rendering dynamic images
WO2005098666A1 (fr) Traitement de donnees et documents utilisant un langage de balisage
US20040267550A1 (en) Automated method for authoring and delivering product catalogs
Peel HTML Macros--Easing the Construction and Maintenance of Web Texts
Morete et al. Creating Digital Libraries Based on CDS/ISIS Databases
Wusteman et al. Electronic Journals Using Guide

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20010820

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

17Q First examination report despatched

Effective date: 20031209

REG Reference to a national code

Ref country code: HK

Ref legal event code: WD

Ref document number: 1043841

Country of ref document: HK

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20080902