DOCSLIB.ORG

Monitoring Multiple Web Pages and Presentation of Xml Pages

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Monitoring Multiple Web Pages and Presentation of Xml Pages WEBVIGIL: MONITORING MULTIPLE WEB PAGES AND PRESENTATION OF XML PAGES Sharavan Chamakura, Alpa Sachde, Sharma Chakravarthy and Akshaya Arora Information Technology Laboratory Computer Science and Engineering Department The University of Texas, Arlington, TX 76019 {chamakura, sachde, sharma, aarora}@cse.uta.edu Abstract Web, and this data is increasing at a rapid pace. This plethora of information often leads to In the case of large-scale distributed situations wherein users looking for specific environments such as the Internet, users are pieces of information are flooded with irrelevant interested in monitoring changes to a particular data. For example, an investment banking web page (XML or HTML). There are many professional who is only interested in news instances in which the change detection is related to his areas of interest, is flooded with required at a finer granularity, such as changes news on many topics when he goes to any to links, images, phrases or keywords in a page. popular news website. In some cases users are WebVigiL is a general-purpose, change concerned in knowing about the updates monitoring, notification and presentation system happening to a particular web page of their for web pages. It handles specification, interest such as the keywords, links or other management, and propagation of customized change types. For example, students might want changes as requested by a user in an efficient to know about the updates that are made to the way. When the user specifies an URL, it may course websites regarding any new projects or contain frames instead of a single content page; assignments. There may be some situations this entails additional pages to be fetched from where users are interested in tracking changes the frames for detecting changes. In this paper across multiple web pages. For example, a user we propose different approaches for detecting of a discussion board related to technical topics changes over pages containing frames and might be interested in knowing about posts generalizing it in terms of depth. We also being made regarding a particular set of topics. address the case of monitoring multiple web In this case, the user wants to be notified of the pages for different change types with a single changes related to various topics present on request. As there are no presentation semantics different web pages. In general, the ability to and tags, manual identification of the detected specify changes to arbitrary documents and get changes is difficult on a XML web page. Once notified in different ways will be useful for detected, changes have to be notified to the reducing the inefficient navigation. user in a meaningful manner. In this paper we WebVigiL [1-3] is a change detection and also propose various presentation schemes to notification system developed to provide users display the changes computed on XML pages . with the ability to monitor web pages (XML/ HTML) according to a profile. Users’ place a request by giving a set of specifications like the Keywords page to be monitored, the type of change to be checked for, when to fetch the page and how to Change Detection, Multiple Web Pages, notify the changes. The user request is in the Presentation. form of a sentinel that is used for change detection and presentation. The changes are 1. Introduction detected and stored in the change repository. The stored changes are then notified to the user. The World Wide Web has outdone traditional Figure 1 summarizes the high level architecture media such as television, to become an of WebVigiL [1]. Information from the sentinel is indispensable source of information. There is extracted, validated and stored in a knowledge data related to each and every context on the base and is used by other modules in the system. The presentation module provides the additional attributes such as insert = delete to various presentation schemes for detected the original XML document. changes to present them in a well-organized and readable format. The fetch module is responsible for fetching the pages in an efficient/optimal manner for detecting changes. The version control module stores different versions of a page until it is no longer needed for detecting changes and for notification of changes. The change detection module interacts with various modules for detecting changes in an efficient manner and placing the results of changes in the knowledge for notification by the presentation/notification module. Many a times, users are interested in monitoring multiple URLs or even entire web sites. Users may place a sentinel on a page without realizing that it is a frame and not an ordinary page. In this case, we want the WebVigiL system to transparently process the Figure 1: System Architecture page with frames taking the user intent into account. Support for monitoring multiple pages Diff and Merge Tool [6] provided by IBM in general allows us to treat frames as a special compares two XML files based on node case of multiple pages. We use the notion of identification. It represents the differences depth to specify how many levels one needs to between the base and the modified XML files consider from the root. using a tree display in the left-hand, Merged This paper extends upon our previous work View pane with symbols and colours to highlight in customized content monitoring of web pages. the differences using the XPath syntax. The contributions of this paper are: a) the DOMMITT [7] is a UNIX diff utility tool improved Change Detection Graph (CDG) which that enables the users to view differences supports the monitoring of multiple URLs for between the DOM representations of two XML either similar or different change types. As a documents. The Diff algorithms on these DOM subset, this includes the monitoring of web [8] representations produces edit scripts, which pages containing frames, b) Presentation are merged into the first document to produce schemes for the semi structured XML pages. an XML document in which the edit operations The rest of the paper is organized as follows. are represented as insert = delete tags for a Section 2 discusses the overview of the related user interactive display of differences. work. Section 3 and 4 will discuss, respectively, AIDE presents a set of tools (collectively a mechanism to monitor multiple URLs, which called AT&T Internet Difference Engine) [9] that includes the class of web pages with frames and detect when pages have been modified and the schemes for presentation of detected present modifications to user through marked up changes for XML webpage. Section 5 provides HTML. AIDE uses HTML diff to graphically the conclusion and future work. present differences using heuristics to determine additions and deletions between versions of a 2. Related Work page. AIDE uses the three most popular schemes the dual frame scheme, merged view and only change scheme. All of the techniques Most of the research has been done in change mentioned above produce edit scripts to apply detection systems for web pages. In WebVigiL on the documents to generate the latest version the change detection is based on an expressive with changes. The requirement of the WebVigiL user specification. was to display the customized changes Delta XML [4] developed by Mosnell computed by the detection algorithms based on provides a plug-in solution for detecting and user input. The changes were at a finer displaying changes to contents between two granularity than a page. Hence the above versions of an XML document. They represent techniques could not be used directly for changes in a merged delta file [5] by adding resolving the issues for presentation of the detection graph constructed for sentinels S1, S2 detected changes in a legible format. and S3 are shown is Figure 2. The Current WebCQ [10] system supports change detection over various primitive S AND S3 change types such as links, images, keywords, 1 lists, and tables but there is no provision to give Sand composite change requests. Also, the current S2 Sand WebCQ system does not support the monitoring of multiple web pages with a single request. group 2 group group 1 Users cannot combine multiple URLs with different change types. It provides the interface Links to display the web page specified by the user, if Images the web page contains frames user have the flexibility to select the particular frame for the change detection, if the frame is not selected Figure 2: Change Detection Graph then the change will only be detected on the main webpage. The base page can be assumed The different types of nodes in the CDG are: to be present at level zero; all the pages pointed 1. URL node: A URL node is a leaf node that by the base page at level one and so on. If denotes the page being monitored. there are links on the frames WebCQ cannot 2. Change type node: All level 1 nodes are monitor changes on the web page said to be change type (links, keywords, corresponding to that links means monitoring the images, phrases) nodes. These nodes web pages in depth is not possible but in perform the change detection over the WebVigiL the user only specifies the URL and respective types. the changes are detected on all the frames if 3. Composite node: A Composite node exists of the webpage specified by the user. represents a combination of change types. Unlike WebCQ, WebVigiL is capable of All nodes above level 1 belong to this type. detecting changes to one level in depth of a web The URL nodes are notified regularly after page. fetching the required pages with the specified periodicity. To reduce redundant fetching, a page is fetched only if it’s last modified time 3.
Load more

