[go: up one dir, main page]

WO2000070511A1 - Systeme de developpement de sites web - Google Patents

Systeme de developpement de sites web Download PDF

Info

Publication number
WO2000070511A1
WO2000070511A1 PCT/AU2000/000468 AU0000468W WO0070511A1 WO 2000070511 A1 WO2000070511 A1 WO 2000070511A1 AU 0000468 W AU0000468 W AU 0000468W WO 0070511 A1 WO0070511 A1 WO 0070511A1
Authority
WO
WIPO (PCT)
Prior art keywords
content
templates
content objects
template
website
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.)
Ceased
Application number
PCT/AU2000/000468
Other languages
English (en)
Inventor
Jonathon Wolfe
Teresa White
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.)
MAXIEM Pty Ltd
Original Assignee
MAXIEM Pty Ltd
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
Application filed by MAXIEM Pty Ltd filed Critical MAXIEM Pty Ltd
Priority to AU45250/00A priority Critical patent/AU4525000A/en
Publication of WO2000070511A1 publication Critical patent/WO2000070511A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/14—Tree-structured documents
    • G06F40/143—Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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

Definitions

  • This invention concerns a website.
  • it concerns a development svstem for the creation, maintenance and publishing of websites on the World Wide Web (WWW).
  • Websites typically contain a number of pages through which a visitor to the site is able to surf using navigation functions.
  • the pages themselves may contain text, graphics, photographs, sound and video as well as the navigation locations.
  • Static websites use file systems as the data repository.
  • the pages are held on the webserver as individual HTML pages. This model allows many different people to add content to the website quite simply by providing new HTML pages to the webserver.
  • the files to be served can be managed easily and it is very easy to set up a website. This ease of set up and management contributed significantly to the growth of the WWW.
  • Dynamic architectures use databases to hold content and use programming or scripting languages to define classes of dynamically generated pages.
  • a template which is a program, extracts the same collection of data from the database and displays the same page to every user who surfs to it.
  • Dynamic page generation solves most of the file-based problems because it defers all decisions about content relationships to the moment when the user's browser requests the page.
  • Dynamic pages address the need to constantly change content by allowing content to be updated in the database.
  • the only way to give every user a unique view of every page involves complex programming to generate a customized page for each user.
  • the production of the code to produce the desired combination of HTML and the information from the database in a dynamic webpage is very tedious and clumsy. This work needs to be done by a specialist programmer who is unlikely to have the necessary artistic skills so prolongs the process.
  • Such systems require large amounts of CPU power to execute and cannot scale to provide an acceptable level of performance on affordable hardware.
  • Dynamic architectures built on programming languages such as C. C+ + , or Java, are even worse. In these systems developing web applications is tedious and time consuming, because everything becomes a programming exercise. Their fundamental problem is that they operate at levels of abstraction that are much too low. For example, just generating simple HTML output requires programming a series of "print" statements to generate the HTML tags. This makes it impossible for designers to handle layout considerations without knowing about programming, and precludes the use of HTML layout and design tools to assist with template development and maintenance.
  • Taglets are a generic way of defining special HTML tags that the server understands and processes rather than sending directly to the browser.
  • Taglets allow the server programmer to define custom, site/purpose specific server-side functionality (in Java) which may be used by HTML writers who have no knowledge of computer programming but are familiar with the syntax of HTML.
  • Taglets are in common use in products such as JRun.
  • Traditional taglet implementations rely on translating the taglet HTML into Java source code and then attempting to "compile" the Java source code automagically. all at the time the page is requested.
  • the invention is a website, including:
  • One or more pages each of which comprises one or more logical parts that are visible to a user.
  • Each of the parts may be any page content, such as a piece of information, text, images, a script or any other type of digital media.
  • Anv selected parts or combinations of parts are defined as content objects.
  • the content objects are arranged in a hierarchy with links to other content objects using URLs which are derived by the location of the content object in the hierarchy.
  • the boundaries of the content objects are also defined by the URLs.
  • Templates which define individual elements in a web application without regard for the specific web pages on which the elements might appear, are also defined as content objects, and the URL of each template instance includes a pointer to one or more parent templates.
  • the templates are constructed using taglets which define the content objects that are to be used to build a page.
  • All the templates and template instances are stored in a database and when the page is requested, the appropriate template is activated and the taglet HTML is interpreted to request the template instances required to build the page.
  • taglets By interpreting the taglets at page request time they become much more useable for average HTML content creators since any errors generated by interpreting a taglet can be presented in a format which can be easily interpreted by relatively unskilled users. This can be contrasted with past practice where taglets have been compiled, and at page request time the user might see Java compilation errors when attempting to use the Taglet which only make sense to the taglet author.
  • templates define individual elements in a web application without regard for the specific web pages on which the elements might appear.
  • Some examples of content objects include index pages, header images, and navigation bars.
  • template documents define actual pages in the web application by specifying which other content objects will be used to build the page. Individual content objects might be used on many types of pages throughout the web site.
  • Content objects provide well-defined interfaces to each other, allowing them to be combined in new ways without fear of interference from hidden assumptions. This is fundamentally different from a static "include” model, which is sometimes found in template architectures.
  • Content objects can be updated independently, allowing pieces of the application to evolve at different rates.
  • Content objects are ideally suited to assisting user navigation.
  • a dealer application which wants to display reports to dealers in an extranet environment. Each report may need to be formatted similarly - this would be a classic example of what template-based approaches are best at.
  • each customer could also receive a completely dynamic element within the reports, to provide the customer with personalised information that is specifically tailored for his or her preferences and context.
  • Dynamic assembly support would allow a content object-based system to combine the appropriate content objects together and provide each user with a customized view of the page.
  • each heading of a document could be stored as a different content object within the data repository. Then each of the heading objects could be listed against a certain set of criteria along with the author to quickly see the representation of this subject area in the data repository and also who had contributed this information. So the combination of a heading object and an author object provides new and important information that is not contained within the original stand alone document at the time of creation.
  • Another example of this might be a contract that is negotiated between two corporate entities, the myriad of documents are produced and fed through a definitive process with an obvious outcome. Some time later these contracts are subject to litigation on some point of implementation it will then be the job of the legal team to examine those documents in a different context.
  • Another advantage of the content object approach with a single repository of components is that it will efficiently serve many more people because of the ability to combine the content objects in many different ways given sufficient granularity. With sufficient granularity it is possible to build a data repository in a cost effective and efficient manner that will service the great majority of users of the information resource. By examination of the website from the point of view of having several different constituencies then it is possible to devise a communication message along identified bands of interest.
  • a Finance Director visiting a site about office machines will want to see information about the product as well as information relating to the total cost of ownership of the product.
  • Content authors can make assumptions about the type of content that the Finance Director will want to see and pull together these content objects in defined ways. If however the Finance Director wanted to stray into other content areas that he is particularly interested in then the site can be constructed uniquely along those lines. The unique combination of different content objects is easily achieved at the time of request against the data repository.
  • the invention is a website development system for the creation, maintenance and publishing of websites, including: An interface to communicate with client browsers to receive webpage content and webpage templates, and to deliver websites to a user.
  • the webpage content may be in any form, such as a piece of information, text, images, a script or any other type of digital media.
  • a parser to convert webpage content received from the interface into predefined parts which are defined as content objects which are all instances of templates. Also, to convert templates, which are constructed using taglets which define the content objects that are to be used to build a page, into content objects. Where the content objects are arranged in a hierarchy with links to other content objects using URLs which are derived by the location of the content object in the hierarch. The boundaries of the content objects are also defined by the URLs, and the URL of each template instance includes a pointer to one or more parent templates.
  • An interpreter to process content objects when a webpage is requested by activating the appropriate template and interpreting the template taglets to request the template instances required to build the page.
  • a content author who has access to the administration module within the system. They are able to access the directory structure of the site and surf to and edit content that is owned by them. This person would not typically have any technical skill. They create static content that they would enter into the website via a template instanciation that they have created.
  • An application programmer who has access to the administration module within the system and is able to access the directory structure of the site and to edit content that is owned by them. These people may construct templates and dynamic elements within the templates. Typically they will be contributing content extracted from a legacy database or some other application.
  • a technical template author with some HTML coding experience This person has access to the administration module within the system and is therefore able to access the directory structure of the site and surf to and edit content that is owned by them. They construct templates, this involves defining the structure and elements and boundaries to the content objects.
  • a website administrator who is a skilled person who controls the access list and the group user model. They are people who ensure that the server continues to operate efficiently and performs the overall tasks required.
  • HTML has varied requirements depending on the skill level of the operator. Highly skilled practitioners edit raw HTML in an environment where their work can be quickly visualised. The lack of editors capable of dealing with frames also force skilled users to operate in an environment where they work with the raw HTML.
  • HTML offers the inexperienced user the ability to create presentably formatted data containing graphics and other multimedia in a form that can be transported to anyone with access to a web browser.
  • HTML offers the inexperienced user the ability to create presentably formatted data containing graphics and other multimedia in a form that can be transported to anyone with access to a web browser.
  • the system enables distribution of content creation and centralisation of website management and control over the website publishing process. In addition it permits designing and delivering relevant and personalised web based content to visitors to a site.
  • the relationship from the template instance to the parent template is maintained only by the URL link. This means that the template has no knowledge of any of it's children. If the either the template or template instances are renamed, the link is not affected because all the objects use unique identifiers internally, and the URLs (which contain the name) are used externally only.
  • a secondary template is a template that references existing content and combines it in a new way or in combination with new content.
  • the secondary template references existing content objects by including the URL for the required objects.
  • each webpage is held in the database and can be used on the webpages in a many combinations and positions.
  • the content of the webpages can be developed independently of each other and it is a simple matter to design a webpage using static and dynamic (continually being updated from the database) elements. In this way large teams of programmers are able to produce a complex website working in parallel. The programmers are able to view the entire website and see how their work will impact the website at any level of detail.
  • the website Production Manager has tools for 'Locking' to prevent conflicting edits and 'Synchronisation' to make the integration of content from various programmers a simple process.
  • To produce a personalised webpage drawing from a customer database is relatively simple using 'conditional include'.
  • the system provides the information through any web browser and content can be created in a WYS/WYG format.
  • the customer can also add to the database if approved by a method that does not effect any of the other data and thereby the customers input becomes part of the website.
  • the production of websites is therefore faster, contain more timely changes and as a result be of better quality and more satisfying to the user.
  • the document template structure is defined using taglets which are simple HTML extensions, and there are no forms to code or scripts to write.
  • An HTML programmer can insert the required tags into the page structure. They can quickly and easily deploy templates that reference a variety of content objects in different contexts.
  • a revision control system must maintain a repository containing information about the files that have existed in a site. It must know which files are required to serve the site and be able to inform the user on which files are active and which are not.
  • revision control system must maintain the data. It should contain the change history of all the files in the site.
  • the system supports the development of complex websites by allowing multiple contributors to make up the web development team.
  • the system manages the permissions and responsibilities of the site development team to the components of the website.
  • the site is developed within the context of the website not as a separate entity.
  • the process of content creation can be removed from the responsibility of the site development team so they can direct their energies towards building site structure and navigational design.
  • With a security model implementation to the component level it is possible to push the responsibility for content creation and updating back to the people responsible for the material while maintaining control of access to that content.
  • the system can restrict access to various objects within any page in order to efficiently divide the development process, so the programmer can concentrate on programming, the layout HTML programmer can focus on their expertise and the graphic artist is restricted to manipulating images and look and feel.
  • the system uses the database to lock down the various elements of the site to the component level enabling the multiple skills and competencies to be applied to the development of the website at the same time. For example a graphic artist can alter an image on the page while a programmer is altering the executable code embedded within the same page. Using this methodology, a series of templates can be constructed that present to the user only the information required to perform their assigned function within the system.
  • the templates can be constructed in HTML with minimal extensions.
  • the concept behind distributed publishing is to ensure the widest possible distribution. This is achieved by only utilising standard Internet technologies so all the content can pass through the various security measures without risk or interference.
  • the template structure therefore also allows the combination of both static and dynamic elements into the same page or view.
  • Figure 1 is a schematic view of a system embodying the invention.
  • Figure 2 is a screen shot of websiteMax displaying an empty directory.
  • Figure 3 is a screen shot of creating a new HTML template called 'product. hint'.
  • Figure 4 is a screen shot of the directory now displaying the 'product.htm' template, which contains 280 bytes of default content.
  • Figure 5 is a screen shot of the HTML source code of the 'product.htm' template, showing its old content.
  • Figure 6 is a screen shot of the contents of a local file called
  • Figure 7 is a screen shot of the websiteMAX directory displaying 'product.htm' with its new content, which has expanded the file size to 618 bytes.
  • Figure 8 is a screen shot of the HTML source code of the 'product.htm' template, showing the new content.
  • Figure 9 is a screen shot of 'product.htm' viewed using the websiteMAX 'Browse' function.
  • Figure 10 is a screen shot of creating a new instance of the
  • Figure 11 is a screen shot of websiteMAX now displaying both files in its directory - 'car.
  • htm' has 150 bytes of default content.
  • Figure 12 is a screen shot of the default content of 'car. htm' viewed using the websiteMAX 'Edit' function.
  • Figure 13 is a screen shot of the default content of the 'car.htn instance viewed using the websiteMAX 'Browse' function.
  • Figure 14 is a screen shot of changing the content of the 'car. htm' instance using a WYSIWYG HTML editor (Netscape Composer).
  • Figure 15 is a screen shot of the updated content of 'car. htm' viewed using the websiteMAX 'Browse' function.
  • Figure 16 is a screen shot of websiteMAX displaying both files in its directory - 'car. htm' is now 356 bytes in size after being updated.
  • the concept of websiteMAX is to provide a platform to facilitate the development of large static/dynamic sites.
  • the platform is designed to provide a logical extension to the current implementation of websites that contain static and dynamic content.
  • the websiteMAX system architecture 1 is broken into four components as shown in Figure 1: the user interface 2. the interpreter 3. the cache 4 and the parser 5.
  • the user interface 2 is implemented on the client machine, while the remaining elements are delivered by the websiteMAX server.
  • the main physical components of websiteMAX are the websiteMAX client which is accessed simply using any standard web browser. It allows users to add. delete, copy, move and modify web pages in a website and automatically open a page in any HTML editor. Alternatively, users can create and modify pages using their favourite HTML editor;
  • the websiteMAX server allows both traditional static serving from content generated automatically from a file system and dynamic serving from content stored in a RDBMS.
  • a fundamental requirement of the user interface for the websiteMAX system is to allow use of the system from a web browser. This has a number of immediate advantages:
  • enabling client machines to use websiteMAX may be achieved by loading a readily available web browser.
  • all interaction between the websiteMAX server and the client occur through a web server communicating via HTTP.
  • websiteMAX will communicate through corporate firewalls with no reconfiguration requirements or displacement of existing proxy servers cause. This approach is critical in an intranet or extranet environment where there are security systems such as firewalls that prevent access via non-standard communications channels.
  • the publishing tool provides some interface functionality improvements for the interface, but will primarily provide productivity gains which will be welcomed by experienced users of the system.
  • the interpreter provides part of the serving functionality of websiteMAX.
  • the websiteMAX interpreter processes objects which have been defined in the cache and reconstitutes them as HTML. It also processes any of the special websiteMAX tags which have been added to enhance the functionality of the HTML. WebsiteMAX offers additional functionality such as being able to define variables in a page, loop statements and conditional statements.
  • the interpreter does not adopt the approach of other systems on the market which are attempting to provide an environment for developers to produce dynamic applications.
  • the command set is slim and only provides simple functionality that is coded by experienced HTML programmers.
  • the cache plays a pivotal role in the websiteMAX system design.
  • the cache is essential to provide the performance required so that the system is scalable.
  • the cache's goal is to minimise the number of times that the system needs to retrieve data from the database as it may be a performance bottleneck with the high level of deconstruction that is performed on individual pages.
  • the cache maps out the relationships between objects in the database. This allows the system to deliver a complete page quickly - pulling all the data required directly from the server.
  • the nature of the database structure provides maximum flexibility for future application design but does not necessarily provide optimal performance without the cache.
  • the implementation of the cache has been carried out in a completely general manner such that the cache can be implemented to operate over a file system in addition to the database.
  • the cache connects to the RDBMS through multiple connections to provide better performance.
  • the cache is not concerned about the number of connections.
  • the pool just supplies requests for drivers to connect to the database for an operation.
  • One connection is reserved for the reading from the database because reading is relatively fast when compared to writing.
  • the other connections are used for those users that wish to update data. There can be any number of connections in the pool and the number of connections utilised is a tunable parameter.
  • the parser provides facilities for breaking the HTML into the smaller objects that are stored in the cache and then into the database. It also takes links and turns them into object identifiers. If there is a file that has a link to another file in websiteMAX. a link identifier comes through the parser. websiteMAX finds the object ID of the referenced document and puts that into the cache.
  • Interpreted languages have always had significant advantage over compiled languages in the area of debugging.
  • Source code debugging and profiling is efficient and well implemented in Java development tools allowing for the enhanced productivity that this capability provides.
  • Java allowed the use of JDBC. which provides a standardised interface to RDBMS's. Individual JDBC drivers are still implemented by vendors, allowing for reasonable performance, but allow for Java code to be written in an RDBMS independent manner. WebsiteMAX has been tested under
  • Figure 2 shows an empty directory.
  • Figure 3 a dialogue box entitled "New Html Template” has been brought up. and the text 'product.htm' has been written in to title the new template.
  • Figure 4 the directory now displays the product.htm template which contains 280 bytes of default content.
  • Figure 5 shows the HTML source code for the content. This content is then changed by calling up the "Publish File" dialogue box, shown in Figure 6. and entering the file name 'a_catalogue_entry_template.htm'. Hitting the OK button publishes this content to websiteMAX and overwrites the default content of the product.htm template.
  • Figure 7 shows the directory in which the content of product.htm has been expanded to 618 bytes, and Figure 8 shows the HTML of those bytes.
  • Figure 9 shows the result which is viewed using the websiteMAX Browse function to view product.htm.
  • a new template instance can now be created using the published HTML template for product.htm as the parent file for the new template instance.
  • the dialogue box entitled "new HTML template instance" which is brought up in Figure 10.
  • the name of the parent file 'product.htm' is entered and the name of the new template instance 'car. htm' is entered.
  • Figure 11 shows both files in the directory, and car.htm can be seen to have 150 bytes of default content.
  • the websiteMAX edit function can then be invoked, as shown in Figure 12 to view the default content of car.htm.
  • Figure 13 shows the default content of car.htm instance when viewed using the websiteMAX browse function.
  • the content of the car.htm instance can then be changed using any WYSIWYG HTML editor such as Netscape Composer, and details are shown entered by the name, number and description of the car instance.
  • Figure 15 shows the updated content which is viewed using the websiteMAX browser function.
  • a return to the directory as shown in Figure 16. shows both files with car.htm having 356 bytes after being updated.

