WO2000049519A1 - Procede et gestion de documents - Google Patents

Procede et gestion de documents Download PDF

Info

Publication number
WO2000049519A1
WO2000049519A1 PCT/GB2000/000552 GB0000552W WO0049519A1 WO 2000049519 A1 WO2000049519 A1 WO 2000049519A1 GB 0000552 W GB0000552 W GB 0000552W WO 0049519 A1 WO0049519 A1 WO 0049519A1
Authority
WO
WIPO (PCT)
Prior art keywords
directory
file
template
stored
content
Prior art date
Application number
PCT/GB2000/000552
Other languages
English (en)
Inventor
Mark Bagley
Rachel Berry
Original Assignee
British Telecommunications Public Limited Company
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 Public Limited Company filed Critical British Telecommunications Public Limited Company
Priority to JP2000600193A priority Critical patent/JP4481507B2/ja
Priority to EP00903863A priority patent/EP1161730A1/fr
Priority to CA002363006A priority patent/CA2363006C/fr
Priority to AU25616/00A priority patent/AU771925B2/en
Publication of WO2000049519A1 publication Critical patent/WO2000049519A1/fr

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

  • the present invention relates to a method of management of documents stored in a computer file system.
  • the present invention also relates to a tool for the management of documents stored in a computer file system.
  • 'template' It has often proved desirable to control the appearance of a document through the use of a so-called 'template' .
  • a template At the time of creation of a document a template will be chosen and the content of the document, for example text, will then be created within that template.
  • a default template might be provided by the word processing system. If however, in accordance with the preferences or needs of the user, a different template is desired then this will have to be manually chosen. In either case the template features will be specified by instructions within the document to which they are intended to apply and hence will be inextricably linked with the document itself.
  • one problem facing the user of a word processing system is that, if another template is subsequently desired to be applied, then a new document will have to be opened with the new template and then the content from the old document will have to be copied and pasted into the new document. Moreover, if such a change were required for a batch of documents then each document would have to be changed individually.
  • a related problem facing the manager of a computer file system implementing a collaborative document store is that each of the collaborating authors may have a different word processing system or a different personal preference for the style of documents. In this way, different documents offered for storage may have different appearances, in which case the collaborative document store will lack a consistent 'look and feel' . To implement such a consistent 'look and feel' would, as indicated above, require the manual application of the desired template or templates to each document.
  • HTML HyperText Markup Language
  • XML extensible Markup Language
  • CSS CSS provide a degree of so-called 'inheritance' of style features to allow for such features to 'cascade' through related documents.
  • style features are specified or called by instructions within the document to which they are intended to apply and hence again, they are inextricably linked with the document itself.
  • each content file being stored in a directory of the computer file system
  • each template file being effective, when applied to a content file, to carry out a respective pre-determined operation on the content file;
  • template files are associated not with particular content files as in the prior art, but with the directory in which the content file is stored. Consequently the template chosen to be applied to a given content file may be selected by associating the chosen template with the directory in which the content file is stored or by moving the content file into a directory with which that chosen template is associated. Should a different template be desired to be applied then, instead of the manual re-editing of the 'templated' file produced by the method which would be necessitated by the prior art, quite simply either the different template is associated with the directory in which the content file is stored, or the content file is moved to a different directory with which the new template is associated, and in either case the method is re-executed.
  • the computer file system is divided into a hierarchical arrangement of directories and the one or more templates associated with each directory located in the direct hierarchical path from a directory in which a content file is stored up to and including the uppermost directory in the hierarchical arrangement are also associated with the directory in which the content file is stored.
  • this will allow the hierarchical application of one or more templates to a given content file in such a way as to allow a cascade of template styles.
  • a consistent 'look and feel' can be brought to the presentation of the content files stored in the hierarchical file system.
  • the templates applied to a content file to achieve this advantage are so applied simply by virtue of their association with the directory in which the content file is stored. Changes in the cascading style can be effected, not through laborious manual re-editing of each and every content file, but quite simply through, either the introduction of the association of the desired template or templates into a given path of the hierarchy or the movement of desired files into a directory in an appropriate path of the hierarchy.
  • association of a template with a directory is made on the basis of the template file being stored in that directory.
  • the method further comprises:
  • this will permit the templates to carry out a wide variety of file management operations on the content files in accordance with the metadata information about the content files.
  • One simple example might relate to the elapsed time (an item of metadata) since the content file was stored in the directory; a template might be effective, when applied, to cause a content file to be archived if the metadata indicated that more than a pre-determined amount of time had elapsed since the content file was stored in the directory.
  • FIG. 1 illustrates a general purpose computer system
  • Figure 2 illustrates a first source file structure and associated content and template files stored therein
  • Figure 3 illustrates a first process flowchart for use with respect to the first source file structure and associated content and template files stored therein;
  • Figure 4 illustrates a second source file structure and a separate directory and associated content and template files stored therein;
  • Figure 5 illustrates a second process flowchart for use with respect to the second source file structure and separate directory and associated content and template files stored therein;
  • Figure 6 illustrates a third process flowchart for setting up a third source file structure with a separate directory and storing associated content and template files therein;
  • Figure 7 illustrates the third source file structure and separate directory with associated content and template files stored therein set up in accordance with the preceding process flowchart
  • Figure 8 illustrates a target file structure generated from the source file structure and associated content and template files as illustrated in Figure 7.
  • Figure 1 illustrates a conventional general purpose computer 100.
  • a computer 100 will typically have at least a central processing unit (CPU) (not shown), read-only memory (ROM) (not shown), random-access memory (RAM) (not shown), a storage device such as a hard disk (not shown), a device for reading from and writing to storage media such as a floppy disk drive 102 for reading from and writing to a floppy disk 104, input devices such as keyboard 106 and a mouse 108, a display device such as a monitor 1 10 and input and output ports (not shown) for connection to other devices or communications networks.
  • the computer 100 is illustrated as connected to a communications network 1 1 2 which in turn allows communication with other computers 1 14, 1 1 6, 1 18 similarly connected.
  • the computer 100 may utilise any suitable operating system, a well known example being Microsoft WindowsTM .
  • Application programs may be written in any suitable language. Such an operating system and application programs may be loaded onto the storage device (not shown) of the computer 100.
  • An application may, for example, be written in JavaTM in which case it is required that a Java Virtual Machine be present on the computer 1 00. As will be well known the Java Virtual Machine is available for downloading from the Sun CorporationTM Website ( http://www.sun.com ) .
  • suitable languages in which to write application programs one example of which is C + + .
  • the tool disclosed in accordance with the first embodiment of the invention may be implemented as a software application program to be executed by the computer 100.
  • the tool implemented as such a software application program may then be stored in any suitable computer readable storage media form, for example on floppy disk 104, for loading into the computer 100, via the floppy disk drive 1 02, for execution.
  • a well known alternative would be to store the software application on a CD-ROM (not shown) for loading into the computer 100 via a CD-ROM drive (not shown) for execution.
  • a further well known alternative would be to download the software application program over the network 1 1 2, for execution by the computer 100.
  • a two-tier hierarchical file structure 200 is indicated, with a first-tier root directory 202 and first, second and third second-tier sub-directories 204,206,208.
  • a first text document 21 0 has been stored in the first- tier root directory 202 and second, third and fourth text documents 21 2,214,21 6 have been stored in the first, second and third second-tier sub-directories 204,206,208 respectively.
  • a first template file 21 8 has been stored in the first-tier root directory 202.
  • a second template file 220 has been stored in the first second-tier sub-directory 204.
  • the tool When invoked, the tool will first perform a conventional 'tree traversing' procedure on the hierarchical file structure 200, in a top down fashion. 'Tree traversing' is also known as 'tree creeping' or 'tree crawling'.
  • 'Tree traversing' is also known as 'tree creeping' or 'tree crawling'.
  • the branching form of the file structure 200 in terms of the root directory 202 and the sub-directories 204,206,208 will be detected and stored by the tool.
  • the description of the branching form stored by the tool may include information as to the name of a given directory, the relationship and name of the parent directory of the given directory, the relationships and names of any subdirectories of the given directory, the relationships and names of any other directories which share the same parent directory as the given directory and so on.
  • Step 300 provides for the selection of one particular content file stored in a given sub-directory.
  • Step 302 provides that the tool will first search the sub-directory in which the content file is itself located for a template file. If such a template file is found then according to step 304 the tool will apply that template to the content file and the process for that particular content file will terminate.
  • a template to a content file
  • the template is, in effect, associated with the (sub) directory in which the content file is located rather than just with the content file itself as in the prior art.
  • the new file may of course be stored anywhere but, by way of example, newly 'templated' files 222,224,226,228 are indicated in Figure 2 (in dashed lines) as being stored in the same (sub) directory as the content file upon which the templated file is based.
  • step 306 the tool will next consider the parent (sub) directory of the sub-directory in which the content file is located, in accordance with step 308. Should such a template still not be found upon repeat of step 302 then, in accordance with further repetition of steps 306, 308 and 302, the tool will continue the search up the hierarchical structure until a template is found. That template would then be applied. If no template is found in the root directory then the process for that particular content file will terminate. It will be appreciated that the process flowchart depicted in Figure 3 indicates an exclusive application of a template. Once a single template has been found, that template is applied.
  • templates may be applied in conjunction with one another, either complementing one another or overriding one another to the extent provided for.
  • bottom-up tree traversing would traverse the tree all the way from the lowest sub-directory under consideration up to the root directory to determine the location of all relevant template files such that the appropriate application of all the relevant templates could be performed.
  • the templates are 'inherited' down the hierarchy form parent directory to child directory, providing a 'cascading' of template style.
  • the first template 21 8 would be applied to the first, third and fourth text documents 21 0,214,21 6. Both, however, the first template 21 8 and the second template 220 would be applied to the second text document 21 2.
  • the first template 21 8 might define a general meetings template, suitable for use with the documents in the first-tier root directory 202 and the second and third second-tier root directories 206,208
  • the second template 220 might define a template for particular meetings, for example board meetings, which require, for example, that the general meetings template be complemented or overridden to the extent provided for by the board meetings template.
  • the tool disclosed in accordance with the second 5 embodiment of the invention may again be implemented as a software application program to be executed by the computer 100.
  • the tool implemented as such a software application program may then be stored in any suitable computer readable storage media form, for example on floppy disk 104 or on a CD-ROM (not shown), for loading into a computer 100 for execution.
  • a well known alternative would be 1 0 to download the software application program over the network 1 1 2, for execution by the computer 1 00.
  • a two-tier hierarchical file structure 400 is indicated, with a first-tier root directory 402 and first, second and third second-tier sub-directories 1 5 404,406,408.
  • a first text document 410 has been placed in the first-tier root directory 402 and second, third and fourth text documents 41 2,414,41 6 have been placed in the first, second and third second-tier sub-directories 404,406,408 respectively.
  • a look-up table 420 is stored outside the hierarchical file structure 400.
  • First and second template files 422,424 are also stored in the separate directory 41 8.
  • the look-up table 420 associates (sub) directories with templates.
  • the look-up table might, for example, indicate that the first template file 422 is associated with the first-tier root directory 402 and the second template file 5 424 is associated with the first second-tier sub-directory 404. It will be appreciated that a look-up table is only one example of providing a correspondence between a (sub) directory and one or more templates. Other examples such as a linked-list will be well known.
  • the tool When invoked, as with the first embodiment, the tool will perform a 'tree traversing' procedure, in a top down fashion. Again, in the course of this first procedure the branching form of the file structure 400 in terms of the root directory 402 and the sub-directories 404,406,408 will be detected and stored by the tool. Yet again, typically the description of the branching form stored by the tool may include information as to the name of a given directory, the relationship and name of the parent directory of the given directory, the relationships and names of any subdirectories of the given directory, the relationships and names of any other directories which share the same parent directory as the given directory, the names of any files stored within the given directory and so on.
  • the tool next performs a tree-traversing procedure in a bottom-up fashion. This second procedure will now be discussed having regard to the process flowchart indicated in Figure 5.
  • Step 500 provides for the selection of a particular content file stored in a given subdirectory.
  • step 502 provides that the tool will first consult the lookup table 420 to find out if there is a template file associated with the sub-directory in which the content file is itself located. If such a template is found then according to step 504 the tool will apply that template to the content file and the process for that particular content file will terminate.
  • a template file associated with the sub-directory in which the content file is itself located.
  • the tool will apply that template to the content file and the process for that particular content file will terminate.
  • an application of a template to a content file will involve the opening of a new file including the template.
  • the body of the content file will be automatically copied and pasted into this new file. In this way the template is automatically applied to the body of the content file.
  • the new file may of course be stored anywhere but, again by way of example, newly 'templated' files 426,428,430,432 are indicated in Figure 4 (in dashed lines) as being stored in the same (sub) directory as the content file upon which the templated file is based.
  • step 508 the tool will consult the lookup table 420 to find out if there is a template associated with the parent (sub) directory of the sub-directory in which the content file is located. Should such a template still not be found upon repeat of step 502, then, in accordance with a repetition of steps 506, 508 and 502, the tool will continue the search up the hierarchical structure until such a template is found. That template would then be applied. If no such template is found to be associated with the root directory 402 then the process for that particular content file will terminate.
  • a non-exclusive application of templates may be considered.
  • the tree-traversing would not terminate in accordance with step 504, but would record the association of that template 424 and carry on up the hierarchy to record the association of the first template 422 in the root directory 402.
  • the appropriate application of both the first template 422 and the second template 424 could then be performed.
  • templates are 'inherited' down the hierarchy form parent directory to child directory, providing a 'cascading' of template style and the associated advantages discussed with respect to the first embodiment.
  • the tool disclosed in accordance with the third embodiment of the invention may again be implemented as a software application program to be executed by the computer 100.
  • the tool as implemented as such a software application program may then again be stored in any suitable computer readable storage media form, for example on a floppy disk 104 or on a CD-ROM (not shown), for loading into a computer 100 for execution. Again a well known alternative would be to download the software application program over the network 1 1 2, for execution by the computer 1 00.
  • the method and tool here described as the third embodiment according to the present invention enhance the functionality of the method as disclosed in the co-pending application.
  • Files containing template information are placed in a separate directory outside the file structure.
  • files containing template information are placed in the directories and sub-directories of the file structure.
  • 'the tool' When the 'enhanced' tool according to the third embodiment of the present invention (hereinafter referred to as 'the tool') is invoked, the appropriate templates are assembled and applied to the respective content containing files, for example the text documents, to create Web pages 'managed' through the application of these templates.
  • Figure 6 illustrates a flow chart indicating a process by which such a 'managed' Website may be created using the tool.
  • the respective steps 600 to 61 2 will be illustrated with further reference to Figures 7. It will be appreciated that since a number of these steps involve the independent setting in place of elements upon which the tool acts when invoked, the order of some of the steps indicated in Figure
  • Step 600 provides for the creation of a 'source' file structure upon which the tool may subsequently act.
  • Figure 7 illustrates an example of a source file structure 700 with a three tier hierarchy.
  • a first-tier root directory 702 is created with first, second and third sub-directories 704N06N08 at the second tier level .
  • Created as subdirectories of the third second-tier sub-directory 708, first and second sub-directories 710,71 2 are provided at the third tier level. It will be well known that this may be done using, for example, Windows File ManagerTM or Windows ExplorerTM when using a WindowsTM operating system.
  • Step 602 provides for the creation of, in this exemplary embodiment, a set of HTML templates. It will be appreciated however that any other suitable form of template could be used.
  • Web 'pages' may be created through the use of a particular markup language, HyperText Markup Language (HTML) . It is through the use of HTML that, for example, the appearance of the text or graphics of a given Web page may be controlled along with the linking of one such Web page to another.
  • HTML instructions are also known as 'tags' .
  • the format of a Web page may thus be defined, for example, through the insertion of HTML tags in an ASCII text document.
  • a wide variety of simple text editors, word processors and more sophisticated HTML editors are available for this purpose.
  • One example of a suitable application program is Microsoft WordTM.
  • instructions may be given, for example, as to the appearance of headers, toolbars and footer sections. The instructions will define templates for these headers, toolbars and footer sections and these templates may then be used, in conjunction if desired, to control the appearance of any one or more Web pages.
  • a separate directory 714 is used to store a set of HTML templates 71 6 so created.
  • Step 604 provides for the insertion of user-defined tags into the HTML templates 71 6.
  • the standard tags recognised in HTML may be augmented by user-defined tags (user-defined in the sense that they are defined by the computer user creating the tags) for use with a given application.
  • the tags are intended for use with the tool and will be referred to hereinafter as 'tool tags' .
  • These tool tags will be included in the HTML defining a given template, in the form, ' ! !TAG_NAME ⁇ ' .
  • the double exclamation marks surrounding the TAG_NAME indicate to the tool that a pre-defined association, typically the insertion of text, is to be made when the tool is invoked.
  • This pre-defined association may be made on the basis of the information gathered about the file structure when the tree traversing is performed.
  • the description of the branching form stored by the tool will include information as to the name of a given directory, the relationship and name of the parent directory of the given directory, the relationships and names of any sub-directories of the given directory, the relationships and names of any other directories which share the same parent directory as the given directory, the names of any files stored within the given directory and so on.
  • Step 606 provides for the creation of, in this exemplary embodiment, a set of extensible Markup Language (XML) templates for storage within the source file structure 700.
  • XML extensible Markup Language
  • XML templates 716 The function of these XML templates is to assemble the HTML templates 716 to create the page format as desired.
  • a given XML template might call an HTML header template, an HTML title template, an HTML text template and an HTML footer template.
  • An example of such an XML template is as follows:
  • ⁇ /PAGE> As will be seen, the XML file begins with ⁇ PAGE > and ends with ⁇ /PAGE > .
  • the COMPONENT NAME is the name assigned to that portion of the page being defined. Examples of COMPONENT NAME might be HEADER, TITLE or FOOTER.
  • the ⁇ FILE > tag is used to indicate a location for the HTML template in question.
  • ⁇ TAG 1 > and ⁇ TAG2 > are the tags used in this component. As noted above, a list of such tags, by way of example, is provided in Table 1 .
  • ⁇ TAG 1 > YES ⁇ /TAG 1 > indicates that TAG 1 will be used within the template being called. All tags used within the template are declared in this manner.
  • this component causes the amount of time that has elapsed since content files were stored in their respective directories to be tested.
  • the date and time of storage of a file within a computer file system is typically available from the operating system as an associated property of the file concerned. If it is found, upon application of a template including such an archive component to a content file, that this time period is greater than a pre-determined period of time then the content file is archived.
  • the archiving process will be discussed further below.
  • these XML templates may be stored throughout the source file structure 700. By way of illustration of the operation of this embodiment however, the placing of such XML templates in only a single sub-directory will be here discussed in detail.
  • the third second-tier subdirectory 708 is shown as storing first and second XML templates 71 8,720.
  • the function of the first XML template 71 8 is to define the appearance of content files as Web pages through the assembly of HTML templates in accordance with the discussion above.
  • the somewhat different function of the second XML template 720 is to allow the creation of directory pages containing links to other pages, as will be discussed further below.
  • the first XML template 71 8 is said to be 'inherited' down the hierarchical source file structure 700. The effect of this application of 'inheritance' will be discussed below in greater detail.
  • Step 608 provides for the possibility of the creation of a file containing global information which may be useful for the operation of the tool. Accordingly control file 722, which may be written in XML, is stored in the separate directory 714.
  • An archive template 726 for example written in XML, may also be created and stored in the separate directory 714, the function of which is to determine the appearance of an archive page.
  • An example of the global information stored in the control file 722 might, for example, be the location of the storage of this archive template 726.
  • Step 610 provides for the introduction of the content files throughout the hierarchical source file structure 700.
  • a text file ( file extension, ' .txt' ) 724 is shown as being stored in the third second-tier sub-directory 708.
  • files are to be understood as stored throughout the source file structure 700 as desired. Again, it will be well known that this may be done using, for example, Windows File ManagerTM or Windows ExplorerTM when using a WindowsTM operating system.
  • Step 61 2 provides for the invocation of the tool.
  • the tool When invoked, the tool may typically be passed at least three parameters: the location in the computer file system of a Control file (in this example in the separate directory 714), the location in the computer file system of a Source file (in this case the location of the source file structure 700) and the location of a 'target' directory into which the 'templated' Web pages may be output.
  • a Control file in this example in the separate directory 714
  • a Source file in this case the location of the source file structure 700
  • a 'target' directory into which the 'templated' Web pages may be output.
  • the tool when invoked the tool will first perform a so-called 'tree traversing' procedure, in a top down fashion. Yet again in the course of this first procedure the branching form of the file structure in terms of the root directory and the subdirectories will be detected and stored by the tool.
  • the description of the branching form stored by the tool includes information as to the name of a given directory, the relationship and name of the parent directory of the given directory, the relationships and names of any sub-directories of the given directory, the relationships and names of any other directories which share the same parent directory as the given directory and so on.
  • the tool next performs a tree-traversing procedure in a bottom-up fashion.
  • This second procedure is similar to that discussed in respect of the first embodiment and will now be discussed having regard to the process flowchart indicated in Figure 3.
  • the templates used in this third embodiment differ from those discussed with respect to the first and second embodiments in that they are themselves assembled from fragment templates.
  • the tool would search not for the template in the sense of the first embodiment but for the first XML template 71 8. It is this template which, when applied by the tool in the equivalent of step 304, would call the relevant HTML templates 71 6 to assemble the specified constructed template to be applied to the content file 724.
  • the text-bearing content file 724 is used to generate an HTML file.
  • the XML template assembled HTML templates are also applied such that the new 'templated' file is not merely in an HTML form suitable for use as a Web page, but has, for example, the appearance desired in accordance with the templates. In this way the content file has been converted into a 'templated' Web page.
  • the tool creates a 'target' file structure at the location specified to the tool upon invocation, into which the newly templated files created by the tool are output.
  • the structure of the target file directory will mirror the source file structure.
  • a mirrored target file structure 800 is created.
  • a first-tier root directory 802 with first, second and third second-tier subdirectories 804,806,808 and first and second third-tier subdirectories 810,81 2 corresponding to those of Figure 7 is illustrated.
  • a newly 'templated' file 814 corresponding to the content file 724 in the third second-tier subdirectory 708 of the source file structure 700 is stored in the third second-tier subdirectory 808 of the target file structure 800.
  • templates of the form of both the first and second XML templates 71 8,720 and content files as desired were to be understood as seeded throughout the source file structure 700.
  • the above method will be performed in respect of each content file stored in the source file structure 700.
  • the relevant template or templates, the equivalents of the first XML template 71 8 will be applied to each content file and a corresponding templated HTML file, suitable for use as a Web page, will be output to the appropriate (sub) directory of the target file structure.
  • the second XML template 720 and its equivalents will be applied by the tool, utilising the description of the branching form of the source file structure 700 stored by the tool, to generate a directory document in respect of each (sub) directory of the target file structure.
  • a directory document 81 6 will be generated in the form of an HTML file, suitable for use as a Web page and is shown, by way of example, as being stored in the third second-tier sub-directory 808.
  • HTML instructions included in this directory page 81 6 will cause links to be provided, for example, not only to allow access to all the 'templated' content-bearing Web pages in that (sub) directory, but also to navigate to, for example, the home or root directory, the parent directory, child (sub) directories and sibling directories ( sharing the same parent directory) or, by way of further example, to an archive page.
  • An 'archive' link in the directory page will lead to an archive page, which may, for example, be created and stored in the same (sub) directory as the relevant directory page.
  • an archive page which may, for example, be created and stored in the same (sub) directory as the relevant directory page.
  • the inclusion of an archive tag in an XML template will, upon the application of that template to a content file stored longer ago than a pre-determined period of time, cause that content file to be deemed to be an 'archived' file.
  • the content file may still be used to generate a 'templated' Web page but no entry will appear in the 'current' directory page for the relevant (sub) directory, rather the directory page will contain a link to the above mentioned archive page, which will then provide links to the 'archived' 'templated' Web pages.
  • an example archive page 81 8 is illustrated, again stored in the third second-tier sub-directory 808.
  • the location of the target directory in the computer file system can simply be provided to a Web server application program.
  • a Web server application program is Microsoft Internet Information ServerTM.
  • the Web server may then render the Web site accessible to external Web browsers upon suitable connection.
  • a 'managed' Web site can be created, not with the attendant difficulties associated with the prior art, as discussed at length in the applicant's copending international patent application, but merely through the creation of a source file structure of appropriate form (for example relating to different types of meetings), the seeding throughout the structure of templates (in this example relating to the different types of meetings and 'cascading' down to allow for more general meeting templates to be complemented or overridden to the extent provided for by more specific ones), the storing in the appropriate directories of the relevant documents (in this example associated with each different type of meeting) and finally, the execution of the method (the running of the tool).
  • the third embodiment of the method and tool according to the invention also provides an advantageous means of Web site maintenance through the simple expedient of re-running the method and tool on a preexisting source file structure.
  • the HTML templates stored in the separate directory could be edited and the tool re-run.
  • the Web site would then be re-created but with the new HTML templates defining a new 'look and feel'.
  • either existing XML templates could be moved to different directories or new XML templates could be introduced into the appropriate directories of the source file hierarchy to alter the cascade of templates in the desired path and the tool re-run.
  • New content files from a wide variety of contributing authors could of course be introduced into the appropriate directories of the source file structure and the tool rerun to render the new content files as Web pages with the desired 'look and feel', as to achieve consistency with the existing pages.
  • the archiving process may take place each time the tool is run, automatically ensuring that older content is archived and yet still reliably accessible.

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

La présente invention concerne un procédé et un outil de gestion de documents contenus dans un système de fichiers informatiques. Cette gestion s'effectue par l'application de modèles aux documents, chaque modèle étant effectif lorsqu'il est appliqué à un document, en vue de réaliser une opération prédéterminée sur le document. Généralement, on effectue aujourd'hui l'association de modèles en introduisant des instructions dans les documents. Ces instructions devront être modifiées ultérieurement lorsque le modèle sera changé. Par contre, dans cette invention, on associe des modèles à des répertoires. Ces procédés et outil sont efficaces pour appliquer le ou les modèles associés à un répertoire donné à des fichiers de contenu mémorisés dans ce répertoire pour créer des versions de modèles des fichier de contenu. Cependant, si le modèle appliqué au fichier de modèle doit être changé, au lieu de modifier le fichier de modèle, il convient d'associer le modèle modifié au répertoire dans lequel est mémorisé le fichier de contenu, et de répéter le procédé par une nouvelle exécution de l'outil. Dans une variante, le fichier de contenu peut être déplacé à un répertoire dans lequel le modèle modifié est déjà associé et le procédé répété par une nouvelle exécution de l'outil. En outre, cette invention concerne une application particulièrement avantageuse pour la création et la gestion de sites Web.
PCT/GB2000/000552 1999-02-17 2000-02-16 Procede et gestion de documents WO2000049519A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
JP2000600193A JP4481507B2 (ja) 1999-02-17 2000-02-16 文書管理の方法およびツール
EP00903863A EP1161730A1 (fr) 1999-02-17 2000-02-16 Procede et gestion de documents
CA002363006A CA2363006C (fr) 1999-02-17 2000-02-16 Procede et gestion de documents
AU25616/00A AU771925B2 (en) 1999-02-17 2000-02-16 Document management method and tool

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
GB9903641.0 1999-02-17
GBGB9903641.0A GB9903641D0 (en) 1999-02-17 1999-02-17 Document management method and tool
EP99304800 1999-06-18
EP99304800.8 1999-06-18

Publications (1)

Publication Number Publication Date
WO2000049519A1 true WO2000049519A1 (fr) 2000-08-24

Family

ID=26153502

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/GB2000/000552 WO2000049519A1 (fr) 1999-02-17 2000-02-16 Procede et gestion de documents
PCT/GB2000/000548 WO2000049520A1 (fr) 1999-02-17 2000-02-16 Creation d'un contenu hypermedia pour site web

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/GB2000/000548 WO2000049520A1 (fr) 1999-02-17 2000-02-16 Creation d'un contenu hypermedia pour site web

Country Status (6)

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

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002059788A1 (fr) * 2001-01-24 2002-08-01 Telefonaktiebolaget Lm Ericsson (Publ) Systeme et procede permettant une presentation personnalisee dans un portique
WO2002059790A1 (fr) * 2001-01-24 2002-08-01 Telefonaktiebolaget Lm Ericsson (Publ) Systeme et procede relatifs a l'acces d'applications/de services
WO2005026979A1 (fr) * 2003-09-18 2005-03-24 80-20 Software Pty. Limited Logiciel de dossier intelligent
EP1617339A1 (fr) * 2004-07-12 2006-01-18 Brother Kogyo Kabushiki Kaisha Dispositif et logiciel d'edition de mise en page
EP1260913A3 (fr) * 2001-05-23 2006-12-20 Oldemeier, Martin R. Dispositif de traitement de données pour créer les documents imprimés
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

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6760043B2 (en) 2000-08-21 2004-07-06 Intellocity Usa, Inc. System and method for web based enhanced interactive television content page layout
US7162697B2 (en) 2000-08-21 2007-01-09 Intellocity Usa, Inc. System and method for distribution of interactive content to multiple targeted presentation platforms
KR20020034672A (ko) * 2000-11-03 2002-05-09 김상수 홈페이지 관리 장치 및 방법
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
DE112008003584B4 (de) * 2008-01-09 2015-11-05 Hewlett-Packard Development Company, L.P. Ein einheitliches Aussehen und Anfühlen schaffende Bios-Graphikmaschine
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
AU2014229331C1 (en) * 2013-03-14 2020-04-16 Wix.Com Ltd. Device, system, and method of website building by utilizing data lists
WO2016033335A1 (fr) * 2014-08-27 2016-03-03 Sgk Système de génération de contenu multimédia et ses procédés de réalisation
JP7106177B1 (ja) * 2021-05-12 2022-07-26 弁理士法人Ipx 情報処理システム、情報処理方法及びプログラム

Citations (4)

* 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
EP0902377A1 (fr) * 1997-09-14 1999-03-17 International Business Machines Corporation Système de gestion de fichiers
JPH11144027A (ja) * 1997-11-04 1999-05-28 Canon Inc ファイル管理システム、方法および記録媒体

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0925542B1 (fr) * 1996-09-09 2002-08-07 Design Intelligence, Inc. Mise en page et mise en forme automatiques d'un contenu avec une presentation dans un support
US5956736A (en) * 1996-09-27 1999-09-21 Apple Computer, Inc. Object-oriented editor for creating world wide web documents

Patent Citations (4)

* 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
EP0902377A1 (fr) * 1997-09-14 1999-03-17 International Business Machines Corporation Système de gestion de fichiers
JPH11144027A (ja) * 1997-11-04 1999-05-28 Canon Inc ファイル管理システム、方法および記録媒体

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
PATENT ABSTRACTS OF JAPAN vol. 1999, no. 10 31 August 1999 (1999-08-31) *

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002059788A1 (fr) * 2001-01-24 2002-08-01 Telefonaktiebolaget Lm Ericsson (Publ) Systeme et procede permettant une presentation personnalisee dans un portique
WO2002059790A1 (fr) * 2001-01-24 2002-08-01 Telefonaktiebolaget Lm Ericsson (Publ) Systeme et procede relatifs a l'acces d'applications/de services
GB2386227A (en) * 2001-01-24 2003-09-10 Ericsson Telefon Ab L M No title
GB2386227B (en) * 2001-01-24 2004-12-15 Ericsson Telefon Ab L M An arrangement and a method for presentation customization in a portal structure
EP1260913A3 (fr) * 2001-05-23 2006-12-20 Oldemeier, Martin R. Dispositif de traitement de données pour créer les documents imprimés
WO2005026979A1 (fr) * 2003-09-18 2005-03-24 80-20 Software Pty. Limited Logiciel de dossier intelligent
EP1617339A1 (fr) * 2004-07-12 2006-01-18 Brother Kogyo Kabushiki Kaisha Dispositif et logiciel d'edition de mise en page
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

Also Published As

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

Similar Documents

Publication Publication Date Title
CA2363006C (fr) Procede et gestion de documents
US7392466B2 (en) Method and system of annotation for electronic documents
KR101099272B1 (ko) 외부 프로그램 테마를 사용하는 웹페이지 렌더링을 위한 테마 적용 방법
Spainhour et al. Webmaster in a Nutshell
EP1927922A1 (fr) Appareil de gestion de données, appareil d édition de données, appareil de parcours de données, méthode de gestion de données, méthode d édition de données et méthode de parcours de données
US20090217151A1 (en) Document processing and management approach for editing a markup language document
US20070277095A1 (en) Data Processing Device And Data Processing Method
EP1258819A2 (fr) Système et procédé pour fournir un fichier en plusieurs langues
US20080040588A1 (en) Data Processing Device and Data Processing Method
EP1901179A1 (fr) Dispositif de traitement de document et méthode de traitement de document
US20090083661A1 (en) System and method for selectively displaying web page elements
EP1816586A1 (fr) Système de traitement de données, méthode de traitement de données et serveur de gestion
US20080133563A1 (en) Data Processing Device And Data Processing Method
US20090021767A1 (en) Document processing device
US20080046809A1 (en) Data Processing Device and Data Processing Method
US7827195B2 (en) Document management device and document management method
US20080010587A1 (en) Document Processing Device and Document Processing Method
Maurer et al. Transclusions in an html-based environment
EP1821220A1 (fr) Dispositif de traitement de donnees, dispositif de traitement d'un document, et procede de traitement de document
US20100077295A1 (en) Document processing device and document processing module
US20080005154A1 (en) Document Processing Device and Document Processing Method
US20080285064A1 (en) Document Processing Device, Document Processing Method, and Electronic Mail Processing Device
US20090077369A1 (en) Data Processing Device And Data Processing Method
US20030055850A1 (en) Method and computer program product for generating a list of items for viewing in a browser
US8639732B2 (en) Method for storing and reading-out data handled by application operating on HTTP client, data storage program, and data read-out program

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 09889349

Country of ref document: US

ENP Entry into the national phase

Ref document number: 2000 600193

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2363006

Country of ref document: CA

Kind code of ref document: A

Ref document number: 2363006

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 25616/00

Country of ref document: AU

REEP Request for entry into the european phase

Ref document number: 2000903863

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2000903863

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2000903863

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWG Wipo information: grant in national office

Ref document number: 25616/00

Country of ref document: AU