Recommended publications
  • ATSC Standard
    Doc. A/100-2 09 March 2003 DTV APPLICATION SOFTWARE ENVIRONMENT LEVEL 1 (DASE-1) PART 2: DECLARATIVE APPLICATIONS AND ENVIRONMENT ATSC Standard Advanced Television Systems Committee 1750 K Street, N.W. Suite 1200 Washington, D.C. 20006 www.atsc.org Blank Page ATSC DASE-1 Declarative Applications and Environment 09 Mar 2003 Table of Contents DASE-1 DECLARATIVE APPLICATIONS AND ENVIRONMENT ..................................1 1. SCOPE....................................................................................................................1 1.1 Status ............................................................................................................................... 1 1.2 Purpose............................................................................................................................ 1 1.3 Application....................................................................................................................... 1 1.4 Organization ....................................................................................................................1 2. REFERENCES........................................................................................................3 2.1 Normative References .................................................................................................... 3 2.2 Informative References .................................................................................................. 4 2.3 Reference Acquisition ...................................................................................................
    [Show full text]
  • Structured Documents on the Web
    Structured Documents on the Web Jacco van Ossenbruggen Multimedia and Human-Computer Interaction Group CWI: Centrum voor Wiskunde en Informatica Amsterdam, The Netherlands Presentation Outline: • Introduction and historical background • Multiple delivery publishing (MDP) • MDP & the Web • Style sheets • Conclusion TUE, 8 January 2001 Structured Documents on the Web Page 1 of 35 Structured Documents on the Web Jacco van Ossenbruggen Multimedia and Human-Computer Interaction Group CWI: Centrum voor Wiskunde en Informatica Amsterdam, The Netherlands Presentation Outline: • Introduction and historical background • Multiple delivery publishing (MDP) • MDP & the Web • Style sheets • Conclusion TUE, 8 January 2001 Structured Documents on the Web Page 2 of 35 Documents vs. other data A document is • a self-contained unit of information, • intended to be communicated to human interpreter • examples: - book, poem - article, paper, report - memo, E-mail, letter, etc. Whereas data can also be • fragmentary • intended solely for further machine processing • examples: - database records - HTTP requests - schemas TUE, 8 January 2001 Structured Documents on the Web Page 3 of 35 TUE, 8 January2001 MyOwnML Web representationlanguages XHTML Documents MathML Structured Documents ontheWeb SVG XML SMIL RDF(S) PICS Data/KR P3P DC Page 4 of35 Structured Documents on the Web Jacco van Ossenbruggen Multimedia and Human-Computer Interaction Group CWI: Centrum voor Wiskunde en Informatica Amsterdam, The Netherlands Presentation Outline: • Introduction and historical
    [Show full text]
  • Xml
    <REPORT NAME> XML USAGE ASSESSMENT REPORT VERSION: 1.0 <FILENAME REFERENCE> XMLUSE.DOC Issue Date: 30-06-2000 Version Number: 1.0 XML ASSESSMENT USAGE REPORT Written by: Dimitrios Oikonomidis & Michael Papaioannou, Students of Department of Informatics at Athens University of Economics and Business Issue Date: 30-06-2000 File Ref :xmluse.doc Page: 1/130 <REPORT NAME> XML USAGE ASSESSMENT REPORT VERSION: 1.0 <FILENAME REFERENCE> XMLUSE.DOC Table of Contents 1. INTRODUCTION...........................................................................................................7 2. XML...............................................................................................................................9 2.1 Introduction in XML........................................................................................................................... 9 2.2 Design goals for XML ......................................................................................................................... 9 2.3 Syntax of XML................................................................................................................................... 10 2.4 DTDs in XML .................................................................................................................................... 12 2.4.1 Introduction in DTDs...................................................................................................................... 12 2.4.2 Syntax of DTDs in XML ...............................................................................................................
    [Show full text]
  • Extensible Stylesheet Language (XSL) Version 1.0
    Extensible Stylesheet Language (XSL) Version 1.0 W3C Candidate Recommendation 21 November 2000 This version: http://www.w3.org/TR/2000/CR-xsl-20001121/ (PDF by RenderX, XML file, HTML (one large file), ZIP file) Latest version: http://www.w3.org/TR/xsl/ Previous version: http://www.w3.org/TR/2000/WD-xsl-20001018 Authors and Contributors: Sharon Adler (IBM) <[email protected]> Anders Berglund (IBM) <[email protected]> Jeff Caruso (Pageflex) <[email protected]> Stephen Deach (Adobe) <[email protected]> Paul Grosso (ArborText) <[email protected]> Eduardo Gutentag (Sun) <[email protected]> Alex Milowski (Lexica) <[email protected]> Scott Parnell (Xerox) <[email protected]> Jeremy Richman (BroadVision) <[email protected]> Steve Zilles (Adobe) <[email protected]> Copyright © 2000 W3C (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. ii Extensible Stylesheet Language (XSL) (xsl-20001121) Abstract XSL is a language for expressing stylesheets. It consists of two parts: 1. a language for transforming XML documents, and 2. an XML vocabulary for specifying formatting semantics. An XSL stylesheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed into an XML document that uses the formatting vocabulary. Status of this document This document is a W3C Candidate Recommendation. The XSL WG considers this specification to be stable and encourges implementation and comment during the CR review period. The Candidate Recommendation review period ends on February 28, 2001. Please send detailed comments and reports of implementation experience to [email protected] before the end of the CR review period.
    [Show full text]
  • Metadata Type System: Integrate Presentation, Data Models and Extraction to Enable Exploratory Browsing Interfaces
    Metadata Type System: Integrate Presentation, Data Models and Extraction to Enable Exploratory Browsing Interfaces Yin Qu, Andruid Kerne, Nic Lupfer, Rhema Linder and Ajit Jain Interface Ecology Lab, Texas A&M University College Station, TX, USA yin, andruid, nic, rhema, [email protected] ABSTRACT on serendipity" [32]. By exploratory browsing, we mean Exploratory browsing involves encountering new information browsing when the task is open-ended and the user is unfa- during open-ended tasks. Disorientation and digression are miliar with the information space. Exploratory browsing is problems that arise, as the user repeatedly loses context while key to berrypicking [3], the iterative process in which the user clicking hyperlinks. To maintain context, exploratory brows- encounters new information, and her understanding and infor- ing interfaces must present multiple web pages at once. mation needs evolve. Browsing and search are complemen- tary strategies for exploring information [32]. In exploratory Design of exploratory browsing interfaces must address the search [46], users engaged in learning and investigation it- limits of display and human working memory. Our approach eratively refine information needs. While this paper directly is based on expandable metadata summaries. Prior seman- addresses exploratory browsing, its implications also impact tic web exploration tools represent documents as metadata, exploratory search. but often depend on semantic web formats and datasets as- sembled in advance. They do not support dynamically en- Users lose context while browsing, as new information is countered information from popular web sites. Optimizing encountered [16]. Interlinked pages are shown in separate presentation of metadata summaries for particular types of viewports, leading to disorientation [10], the problem of not documents is important as a further means for reducing the knowing where you are or how to return to an encountered cognitive load of rapidly browsing across many documents.
    [Show full text]
  • HTML Elements
    Web Basics HTML HTML or HyperText Markup Language is the standard markup language used to create web pages. HTML is written in the form of HTML elements consisting of tags enclosed in angle brackets (like <html>). HTML tags most commonly come in pairs like <h1> and </h1>, although some tags represent empty elements and so are unpaired, for example <img>. The first tag in a pair is the start tag, and the second tag is the end tag (they are also called opening tags and closing tags). A web browser can read HTML files and compose them into visible or audible web pages. The browser does not display the HTML tags, but uses them to interpret the content of the page. HTML describes the structure of a website semantically along with cues for presentation, making it a markup language rather than a programming language. HTML elements form the building blocks of all websites. HTML allows images and objects to be embedded and can be used to create interactive forms. It provides a means to create structured docu- ments by denoting structural semantics for text such as headings, paragraphs, lists, links, quotes and other items. It can embed scripts written in languages such as JavaScript which affect the behavior of HTML web pages. Web browsers can also refer to Cascading Style Sheets (CSS) to define the look and layout of text and other material. The W3C, maintainer of both the HTML and the CSS standards, encourages the use of CSS over explicit presenta- tional HTML* Markup Language A (document) markup language is a modern system for annotating a document in a way that is syntactically dis- tinguishable from the text.
    [Show full text]
  • XML Tutorial: Overview
    XML tutorial: Overview Contents 1. HTML and XML - structuring information for the future (21 pp.) 2. Namespaces, XInclude, and XML Base - common extensions to the XML specification (8 pp.) 3. DTD, XML Schema, and DSD - defining language syntax with schemas (27 pp.) 4. XLink, XPointer, and XPath - linking and addressing (24 pp.) 5. XSL and XSLT - stylesheets and document transformation (19 pp.) 6. XQuery - document querying (15 pp.) 7. DOM, SAX, and JDOM - programming for XML (15 pp.) 8. W3C - some background on the World Wide Web Consortium (5 pp.) http://www.brics.dk/~amoeller/XML/overview.html [4/9/2002 4:43:22 PM] XML tutorial: HTML and XML THE XML REVOLUTION - TECHNOLOGIES FOR THE FUTURE WEB Markup Languages: HTML and XML HTML - original motivation, development, and inherent limitations: ● Hyper-Text Markup Language - the Web today ● Original motivation for HTML - some history ● Compact and human readable - alternative document formats ● From logical to physical structure - requirements from users ● Stylesheets - separating logical structure and layout ● Different versions of HTML - a decade of development ● Syntax and validation - HTML as a formal language ● Browsers are forgiving - the real world ● Structuring general information - not everything is hypertext ● Problems with HTML - why HTML is not the solution XML as the universal format for structuring information: ● What is XML? - the universal data format ● HTML vs. XML - the key differences ● A conceptual view of XML - XML documents as labeled trees ● A concrete view of XML - XML documents as text with markup ● Applications of XML - an XML language for every domain ● The recipe example - designing a small XML language ● From SGML to SML - a word on doc-heads and development ● SGML relics - things to avoid ● XML technologies - generic languages and tools for free Selected links: ● Basic XML tools ● Links to more information COPYRIGHT © 2001 ANDERS MØLLER & MICHAEL I.
    [Show full text]
  • Extensible Stylesheet Language (XSL) Version 1.0
    Extensible Stylesheet Language (XSL) Version 1.0 W3C Candidate Recommendation 21 November 2000 This version: http://www.w3.org/TR/2000/CR-xsl-20001121/ (PDF by RenderX, XML file, HTML (one large file), ZIP file) Latest version: http://www.w3.org/TR/xsl/ Previous version: http://www.w3.org/TR/2000/WD-xsl-20001018 Authors and Contributors: Sharon Adler (IBM) <[email protected]> Anders Berglund (IBM) <[email protected]> Jeff Caruso (Pageflex) <[email protected]> Stephen Deach (Adobe) <[email protected]> Paul Grosso (ArborText) <[email protected]> Eduardo Gutentag (Sun) <[email protected]> Alex Milowski (Lexica) <[email protected]> Scott Parnell (Xerox) <[email protected]> Jeremy Richman (BroadVision) <[email protected]> Steve Zilles (Adobe) <[email protected]> Copyright © 2000 W3C (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. ii Extensible Stylesheet Language (XSL) (xsl-20001121) Abstract XSL is a language for expressing stylesheets. It consists of two parts: 1. a language for transforming XML documents, and 2. an XML vocabulary for specifying formatting semantics. An XSL stylesheet specifies the presentation of a class of XML documents by describing how an instance of the class is transformed into an XML document that uses the formatting vocabulary. Status of this document This document is a W3C Candidate Recommendation. The XSL WG considers this specification to be stable and encourges implementation and comment during the CR review period. The Candidate Recommendation review period ends on February 28, 2001. Please send detailed comments and reports of implementation experience to [email protected] before the end of the CR review period.
    [Show full text]
  • Extensible Markup Language XHTML: HTML Based on XML HTML5: Redefinition of HTML for Browsing Without Plugins
    R0 G49 B82 Chair of Mobile Business & R105 G133 B153 R111 G118 B127 Multilateral Security R226 G0 B116 R255 G71 B167 R255 G185 B222 Lecture 10 R0 G0 B00 Business Informatics 2 (PWIN) SS 2017 ICS Development III Markup Languages Prof. Dr. Kai Rannenberg Deutsche Telekom Chair of Mobile Business & Multilateral Security Johann Wolfgang Goethe University Frankfurt a. M. 1 R0 G49 B82 R105 G133 B153 News on the Internet and the R111 G118 B127 R226 G0 B116 Digital Society R255 G71 B167 R255 G185 B222 R0 G0 B00 . Schneier, Bruce (2013): The US government has betrayed the internet. We need to take it back. www.theguardian.com/commentisfree/2013/sep/05/govern ment-betrayed-internet-nsa-spying . Schneier, Bruce (2013): The Battle for Power on the Internet; www.theatlantic.com/technology/archive/2013/10/the- battle-for-power-on-the-internet/280824/ . Lobo, Sascha (2014): Abschied von der Utopie; Die digitale Kränkung des Menschen; www.faz.net/aktuell/feuilleton/debatten/abschied-von- der-utopie-die-digitale-kraenkung-des-menschen- 12747258.html . Scahill, Jeremy; Begley, Josh (2015): The Great SIM Heist. How Spies Stole the Key to the Encryption Castle; https://firstlook.org/theintercept/2015/02/19/great-sim- heist/ 2 R0 G49 B82 R105 G133 B153 R111 G118 B127 Agenda R226 G0 B116 R255 G71 B167 R255 G185 B222 R0 G0 B00 . From HTML to XML . XML Concepts . Processing of XML Documents . XML Example Applications 3 R0 G49 B82 R105 G133 B153 R111 G118 B127 Overview of HTML R226 G0 B116 R255 G71 B167 R255 G185 B222 R0 G0 B00 .
    [Show full text]
  • ATSC Standard
    Doc. A/100-2 09 March 2003 DTV APPLICATION SOFTWARE ENVIRONMENT LEVEL 1 (DASE-1) PART 2: DECLARATIVE APPLICATIONS AND ENVIRONMENT ATSC Standard Advanced Television Systems Committee 1750 K Street, N.W. Suite 1200 Washington, D.C. 20006 www.atsc.org Blank Page ATSC DASE-1 Declarative Applications and Environment 09 Mar 2003 Table of Contents DASE-1 DECLARATIVE APPLICATIONS AND ENVIRONMENT ..................................1 1. SCOPE....................................................................................................................1 1.1 Status ............................................................................................................................... 1 1.2 Purpose............................................................................................................................ 1 1.3 Application....................................................................................................................... 1 1.4 Organization ....................................................................................................................1 2. REFERENCES........................................................................................................3 2.1 Normative References .................................................................................................... 3 2.2 Informative References .................................................................................................. 4 2.3 Reference Acquisition ...................................................................................................
    [Show full text]
  • Practical Transformation Using XSLT and Xpath (XSL Transformations and the XML Path Language) Crane Softwrights Ltd
    Practical Transformation Using XSLT and XPath (XSL Transformations and the XML Path Language) Crane Softwrights Ltd. http://www.CraneSoftwrights.com +//ISBN 1-894049::CSL::Courses::PTUX//DOCUMENT Practical Transformation Using XSLT and XPath 2001-12-06 12:00UTC//EN Tenth Edition - 2001-12-06 http://www.CraneSoftwrights.com ISBN 1-894049-08-XPREVIEW EXCERPTCopyright © Crane Softwrights Ltd. PREVIEW EXCERPT Practical Transformation Using XSLT and XPath Practical Transformation Using XSLT and XPath (XSL Transformations and the XML Path Language) Crane Softwrights Ltd. http://www.CraneSoftwrights.com Copyrights - Pursuant to http://www.w3.org/Consortium/Legal/ipr-notice.html, some information included in this publication is from copyrighted material from the World Wide Web Consortium as described in http://www.w3.org/Consortium/Legal/copyright-documents.html: Copyright (C) 1995-2001 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved. The status and titles of the documents referenced are listed in the body of this work where first used. - Other original material herein is copyright (C) 1998-2001 Crane Softwrights Ltd. This is commercial material and may not be copied or distributed by any means whatsoever without the expressed permission of Crane Softwrights Ltd. Disclaimer - By purchasing and/or using any product from Crane Softwrights Ltd. ("Crane"), the product user ("reader") understands that this product may contain errors and/or other inaccuracies that may result in a failure to use the product itself or other software claiming to utilize any proposed or finalized standards or recommendations referenced therein. Consequently, it is provided "AS IS" and Crane disclaims any warranty, conditions, or liability obligations to the reader of any kind.
    [Show full text]
  • Open and Accessible Presentations
    Open and Accessible Presentations Erik Wilde School of Information UC Berkeley, USA Email: [email protected] Abstract—E-learning often is perceived as something that, on as well. Ideally, e-learning applications should be designed to the technical level, can be addressed by designing an e-learning “blend into the Web” so that they can benefit from the Web, system, which often is equipped with a Web-based interface. and that the Web can benefit from them. We argue that this traditional approach of e-learning system design should be reversed in today’s Web-oriented environment, In this article, we first investigate the fundamental chal- in the sense that e-learning applications should be designed as lenges e-learning faces today. These challenges mostly arise well-behaving Web citizens and expose their services through from the dynamics and the loosely coupled nature of today’s nothing else but the Web’s loose coupling principles. This article Web [2]. We then progress to investigating these challenges presents a system for Web-based presentations which follows this in more detail, looking at services and content as the two approach in publishing presentation material in a way that is as Web-friendly as possible. We show how such a system can be used main problems in bridging the gap between e-learning systems as one building block in an e-learning infrastructure; replacing and the Web as an information system. We then describe our the traditional view of monolithic e-learning systems with an solution for structuring presentation material, and continue open and loosely coupled ecosystem of cooperating e-learning with describing the way of how this content can be used for Web applications.
    [Show full text]