Landscapes

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

Abstract

L'invention concerne un site Web. Elle concerne également un système de développement pour la création, la mise à jour et l'édition de sites Web. Les sites Web contiennent généralement un nombre de pages sur lesquelles un visiteur peut naviguer au moyen de fonctions de navigation. Les pages elles-même contiennent du texte, des éléments graphiques, des photographies, du son et des images vidéo, ainsi que les emplacements de navigation. Les parties sélectionnées ou les combinaisons de parties sélectionnées sont définies comme objets de contenu et organisées en hiérarchie dotée de liens à d'autres objets de contenu utilisant des adresses URL dérivées à partir de l'emplacement de l'objet de contenu dans la hiérarchie. Des modèles définissent des éléments individuels dans une application Web sans prendre en compte les pages Web spécifiques sur lesquelles les éléments peuvent apparaître, et sont également définis comme objets de contenu. L'adresse URL de chaque instance de modèle comprend un pointeur vers un ou plusieurs modèles parents. Les modèles sont construits au moyen d'étiquettes qui définissent les objets de contenu à utiliser pour construire la page. Tous les modèles et les instances de modèle sont stockés dans une base de données et, lorsqu'une page est demandée, le modèle adéquat est activé et l'étiquette HTML est interprétée pour demander les instances de modèle nécessaires à la construction de la page. Le système de développement comporte une interface permettant de communiquer avec les navigateurs clients pour recevoir le contenu d'une page Web et les modèles de la page Web, et pour fournir des sites Web à un utilisateur. L'invention concerne également un analyseur qui convertit le contenu de la page Web, reçue de l'interface, en parties prédéfinies qui sont définies comme objets de contenu étant tous des instances de modèles. L'analyseur est également conçu pour convertir des modèles, construits au moyen d'étiquettes définissant les objets de contenu à utiliser pour la construction d'une page, en objets de contenu. L'invention concerne en outre un programme d'interprétation destiné à traiter les objets de contenu, lorsqu'une page Web est demandée par activation du modèle adéquat et par interprétation des étiquettes du modèle afin de demander les instances de modèles nécessaires à la construction de la page.
PCT/AU2000/000468 1999-05-18 2000-05-18 Systeme de developpement de sites web Ceased WO2000070511A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU45250/00A AU4525000A (en) 1999-05-18 2000-05-18 A website development system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
AUPQ0422 1999-05-18
AUPQ0422A AUPQ042299A0 (en) 1999-05-18 1999-05-18 A website development system

