DOCSLIB.ORG

Differences from HTML4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Differences from HTML4 Differences from HTML4 W3C Working Draft 28 May 2013 This Version: http://www.w3.org/TR/2013/WD-html5-diff-20130528/ Latest Version: http://www.w3.org/TR/html5-diff/ Latest Editor's Draft: https://rawgithub.com/whatwg/html-differences/master/Overview.html Participate: File a bug (open bugs) Version History: https://github.com/whatwg/html-differences/commits Previous Versions: http://www.w3.org/TR/2012/WD-html5-diff-20121025/ http://www.w3.org/TR/2012/WD-html5-diff-20120329/ http://www.w3.org/TR/2011/WD-html5-diff-20110525/ http://www.w3.org/TR/2011/WD-html5-diff-20110405/ http://www.w3.org/TR/2011/WD-html5-diff-20110405/ http://www.w3.org/TR/2011/WD-html5-diff-20110113/ http://www.w3.org/TR/2010/WD-html5-diff-20101019/ http://www.w3.org/TR/2010/WD-html5-diff-20100624/ http://www.w3.org/TR/2010/WD-html5-diff-20100304/ http://www.w3.org/TR/2009/WD-html5-diff-20090825/ http://www.w3.org/TR/2009/WD-html5-diff-20090423/ http://www.w3.org/TR/2009/WD-html5-diff-20090212/ http://www.w3.org/TR/2008/WD-html5-diff-20080610/ http://www.w3.org/TR/2008/WD-html5-diff-20080122/ Editor: Simon Pieters (Opera Software ASA) <[email protected]> Previous Editor: Anne van Kesteren <[email protected]> Copyright © 2013 W3C® (MIT, ERCIM, Keio, Beihang), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract HTML is the core language of the World Wide Web. The W3C publishes HTML5 and HTML5.1. The WHATWG publishes HTML, which is a rough superset of W3C HTML5.1. "Differences from HTML4" describes the differences of the HTML specifications from those of HTML4, and calls out cases where they differ from each other. This document may not provide accurate information, as the specifications are still actively in development. When in doubt, always check the specifications themselves. [HTML5] [HTML5NIGHTLY] [HTML] Status of This Document This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/. This is the 28 May 2013 W3C Working Draft produced by the HTML Working Group, part of the HTML Activity. The Working Group intends to publish this document as a Working Group Note. The appropriate forum for comments is W3C Bugzilla. (public- [email protected], a mailing list with a public archive, is no longer used for tracking comments.) Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress. This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy. Table of Contents 1 Introduction 1.1 Scope of This Document 1.2 History of HTML 1.3 Open Issues 1.4 Backward Compatibility 1.5 Development Model 2 Syntax 2.1 Character Encoding 2.2 The Doctype 2.3 MathML and SVG 2.4 Miscellaneous 3 Language 3.1 New Elements 3.2 New Attributes 3.3 Changed Elements 3.4 Changed Attributes 3.5 Obsolete Elements 3.6 Obsolete Attributes 4 Content Model 5 APIs 5.1 New APIs 5.2 Changed APIs 5.3 Extensions to Document 5.4 Extensions to HTMLElement 5.5 Extensions to Other Interfaces 5.6 Obsolete APIs 6 HTML Changelogs 6.1 Changes from 14 September 2012 to 6 May 2013 6.2 Changes from 29 March 2012 to 14 September 2012 6.3 Changes from 25 May 2011 to 29 March 2012 6.4 Changes from 5 April 2011 to 25 May 2011 6.5 Changes from 13 January 2011 to 5 April 2011 6.6 Changes from 19 October 2010 to 13 January 2011 6.7 Changes from 24 June 2010 to 19 October 2010 6.8 Changes from 4 March 2010 to 24 June 2010 6.9 Changes from 25 August 2009 to 4 March 2010 6.10 Changes from 23 April 2009 to 25 August 2009 6.11 Changes from 12 February 2009 to 23 April 2009 6.12 Changes from 10 June 2008 to 12 February 2009 6.13 Changes from 22 January 2008 to 10 June 2008 Acknowledgments References 1 Introduction 1.1 Scope of This Document This document covers the W3C HTML5 specification, W3C HTML5.1 specification, and the WHATWG HTML standard. For readability, these are referred to as if they were a single specification: "the HTML specification" or simply "HTML" when something applies equally to all of them; otherwise, they are called out explicitly. 1.2 History of HTML HTML has been in continuous evolution since it was introduced to the Internet in the early 1990s. Some features were introduced in specifications; others were introduced in software releases. In some respects, implementations and Web developer practices have converged with each other and with specifications and standards, but in other ways, they have diverged. HTML4 became a W3C Recommendation in 1997. While it continues to serve as a rough guide to many of the core features of HTML, it does not provide enough information to build implementations that interoperate with each other and, more importantly, with Web content. The same goes for XHTML1, which defines an XML serialization for HTML4, and DOM Level 2 HTML, which defines JavaScript APIs for both HTML and XHTML. HTML replaces these documents. [DOM2HTML] [HTML4] [XHTML1] The HTML specification reflects an effort, started in 2004, to study contemporary HTML implementations and Web content. The specification: 1. Defines a single language called HTML which can be written in HTML syntax and in XML syntax. 2. Defines detailed processing models to foster interoperable implementations. 3. Improves markup for documents. 4. Introduces markup and APIs for emerging idioms, such as Web applications. 1.3 Open Issues The contents of HTML, as well as the contents of this document which depend on HTML, are still being discussed on the HTML Working Group and WHATWG mailing lists. Open issues for WHATWG HTML, see "Issues:" at the top of the specification. The specification also has annotation boxes in the margin which can link to bugs. Open issues for W3C HTML5 and W3C HTML5.1, see the "Status of This Document" section. 1.4 Backward Compatibility HTML is defined in a way that is backward compatible with the way user agents handle content. To keep the language relatively simple for Web developers, several older elements and attributes are not included, as outlined in the other sections of this document, such as presentational elements that are better handled using CSS. User agents, however, will always have to support these older elements and attributes. This is why the HTML specification clearly separates requirements for Web developers (referred to as "authors" in the specification) and user agents; for instance, this means that Web developers cannot use the isindex or the plaintext element, but user agents are required to support them in a way that is compatible with how these elements need to behave for compatibility with Web content. Since HTML has separate conformance requirements for Web developers and user agents there is no longer a need for marking features "deprecated". 1.5 Development Model The HTML4 specification reached Recommendation status before it was completely implemented in user agents. HTML4 still is not completely implemented, because it contains various bugs that have been fixed in the current HTML specification, which user agents are much closer to implementing than HTML4. The WHATWG HTML standard is under continual development where bugs are fixed and new features are introduced over time. Features can also be removed from the specification if they lack implementor interest, are not being used by Web developers, or for other reasons. The WHATWG does not publish frozen snapshots. The W3C HTML5 specification is trying to reach Recommendation status. New features are generally not added unless they are implemented by at least two browsers and have tests demonstrating interoperability. Minor bug fixes can be applied. This means that W3C HTML5 may contain bugs that have been fixed in WHATWG HTML or W3C HTML5.1, or both. The W3C HTML5.1 specification is similar to WHATWG HTML: it is under continual development where bugs are fixed and new features are introduced over time, and features can be removed from the specification for the same reasons as with WHATWG HTML. It cherry-picks changes from the WHATWG HTML standard and also gets direct changes. It is expected to eventually go through the same procedure as W3C HTML5, and then a new version will be minted. 2 Syntax HTML defines a syntax, referred to as "the HTML syntax", that is mostly compatible with HTML4 and XHTML1 documents published on the Web, but is not compatible with the more esoteric SGML features of HTML4, such as processing instructions and shorthand markup as these are not supported by most user agents. Documents using the HTML syntax are served with the text/html media type. HTML also defines detailed parsing rules (including "error handling") for this syntax which are largely compatible with HTML4-era implementations.
Load more

