DOCSLIB.ORG

Html-Elements.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Html-Elements.Pdf All elements are sorted with in their groups in prioritized order. Recom mended (X)HTML ver sions are mint- colored. - Element Document structure - <html> - <head> <body> <title> <meta> HTML 3.2 <link> HTML 4.01 strict <style> HTML 4.01 transitional <script> HTML 4.01 frameset <noscript> Standards XHTML 1.0 strict <base> <basefont> Non element markup constructs XHTML 1.0 transitional <?xml ?> XHTML 1.0 frameset <!DOCTYPE> XHTML 1.1 <!-- --> XHTML 1.1 Basic <![CDATA[ ]]> XHTML 2.0 D (X)HTML 5.0 Information D [B]lock/[I]nline/[T]able D B [I]nvisible/[N]ormal/[R]eplaced Copyright: Lars Gunther. Creative Commons: Attribution-NonCommercial-ShareAlike 2.5 B http://creativecommons.org/licenses/by-nc-sa/2.5/ D N (X)HTML Best Practice Cheat Sheet I D N Semantic meaning The main I D content The docu ments title or I name I s Indicates explicit relationship between- this docu ment and other resources. As such there are I good uses! Usability & Accessibility I* Make unique for I every page s I I I Best practice I Unobtrusive DOM-scripts, s XML declara please! I tion Unnecessary with unobtrusive script What flavour ing techniques! Forbidden in XHTML of (X)HTML is 5. I used? Code com I ment External style - Unparsed Better skip. It will put MSIE <= 6 in quirks mode and is NOT obligatory. In sheets are usually character theory best place to specify encoding for offline usage of an XHTML docubest SEO notes data ment. Keep scripts ex Highly ranked ternal and will be the - many link-text - Only ”name = 'description'” is useful Use CSS - Notable browser issues Required in every - version since HTML 2.0! Use richly while learning and de veloping Use for inline JavaScript in XHTML Margin: 8px; Unstyled appearance Test for capabili ties, not browsers! Text on the title-bar - Not ignored by true XML parsers! Ignored by MSIE for scripts Page - Will control stan Script may have output 1 dards compliance or quirks mode MSIE has tional Opera may ignore CSS if MIME is true XHTML comments - condi - - Version: 1.09 All elements are sorted with in their groups in prioritized order. Recom mended (X)HTML ver sions are mint- colored. - Element Basic semantics - <h1> to <h6> - <hgroup> <p> <em> HTML 3.2 <strong> <abbr> HTML 4.01 strict <acronym> HTML 4.01 transitional <blockquote> HTML 4.01 frameset <q> <cite> StandardsXHTML 1.0 strict <ins> <del> XHTML 1.0 transitional <dfn> <h> XHTML 1.0 frameset <mark> Hypertext XHTML 1.1 XHTML 1.1 Basic <a> XHTML 2.0 (X)HTML 5.0 Information [ c li /[ B]lo k/[I]n ne T]able B [I]nvisible/[N]ormal/[R]eplaced Copyright: Lars Gunther. Creative Commons: Attribution-NonCommercial-ShareAlike 2.5 http://creativecommons.org/licenses/by-nc-sa/2.5/ (X)HTML Best Practice Cheat Sheet B N B Heading N Semantic meaning I The hgroup element represents the heading of a section. The element is used to group a set of h1– I N h6 elements when the heading has multiple levels, N such as subheadings, alternative titles, or taglines. I Paragraph N Emphasized I text Use in correct or N Strongly em der B phasised text Usability & Accessibility N Abbreviation I N I Acronym N I* Longer quote Usually spoken - louder I* N Short quote Usually spoken I really loud! - N B Who is cited ” All acronyms are abbreviations”. N Make sure they are not confused with N Inserted text links. CSS-speech: Spell out ini I tialisms. Best practice N Deleted text Defined word N Heading Marked or Do not equate with highlighted ”italics” I text Do not equate with Better turn under ”bold” lining off N Highly ranked Link SEO notes Do not equate with ”indentation” Not the quote as Emphasised - words may get such - Link text should higher ranking. be understand able out of con text. May contain block elements in (X)HTML 5. Use with ”section” Notable browser issues In future, use to highlight matches to search string - - Any element with an id can replace Not in MSIE Large bold text, its use as ”anchor” gradually smaller. Margin-top/bottom Unstyled appearance No quotation marks in MSIE Margin-top: 1em; Italics rel=”nofollow” means it will not Bolder increase targets page rank. abbr[title], acro rel=”canonical” nym[title] { border- marks the pre bottom: dotted 1px; Page ferred URL for a ] resource. Indented right and left. 2 Quotation marks Italics - - Underlined Strike through Italics Probably like h1, h2, etc. Blue underlined text. Images get a blue border. Version: 1.09 All elements are sorted with in their groups in prioritized order. Recom mended (X)HTML ver sions are mint- colored. - Element Page structure - <div> - <span> <pre> <hr> <address> HTML 3.2 <section> HTML 4.01 strict <article> HTML 4.01 transitional <aside> HTML 4.01 frameset Standards XHTML 1.0 strict <header> XHTML 1.0 transitional <footer> XHTML 1.0 frameset <figure> XHTML 1.1 <headings> XHTML 1.1 Basic <listing> <xmp> XHTML 2.0 (X)HTML 5.0 Information [B]lock/[I]nline/[T]able D B D I [I]nvisible/[N]ormal/[R]eplaced Copyright: Lars Gunther. Creative Commons: Attribution-NonCommercial-ShareAlike 2.5 http://creativecommons.org/licenses/by-nc-sa/2.5/ B N (X)HTML Best Practice Cheat Sheet N B Part of page N Semantic meaning B R B Thematic N break B Contact in R formation Is a semantic el ement available? Document or If so, use that in B application N stead. Usability & Accessibility section Stand alone N capable sec - tion ” B tangentially Always use hCard for addresses, but related to the in combination with <address> for content” contact info. The header element represents - Section takes pri N a group of introductory or Avoid ”divitis” ority over h1-h6 - gational Avoid ”spanma - B typically contains the section's nia” heading (an h1–h6 element or Best tice an prac contain other content, such as a B Do not use for N table of contents,hgroup a search form, aids. A header element visual purposes or any relevant only. Footer for a R section B element), but can also - Paragraph - B with a caption Does not equal <div> Set a heading SEO notes logos navi Caption will prob - ably be mandated. Content may be a Today: Good val image. ues for id or class attributes! May override Notable browser issues ”width” in MSIE - Color' for MSIE, 'background-color' Proposed re - for Gecko placement for misuse of fieldset' - Preformatted Unstyled appearance A bar Italics Page 3 (Parsed as CDA TA, preserved whitespace) - Version: 1.09 All elements are sorted with in their groups in prioritized order. Recom mended (X)HTML ver sions are mint- colored. - Element Visual formatting - <br> - <b> <i> <sub> <sup> <big> HTML 3.2 <small> <tt> HTML 4.01 strict <center> <font> HTML 4.01 transitional <u> HTML 4.01 frameset <s> <strike> Standards XHTML 1.0 strict <nobr> <wbr> XHTML 1.0 transitional XHTML 1.0 frameset D XHTML 1.1 D D XHTML 1.1 Basic D D D XHTML 2.0 D D D D (X)HTML 5.0 D D D Information [B]lock/[I]nline/[T]able D D I D D D I [I]nvisible/[N]ormal/[R]eplaced Copyright: Lars Gunther. Creative Commons: Attribution-NonCommercial-ShareAlike 2.5 http://creativecommons.org/licenses/by-nc-sa/2.5/ I D N (X)HTML Best Practice Cheat Sheet D I N (Line break) I N I N Semantic meaning I N N s I B N N (”Smallprint” I in (X)HTML N 5) sab l ty Acc bility I N U i i & essi I E.g. Use with simple math, footnotes, I N and when part of language idiom. I N I N N May be only op N tion for a WYSI WYG editor Best practice Avoid underlining always (even with CSS), since it will look like a link. - - Use CSS May get a sligthly elevated rank SEO notes Use CSS or <del> Use CSS instead Notable browser issues Line break Bolder Italics Unstyled appearance Subscript Superscript Bigger Smaller NS 4 proprietary, but works in all Fixed width font MSIE proprietary Centers every thing! Page Changes font set tings 4 Underlined Strike through - No line breaks in cell Suggestion for line - break. Version: 1.09 All elements are sorted with in their groups in prioritized order. Recom mended (X)HTML ver sions are mint- colored. - Element Tables - <table> - <tr> <th> <td> <caption> HTML 3.2 <thead> <tbody> HTML 4.01 strict <tfoot> HTML 4.01 transitional <col> <colgroup> HTML 4.01 frameset StandardsXHTML 1.0 strict XHTML 1.0 transitional XHTML 1.0 frameset XHTML 1.1 XHTML 1.1 Basic XHTML 2.0 (X)HTML 5.0 Information [B]lock/[I]nline/[T]able T [I]nvisible/[N]ormal/[R]eplaced Copyright: Lars Gunther. Creative Commons: Attribution-NonCommercial-ShareAlike 2.5 T http://creativecommons.org/licenses/by-nc-sa/2.5/ (X)HTML Best Practice Cheat Sheet T N N T Tabular data T N Semantic meaning Table row T N Heading for row or col N umn T Table data N Table caption T Describe format T N Table head - with ”summary” N T Table body Use ”scope” or Usability & Accessibility I ”headers/id” Table footer I Table column Often a good idea to have Group of col umns Not for layout Best practice - Can be used in stead of grouping <tr> with the class attribute SEO notes - Notable browser issues Hard to style MSIE needs this one for dynamical ly created tables Visible borders MSIE catches too Table cell with Unstyled appearance many style-rules! bold, centered text Safari does not support colgroup A table cell Centered above the table Repeats on each page when printing - Page 5 Version: 1.09 All elements are sorted with in their groups in prioritized order.
Load more

