DOCSLIB.ORG

Declarative Techniques in Distributed Media Center System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Declarative Techniques in Distributed Media Center System declarative techniques in Distributed Media Center Jari Kleimola and Petri Vuorimaa Telecommunications Software and Multimedia Lab Helsinki University of Technology June 5, 2007 Outline DMC Compound Model Remote UIs Interaction Loop XProc Conclusion W3C Workshop on Declarative Models of Distributed Web Applications June 5-6 2007, Dublin Application Scenario Home UI devices Another Home UI devices UI devices DMC DMC Target devices Target devices Web content Target devices Problem: Unified control and monitoring of networked Targets UI devices • media devices + apps • PCs + laptops • media services + content • phones, PDAs • home automation • TVs, legacy remotes Possible solution: DMC = Distributed Media Center • remote control hub • runs in a PC / STB / gateway 5.6.2007 [email protected] DMC Architecture Browser Midlet thin client application user actions Browser HID UIs TV renderer decoupled IO Midlet IR Remote application Midi device LAN / internet LAN / internet LAN / internet markup RFB custom input - XHTML - XForms - JPG fragm. - eg. bytecode - HTTP REST / XPointer - CSS, SVG - MIDPML - markup (REX) - REX - JavaScript - OSC, MIDI, IR Concrete UI Localization, Personalization, Branding (XML), optional DMC LT S Abstract UI (XML) X Models (XML + DOM, state variables) UPnP oBIX Zeroconf MIDP Web other generics adapter adapter /Bonjour adapter adapter adapters adapter CE devices home control other DMCs cell phones shares media apps XML files media apps automation Macs stores games XMLDB Targets home control VoD presentation automation live streams home studio 5.6.2007 videoVOIP [email protected] DMC Architecture Browser Midlet thin client application user actions Browser HID UIs TV renderer decoupled IO IR Remote Midi device LAN / internet LAN / internet LAN / internet markup RFB custom input - XHTML - XForms - JPG fragm. - eg. bytecode - HTTP REST / XPointer - CSS, SVG - MIDPML - markup (REX) - REX - JavaScript Concrete UI Localization, Personalization, Branding (XML) DMC LT S Abstract UI (XML) X Models (XML + DOM, state variables) Adapters generics CE devices home control other DMCs cell phones shares media apps XML files media apps automation Macs stores games XMLDB Targets home control VoD presentation automation live streams home studio 5.6.2007 videoVOIP [email protected] Compound Model Distributed into • Dynamic infrastructure DOM (zones, devices, services, people, content) • updated by adapters and components • only topmost levels • Virtual models that extend infrastructure DOM • handled by adapters • state variables • Generic XML files hosted by DMC • eg. for RAD + testing Addressing • Dispatcher parses URI to model and resource reference (http://host:port/model#resource) • eg. /dmc/zones#bedroom/TV/channel infra adapter Mutation and Access • REST and/or REX • ui: GET + PUT, adapter: POST + DELETE + PUT • POST /dmc/devices body: <device name=”TV” id=”udn”>...</device> • PUT /dmc/zones#bedroom/tv/channel=5 5.6.2007 [email protected] Remote UIs UI Fragments • extend XHTML controls (currently scripted) • eg. bound list, slider, popup • patterns, microformats / RDF description ? • can be updated without loading entire page • XHR • binding to other controls • bound into micromodel using XPath • eg. bind=”/dmps/device[@id=$current]” micromodel (uDOM compliant) • state, maybe some frequently used items as well • mutated using REX Other things • On-the-fly interaction style change • eg. forms -> direct manipulation • IO decoupling • attach display from mobile phone to TV • continue using mobile keys as input device 5.6.2007 [email protected] Interaction Loop Browser micromodel ConcreteUI XML + DOM REST + XPointer Binding logic Adaptation XSLT + XProc Dispatcher Declarative • XHTML, SVG RemotePort (xhr, ajax, comet) • XSLT + XProc • XPath REX REST XPointer UI markup (mutation) REX (input) • REX Hub • XML fragments RemotePort (server, servlet, sockets) Procedural Dispatcher Adaptation • Java XSLT + XProc • ECMAScript XML + DOM REX AbstractUI Distributed Model REST XPointer, XML XSLT + XProc Adapters devices, services XML files + DBs content, communication 5.6.2007 [email protected] Sample Loop idGroup idDevice <ul id=”idGroup”> <li href=”/zones/home/livingroom” onclick=”httpGET(this)” xhrTarget=”idDevice”>Living Room</li> <li href=”/zones/home/library” onclick=”httpGET(this)” xhrTarget=“idDevice”>Library</li> ... </ul> 5.6.2007 [email protected] Sample Loop Browser 1. Addressing micromodel ConcreteUI - host / model # resource XML + DOM - GET http://dmc/zones#home/livingroom/ Binding logic Dispatcher - loop all models Dispatcher - registered for ”/zones” ? - yes: redirect ”/home/livingroom/” RemotePort (xhr, ajax, comet) REX REST XPointer UI markup 1 (mutation) REX (input) Hub RemotePort (server, servlet, sockets) Adaptation Dispatcher XSLT + XProc XML + DOM REX AbstractUI Distributed Model REST XPointer, XML XSLT + XProc Adapters devices, services XML files + DBs content, communication 5.6.2007 [email protected] Sample Loop Browser 1. Addressing micromodel ConcreteUI - host / model # resource XML + DOM - GET http://dmc/zones#home/livingroom/ Binding logic 2. Fetch XML fragment Dispatcher - from DOM or Adapter or file - select = ”/home/livingroom/” RemotePort (xhr, ajax, comet) <devices> <dev name=”TV” ref=”…”/> REX REST XPointer <dev name=”mediaServer” ref=“…”/> UI markup (mutation) REX (input) <dev name=”lights” ref=”…”/> Hub </devices> RemotePort (server, servlet, sockets) Adaptation Dispatcher XSLT + XProc XML + DOM 2 REX AbstractUI Distributed Model REST XPointer, XML XSLT + XProc Adapters devices, services XML files + DBs content, communication 5.6.2007 [email protected] Sample Loop Browser 1. Addressing micromodel ConcreteUI - host / model # resource XML + DOM - GET http://dmc/zones#home/livingroom/ Binding logic 2. Fetch XML fragment Dispatcher - from DOM or Adapter or file - select = ”/home/livingroom/” RemotePort (xhr, ajax, comet) 3. Transform into abstract UI REX REST XPointer - browserAbstr.xsl (or /session[@id]/abstract) UI markup (mutation) REX (input) - template match= ”devices” Hub <select1> RemotePort (server, servlet, sockets) <item label=”TV” ref=”…” … /> <item label=”mediaServer” ref=“…” … /> <item label=”lights” ref=”…” … /> Adaptation Dispatcher </select1> XSLT + XProc XML + DOM REX AbstractUI Distributed Model REST XPointer, XML XSLT + XProc 3 Adapters devices, services XML files + DBs content, communication 5.6.2007 [email protected] Sample Loop Browser 1. Addressing micromodel ConcreteUI - host / model # resource XML + DOM - GET http://dmc/zones#home/livingroom/ Binding logic 2. Fetch XML fragment Dispatcher - from DOM or Adapter or file - select = ”/home/livingroom/” RemotePort (xhr, ajax, comet) 3. Transform into abstract UI REX REST XPointer - browserAbstr.xsl (or /session[@id]/abstract) UI markup (mutation) REX (input) - <xsl:template match=”devices”/> Hub 4. Transform into concrete UI RemotePort (server, servlet, sockets) 4 - browserConcr.xsl (or /session[@id]/concrete) - <xsl:template match=”select1”/> Adaptation Dispatcher <ul> XSLT + XProc <li href=”…” … >TV</li> XML + DOM <li href=”…” … >Media Server</li> <li href=”…” … >Lights</li> REX AbstractUI Distributed Model </ul> REST XPointer, XML XSLT + XProc Adapters devices, services XML files + DBs content, communication 5.6.2007 [email protected] Result idGroup idDevice idControls <rex> <event target=”idDevice” name=”DOMNodeRemoved”> <ul id=”idDevice”> <li href=”…” onclick=”httpGET(this)” xhrTarget=”idControls”>TV</li> <li href=”…” onclick=”httpGET(this)” xhrTarget=“idControls”>Media Server A</li> ... </ul> </event> </rex> 5.6.2007 [email protected] XProc infra request stylesheets 1. Addressing - host / model # resource - GET http://dmc/zones#home/livingroom/ xinclude 2. Fetch XML fragment select = - from DOM or Adapter or file /model/fragment - select = ”/home/livingroom/” 3. Transform into abstract UI choose - browserAbstr.xsl (or /session[@id]/abstract) count(*) - template match= ”devices” >0 =0 4. Transform into concrete UI identity http-request - browserConcr.xsl (or /session[@id]/concrete) - template match= ”choice” xinclude • 58 lines of markup ! xslt • procedural: - server pipeline - uri + header parser 5.6.2007 [email protected] XProc W3C working draft (April 5 2007) • pipelines of (compound) steps . input and output ports . xinclude, xslt, validate, http-request . load, store, serialize, parse, identity, join, subsequence . xslt2, xquery, formatter • micro-operations . delete, insert, rename, replace, set, (un)wrap, label • conditionals, loops, exceptions • parameters, options • pipeline libraries for example • get UI components from web (eg. icons from Tango) • mashups: get metadata from IMDB or AMG 5.6.2007 [email protected] Techniques Summary XProc declarative glue XSLT to create ui pages / ui fragments / rex mutation, adapters also REX DOM mutation, user input, model state change notifications REST sync ui – model – target, access external devices/services XPointer XPath endian URIs to address resources XPath used in many places 5.6.2007 [email protected] Conclusion Observations • XProc seems to fit well into DMC scenario • usable techniques are available, but might be difficult to find • REST scales well, cleaner code than RPC, modeless, passes firewalls Some concerns • tools for design, debug etc. • security issues • performance issues 5.6.2007 [email protected] DMC Examples Targets Concretized UIs 5.6.2007 [email protected] Thank You ! Questions ? 5.6.2007 [email protected].
Load more

Recommended publications
  • Toward the Discovery and Extraction of Money Laundering Evidence from Arbitrary Data Formats Using Combinatory Reductions
    Toward the Discovery and Extraction of Money Laundering Evidence from Arbitrary Data Formats using Combinatory Reductions Alonza Mumford, Duminda Wijesekera George Mason University [email protected], [email protected] Abstract—The evidence of money laundering schemes exist undetected in the electronic files of banks and insurance firms scattered around the world. Intelligence and law enforcement analysts, impelled by the duty to discover connections to drug cartels and other participants in these criminal activities, require the information to be searchable and extractable from all types of data formats. In this overview paper, we articulate an approach — a capability that uses a data description language called Data Format Description Language (DFDL) extended with higher- order functions as a host language to XML Linking (XLink) and XML Pointer (XPointer) languages in order to link, discover and extract financial data fragments from raw-data stores not co- located with each other —see figure 1. The strength of the ap- Fig. 1. An illustration of an anti-money laundering application that connects proach is grounded in the specification of a declarative compiler to multiple data storage sites. In this case, the native data format at each site for our concrete language using a higher-order rewriting system differs, and a data description language extended with higher-order functions with binders called Combinatory Reduction Systems Extended and linking/pointing abstractions are used to extract data fragments based on (CRSX). By leveraging CRSX, we anticipate formal operational their ontological meaning. semantics of our language and significant optimization of the compiler. Index Terms—Semantic Web, Data models, Functional pro- II.
    [Show full text]
  • O'reilly Xpath and Xpointer.Pdf
    XPath and XPointer John E. Simpson Publisher: O'Reilly First Edition August 2002 ISBN: 0-596-00291-2, 224 pages Referring to specific information inside an XML document is a little like finding a needle in a haystack. XPath and XPointer are two closely related Table of Contents languages that play a key role in XML processing by allowing developers Index to find these needles and manipulate embedded information. By the time Full Description you've finished XPath and XPointer, you'll know how to construct a full Reviews XPointer (one that uses an XPath location path to address document Reader reviews content) and completely understand both the XPath and XPointer features it Errata uses. 1 Table of Content Table of Content ............................................................................................................. 2 Preface............................................................................................................................. 4 Who Should Read This Book?.................................................................................... 4 Who Should Not Read This Book?............................................................................. 4 Organization of the Book............................................................................................ 5 Conventions Used in This Book ................................................................................. 5 Comments and Questions ........................................................................................... 6 Acknowledgments......................................................................................................
    [Show full text]
  • Annotea: an Open RDF Infrastructure for Shared Web Annotations
    Proceedings of the WWW 10th International Conference, Hong Kong, May 2001. Annotea: An Open RDF Infrastructure for Shared Web Annotations Jos´eKahan,1 Marja-Riitta Koivunen,2 Eric Prud’Hommeaux2 and Ralph R. Swick2 1 W3C INRIA Rhone-Alpes 2 W3C MIT Laboratory for Computer Science {kahan, marja, eric, swick}@w3.org Abstract. Annotea is a Web-based shared annotation system based on a general-purpose open RDF infrastructure, where annotations are modeled as a class of metadata.Annotations are viewed as statements made by an author about a Web doc- ument. Annotations are external to the documents and can be stored in one or more annotation servers.One of the goals of this project has been to re-use as much existing W3C technol- ogy as possible. We have reacheditmostlybycombining RDF with XPointer, XLink, and HTTP. We have also implemented an instance of our system using the Amaya editor/browser and ageneric RDF database, accessible through an Apache HTTP server. In this implementation, the merging of annotations with documents takes place within the client. The paper presents the overall design of Annotea and describes some of the issues we have faced and how we have solved them. 1Introduction One of the basic milestones in the road to a Semantic Web [22] is the as- sociation of metadata to content. Metadata allows the Web to describe properties about some given content, even if the medium of this content does not directly provide the necessary means to do so. For example, ametadata schema for digital photos [15] allows the Web to describe, among other properties, the camera model used to take a photo, shut- ter speed, date, and location.
    [Show full text]
  • Advanced XHTML Plug-In for Iserver
    Advanced XHTML Plug-in for iServer Semester work Stefan Malaer <[email protected]> Prof. Dr. Moira C. Norrie Dr. Beat Signer Global Information Systems Group Institute of Information Systems Department of Computer Science 12th October 2005 Copyright © 2005 Global Information Systems Group. Abstract The iServer architecture is an extensible cross-media information platform enabling links between arbitrary typed objects. It provides some fundamental link concepts and is based on a plug-in mechanism to support various media types. The goal of this semester work was to develop a XHTML plug-in for iServer which enables links from XHTML documents to other XHTML documents as well as parts of them. The resulting iServext is a Firefox extension for iServer which provides visualization and authoring functionality for XHTML links. Furthermore, we investigated research in the area of link augmentation and provide an overview of recent technologies. iii iv Contents 1 Introduction 1 2 Augmented Linking 3 2.1 Need for augmented linking ........................... 3 2.1.1 Current link model ............................ 3 2.1.2 Approaches for link augmentation ................... 5 2.2 Related work .................................... 6 2.2.1 Chimera .................................. 6 2.2.2 Hyper-G/Hyperwave ........................... 6 2.2.3 Distributed Link Service ......................... 6 2.2.4 DHM/WWW and Extend Work ..................... 6 2.2.5 HyperScout ................................. 7 2.2.6 Link Visualization with DHTML ..................... 7 2.2.7 Amaya project ............................... 8 2.3 Link integration and authoring ......................... 9 2.4 Link visualization .................................. 11 2.4.1 Today’s link visualization ......................... 11 2.4.2 Possible presentations of link information .............. 11 2.4.3 Examples of link visualization .....................
    [Show full text]
  • Dynamic and Interactive R Graphics for the Web: the Gridsvg Package
    JSS Journal of Statistical Software MMMMMM YYYY, Volume VV, Issue II. http://www.jstatsoft.org/ Dynamic and Interactive R Graphics for the Web: The gridSVG Package Paul Murrell Simon Potter The Unversity of Auckland The Unversity of Auckland Abstract This article describes the gridSVG package, which provides functions to convert grid- based R graphics to an SVG format. The package also provides a function to associate hyperlinks with components of a plot, a function to animate components of a plot, a function to associate any SVG attribute with a component of a plot, and a function to add JavaScript code to a plot. The last two of these provides a basis for adding interactivity to the SVG version of the plot. Together these tools provide a way to generate dynamic and interactive R graphics for use in web pages. Keywords: world-wide web, graphics, R, SVG. 1. Introduction Interactive and dynamic plots within web pages are becomingly increasingly popular, as part of a general trend towards making data sets more open and accessible on the web, for example, GapMinder (Rosling 2008) and ManyEyes (Viegas, Wattenberg, van Ham, Kriss, and McKeon 2007). The R language and environment for statistical computing and graphics (R Development Core Team 2011) has many facilities for producing plots, and it can produce graphics formats that are suitable for including in web pages, but the core graphics facilities in R are largely focused on static plots. This article describes an R extension package, gridSVG, that is designed to embellish and transform a standard, static R plot and turn it into a dynamic and interactive plot that can be embedded in a web page.
    [Show full text]
  • Bibliography of Erik Wilde
    dretbiblio dretbiblio Erik Wilde's Bibliography References [1] AFIPS Fall Joint Computer Conference, San Francisco, California, December 1968. [2] Seventeenth IEEE Conference on Computer Communication Networks, Washington, D.C., 1978. [3] ACM SIGACT-SIGMOD Symposium on Principles of Database Systems, Los Angeles, Cal- ifornia, March 1982. ACM Press. [4] First Conference on Computer-Supported Cooperative Work, 1986. [5] 1987 ACM Conference on Hypertext, Chapel Hill, North Carolina, November 1987. ACM Press. [6] 18th IEEE International Symposium on Fault-Tolerant Computing, Tokyo, Japan, 1988. IEEE Computer Society Press. [7] Conference on Computer-Supported Cooperative Work, Portland, Oregon, 1988. ACM Press. [8] Conference on Office Information Systems, Palo Alto, California, March 1988. [9] 1989 ACM Conference on Hypertext, Pittsburgh, Pennsylvania, November 1989. ACM Press. [10] UNIX | The Legend Evolves. Summer 1990 UKUUG Conference, Buntingford, UK, 1990. UKUUG. [11] Fourth ACM Symposium on User Interface Software and Technology, Hilton Head, South Carolina, November 1991. [12] GLOBECOM'91 Conference, Phoenix, Arizona, 1991. IEEE Computer Society Press. [13] IEEE INFOCOM '91 Conference on Computer Communications, Bal Harbour, Florida, 1991. IEEE Computer Society Press. [14] IEEE International Conference on Communications, Denver, Colorado, June 1991. [15] International Workshop on CSCW, Berlin, Germany, April 1991. [16] Third ACM Conference on Hypertext, San Antonio, Texas, December 1991. ACM Press. [17] 11th Symposium on Reliable Distributed Systems, Houston, Texas, 1992. IEEE Computer Society Press. [18] 3rd Joint European Networking Conference, Innsbruck, Austria, May 1992. [19] Fourth ACM Conference on Hypertext, Milano, Italy, November 1992. ACM Press. [20] GLOBECOM'92 Conference, Orlando, Florida, December 1992. IEEE Computer Society Press. http://github.com/dret/biblio (August 29, 2018) 1 dretbiblio [21] IEEE INFOCOM '92 Conference on Computer Communications, Florence, Italy, 1992.
    [Show full text]
  • XML Pipeline Performance
    XML Pipeline Performance Nigel Whitaker DeltaXML Ltd <[email protected]> Tristan Mitchell DeltaXML Ltd <[email protected]> Abstract This paper considers XML pipeline performance of a case study constructed from real code and data. It extends our original small study into 'Filter Pipeline Performance' on the saxon-help email list. The system used in this case study is a comparison tool for OASIS OpenDocument Text or '.odt' files. We will not describe the code in detail, but rather concentrate on the mechanisms used to interlink the various pipeline components used. These components include XML parsers, XSLT filter stages, XML comparison, Java filters based on the SAX XMLFilter interface and serialization. In the previous study we compared two pipelining techniques; this paper will extend this to consider three mechanisms which can be used to construct pipelines; these are: • The Java API for XML Processing (JAXP) included in Java Standard Edition 1.4 and subsequent releases • The s9api package provided by the Saxon XSLT processor 9.0 and sub- sequent releases • The Calabash implementation of the XProc XML pipeline language Our primary focus is performance and we will look at run times and memory sizes using these technologies. The overall runtime of the complete system will be described, but we will then concentrate on the performance of running a chain of filters (XSLT and Java based) as this is likely to be of moregeneral interest. We will also discuss some optimization techniques we have implemen- ted during the development process and further ideas for future performance improvement work. 1. Introduction In this section we will introduce the system being studied, briefly describe the data and also some aspects of the experimental approach.
    [Show full text]
  • Interactive Topographic Web Mapping Using Scalable Vector Graphics
    University of Nebraska at Omaha DigitalCommons@UNO Student Work 12-1-2003 Interactive topographic web mapping using scalable vector graphics Peter Pavlicko University of Nebraska at Omaha Follow this and additional works at: https://digitalcommons.unomaha.edu/studentwork Recommended Citation Pavlicko, Peter, "Interactive topographic web mapping using scalable vector graphics" (2003). Student Work. 589. https://digitalcommons.unomaha.edu/studentwork/589 This Thesis is brought to you for free and open access by DigitalCommons@UNO. It has been accepted for inclusion in Student Work by an authorized administrator of DigitalCommons@UNO. For more information, please contact [email protected]. INTERACTIVE TOPOGRAPHIC WEB MAPPING USING SCALABLE VECTOR GRAPHICS A Thesis Presented to the Department of Geography-Geology and the Faculty of the Graduate College University of Nebraska in Partial Fulfillment of the Requirements for the Degree Master of Arts University of Nebraska at Omaha by Peter Pavlicko December, 2003 UMI Number: EP73227 All rights reserved INFORMATION TO ALL USERS The quality of this reproduction is dependent upon the quality of the copy submitted. In the unlikely event that the author did not send a complete manuscript and there are missing pages, these will be noted. Also, if material had to be removed, a note will indicate the deletion. Dissertation WWisMng UMI EP73227 Published by ProQuest LLC (2015). Copyright in the Dissertation held by the Author. Microform Edition © ProQuest LLC. All rights reserved. This work is protected against unauthorized copying under Title 17, United States Code ProQuest LLC. 789 East Eisenhower Parkway P.O. Box 1346 Ann Arbor, Ml 48106-1346 THESIS ACCEPTANCE Acceptance for the faculty of the Graduate College, University of Nebraska, in Partial fulfillment of the requirements for the degree Master of Arts University of Nebraska Omaha Committee ----------- Uf.A [JL___ Chairperson.
    [Show full text]
  • Extended Link Visualization with DHTML: the Web As an Open Hypermedia System
    Extended Link Visualization with DHTML: The Web as an Open Hypermedia System Glenn Oberholzer and Erik Wilde Computer Engineering and Networks Laboratory Swiss Federal Institute of Technology, Z¨urich TIK Report 125 January 2002 Abstract The World Wide Web is by far the most successful hypermedia system, its name often being used synonymously for the Internet. However, it is based on a rather restricted hy- permedia model with limited linking functionality. Even though underlying systems may provide a richer data model, there is still the question of how to present this informa- tion in a Web-based interface in an easily understandable way. Assuming an underlying system similar to Topic Maps, which allows storing, managing, and categorizing meta data and links, we propose a presentation of extended links. We try to provide a usable way for users to handle the additional functionality. The mechanism is based on already available technologies like DHTML. It is one facet of our approach to make the Web more interconnected and to work towards a more richly and openly linked Web. Keywords: Electronic publishing (020), Graphic design (029), Hypermedia (036), Internet (045), World Wide Web (084), XLink, Linkbases, DHTML 1 Introduction Compared to many other hypermedia systems [24,11,16], the linking capabilities of the World Wide Web are rather limited. It only makes use of a few concepts of hypermedia. In recent years, however, new recommendations issued by the W3C like XML [3], XLink [10], and XPointer [9], or ISO/IEC’s Topic Maps [19] have tried to overcome this shortcoming. Due to the popularity of the Web, efforts have to be made to integrate and improve the current system with more sophisticated hypermedia concepts.
    [Show full text]
  • Access Control Models for XML
    Access Control Models for XML Abdessamad Imine Lorraine University & INRIA-LORIA Grand-Est Nancy, France [email protected] Outline • Overview on XML • Why XML Security? • Querying Views-based XML Data • Updating Views-based XML Data 2 Outline • Overview on XML • Why XML Security? • Querying Views-based XML Data • Updating Views-based XML Data 3 What is XML? • eXtensible Markup Language [W3C 1998] <files> "<record>! ""<name>Robert</name>! ""<diagnosis>Pneumonia</diagnosis>! "</record>! "<record>! ""<name>Franck</name>! ""<diagnosis>Ulcer</diagnosis>! "</record>! </files>" 4 What is XML? • eXtensible Markup Language [W3C 1998] <files>! <record>! /files" <name>Robert</name>! <diagnosis>! /record" /record" Pneumonia! </diagnosis> ! </record>! /name" /diagnosis" <record …>! …! </record>! Robert" Pneumonia" </files>! 5 XML for Documents • SGML • HTML - hypertext markup language • TEI - Text markup, language technology • DocBook - documents -> html, pdf, ... • SMIL - Multimedia • SVG - Vector graphics • MathML - Mathematical formulas 6 XML for Semi-Structered Data • MusicXML • NewsML • iTunes • DBLP http://dblp.uni-trier.de • CIA World Factbook • IMDB http://www.imdb.com/ • XBEL - bookmark files (in your browser) • KML - geographical annotation (Google Maps) • XACML - XML Access Control Markup Language 7 XML as Description Language • Java servlet config (web.xml) • Apache Tomcat, Google App Engine, ... • Web Services - WSDL, SOAP, XML-RPC • XUL - XML User Interface Language (Mozilla/Firefox) • BPEL - Business process execution language
    [Show full text]
  • SMIL 2.0 — Interactive Multimedia on the Web Lloyd Rutledge
    SMIL 2.0 — Interactive Multimedia on the Web Lloyd Rutledge Multimedia and Human-Computer Interaction Group CWI, Amsterdam, The Netherlands W3C SYMM working group Lynda Hardman, Jacco van Ossenbruggen: CWI Dick Bulterman, Jack Jansen, Sjoerd Mullender: Oratrix W3C SYMM working group http://www.cwi.nl/~media/SMIL/Tutorial/{SMIL-4hr.html} Includes material from the upcoming book "SMIL 2.0 — Interactive Multimedia on the Web" Copyright © 2002, Lloyd Rutledge Synchronized Multimedia Integration Language (SMIL) Main Points Pronounced smile Multimedia for the Web — for multimedia what HTML is for hypertext Integration format for presentable mono-medium formats Structure SMIL 1.0 — W3C Recommendation on 15th June 1998 SMIL 2.0 "meta-language" W3C Recommendation on 7th August 2001 SMIL 2.0 family formats SMIL Profile and SMIL Basic released with SMIL 2.0 SMIL 2.0 family format XHTML+SMIL comes after SMIL 2.0 Main Themes Powerful timing and synchronization Adaptive to users and systems Models a flexible but consistent presentation and user interface SMIL Isn't Flash — Flash is mono-medium animation on steriods MPEG-{4 / 7 / 21} — MPEG looks at content and coding, and player architecture and a whole lot more, but is more media centric than web centric D-HTML — D-HTML uses scripted definitions of local behaviors, without a notion of the presentation's context SMIL 2.0 Profiles What is a Profile? A language for which a browser can be built A combination of modules from the SMIL 2.0 "meta-language" Possibly non-SMIL constructs with SMIL constructs
    [Show full text]
  • XML Projects in Japan and Fujitsu's Approach to Xlink/Xpointer
    UDC 621.395.74:651.55:681.32 XML Projects in Japan and Fujitsu’s Approach to XLink/XPointer VToshimitsu Suzuki VMasatomo Goto (Manuscript received June 2, 2000) The Extensible Markup Language (XML)1) is a markup language developed in response to a recommendation by the World Wide Web Consortium (W3C).2) It is a meta lan- guage used to make an information structure. XML’s original specification is the Stan- dard Generalized Markup Language (SGML).3) Now, XML is used not only as a format language but also as a framework in various areas beyond the SGML field. This paper describes the XML technology trends, the current state of XML technology, and some case studies in Japan and at Fujitsu. This paper also describes HyBrick,4) which is an XML/SGML browser that was demonstrated at SGML’97, and the XLink5)/XPointer6) technology. 1. Introduction verified through these experiments. The specification of XML has been in use by Up to now, XML has been related to infor- the W3C since 1996. XML version 1.0 was released mation technology (IT), and because of the IT as a W3C recommendation in February 1998. revolution it is becoming a secure part of the foun- XML is a meta language for marking up informa- dation of new IT systems. Last year, a lineup of tion. XML’s original specification is the Standard XML parsers and other XML basic software ap- Generalized Markup Language (SGML), which is peared, establishing a development environment used to mark up documents for archiving and re- for application software.
    [Show full text]