DOCSLIB.ORG

Synchronized Multimedia Integration Language (SMIL) Boston Specification

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Synchronized Multimedia Integration Language (SMIL) Boston Specification Synchronized Multimedia Integration Language (SMIL) Boston Specification Synchronized Multimedia Integration Language (SMIL) Boston Specification W3C Working Draft 25 February 2000 This version: http://www.w3.org/TR/2000/WD-smil-boston-20000225 (Other formats: single PostScript file, single PDF file, zip archive) Latest version: http://www.w3.org/TR/smil-boston Previous version: http://www.w3.org/TR/1999/WD-smil-boston-19991115 Editors: Jeff Ayars (RealNetworks), Dick Bulterman (Oratrix), Aaron Cohen (Intel), Erik Hodge (RealNetworks), Philipp Hoschka (W3C), Eric Hyche (RealNetworks), Ken Day (Macromedia), Kenichi Kubota (Panasonic), Rob Lanphier (RealNetworks), Nabil Layaïda (INRIA), Philippe Le Hégaret (W3C), Thierry Michel (W3C), Jacco van Ossenbruggen (CWI), Lloyd Rutledge (CWI), Bridie Saccocio (RealNetworks), Patrick Schmitz (Microsoft), Warner ten Kate (Philips), Ted Wugofski (Gateway). Copyright ©2000 W3C® (MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Abstract This document specifies the "Boston" version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile"). SMIL Boston has the following two design goals: Define a simple XML-based language that allows authors to write interactive multimedia presentations. Using SMIL Boston, an author can describe the temporal behavior of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen. Allow reusing of SMIL syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL Boston components should be used for integrating timing into XHTML [XHTML10]. 1 24 Feb 2000 08:26 Synchronized Multimedia Integration Language (SMIL) Boston Specification Status of this document This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C. This document is the third Working Draft of the specification for the next version of SMIL code-named "Boston". It has been produced as part of the W3C Synchronized Multimedia Activity. The document has been written by the SYMM Working Group (members only). The goals of this group are discussed in the SYMM Working Group charter (members only). Many parts of the document are still preliminary, and do not constitute full consensus within the Working Group. Also, some of the functionality planned for SMIL Boston is not contained in this draft. Many parts are not yet detailed enough for implementation, and other parts are only suitable for highly experimental implementation work. At this point, the W3C SYMM WG seeks input by the public on the concepts and directions described in this specification. Please send your comments to [email protected]. Since it is difficult to anticipate the number of comments that come in, the WG cannot guarantee an individual response to all comments. However, we will study each comment carefully, and try to be as responsive as time permits. This working draft may be updated, replaced or rendered obsolete by other W3C documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". This document is work in progress and does not imply endorsement by the W3C membership. 24 Feb 2000 08:26 2 Synchronized Multimedia Integration Language (SMIL) Boston Specification A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR. Quick Table of Contents 1. About SMIL Boston . 15. 2. Synchronized Multimedia Integration Language (SMIL) Modules . 19. 3. The SMIL Animation Module . 31. 4. SMIL Content Control . 67. 5. SMIL Layout Module . 81. 6. The SMIL Linking Module . 95. 7. The SMIL Media Object Module . 109. 8. The SMIL Metadata Module . 123. 9. SMIL Structure Module . 129. 10. The SMIL Timing and Synchronization Module . 135. 11. Integrating SMIL Timing into Other XML-Based Languages . 233. 12. The SMIL Transition Effects Module . 255. 13. The SMIL Document Object Model Module . 275. 14. SMIL Boston Language Profile . 277. 15. HTML+SMIL Language Profile . 287. 16. Requirements for a SMIL Basic Profile . 299. 17. Baseline Media Formats . 305. Appendix A. References . 309. 3 24 Feb 2000 08:26 Synchronized Multimedia Integration Language (SMIL) Boston Specification Full Table of Contents 1. About SMIL Boston . 15. 1.1 Introduction . 15. 1.2 Acknowledgements . 16. 2. Synchronized Multimedia Integration Language (SMIL) Modules . 19. 2.1 Introduction . 19. 2.2 SMIL Modules . 20. 2.2.1 Animation Module . 21. 2.2.2 Content Control Module . 21. 2.2.3 Layout Module . 22. 2.2.4 Linking Module . 22. 2.2.5 Media Object Module . 23. 2.2.6 Metainformation Module . 23. 2.2.7 Structure Module . 23. 2.2.8 Timing and Synchronization Module . 24. 2.2.9 Transition Effects Module . 25. 2.3 Isomorphism . 25. 2.4 Multimedia Profiles . 27. 2.4.1 Lightweight Presentations Profile . 27. 2.4.2 SMIL-Boston Profile . 27. 2.4.3 SMIL-Basic Profile . 28. 2.4.4 HTML+SMIL Profile . 28. 2.4.5 Web Enhanced Media Profile . 28. 3. The SMIL Animation Module . 31. 3.1 Introduction . 31. 3.2 Overview and terminology . 32. 3.2.1 Basics of animation . 32. 3.2.2 Animation function values . 33. 3.2.3 Symbols used in the semantic descriptions . 34. 3.3 Animation model . 34. 3.3.1 Specifying the animation target . 35. The Target attribute . 35. The Target element . 36. 3.3.2 Specifying the animation function f(t) . 37. Interpolation and indefinite simple durations . 39. Animation function calculation modes . 40. Examples . 42. 3.3.3 Specifying the animation effect F(t) . 44. Repeated animations . 44. Examples . 44. Controlling behavior of repeating animation - Cumulative animation . 45. 24 Feb 2000 08:26 4 Synchronized Multimedia Integration Language (SMIL) Boston Specification Freezing animations . 46. Additive animation . 48. How from, to and by attributes affect additive behavior. 50. Additive and Cumulative animation . 51. Restarting animations . 52. 3.3.4 Handling syntax errors . 52. 3.3.5 The animation sandwich model . 52. 3.3.6 Implications of Timing Model for animation . 55. 3.3.7 Animation function value details . 56. 3.4 Animation elements . 57. 3.4.1 Common syntax DTD definitions . 57. 3.4.2 The animate element . 58. 3.4.3 The set element . 58. 3.4.4 The animateMotion element . 59. 3.4.5 The animateColor element . 62. 3.5 Integrating SMIL Animation into a host language . 63. 3.5.1 Required host language definitions . 63. 3.5.2 Required definitions and constraints on animation targets . 64. Specifying the target element . 64. Target attribute issues . 64. Integrating animateMotion functionality . 65. Example: SVG . 65. 3.5.3 Constraints on manipulating animation elements . 65. 3.5.4 Extending animation . 66. 3.5.5 Error handling semantics . 66. 3.5.6 SMIL Animation namespace . 66. 4. SMIL Content Control . 67. 4.1 Introduction . 67. 4.2 Content Selection . 67. 4.2.1 The <switch> Element . 68. 4.2.2 Predefined Test Attributes . 68. 4.2.3 System Test Attribute In-Line Use . 73. 4.2.4 User Groups . 75. The <user_attributes> element . 75. The <u_group> element . 75. The u_group attribute . 75. 4.3 Presentation Priority/Grouping . 77. 4.4 User-Centered Adaptation . 77. 4.5 Presentation Optimization . 77. 4.5.1 The <prefetch> element . 77. The mediaSize, mediaTime, and bandwidth Attributes . 78. Attribute value syntax . 79. Examples . 79. 5 24 Feb 2000 08:26 Synchronized Multimedia Integration Language (SMIL) Boston Specification 4.6 Open Issues . 80. 5. SMIL Layout Module . 81. 5.1 Introduction . 81. 5.2 Brief overview of SMIL basic layout . 81. 5.3 Extensions to SMIL 1.0 Basic Layout . 82. 5.3.1 Multiple Top-Level Window Support . 83. 5.3.2 Hierarchical Region Layout . 84. 5.4 SMIL basic layout syntax and semantics . 84. 5.4.1 Elements and attributes . 84. The <layout> element . 85. The <region> element . 86. The <root-layout> element . 90. The <top-layout> element . 91. The region attribute . 92. 5.4.2 SMIL basic layout language details . 92. 5.5 Differences from SMIL 1.0 basic layout . 94. 5.6 Open Issues . 94. 6. The SMIL Linking Module . 95. 6.1 Introduction . 95. 6.2 Linking into SMIL documents . 95. 6.2.1 Error handling . 96. 6.3 Link Elements . 96. 6.3.1 Handling of Links in Embedded Documents . 96. 6.3.2 The <a> Element . 97. 6.3.3 The <area> Element . 102. 7. The SMIL Media Object Module . 109. 7.1 Introduction . 109. 7.2 The ref, animation, audio, img, video, text and textstream elements . 109. 7.2.1 Element Attributes . 109. abstract . 110. alt . 110. author . 110. begin . 110. clipBegin (clip-begin) . 110. clipEnd (clip-end) . 112. copyright . 112. longdesc . 112. port . 112. readIndex . 113. rtpformat . 113. src . 113. stripRepeat . 114. 24 Feb 2000 08:26 6 Synchronized Multimedia Integration Language (SMIL) Boston Specification title . 114. transport . 114. type . 114. xml:lang . 115. 7.2.2 Element Content . 115. 7.2.3 Media object initialization: the param element . 115. Attribute definitions . 115. name . 115. value . 115. valuetype . 115. type . 116. Element Description . 116. 7.2.4 The rtpmap element . 117. Attributes . 117. payload . 117. encoding . 117. 7.3 Support for media player extensions . 118. 7.3.1 Appendix A: Changes to SMIL 1.0 Media Object Attributes . 118. clipBegin, clipEnd, clip-begin, clip-end . 118. Handling of new clipBegin/clipEnd syntax in SMIL 1.0 software 119. SDP Attributes . 120. stripRepeat . 121. 7.3.2 Appendix B: Element Content . 121. 7.3.3 Appendix C: New sections . 121. The param element . 121. The rtpmap element . 121. Support for media player extensions . 121. 7.3.4 Appendix D: Backburner . 121. 8. The SMIL Metadata Module .
Load more