Recommended publications
  • Sample XHTML Code
    Sample XHTML Code Docs version: 2.0 Version date 7/29/2009 Contents • Introduction • Home page • General page structure • Tabbed content • Navigation lists • iPhone action links Introduction These code samples illustrate how we designed and developed the user for the MIT Mobile Web. These code samples are taken from the original XHTML design mockups which were the basis of the final implementation of the live MIT Mobile Web. We’re presenting these design mockups here because showing the final functional code with its back-end integration would make it harder to read the actual markup as the web browser sees it – which is what determines what the end user actually sees and interacts with. The XHTML and CSS generated by the functional code is in any case very close to these original design mockups. We’re not presenting every page for every module here. Rather, we’re showing representative pages that illustrate user-interface patterns that appear throughout the MIT Mobile Web. After studying these code snippets and the patterns they represent, you should be able to easily understand how specific pages in the MIT Mobile Web were built, as well as how to go about building new page layouts sharing a consistent basic structure, function and building blocks. For background on why we optimized the UI for three different categories of devices, please read the Introduction to the Mobile Web document. Commented source code, images and other assets for the entire MIT Mobile Web – including functional code for back-end integration – is online as a SourceForge project at http://sourceforge.net/projects/mitmobileweb/.
    [Show full text]
  • Microsoft, Adobe & W3C to Shake up Electronic Forms Market
    Vol. 11, No, 8 October 2003 www.gilbane.com Published by: Bluebill Advisors, Inc. 763 Massachusetts Ave. Cambridge, MA 02139 USA (617) 497.9443 Fax (617) 497.5256 www.bluebilladvisors.com Editor: Frank Gilbane [email protected] (617) 497.9443 Content Technology Works! Editors Emeriti: Tim Bray [email protected] (604) 708.9592 MICROSOFT, ADOBE & XFORMS TO David Weinberger [email protected] (617) 738.8323 SHAKE UP ELECTRONIC FORMS MARKET Senior Editors: Sebastian Holst [email protected] Our title this month reads like a news headline on purpose. There are a number Bill Trippe [email protected] of new, and upcoming, developments in electronic forms (eForms) technology (617) 497.9443 that should be grabbing your attention. Some of these are of major importance Recent Contributors: on their own, but taken together, they signal the start of a major improvement Kathleen Reidy in businesses’ ability to easily collect, integrate, and process information. [email protected] Bob Doyle [email protected] “Electronic forms” have been around for years, but the term refers to a wide variety of technologies – from scanned image applications to HTML forms – Production Assistant: Sarah G. Dionne that are not at all similar and far from equal in their ability to accelerate and [email protected] smooth business processes. What eForm technology has shared is: a level of (617) 497.9443 difficulty that kept it out of the reach of office professionals who were com- Subscriptions: fortable enough with documents and spreadsheets, but scared-off by forms, [email protected] (617) 497.9443 and proprietary data formats that made information integration costly and complex.
    [Show full text]
  • XHTML Mobile Profile Reference
    XHTML Mobile Profile Reference Version 1.0 Openwave Systems Inc. 1400 Seaport Boulevard Redwood City, CA 94063 USA http://www.openwave.com Part Number XHRF-10-004 October 2001 LEGAL NOTICE Copyright © 1994–2001, Openwave Systems Inc. Portions copyright © 1994–1999, Netscape Communications Corporation. Portions copyright © 1994–1999, Oracle Corporation. All rights reserved. These files are part of the Openwave Software Developer’s Kit (SDK). Subject to the terms and conditions of the SDK License Agreement, Openwave Systems Inc. (“Openwave”) hereby grants you a license to use the SDK software and its related documentation. OPENWAVE MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, REGARDING THE SDK SOFTWARE, INCLUDING, BUT NOT LIMITED TO, ANY IMPLIED WARRANTIES THAT THE SDK SOFTWARE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE, OR NONINFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LICENSED SOFTWARE IS BORNE BY USER. USER UNDERSTANDS AND ACCEPTS THE SDK SOFTWARE AND ANY SOFTWARE SECURITY FEATURES INCLUDED WITH THE SDK SOFTWARE ARE PROVIDED ON AN “AS IS” BASIS FROM OPENWAVE, AND OPENWAVE DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE OF, OR THE RESULTS OF THE USE OF THE SDK SOFTWARE IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL OPENWAVE OR ITS SUPPLIERS OR DISTRIBUTORS BE LIABLE FOR ANY DAMAGES RESULTING FROM OR ARISING OUT OF USER’S USE OF THE SDK SOFTWARE, INCLUDING, WITHOUT LIMITATION, ANY DIRECT, INDIRECT, SPECIAL, INCIDENTIAL, OR CONSEQUENTIAL DAMAGES OF ANY KIND INCLUDING WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES.
    [Show full text]
  • Relatório Comparativo Da Produção De Programas Hipermídia Interativos Em XHTML, SMIL/Grins E NCL/Maestro
    Rafael Ferreira Rodrigues Rodrigo Laiola Guimarães Relatório comparativo da produção de programas hipermídia interativos em XHTML, SMIL/GRiNS e NCL/Maestro MONOGRAFIA DA DISCIPLINA DE FUNDAMENTOS DE SISTEMAS MULTIMÍDIA DEPARTAMENTO DE INFORMÁTICA Programa de Pós-Graduação em Informática Rio de Janeiro Dezembro de 2005 Rafael Ferreira Rodrigues Rodrigo Laiola Guimarães Relatório comparativo da produção de programas hipermídia interativos em XHTML, SMIL/GRiNS e NCL/Maestro Monografia da Disciplina de Fundamentos de Sistemas Multimídia Monografia apresentada como requisito parcial para aprovação na disciplina de Fundamentos de Sistemas Multimídia do Programa de Pós- Graduação em Informática da PUC-Rio. Orientador: Luiz Fernando Gomes Soares Rio de Janeiro, dezembro de 2005 Rafael Ferreira Rodrigues Rodrigo Laiola Guimarães Relatório comparativo da produção de programas hipermídia interativos em XHTML, SMIL/GRiNS e NCL/Maestro Monografia apresentada como requisito parcial para aprovação na disciplina de Fundamentos de Sistemas Multimídia do Programa de Pós -Graduação em Informática da PUC-Rio. Luiz Fernando Gomes Soares Orientador Departamento de Informática - PUC -Rio Rio de Janeiro, 12 de dezembro de 2005 Todos os direitos reservados. É proibida a reprodução total ou parcial do trabalho sem autorização da universidade, dos autores e do orientador. Rafael Ferreira Rodrigues Graduado em Engenharia de Computação pelo Instituto Militar de Engenharia (IME) em 2004. Atualmente, integra o grupo de pesquisadores do Laboratório TeleMídia da PUC-Rio, desenvolvendo pesquisa na área de Redes de Computadores e Sistemas Hipermídia. Rodrigo Laiola Guimarães Graduado em Engenharia de Computação pela Universidade Federal do Espírito Santo (UFES) em 2004. Atualmente, integra o grupo de pesquisadores do Laboratório TeleMídia da PUC-Rio, desenvolvendo pesquisa na área de Redes de Computadores e Sistemas Hipermídia.
    [Show full text]
  • Schema Matching for Structured Document Transformations
    Schema Matching For Structured Document Transformations THÈSE Nº 3108 (2004) PRÉSENTÉE À LA FACULTÉ INFORMATIQUE ET COMMUNICATIONS Institut des systèmes informatiques et multimédias SECTION D’INFORMATIQUE ÉCOLE POLYTECHNIQUE FÉDÉRALE DE LAUSANNE POUR L’OBTENTION DU GRADE DE DOCTEUR ÈS SCIENCES PAR AIDA BOUKOTTAYA Diplôme National d’Ingénieur en Informatique, Ecole Nationale des Sciences de l’Informatique Tunis et de nationalité tunisienne Acceptée sur proposition du jury: Prof. Giovanni Coray, co-directeur de thèse Dr. Christine Vanoirbeek, co-directrice de thèse Prof. Gilles Falquet, rapporteur Prof. Martin Rajman, rapporteur Dr. Vincent Quint, rapporteur Lausanne, EPFL 2004 ACKNOWLEDGMENTS This thesis is the outcome of three years experience at the Theoretical Computer Science Laboratory (LITH) at EPFL. There are many people who helped me in this work, either directly by working on projects with me or indirectly by giving me vision and support. I would like to express my deep gratitude to my advisors Prof. Giovanni Coray and Dr. Christine Vanoirbeek. They offer me the great opportunity of working with them. Thank you for the support you gave to me through your continuous encouragements, your constructive suggestions, your focus and vision on my research and your precious help in reviewing my PhD dissertation. I would like to thank Prof. Gilles Falquet for the long discussions we had, for his constructive remarks, his availability and his precious feedback during the course of this research and the writing of my PHD. I would like to thank the members of my examining committee: Prof. Gilles Falquet, Prof. Martin Rajman and Dr.Vincent Quint, who honoured me by accepting to review and evaluate my thesis.
    [Show full text]
  • Modularization of XHTML™ 2.0 Modularization of XHTML™ 2.0
    Modularization of XHTML™ 2.0 Modularization of XHTML™ 2.0 Modularization of XHTML™ 2.0 W3C Editor’s Draft 23 January 2009 This version: http://www.w3.org/MarkUp/2009/ED-xhtml-modularization2-20090123 Latest public version: http://www.w3.org/TR/xhtml-modularization2 Previous Recommendation: http://www.w3.org/TR/2008/REC-xhtml-modularization-20081008 Editors: Mark Birbeck, x-port.net Markus Gylling, DAISY Consortium Shane McCarron, Applied Testing and Technology Steven Pemberton, CWI (XHTML 2 Working Group Co-Chair) This document is also available in these non-normative formats: Single XHTML file [p.1] , PostScript version, PDF version, ZIP archive, and Gzip’d TAR archive. Copyright © 2001-2009 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply. Abstract This Working Draft specifies an abstract modularization of XHTML and an implementation of the abstraction using XML Document Type Definitions (DTDs), XML Schema, and RelaxNG. This modularization provides a means for subsetting and extending XHTML, a feature needed to permit the definition of custom markup languages that are targeted at specific classes of devices or specific types of documents. 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 development version of a very early form and is riddled with errors. It should in no way be considered stable, and should not be referenced for any purposes whatsoever. - 1 - Quick Table of Contents Modularization of XHTML™ 2.0 This document has been produced by the W3C XHTML 2 Working Group as part of the HTML Activity.
    [Show full text]
  • XSL Formatting Objects XSL Formatting Objects
    XSL Formatting Objects XSL Formatting Objects http://en.wikipedia.org/wiki/XSL_Formatting_Objects This Book Is Generated By WikiType using RenderX DiType, XML to PDF XSL-FO Formatter Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". 29 September 2008 XSL Formatting Objects Table of Contents 1. XSL Formatting Objects.........................................................4 XSL-FO basics. ...............4 XSL-FO language concepts. 6 XSL-FO document structure. 6 Capabilities of XSL-FO v1.0. 7 Multiple columns. ...........7 Lists.........................................................................8 Pagination controls. 8 Footnotes....................................................................8 Tables................................................ ........................8 Text orientation controls. 9 Miscellaneous...............................................................9 Capabilities of XSL-FO v1.1. 9 Multiple flows and flow mapping. 9 Bookmarks.................................................................10 Indexing....................................................................10 Last page citation. 10 Table markers. 10 Inside/outside floats. 10 Refined graphic sizing. 11 Advantages of XSL-FO. 11 Drawbacks
    [Show full text]
  • Web Application Development And/Or Html5
    Web Application Development and/or html5 Toni Ruottu <toni.ruottu@cs. helsinki.fi> Why Develop Web Apps? secure portable easy good quality debugger everywhere Really Short Computer System History 1. mainframe 2. mainframe - cable - multiple terminals 3. personal computer (PC) 4. PC - cable - PC 5. PC - acoustic coupler - phone - acoustic coupler - PC 6. PC - modem - PC 7. bulletin board system - modem - multiple PCs 8. multiple servers - Internet - multiple PCs The Early Internet Servers that reveal hierarchies: ftp Usenet news gopher HyperText Markup Language (HTML) html a new (at that time) hypertext format text with links Standard Generalized Markup Language (SGML) based web 1.0 is born! html2 standardization html3 tables lists web forms ~feature complete Clean-up html4 styling markup separated to css xhtml1 changed from SGML to XML as base xhtml2 move out "as much as possible" (xforms, xframes) making the syntax elegant Xhtml2 Implementations not too much support from industrial browser-vendors Mozilla, Opera, IE instead separate translators Chiba (server-side "browser") Deng (flash based browser in a browser) special xml-browsers X-smiles (TKK heavily involved afaik) The Era of Java, and NPAPI Plug-ins (x)html focuses on textual documents you can use javascript, but it is sloooow and the sandbox is lacking lots of useful interfaces to do something "cool" you need to use the Netscape Plug- in Application Programming Interface (NPAPI) which makes doing something "cool" less cool the most used NPAPI plug-ins include: flash, java, pdf, audio, and video still, there are empires built on top of these plug-ins no-one can deny impact of flash in taking the web forward ( e.g.
    [Show full text]
  • An Intruduction to HTML5
    Agenda * What is HTML5 -- Its history and motivation * HTML/XHTML as Human / Machine Readable Format * HTML and its related technologies * Brief summary of the changes * Models of HTML5 * Examples and demonstrations What is HTML5 -- Its history and motivation * W3C and HTML * Brief history of HTML * WHATWG and HTML5 * 'Working Draft' and 'Recommendation' * HTML5 as IDL -- Interface Definition via IDL What is HTML5 - W3C and HTML What is HTML5 - W3C and HTML What is HTML5 - Brief history of HTML HTML is born for 'Scientists' at CERN. First website (from archive@cern) Tim Berners Lee What is HTML5 - Brief history of HTML HTML (1989; CERN) HTML = HyperText Markup Language HTML 1.0 (1993; IETF) HTML 2.0 (1995; W3C) HTML 3.2 (1997; W3C) XML 1.0 (1998) HTML 4.0.1 (1999; W3C) XHTML 1.0 (2000) XHTML Basic 1.0 (2000) XHTML 1.1 (2001) XHTML Basic 1.1 (2008) What is HTML5 - Brief history of HTML HTML 4.0.1 (1999; W3C) XML 1.0 (1998) XHTML 1.0 (2000) XHTML 1.1 (2001) Extension to HTML4 (2003;Opera) PositionPaper (2004;Opera/Mozilla) What is HTML5 - Brief history of HTML http://www.w3.org/2004/04/webapps-cdf-ws/papers/opera.html What is HTML5 - Brief history of HTML HTML 4.0.1 (1999; W3C) XML 1.0 (1998) XHTML 1.0 (2000) XHTML 1.1 (2001) Extension to HTML4 (2003;Opera) PositionPaper (2004;Opera/Mozilla) WHATWG (2004;Opera/Mozilla/Apple) What is HTML5 - Brief history of HTML The Web Hypertext Application Technology Working Group (WHATWG) What is HTML5 - Brief history of HTML HTML 4.0.1 (1999; W3C) XML 1.0 (1998) XHTML 1.0 (2000) XHTML 1.1 (2001) Extension
    [Show full text]
  • Web Application Developer's Guide for the Polycom® Soundpoint® IP
    Web Application Developer’s Guide for the Polycom® SoundPoint® IP/SoundStation® IP Family SIP 3.1 August, 2008 Edition 1725-17693-310 Rev. A SIP 3.1 Trademark Information Polycom®, the Polycom logo design, SoundPoint® IP, SoundStation®, SoundStation VTX 1000®, ViaVideo®, ViewStation®, and Vortex® are registered trademarks of Polycom, Inc. Conference Composer™, Global Management System™, ImageShare™, Instructor RP™, iPower™, MGC™, PathNavigator™, People+Content™, PowerCam™, Pro-Motion™, QSX™, ReadiManager™, Siren™, StereoSurround™, V2IU™, Visual Concert™, VS4000™, VSX™, and the industrial design of SoundStation are trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of their respective owners. Patent Information The accompanying product is protected by one or more U.S. and foreign patents and/or pending patent applications held by Polycom, Inc. © 2008 Polycom, Inc. All rights reserved. Polycom Inc. 4750 Willow Road Pleasanton, CA 94588-2708 USA No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format. As between the parties, Polycom, Inc. retains title to, and ownership of, all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g. a book or sound recording). Every effort has been made to ensure that the information in this manual is accurate. Polycom, Inc. is not responsible for printing or clerical errors.
    [Show full text]
  • Adaptation De Contenu Multimédia Avec MPEG-21: Conversion De Ressources Et Adaptation Sémantique De Scènes Mariam Kimiaei Asadi
    Adaptation de Contenu Multimédia avec MPEG-21: Conversion de Ressources et Adaptation Sémantique de Scènes Mariam Kimiaei Asadi To cite this version: Mariam Kimiaei Asadi. Adaptation de Contenu Multimédia avec MPEG-21: Conversion de Ressources et Adaptation Sémantique de Scènes. domain_other. Télécom ParisTech, 2005. English. pastel- 00001615 HAL Id: pastel-00001615 https://pastel.archives-ouvertes.fr/pastel-00001615 Submitted on 13 Mar 2006 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Thèse présentée pour obtenir le grade de docteur de l’Ecole Nationale Supérieure des Télécommunications Spécialité : Informatique et Réseaux Mariam Kimiaei Asadi Adaptation de Contenu Multimédia avec MPEG-21 : Conversion de Ressources et Adaptation Sémantique de Scènes Soutenue le 30 juin 2005 devant le jury composé de: Cécile Roisin Rapporteurs Fernando Pereira Yves Mathieu Examinateurs Vincent Charvillat Nabil Layaïda Alexandre Cotarmanac’h Invité Jean-Claude Dufourd Directeur de thèse ام دل، ـــــ دل ــــ ــر ـــ ج رهـــ رهـــ، رهـــ ز ــــ ه ــ او دور، ـ دل &%$ #د"! ـــ ه ـ #د"!، ازو )ــــــ'ا، )ــــ'ا +ــــ* دل &ـــــ"(، د در & "( ــــ ـــــ$* -ـ,ــــ ـــ"(، "د .$ــــــ &ــــــ ر هــــ 0ـــــــ/ در &3ـــــن اــــي د6ــــــ* -5 اي دو&4، هـــــاي -"ــ : ﺱ Acknowledgments I have very limited space to thank all the people who contributed in a way or another to the accomplishment of this thesis.
    [Show full text]
  • HTML5 Audio 1 HTML5 Audio
    HTML5 Audio 1 HTML5 Audio HTML • HTML and HTML5; HTML editor • Dynamic HTML • XHTML • XHTML Basic (Mobile) • XHTML Mobile Profile and C-HTML • HTML element • Span and div • HTML attribute • Character encodings; Unicode • Language code • Document Object Model • Browser Object Model • Style sheets and CSS • Font family and Web colors • HTML scripting and JavaScript • W3C, WHATWG, and validator • Quirks mode • HTML Frames • HTML5 Canvas, WebGL, and WebCL • HTML5 Audio and HTML5 video • Web storage • Web browser (layout) engine • Comparison of • document markup languages • web browsers • layout engine support for • HTML; Non-standard HTML • XHTML (1.1) • HTML5; HTML5 canvas, • HTML5 media (Audio, Video) • v • t [1] • e HTML5 Audio is a subject of the HTML5 specification, investigating audio input, playback, synthesis, as well as speech to text in the browser. HTML5 Audio 2 <audio> element The <audio> element represents a sound, or an audio stream.[2] It is commonly used to play back a single audio file within a web page, showing a GUI widget with play/pause/volume controls. Supported browsers • PC • Google Chrome • Internet Explorer 9 • Mozilla Firefox 3.5 • Opera 10.5 • Safari 3.1[3] • Mobile • Android Browser 2.3 • Blackberry Browser • Google Chrome for Android • Internet Explorer Mobile 9 • Mobile Safari 4 • Mozilla Firefox for Android • Opera Mobile 11 • Tizen Supported audio codecs This table documents the current support for audio codecs by the <audio> element. Browser Operating Formats supported by different web browsers system Ogg
    [Show full text]