Publications (1)

Publication Number Publication Date
WO2000070511A1 true WO2000070511A1 (fr) 2000-11-23

Family

ID=3814625

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU2000/000468 Ceased WO2000070511A1 (fr) 1999-05-18 2000-05-18 Systeme de developpement de sites web

Country Status (2)

Country Link
AU (1) AUPQ042299A0 (fr)
WO (1) WO2000070511A1 (fr)

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002003243A1 (fr) * 2000-06-30 2002-01-10 Westfield Limited Integration de sites de tiers dans un centre commercial internet
FR2823332A1 (fr) * 2001-04-05 2002-10-11 Smart Brochure Procede d'enrichissement de catalogue electrique
GB2377520A (en) * 2001-02-23 2003-01-15 Amt Sybex A utility hub system
EP1338987A1 (fr) * 2002-02-19 2003-08-27 Hewlett-Packard Company Diffusion d'informations dans un réseau informatique
WO2003098468A3 (fr) * 2002-05-16 2004-05-27 Vivendi Technologies Inc Systeme et procede de gestion de contenu de site web
EP1223530A3 (fr) * 2001-01-10 2004-12-15 Fuji Photo Film Co., Ltd. Système et procédé de distribution de contenu numérique
EP1330718A4 (fr) * 2000-10-27 2006-06-21 Getthere Inc Systeme et procede de duplication de sites web
US7200645B2 (en) 2002-06-26 2007-04-03 International Business Machines Corporation Running dynamic web pages off-line with a wizard
US7249313B2 (en) 2002-06-26 2007-07-24 International Business Machines Corporation Creating and utilizing a wizard to capture an application's interdependencies between web pages and data accesses for running the application's downloadable dynamic web pages off-line
US7356559B1 (en) * 1999-07-01 2008-04-08 Affinity Internet, Inc. Integrated platform for developing and maintaining a distributed multiapplication online presence
GB2444284A (en) * 2006-09-18 2008-06-04 Yann Emmanuel Motte Method and apparatus for selection of information and web page generation
US7428549B2 (en) 2001-12-18 2008-09-23 International Business Machines Corporation Method and apparatus for editing a production data store by shadowing content
US7441116B2 (en) 2002-12-30 2008-10-21 International Business Machines Corporation Secure resource distribution through encrypted pointers
US7814413B2 (en) * 2003-04-17 2010-10-12 Oracle International Corporation System and method for controlling web pages
EP1581879A4 (fr) * 2002-12-20 2011-08-03 Optimost Llc Procede et appareil permettant de modifier dynamiquement un contenu electronique
EP2431933A1 (fr) * 2010-09-14 2012-03-21 Accenture Global Services Limited Contrôleur de traitement

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999057657A1 (fr) * 1998-05-04 1999-11-11 Lextron Systems, Inc. Adaptation d'un protocole de donnees et de transmission pour des transactions de donnees interactives efficaces sur des reseaux etendus
US6026433A (en) * 1997-03-17 2000-02-15 Silicon Graphics, Inc. Method of creating and editing a web site in a client-server environment using customizable web site templates
US6035330A (en) * 1996-03-29 2000-03-07 British Telecommunications World wide web navigational mapping system and method

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6035330A (en) * 1996-03-29 2000-03-07 British Telecommunications World wide web navigational mapping system and method
US6026433A (en) * 1997-03-17 2000-02-15 Silicon Graphics, Inc. Method of creating and editing a web site in a client-server environment using customizable web site templates
WO1999057657A1 (fr) * 1998-05-04 1999-11-11 Lextron Systems, Inc. Adaptation d'un protocole de donnees et de transmission pour des transactions de donnees interactives efficaces sur des reseaux etendus

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7356559B1 (en) * 1999-07-01 2008-04-08 Affinity Internet, Inc. Integrated platform for developing and maintaining a distributed multiapplication online presence
WO2002003243A1 (fr) * 2000-06-30 2002-01-10 Westfield Limited Integration de sites de tiers dans un centre commercial internet
EP1330718A4 (fr) * 2000-10-27 2006-06-21 Getthere Inc Systeme et procede de duplication de sites web
EP1223530A3 (fr) * 2001-01-10 2004-12-15 Fuji Photo Film Co., Ltd. Système et procédé de distribution de contenu numérique
US7043527B2 (en) 2001-01-10 2006-05-09 Fuji Photo Film Co.,Ltd. System and method for offering information service, method of assisting information release service, and information sharing server
GB2377520A (en) * 2001-02-23 2003-01-15 Amt Sybex A utility hub system
FR2823332A1 (fr) * 2001-04-05 2002-10-11 Smart Brochure Procede d'enrichissement de catalogue electrique
US7428549B2 (en) 2001-12-18 2008-09-23 International Business Machines Corporation Method and apparatus for editing a production data store by shadowing content
US8572032B2 (en) 2001-12-18 2013-10-29 International Business Machines Corporation Method and apparatus for editing a production data store by shadowing content
EP1338987A1 (fr) * 2002-02-19 2003-08-27 Hewlett-Packard Company Diffusion d'informations dans un réseau informatique
WO2003098468A3 (fr) * 2002-05-16 2004-05-27 Vivendi Technologies Inc Systeme et procede de gestion de contenu de site web
US7200645B2 (en) 2002-06-26 2007-04-03 International Business Machines Corporation Running dynamic web pages off-line with a wizard
US7249313B2 (en) 2002-06-26 2007-07-24 International Business Machines Corporation Creating and utilizing a wizard to capture an application's interdependencies between web pages and data accesses for running the application's downloadable dynamic web pages off-line
EP1581879A4 (fr) * 2002-12-20 2011-08-03 Optimost Llc Procede et appareil permettant de modifier dynamiquement un contenu electronique
US7441116B2 (en) 2002-12-30 2008-10-21 International Business Machines Corporation Secure resource distribution through encrypted pointers
US7814413B2 (en) * 2003-04-17 2010-10-12 Oracle International Corporation System and method for controlling web pages
GB2444284A (en) * 2006-09-18 2008-06-04 Yann Emmanuel Motte Method and apparatus for selection of information and web page generation
EP2431933A1 (fr) * 2010-09-14 2012-03-21 Accenture Global Services Limited Contrôleur de traitement
US9558285B2 (en) 2010-09-14 2017-01-31 Accenture Global Services Limited Treatment controller
US10417318B2 (en) 2010-09-14 2019-09-17 Accenture Global Services Limited Treatment controller