Recommended publications
  • Style Sheets CSS
    P1: OSO/OVY P2: OSO/OVY QC: OSO/OVY T1: OSO GTBL013-03 GTBL013-Jackson-v10 July 12, 2006 10:36 CHAPTER 3 Style Sheets CSS As we have learned, HTML markup can be used to indicate both the semantics of a document (e.g., which parts are elements of lists) and its presentation (e.g., which words should be italicized). However, as noted in the previous chapter, it is advisable to use markup predominantly for indicating the semantics of a document and to use a separate mechanism to determine exactly how information contained in the document should be presented. Style sheets provide such a mechanism. This chapter presents basic information about Cascading Style Sheets (CSS), a style sheet technology designed to work with HTML and XML documents. CSS provides a great deal of control over the presentation of a document, but to exercise this control intelligently requires an understanding of a number of features. And, while you as a software developer may not be particularly interested in getting your web page to look “just so,” many web software developers are members of teams that include professional web page designers, some of whom may have precise presentation require- ments. Thus, while I have tried to focus on what I consider key features of CSS, I’ve also included a number of finer points that I believe may be more useful to you in the future than you might expect on first reading. While CSS is used extensively to style HTML documents, it is not the only style- related web technology.
    [Show full text]
  • Presentation of XML Documents
    Presentation of XML Documents Patryk Czarnik Institute of Informatics University of Warsaw XML and Modern Techniques of Content Management – 2012/13 Stylesheets Separation of content and formatting Separating content and formatting According to XML best practices, documents should contain: “pure” content / data markup for structure and meaning (“semantic” or “descriptive” markup) no formatting How to present? “hard-coded” interpretation of known document types, e.g. Libre Office rendering Writer document importing or pasting content into word processor or DTP tool and manual or automatic formatting, e.g. Adobe InDesign approach external style sheets Patryk Czarnik 05 – Presentation XML 2012/13 4 / 1 Idea of stylesheet <person id="102103" position="specialist"><person id="102105" position="assistant"> <first-name>Dawid</first-name> <first-name>Arkadiusz</first-name> <last-name>Paszkiewicz</last-name> <last-name>Gierasimczyk</last-name> <phone type="office">+48223213203</phone> <phone type="office">+48223213213</phone> <phone type="fax">+48223213200</phone> <phone type="mobile">+48501502503</phone> <email>[email protected]</email> <email>[email protected]</email> </person> </person> * font 'Times 10pt' * yellow backgorund * 12pt for name * blue font and border * abbreviation before * italic font for name phone number * typewritter font for email Stylesheets Separation of content and formatting Benefits of content and formatting separation General advantages of descriptive markup better content understanding and easier analysis Ability to present in the same way: the same document after modification another document of the same structure Formatting managed in one place easy to change style of whole class of documents Ability to define many stylesheets for a document class, depending on purpose and expectations: medium (screen / paper / voice) expected number of details (full report / summary) reader preferences (font size, colors, .
    [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]
  • SMIL) Boston Specification W3C Working Draft 3-August-1999
    next contents Synchronized Multimedia Integration Language (SMIL) Boston Specification W3C Working Draft 3-August-1999 This version: http://www.w3.org/1999/08/WD-smil-boston-19990803 Latest version: http://www.w3.org/TR/smil-boston Previous version: http://www.w3.org/AudioVideo/Group/smil-boston-19990723 (W3C members only) Editors: Jeff Ayars (RealNetworks), Aaron Cohen (Intel), Ken Day (Macromedia), Erik Hodge (RealNetworks), Philipp Hoschka (W3C), Rob Lanphier (RealNetworks), Nabil Layaïda (INRIA), Jacco van Ossenbruggen (CWI), Lloyd Rutledge (CWI), Bridie Saccocio (RealNetworks), Patrick Schmitz (Microsoft), Warner ten Kate (Philips), Ted Wugofski (Gateway), Jin Yu (Compaq) Copyright © 1999 W3C ® ( MIT, INRIA, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply. Abstract This document specifies the "Boston" version of the Synchronized Multimedia Integration Language (SMIL, pronounced "smile"). SMIL Boston has the following two design goals: ● Define a simple XML-based language that allows authors to write interactive multimedia presentations. Using SMIL Boston, an author can describe the temporal behavior of a multimedia presentation, associate hyperlinks with media objects and describe the layout of the presentation on a screen. ● Allow reusing of SMIL syntax and semantics in other XML-based languages, in particular those who need to represent timing and synchronization. For example, SMIL Boston components should be used for integrating timing into XHTML. Status of this document This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C. This document is the first working draft of the specification for the next version of SMIL code-named "Boston".
    [Show full text]
  • Ontology Matching • Semantic Social Networks and Peer-To-Peer Systems
    The web: from XML to OWL Rough Outline 1. Foundations of XML (Pierre Genevès & Nabil Layaïda) • Core XML • Programming with XML Development of the future web • Foundations of XML types (tree grammars, tree automata) • Tree logics (FO, MSO, µ-calculus) • Expressing information ! Languages • A taste of research: introduction to some grand challenges • Manipulating it ! Algorithms 2. Semantics of knowledge representation on the web (Jérôme Euzenat & • in the most correct, efficient and ! Logic Marie-Christine Rousset) meaningful way ! Semantics • Semantic web languages (URI, RDF, RDFS and OWL) • Querying RDF and RDFS (SPARQL) • Querying data though ontologies (DL-Lite) • Ontology matching • Semantic social networks and peer-to-peer systems 1 / 8 2 / 8 Foundations of XML Semantic web We will talk about languages, algorithms, and semantics for efficiently and meaningfully manipulating formalised knowledge. We will talk about languages, algorithms, and programming techniques for efficiently and safely manipulating XML data. You will learn about: You will learn about: • Expressing formalised knowledge on the semantic web (RDF) • Tree structured data (XML) ! Syntax and semantics ! Tree grammars & validation You will not learn about: • Expressing ontologies on the semantic • XML programming (XPath, XSLT...) You will not learn about: web (RDFS, OWL, DL-Lite) • Tagging pictures ! Queries & transformations ! Syntax and semantics • Hacking CGI scripts ! Reasoning • Sharing MP3 • Foundational theory & tools • HTML • Creating facebook ! Regular expressions
    [Show full text]
  • Refactoring XSLT
    XSLT and XQuery September 19, 2019 Refactoring XSLT Priscilla Walmsley, Datypic, Inc. Class Outline Introduction ......................................................................................................................................2 Cleaning Up......................................................................................................................................9 Improving Code Quality..................................................................................................................14 Other Improvements.......................................................................................................................21 Introduction 2 Obligatory Wikipedia Quote 3 Code refactoring is the process of restructuring existing computer code - changing the factoring - without changing its external behavior. Refactoring improves nonfunctional attributes of the software. Advantages include improved code readability and reduced complexity; these can improve source code maintainability and create a more expressive internal architecture or object model to improve extensibility. Typically, refactoring applies a series of standardised basic micro-refactorings, each of which is (usually) a tiny change in a computer program's source code that either preserves the behaviour of the software, or at least does not modify its conformance to functional requirements. Many development environments provide automated support for performing the mechanical aspects of these basic refactorings. If done extremely well, code
    [Show full text]
  • SVG-Based Knowledge Visualization
    MASARYK UNIVERSITY FACULTY}w¡¢£¤¥¦§¨ OF I !"#$%&'()+,-./012345<yA|NFORMATICS SVG-based Knowledge Visualization DIPLOMA THESIS Miloš Kaláb Brno, spring 2012 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Advisor: RNDr. Tomáš Gregar Ph.D. ii Acknowledgement I would like to thank RNDr. Tomáš Gregar Ph.D. for supervising the thesis. His opinions, comments and advising helped me a lot with accomplishing this work. I would also like to thank to Dr. Daniel Sonntag from DFKI GmbH. Saarbrücken, Germany, for the opportunity to work for him on the Medico project and for his supervising of the thesis during my erasmus exchange in Germany. Big thanks also to Jochen Setz from Dr. Sonntag’s team who worked on the server background used by my visualization. Last but not least, I would like to thank to my family and friends for being extraordinary supportive. iii Abstract The aim of this thesis is to analyze the visualization of semantic data and sug- gest an approach to general visualization into the SVG format. Afterwards, the approach is to be implemented in a visualizer allowing user to customize the visualization according to the nature of the data. The visualizer was integrated as an extension of Fresnel Editor. iv Keywords Semantic knowledge, SVG, Visualization, JavaScript, Java, XML, Fresnel, XSLT v Contents Introduction . .3 1 Brief Introduction to the Related Technologies ..........5 1.1 XML – Extensible Markup Language ..............5 1.1.1 XSLT – Extensible Stylesheet Lang.
    [Show full text]
  • Content Processing Framework Guide (PDF)
    MarkLogic Server Content Processing Framework Guide 2 MarkLogic 9 May, 2017 Last Revised: 9.0-7, September 2018 Copyright © 2019 MarkLogic Corporation. All rights reserved. MarkLogic Server Version MarkLogic 9—May, 2017 Page 2—Content Processing Framework Guide MarkLogic Server Table of Contents Table of Contents Content Processing Framework Guide 1.0 Overview of the Content Processing Framework ..........................................7 1.1 Making Content More Useful .................................................................................7 1.1.1 Getting Your Content Into XML Format ....................................................7 1.1.2 Striving For Clean, Well-Structured XML .................................................8 1.1.3 Enriching Content With Semantic Tagging, Metadata, etc. .......................8 1.2 Access Internal and External Web Services ...........................................................8 1.3 Components of the Content Processing Framework ...............................................9 1.3.1 Domains ......................................................................................................9 1.3.2 Pipelines ......................................................................................................9 1.3.3 XQuery Functions and Modules .................................................................9 1.3.4 Pre-Commit and Post-Commit Triggers ...................................................10 1.3.5 Creating Custom Applications With the Content Processing Framework 11 1.4
    [Show full text]
  • Will HTML 5 Restandardize the Web?
    TECHNOLOGY NEWS Will HTML 5 Restandardize the Web? Steven J. Vaughan-Nichols The World Wide Web Consortium is developing HTML 5 as a stan- dard that provides Web users and developers with enhanced func- tionality without using the proprietary technologies that have become popular in recent years. n theory, the Web is a resource enhanced functionality without using “Microsoft is investing heavily in that is widely and uniformly proprietary technologies. the W3C HTML 5 effort, working with usable across platforms. As Indeed, pointed out Google our competitors and the Web commu- such, many of the Web’s researcher Ian Hickson, one of the nity at large. We want to implement key technologies and archi- W3C’s HTML 5 editors, “One of our ratified, thoroughly tested, and stable Itectural elements are open and goals is to move the Web away from standards that can help Web interop- platform-independent. proprietary technologies.” erability,” said Paul Cotton, cochair of However, some vendors have The as-yet-unapproved standard the W3C HTML Working Group and developed their own technologies takes HTML from simply describing Microsoft’s group manager for Web that provide more functionality than the basics of a text-based Web to creat- services standards and partners in Web standards—such as the ability to ing and presenting animations, audio, the company’s Interoperability Strat- build rich Internet applications. mathematical equations, typefaces, egy Team. Adobe System’s Flash, Apple’s and video, as well as providing offline At the same time though, Web QuickTime, and Microsoft’s Silverlight functionality. It also enables geoloca- companies say their proprietary tech- are examples of such proprietary tion, a rich text-editing model, and nologies are already up and running, formats.
    [Show full text]
  • Webwatch Final Report
    British Library Research and Innovation Report 146 WebWatching UK Web Communities: Final Report For The WebWatch Project Brian Kelly and Ian Peacock British Library Research and Innovation Centre 1999 Abstract This document is the final report for the WebWatch project. The aim of the project was to develop and use robot software for analysing and profiling Web sites within various UK communities and to report on the findings. This document reviews the original bid, gives a background to robot software, describes the robot software used by the WebWatch project, and summaries the conclusions gained from the WebWatch trawls. A list of recommendations for further work in this area is given. The appendices include a number of the reports which have been produced which describe the main trawls carried out by the project. Author(s) Brian Kelly and Ian Peacock, UKOLN (UK Office for Library and Information Networking). Brian Kelly is UK Web Focus at UKOLN, the University of Bath. Brian managed the WebWatch project. Ian Peacock is WebWatch Computer Officer at UKOLN, the University of Bath. Ian was responsible for software development and analysis and producing reports. Disclaimer The opinions expressed in this report are those of the authors and not necessarily those of the British Library. Grant Number RIC/G/383 Availability of this Report British Library Research and Innovation Reports are published by the British Library Research and Innovation Centre and may be purchased as photocopies or microfiche from the British Thesis Service, British Library Document Supply Centre, Boston Spa, Wetherby, West Yorkshire LS23 7BQ, UK. In addition this report is freely available on the World Wide Web at the address <URL: http://www.ukoln.ac.uk/web-focus/webwatch/reports/final/>.
    [Show full text]
  • There's a Lot to Know About XML, and It S Constantly Evolving. but You Don't
    < Day Day Up > • Table of Contents • Index • Reviews • Reader Reviews • Errata • Academic XML in a Nutshell, 3rd Edition By Elliotte Rusty Harold, W. Scott Means Publisher: O'Reilly Pub Date: September 2004 ISBN: 0-596-00764-7 Pages: 712 There's a lot to know about XML, and it s constantly evolving. But you don't need to commit every syntax, API, or XSLT transformation to memory; you only need to know where to find it. And if it's a detail that has to do with XML or its companion standards, you'll find it--clear, concise, useful, and well-organized--in the updated third edition of XML in a Nutshell. < Day Day Up > < Day Day Up > • Table of Contents • Index • Reviews • Reader Reviews • Errata • Academic XML in a Nutshell, 3rd Edition By Elliotte Rusty Harold, W. Scott Means Publisher: O'Reilly Pub Date: September 2004 ISBN: 0-596-00764-7 Pages: 712 Copyright Preface What This Book Covers What's New in the Third Edition Organization of the Book Conventions Used in This Book Request for Comments Acknowledgments Part I: XML Concepts Chapter 1. Introducing XML Section 1.1. The Benefits of XML Section 1.2. What XML Is Not Section 1.3. Portable Data Section 1.4. How XML Works Section 1.5. The Evolution of XML Chapter 2. XML Fundamentals Section 2.1. XML Documents and XML Files Section 2.2. Elements, Tags, and Character Data Section 2.3. Attributes Section 2.4. XML Names Section 2.5. References Section 2.6. CDATA Sections Section 2.7.
    [Show full text]
  • D3.3 Workshop Report
    Ref. Ares(2011)1319643 - 07/12/2011 OMWeb Open Media Web Deliverable N° D3.3 Standardisation Workshop report 3 December 2011 D3.3 Standardisation Workshop Report 3 Page 1 of 71 Standardisation Workshop Report 3 Name, title and organisation of the scientific representative of the project's coordinator1: Dr Philipp Hoschka Tel: +33-4-92385077 Fax: +33-4-92385011 E-mail: [email protected] Project website2 address: http://openmediaweb.eu/ Project Grant Agreement number 248687 Project acronym: OMWeb Project title: Open Media Web Funding Scheme: Coordination & Support Action Date of latest version of Annex I against which the August 15, 2009 assessment will be made: Deliverable number: D3.3 Deliverable title Standardisation Workshop Report 3 Contractual Date of Delivery: M24 Actual Date of Delivery: December 5, 2011 Editor (s): François Daoust Author (s): François Daoust Reviewer (s): Dr. Philipp Hoschka Participant(s): ERCIM/W3C Work package no.: 3 Work package title: Standardisation Work package leader: François Daoust Work package participants: ERCIM/W3C Distribution: PU Version/Revision (Draft/Final): Version 1 Total N° of pages (including cover): 71 Keywords: HTML5, Games, Standardisation, W3C 1 Usually the contact person of the coordinator as specified in Art. 8.1. of the grant agreement 2 The home page of the website should contain the generic European flag and the FP7 logo which are available in electronic format at the Europa website (logo of the European flag: http://europa.eu/abc/symbols/emblem/index_en.htm ; logo of the 7th FP: http://ec.europa.eu/research/fp7/index_en.cfm?pg=logos). The area of activity of the project should also be mentioned.
    [Show full text]