Recommended publications
  • GS1 Digital Link Standard (DRAFT) Enabling Consistent Representation of GS1 Identification Keys Within Web Addresses to Link to Online Information and Services
    GS1 Digital Link Standard (DRAFT) enabling consistent representation of GS1 identification keys within web addresses to link to online information and services Release [ToBe]1.1, Draft, 10 June 2019 IMPORTANT Disclaimer applicable to this Community Review public draft This document is a DRAFT, a work in progress and NOT the final GS1 standard. This document is for review only and it is provided "as is". GS1 does not make any representation or warranty, express or implied, including, but not limited to, warranties of merchantability, fitness for a particular purpose or use, non-infringement, or title; that the contents of the document are suitable for specific purposes; nor that the implementation of such contents will not infringe any third party patents, copyrights, trademarks or other rights. Furthermore, GS1 assumes no liability whatsoever for any inadvertent errors or omissions that may appear in the document. In no event shall GS1 be liable for any direct, indirect, special or consequential damages arising out of any use of the document or the performance or implementation of the contents thereof. Although the standard development process is in progress and governed by the GS1 Intellectual Property Policy, intellectual property right issues could occur any time. The document itself cannot infringe patent rights, but the implementation thereof could. Therefore, if you implement the draft standard contained in the document, you do so entirely at your own risk. Implementers and distributors of software products are encouraged to provide feedback, but should consult with their own attorneys, and form their own conclusions concerning the implementability and possible infringement of third-party rights.
    [Show full text]
  • La Promotion Du Web Ouvert a Bien Changé Mais Mozilla Est Toujours Là
    La promotion du Web Ouvert a bien changé mais Mozilla est toujours là Promouvoir le Web ouvert est l’une des missions de Mozilla. Mission parfaitement assumée et réussie il y a quelques années avec l’avènement de Firefox qui obligea Internet Explorer à quitter son arrogance pour rentrer dans le rang et se montrer plus respectueux des standards et donc des internautes. Sauf qu’aujourd’hui la donne a sensiblement changé. Avec la mobilité, les stores, les apps, les navigateurs intégrés, etc. c’est en effet un Web bien plus complexe qui se présente devant nous. Un Web enthousiasmant[1] mais plein d’embûches pour ceux qui sont attachés à son ouverture et à sa neutralité. C’est tout l’objet de ce très intéressant récent billet du développeur Mozilla Robert O’Callahan. Des changements dans la façon de promouvoir le Web Ouvert Shifts In Promoting The Open Web Robert O’Callahan – 30 septembre 201 – Blog personnel (Traduction Framalang : Antistress et Goofy) Historiquement Mozilla a dépensé pas mal d’énergie pour promouvoir l’usage du « Web ouvert » plutôt que de plateformes propriétaires et de code spécifique à des navigateurs non standards (IE6). Cette évangélisation reste nécessaire mais le paysage s’est modifié et je pense que notre discours doit s’adapter. Les plateformes dont nous devons nous préoccuper ont beaucoup changé. Au lieu de WPF, Slivertlight and Flash, les outils propriétaires pour développeurs avec lesquelles il faut rivaliser dorénavant sont iOS et Android. En conséquence, les fonctionnalités que le Web doit intégrer sont à présent orientées vers la mobilité.
    [Show full text]
  • Consonant Characters and Inherent Vowels
    Global Design: Characters, Language, and More Richard Ishida W3C Internationalization Activity Lead Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 1 Getting more information W3C Internationalization Activity http://www.w3.org/International/ Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 2 Outline Character encoding: What's that all about? Characters: What do I need to do? Characters: Using escapes Language: Two types of declaration Language: The new language tag values Text size Navigating to localized pages Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 3 Character encoding Character encoding: What's that all about? Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 4 Character encoding The Enigma Photo by David Blaikie Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 5 Character encoding Berber 4,000 BC Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 6 Character encoding Tifinagh http://www.dailymotion.com/video/x1rh6m_tifinagh_creation Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 7 Character encoding Character set Character set ⴰ ⴱ ⴲ ⴳ ⴴ ⴵ ⴶ ⴷ ⴸ ⴹ ⴺ ⴻ ⴼ ⴽ ⴾ ⴿ ⵀ ⵁ ⵂ ⵃ ⵄ ⵅ ⵆ ⵇ ⵈ ⵉ ⵊ ⵋ ⵌ ⵍ ⵎ ⵏ ⵐ ⵑ ⵒ ⵓ ⵔ ⵕ ⵖ ⵗ ⵘ ⵙ ⵚ ⵛ ⵜ ⵝ ⵞ ⵟ ⵠ ⵢ ⵣ ⵤ ⵥ ⵯ Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 8 Character encoding Coded character set 0 1 2 3 0 1 Coded character set 2 3 4 5 6 7 8 9 33 (hexadecimal) A B 52 (decimal) C D E F Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 9 Character encoding Code pages ASCII Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 10 Character encoding Code pages ISO 8859-1 (Latin 1) Western Europe ç (E7) Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 11 Character encoding Code pages ISO 8859-7 Greek η (E7) Copyright © 2005 W3C (MIT, ERCIM, Keio) slide 12 Character encoding Double-byte characters Standard Country No.
    [Show full text]
  • Rdfa in XHTML: Syntax and Processing Rdfa in XHTML: Syntax and Processing
    RDFa in XHTML: Syntax and Processing RDFa in XHTML: Syntax and Processing RDFa in XHTML: Syntax and Processing A collection of attributes and processing rules for extending XHTML to support RDF W3C Recommendation 14 October 2008 This version: http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014 Latest version: http://www.w3.org/TR/rdfa-syntax Previous version: http://www.w3.org/TR/2008/PR-rdfa-syntax-20080904 Diff from previous version: rdfa-syntax-diff.html Editors: Ben Adida, Creative Commons [email protected] Mark Birbeck, webBackplane [email protected] Shane McCarron, Applied Testing and Technology, Inc. [email protected] Steven Pemberton, CWI Please refer to the errata for this document, which may include some normative corrections. This document is also available in these non-normative formats: PostScript version, PDF version, ZIP archive, and Gzip’d TAR archive. The English version of this specification is the only normative version. Non-normative translations may also be available. Copyright © 2007-2008 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract The current Web is primarily made up of an enormous number of documents that have been created using HTML. These documents contain significant amounts of structured data, which is largely unavailable to tools and applications. When publishers can express this data more completely, and when tools can read it, a new world of user functionality becomes available, letting users transfer structured data between applications and web sites, and allowing browsing applications to improve the user experience: an event on a web page can be directly imported - 1 - How to Read this Document RDFa in XHTML: Syntax and Processing into a user’s desktop calendar; a license on a document can be detected so that users can be informed of their rights automatically; a photo’s creator, camera setting information, resolution, location and topic can be published as easily as the original photo itself, enabling structured search and sharing.
    [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]
  • HTML5 Favorite Twitter Searches App Browser-Based Mobile Apps with HTML5, CSS3, Javascript and Web Storage
    Androidfp_19.fm Page 1 Friday, May 18, 2012 10:32 AM 19 HTML5 Favorite Twitter Searches App Browser-Based Mobile Apps with HTML5, CSS3, JavaScript and Web Storage Objectives In this chapter you’ll: ■ Implement a web-based version of the Favorite Twitter Searches app from Chapter 5. ■ Use HTML5 and CSS3 to implement the interface of a web app. ■ Use JavaScript to implement the logic of a web app. ■ Use HTML5’s Web Storage APIs to store key-value pairs of data that persist between executions of a web app. ■ Use a CSS reset to remove all browser specific HTML- element formatting before styling an HTML document’s elements. ■ Save a shortcut for a web app to your device’s home screen so you can easily launch a web app. = DRAFT: © Copyright 1992–2012 by Deitel & Associates, Inc. All Rights Reserved. Androidfp_19.fm Page 2 Friday, May 18, 2012 10:32 AM 2 Chapter 19 HTML5 Favorite Twitter Searches App 19.1 Introduction 19.5 Building the App 19.2 Test-Driving the Favorite Twitter 19.5.1 HTML5 Document Searches App 19.5.2 CSS 19.5.3 JavaScript 19.3 Technologies Overview Outline 19.6 Wrap-Up 19.1 Introduction The Favorite Twitter Searches app from Chapter 5 allowed users to save their favorite Twit- ter search strings with easy-to-remember, user-chosen, short tag names. Users could then conveniently follow tweets on their favorite topics. In this chapter, we reimplement the Fa- vorite Twitter Searches app as a web app, using HTML5, CSS3 and JavaScript.
    [Show full text]
  • An Investigation Into World Wide Web Publishing with the Hypertext Markup Language Eric Joseph Cohen
    Rochester Institute of Technology RIT Scholar Works Theses Thesis/Dissertation Collections 11-1-1995 An Investigation into world wide web publishing with the hypertext markup language Eric Joseph Cohen Follow this and additional works at: http://scholarworks.rit.edu/theses Recommended Citation Cohen, Eric Joseph, "An Investigation into world wide web publishing with the hypertext markup language" (1995). Thesis. Rochester Institute of Technology. Accessed from This Thesis is brought to you for free and open access by the Thesis/Dissertation Collections at RIT Scholar Works. It has been accepted for inclusion in Theses by an authorized administrator of RIT Scholar Works. For more information, please contact [email protected]. An Investigation into World Wide Web Publishing with the Hypertext Markup Language by Eric Joseph Cohen A thesis submitted in partial fulfillment of the requirements for the degree of Master of Science in the School of Printing Management and Sciences in the College of Imaging Arts and Sciences of the Rochester Institute of Technology November 1995 Thesis Advisor: Professor Frank Romano School of Printing Management and Sciences Rochester Institute of Technology Rochester, New York Certificate of Approval Master1s Thesis This is to certify that the Master's Thesis of Eric joseph Cohen With a major in Graphic Arts Publishing has been approved by the Thesis Committee as satisfactory for the thesis requirement for the Master of Science degree at the convocation of November 1995 Thesis Committee: Frank Romano Thesis Advisor Marie Freckleton Graduate Program Coordinator C. Harold Goffin Director or Designate Title of Thesis: An Investigation into World Wide Web Publishing with the Hypertext Markup Language September 12, 1995 I, Eric Joseph Cohen, hereby grant permission to the Wallace Memorial Library of RIT to reproduce my thesis in whole or in part.
    [Show full text]
  • Scott Guthrie Keynote Speaker at NDC 2011 See Agenda at P.42-43
    For software developers and leaders NDC motivates Unit 4, Agresso see why at p.28 Scott Guthrie Keynote Speaker at NDC 2011 see Agenda at p.42-43 The Big Wall: Who needs How to Bring a Huge a service bus, Product Backlog anyway? Down to Size by Udi Dahan by Mitch Lacey ALSO FEATURING: IAN ROBINSON ANDERS NORÅS ROD PADDOCK GASPAR NAGY JONAS BANDI JEFF WILCOX GREG SHACKLES DOMINICK BAIER JON SKEET GILL CLEEREN GARY SHORT BILLY HOLLIS MARK SEEMANN SCOTT bellware NORWEGIAN DEVELOPERS CONFERENCE 2011 Oslo Spektrum, Oslo June 8 -10th Navn: Hege Lidenskap: Spreke løsningskonsepter Jobb: Senior Business Consultant Navn: Terje Lidenskap: SharePoint Jobb: Senior Software Engineer FOTO: BO MATHISEN Bli en del av vårt sterke fagmiljø innen samhandling og SharePoint Steria er blitt kåret til en av Norges beste arbeidsplasser fire år på rad. Det er ikke uten grunn. Mye skyldes de gode utviklingsmulighetene. Mye skyldes de utfordrende prosjektene. Mye skyldes det sterke og gode fagmiljøet. Velkommen til et av Europas største Vårt fagmiljø innen samhandling og informasjons- Spennende utfordringer it-konsulentselskaper håndtering er trolig et av Nord-Europas sterkeste. Vi er Steria er en kunnskapsbedrift. Vi lever av å gi gode Det har skjedd mye siden vi etablerte oss i 1969 i EMC Documentum partner og den eneste leverandøren råd om ledelse og it. Basert på våre sterke fagmiljøer Paris. Vi er nå et av Europas 10 største it-konsulent- som har godkjent Noark 5 kjerne for Documentum med bistår vi en rekke av Norges største virksomheter innen selskaper med 20 000 medarbeidere i 16 land og sakarkiv.
    [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]
  • Next Media Deliverable Template
    WP 1 AND EREADING AND D 1.1.4.1 STATE-OF-THE-ART-STANDARDS Deliverable number 1.1.4.1 State-of-the art, html5-standard Author(s): Olli Nurmi Confidentiality: Public Date and status: 7.9.2011 - Status: Version 1.0 This work was supported by TEKES as part of the next Media programme of TIVIT (Finnish Strategic Centre for Science, Technology and Innovation in the field of ICT) Next Media - a Tivit Programme Phase 2 (1.1-31.12.2011) Version history: Version Date State Author(s) OR Remarks (draft/ /update/ final) Editor/Contributors 0.9 30.6.2011 draft Olli Nurmi 1.0 1.9.2011 update Olli Nurmi 1.1 28.9.2011 final Olli Nurmi 1.2 4.10.2011 final Olli Nurmi Issues about Onix is removed to separate deliverable next Media www.nextmedia.fi www.tivit.fi WP 1 AND EREADING AND D 1.1.4.1 1 (12) STATE-OF-THE-ART-STANDARDS Next Media - a Tivit Programme Phase 2 (1.1-31.12.2011) Table of Contents 1 Introduction ............................................................................................................. 3 1.1 Web browsers ................................................................................................. 3 1.2 HTML5 – an open standard ............................................................................ 4 1.3 CSS - Cascading Style Sheets ....................................................................... 6 1.4 HTML5 vs native applications ......................................................................... 6 2 HTML5/CSS3 standards ........................................................................................
    [Show full text]
  • Communications Cacm.Acm.Org of Theacm 06/2009 Vol.52 No.06
    COMMUNICATIONS CACM.ACM.ORG OF THEACM 06/2009 VOL.52 NO.06 One Laptop Per Child: Vision vs. Reality Hard-Disk Drives: The Good, The Bad, and the Ugly How CS Serves The Developing World Network Front-End Processors The Claremont Report On Database Research Autonomous Helicopters Association for Computing Machinery Think Parallel..... It’s not just what we make. It’s what we make possible. Advancing Technology Curriculum Driving Software Evolution Fostering Tomorrow’s Innovators Learn more at: www.intel.com/thinkparallel ACM Ad.indd 1 4/17/2009 11:20:03 AM ABCD springer.com Noteworthy Computer Science Journals Autonomous Biological Personal and Robots Cybernetics Ubiquitous G. Sukhatme, University W. Senn, Universität Bern, Computing of Southern California, Physiologisches Institut; ACM Viterbi School of Engi- J. Rinzel, National neering, Dept. Computer Institutes of Health (NIH), P. Thomas, Univ. Coll. Science Dept. Health Education & London Interaction Centre Autonomous Robots Welfare; J. L. van Hemmen, reports on the theory and TU München, Abt. Physik Personal and Ubiquitous applications of robotic systems capable of Biological Cybernetics is an interdisciplinary Computing publishes peer-reviewed some degree of self-sufficiency. It features medium for experimental, theoretical and international research on handheld, wearable papers that include performance data on actual application-oriented aspects of information and mobile information devices and the robots in the real world. The focus is on the processing in organisms, including sensory, pervasive communications infrastructure that ability to move and be self-sufficient, not on motor, cognitive, and ecological phenomena. supports them to enable the seamless whether the system is an imitation of biology.
    [Show full text]
  • Introduction to Closed Captions
    TECHNICAL PAPER Introduction to Closed Captions By Glenn Eguchi Senior Computer Scientist April 2015 © 2015 Adobe Systems Incorporated. All rights reserved. If this whitepaper is distributed with software that includes an end user agreement, this guide, as well as the software described in it, is furnished under license and may be used or copied only in accordance with the terms of such license. Except as permitted by any such license, no part of this guide may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, recording, or otherwise, without the prior written permission of Adobe Systems Incorporated. Please note that the content in this guide is protected under copyright law even if it is not distributed with software that includes an end user license agreement. The content of this guide is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Adobe Systems Incorporated. Adobe Systems Incorporated assumes no responsibility or liability for any errors or inaccuracies that may appear in the informational content contained in this guide. This article is intended for US audiences only. Any references to company names in sample templates are for demonstration purposes only and are not intended to refer to any actual organization. Adobe and the Adobe logo, and Adobe Primetime are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Adobe Systems Incorporated, 345 Park Avenue, San Jose, California 95110, USA. Notice to U.S. Government End Users.
    [Show full text]