Also Published As

Publication number Publication date
AUPQ042299A0 (en) 1999-06-10

Similar Documents

Publication Publication Date Title
DE10042601B4 (de) Sprache für XML-Server-Seiten
KR101099272B1 (ko) 외부 프로그램 테마를 사용하는 웹페이지 렌더링을 위한 테마 적용 방법
WO2000070511A1 (fr) Systeme de developpement de sites web
US20050177784A1 (en) Creating an html document from a source document
US20020133516A1 (en) Method and apparatus for end-to-end content publishing system using XML with an object dependency graph
US20040041818A1 (en) Design system for website text graphics
JP2005530241A (ja) 電子文書のスタイルを管理するための方法およびシステム
MXPA01012818A (es) Metodo y aparato para crear servicios de red.
Hall et al. Core web programming
Engel et al. A Concerted Model-driven and Pattern-based Framework for Developing User Interfaces of Interactive Ubiquitous Applications.
Kerer et al. Layout, content and logic separation in web engineering
EP1695206A2 (fr) Systeme et procede d'adaptation de structure de contenu
Roisin Authoring structured multimedia documents
Suzuki et al. Making UML models exchangeable over the Internet with XML: UXF approach
Fiala et al. Design and implementation of component-based adaptive web presentations
Weitzman et al. Transforming the content management process at IBM. com
Kerer et al. Building and managing XML/XSL-powered Web sites: an experience report
Holzner Real World XML
Zdun et al. Content conversion and generation on the web: A pattern language
Quint et al. Structured templates for authoring semantically rich documents
Bottoni et al. SWOWS and dynamic queries to build browsing applications on linked data
Kirda Engineering device-independent web services
Muller et al. Model-driven generative approach for concrete syntax composition
Reinefeld et al. GuiGen: A toolset for creating customized interfaces for grid user communities
Petropoulos et al. Building XML query forms and reports with XQForms

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ 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 MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ 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 MZ 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

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

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP