The document discusses the history and standardization of HTML. It notes that HTML was originally created by Tim Berners-Lee at CERN in 1990 for scientific purposes. The development of graphical web browsers by Mosaic and Netscape in the early 1990s and the subsequent "Browser Wars" led to HTML being defined by each browser instead of standards. The World Wide Web Consortium was founded in 1994 to establish standards for HTML. The document outlines that HTML standardization involves both syntax, which defines valid characters and strings, and semantics, which describes the meaning of elements.
The document discusses the key changes and new features in HTML5 compared to previous versions of HTML and XHTML. It notes that the HTML5 specification is larger and covers new elements, forms, APIs, and structural tags. It provides examples of several new elements like <article>, <aside>, <section>, <header>, and <canvas> and explains their purpose in HTML5 pages. It also covers new attributes for multimedia like <audio> and <video> elements and their <source> child elements.
Markup language classification, designing static and dynamicAnkita Bhalla
The document discusses various markup languages used to create static and dynamic web pages. It describes how static pages are fixed and do not change, while dynamic pages can be modified at runtime through scripts. It provides details on HTML, CSS, JavaScript and server-side scripts for creating dynamic content. Key topics covered include using tags like <div> for layouts, <img> for images, and JavaScript for basic interactivity. The document compares the processing of static versus dynamic pages and outlines benefits of dynamic pages like personalization and database access.
A markup language is a modern system for annotating a document in a way that is syntactically distinguishable from the text. The idea and terminology evolved from the "marking up" of manuscripts, i.e., the revision instructions by editors, traditionally written with a blue pencil on authors' manuscripts. Examples are typesetting instructions such as those found in troff, TeX and LaTeX, or structural markers such as XML tags. Markup instructs the software displaying the text to carry out appropriate actions, but is omitted from the version of the text that is displayed to users. Some markup languages, such as HTML, have pre-defined presentation semantics, meaning that their specification prescribes how the structured data are to be presented; others, such as XML, do not.
A widely-used markup language is HyperText Markup Language (HTML), one of the document formats of the World Wide Web. HTML, which is an instance of SGML (though, strictly, it does not comply with all the rules of SGML), follows many of the markup conventions used in the publishing industry in the communication of printed work between authors, editors, and printers.
This document provides an overview of XML, including what it is, its syntax and structure, common technologies used with XML, and advantages of using XML. XML is a markup language that uses tags to structure information to make it readable, unambiguous, and extensible. It allows data exchange between applications and includes elements, attributes, and comments. Related technologies include DTDs, schemas, and stylesheets.
XML is a markup language that is used to transport and store data. It uses tags and attributes to provide extra information about the data. XML documents are structured as trees, with a single root element and child elements nested within parent elements. The structure and elements of an XML document can be defined using a DTD or XML schema. Benefits of XML include being text-based, modular, and able to represent semantics along with data, while obstacles include verbosity and lack of intrinsic data types.
The document discusses various web design issues including different types of editors, image formats like GIF and JPEG, programming languages for web development like Java and JavaScript, factors to consider like browser targeting and testing on multiple systems, and costs associated with professional web design which can range from $5,000 to millions of dollars for large sites. Newer web editors aim to combine visual and code editing to give designers more control while abstracting some complexities, and site statistics are important to understand user traffic and engagement.
This document provides an overview of introductory front-end web development topics including web fonts, HTML5, CSS3, and mobile development. It discusses the history of web fonts and font services, what's new in HTML5 like semantic elements and APIs, an introduction to CSS3 features, considerations for mobile and responsive design using media queries and frameworks like jQuery Mobile, and recommends following leaders in the field.
The document discusses the key changes and new features in HTML5 compared to previous versions of HTML and XHTML. It notes that the HTML5 specification is larger and covers new elements, forms, APIs, and structural tags. It provides examples of several new elements like <article>, <aside>, <section>, <header>, and <canvas> and explains their purpose in HTML5 pages. It also covers new attributes for multimedia like <audio> and <video> elements and their <source> child elements.
Markup language classification, designing static and dynamicAnkita Bhalla
The document discusses various markup languages used to create static and dynamic web pages. It describes how static pages are fixed and do not change, while dynamic pages can be modified at runtime through scripts. It provides details on HTML, CSS, JavaScript and server-side scripts for creating dynamic content. Key topics covered include using tags like <div> for layouts, <img> for images, and JavaScript for basic interactivity. The document compares the processing of static versus dynamic pages and outlines benefits of dynamic pages like personalization and database access.
A markup language is a modern system for annotating a document in a way that is syntactically distinguishable from the text. The idea and terminology evolved from the "marking up" of manuscripts, i.e., the revision instructions by editors, traditionally written with a blue pencil on authors' manuscripts. Examples are typesetting instructions such as those found in troff, TeX and LaTeX, or structural markers such as XML tags. Markup instructs the software displaying the text to carry out appropriate actions, but is omitted from the version of the text that is displayed to users. Some markup languages, such as HTML, have pre-defined presentation semantics, meaning that their specification prescribes how the structured data are to be presented; others, such as XML, do not.
A widely-used markup language is HyperText Markup Language (HTML), one of the document formats of the World Wide Web. HTML, which is an instance of SGML (though, strictly, it does not comply with all the rules of SGML), follows many of the markup conventions used in the publishing industry in the communication of printed work between authors, editors, and printers.
This document provides an overview of XML, including what it is, its syntax and structure, common technologies used with XML, and advantages of using XML. XML is a markup language that uses tags to structure information to make it readable, unambiguous, and extensible. It allows data exchange between applications and includes elements, attributes, and comments. Related technologies include DTDs, schemas, and stylesheets.
XML is a markup language that is used to transport and store data. It uses tags and attributes to provide extra information about the data. XML documents are structured as trees, with a single root element and child elements nested within parent elements. The structure and elements of an XML document can be defined using a DTD or XML schema. Benefits of XML include being text-based, modular, and able to represent semantics along with data, while obstacles include verbosity and lack of intrinsic data types.
The document discusses various web design issues including different types of editors, image formats like GIF and JPEG, programming languages for web development like Java and JavaScript, factors to consider like browser targeting and testing on multiple systems, and costs associated with professional web design which can range from $5,000 to millions of dollars for large sites. Newer web editors aim to combine visual and code editing to give designers more control while abstracting some complexities, and site statistics are important to understand user traffic and engagement.
This document provides an overview of introductory front-end web development topics including web fonts, HTML5, CSS3, and mobile development. It discusses the history of web fonts and font services, what's new in HTML5 like semantic elements and APIs, an introduction to CSS3 features, considerations for mobile and responsive design using media queries and frameworks like jQuery Mobile, and recommends following leaders in the field.
The document provides an introduction to markup languages like HTML, XML, and XHTML. It discusses the purpose and key differences between these languages. It also covers important XHTML tags and elements for structuring web pages, including the DOCTYPE, head, body, headings, paragraphs, lists, links, and special characters. The last section emphasizes writing valid XHTML and using validation tools to check for syntax errors.
Struts2 course chapter 1: Evolution of Web ApplicationsJavaEE Trainers
The document outlines the topics covered in a Struts2 course, including evolution of web applications, Struts2 installation and configuration, actions and results, OGNL, form tags, generic tags, type conversion, input validation, internationalization, interceptors, persistence, file upload/download, security, custom interceptors, custom result types, preventing double submits, the execute and wait interceptor, decorating with Tiles and SiteMesh, zero configuration, and AJAX. It then provides more details on the evolution of web applications from no MVC to MVC model 1 and 2, and how Struts1 and Struts2 implement MVC model 2 with improvements like easier testing and reduced servlet dependencies.
The web is constantly changing and what we know as the web today is quite different from how it started. What will the web look like in the future? How do we continue to adapt to create content on an increasingly complex medium? In this talk I will explore these questions showcasing examples of how the web has been evolving and innovative ways to create content for it.
This document discusses the key aspects of system implementation including coding, testing, installation strategies, documentation, training, support, and reasons for failure. It covers delivering code, testing plans and results, user guides and training plans. Documentation includes both system and user documentation. Training methods like courses and tutorials are discussed. Support is provided through help desks and information centers. Factors for successful implementation include management support and user involvement.
The slides used in a guest lecture by Dot Tourism at the University of Brighton.
Kate Waite from Dot Tourism, digital marketing specialists for the tourism and travel industry, presented the lecture to 55 final year students studying an e-tourism module as part of their Travel Marketing BA(Hons) and Tourism Management BA(Hons) degrees.
The lecture presented an overview of developing websites for the travel and tourism industry.
www.dottourism.com
The document discusses XML, including its benefits over HTML and how XML documents are structured. It defines XML, describes how XML addresses limitations of HTML, and outlines the key components of an XML document, including elements, attributes, comments, and more. The goal is to introduce XML and explain how to build a basic but complete XML document.
eXtensible Markup Language (By Dr.Hatem Mohamed)MUFIX Community
XML is used to mark up data so it can be processed by computers, whereas HTML is used to mark up text for display to users. XML allows users to define their own tags, and elements in XML must have both a start and end tag. Well-formed XML requires proper nesting of elements and attributes enclosed in quotes.
This document provides an overview of client-side and server-side scripting. It defines scripting as a set of instructions for the web browser or server, and explains the key differences between the two types. Client-side scripting includes JavaScript and runs on the user's device, while server-side scripting interfaces with databases and adds dynamic content to pages. Both are often used together to make sites interactive.
My presentation presents the basic concepts and some generally accepted rules of thumb for designing good web sites. Sites with different objectives will obviously have different needs.
Moreover, individuality and uniqueness of web sites are also valued features.
With that in mind, those guidelines are offered as a starting point for developing good web design skills, not as formula that should be followed point by point.
Web 1 allowed users to access information on read-only websites like dictionaries and university pages. Web 2 emerged in 2004, enabling users to interact and contribute to content through wikis and social networks. Web 3 is an intelligent version that is becoming smarter through machine learning and AI, delivering personalized content by understanding individual browsing histories.
This document discusses the evolution of the web and semantic technologies. It describes how the web has progressed from basic websites and search (Web 1.0) to user-generated content and social aspects (Web 2.0) to the semantic web that adds meaning and structure to data (Web 3.0). It argues that semantic technologies will help address the problem of information overload by making data smarter and more accessible. The document outlines different approaches to semantics including tagging, statistics, linguistics, and artificial intelligence, and how the semantic web aims to move intelligence from software to structured data.
Web 1.0 was the first generation of the world wide web and allowed for one-way broadcasting of information from website owners. Web 2.0 focused on enabling collaboration and information sharing between users online through things like social media platforms and wikis. Web 3.0 extended on these social aspects and aimed to provide location-aware and moment-relevant experiences across multiple devices. Web 4.0, still in development, envisions a symbiotic relationship between humans and machines through technologies like ambient intelligence and mind-controlled interfaces. Each generation brought new interactive capabilities to the internet and how people engage with online information.
Web 1.0 to Web 3.0 - Evolution of the Web and its Various ChallengesSubhash Basistha
The document discusses the evolution of the World Wide Web from Web 1.0 to Web 3.0. Web 1.0 allowed only read-only access to static web pages. Web 2.0 enabled user-generated content and interaction through features like blogs and social media. Web 3.0, also called the Semantic Web, will feature an intelligent web that can understand the meaning of information through standards like XML, RDF, and OWL that structure and define relationships in data. This intelligent web of linked and integrated databases will enable more advanced searches and interactions that go beyond just keywords.
This is the material of my technical training about "Fundamentals of Web" to non-developers, especially to business people. In this presentation, I tried to cover concepts with details that everyone can understand. Even though most of the information I mention verbally in the training, the slides could help the ones who are not very familiar with web and web applications.
The ARPANET was a network created in the 1960s by the US Department of Defense to enable resource sharing between universities and research centers. It connected 4 major universities using packet switching technology over interconnected nodes. This allowed the network to remain operational even if some nodes failed. The ARPANET pioneered internet technology and expanded to include more nodes, eventually evolving into today's internet.
The document provides an overview of basic web concepts including definitions of a network, the internet, the world wide web, web pages, home pages, splash pages, types of internet connections, web browsers, basic web design principles, essential elements of web content, and steps for planning a website. It defines key terms like network, internet, www, web page, and home page. It also lists different types of internet connections, web browsers, and basic principles of web design.
The document discusses XHTML 1.0, which is an XML-based markup language that extends HTML. It defines XHTML as a family of current and future document types that reproduce, subset, and extend HTML 4. The document outlines the rules for XHTML documents, provides an example of valid XHTML code, and describes various elements and tags that can be used in XHTML such as links, images, lists, and tables.
The document summarizes changes between older HTML standards and HTML5. It outlines updates to document type declarations, HTML tags, character encoding metadata, page structure elements, new semantic elements, multimedia tags, form input types, use of semantic HTML5 tags to provide structure and meaning instead of non-semantic divs, new JavaScript APIs, tools to check browser compatibility, HTML5 game development resources, and recommended references for learning more about HTML5.
The document provides an overview of learning HTML and CSS. It discusses HTML topics like DOCTYPE declarations, the HTML DOM, elements, attributes, and comments. It also covers CSS topics such as what CSS stands for, inserting stylesheets, the cascade order, external stylesheets, syntax, and examples of CSS code and selectors. The document includes code snippets of HTML boilerplate, elements, and an external CSS stylesheet.
This document provides an introduction to web standards. It discusses that web standards are formal specifications that describe the World Wide Web. The main standards organizations are the World Wide Web Consortium (W3C) which makes recommendations for technologies like HTML, CSS, XML; and the Internet Engineering Task Force (IETF) which publishes RFC documents. It then gives examples of specific W3C recommendations including XHTML, CSS, XML, and how they are used to structure web pages and apply styles.
The document provides an introduction to markup languages like HTML, XML, and XHTML. It discusses the purpose and key differences between these languages. It also covers important XHTML tags and elements for structuring web pages, including the DOCTYPE, head, body, headings, paragraphs, lists, links, and special characters. The last section emphasizes writing valid XHTML and using validation tools to check for syntax errors.
Struts2 course chapter 1: Evolution of Web ApplicationsJavaEE Trainers
The document outlines the topics covered in a Struts2 course, including evolution of web applications, Struts2 installation and configuration, actions and results, OGNL, form tags, generic tags, type conversion, input validation, internationalization, interceptors, persistence, file upload/download, security, custom interceptors, custom result types, preventing double submits, the execute and wait interceptor, decorating with Tiles and SiteMesh, zero configuration, and AJAX. It then provides more details on the evolution of web applications from no MVC to MVC model 1 and 2, and how Struts1 and Struts2 implement MVC model 2 with improvements like easier testing and reduced servlet dependencies.
The web is constantly changing and what we know as the web today is quite different from how it started. What will the web look like in the future? How do we continue to adapt to create content on an increasingly complex medium? In this talk I will explore these questions showcasing examples of how the web has been evolving and innovative ways to create content for it.
This document discusses the key aspects of system implementation including coding, testing, installation strategies, documentation, training, support, and reasons for failure. It covers delivering code, testing plans and results, user guides and training plans. Documentation includes both system and user documentation. Training methods like courses and tutorials are discussed. Support is provided through help desks and information centers. Factors for successful implementation include management support and user involvement.
The slides used in a guest lecture by Dot Tourism at the University of Brighton.
Kate Waite from Dot Tourism, digital marketing specialists for the tourism and travel industry, presented the lecture to 55 final year students studying an e-tourism module as part of their Travel Marketing BA(Hons) and Tourism Management BA(Hons) degrees.
The lecture presented an overview of developing websites for the travel and tourism industry.
www.dottourism.com
The document discusses XML, including its benefits over HTML and how XML documents are structured. It defines XML, describes how XML addresses limitations of HTML, and outlines the key components of an XML document, including elements, attributes, comments, and more. The goal is to introduce XML and explain how to build a basic but complete XML document.
eXtensible Markup Language (By Dr.Hatem Mohamed)MUFIX Community
XML is used to mark up data so it can be processed by computers, whereas HTML is used to mark up text for display to users. XML allows users to define their own tags, and elements in XML must have both a start and end tag. Well-formed XML requires proper nesting of elements and attributes enclosed in quotes.
This document provides an overview of client-side and server-side scripting. It defines scripting as a set of instructions for the web browser or server, and explains the key differences between the two types. Client-side scripting includes JavaScript and runs on the user's device, while server-side scripting interfaces with databases and adds dynamic content to pages. Both are often used together to make sites interactive.
My presentation presents the basic concepts and some generally accepted rules of thumb for designing good web sites. Sites with different objectives will obviously have different needs.
Moreover, individuality and uniqueness of web sites are also valued features.
With that in mind, those guidelines are offered as a starting point for developing good web design skills, not as formula that should be followed point by point.
Web 1 allowed users to access information on read-only websites like dictionaries and university pages. Web 2 emerged in 2004, enabling users to interact and contribute to content through wikis and social networks. Web 3 is an intelligent version that is becoming smarter through machine learning and AI, delivering personalized content by understanding individual browsing histories.
This document discusses the evolution of the web and semantic technologies. It describes how the web has progressed from basic websites and search (Web 1.0) to user-generated content and social aspects (Web 2.0) to the semantic web that adds meaning and structure to data (Web 3.0). It argues that semantic technologies will help address the problem of information overload by making data smarter and more accessible. The document outlines different approaches to semantics including tagging, statistics, linguistics, and artificial intelligence, and how the semantic web aims to move intelligence from software to structured data.
Web 1.0 was the first generation of the world wide web and allowed for one-way broadcasting of information from website owners. Web 2.0 focused on enabling collaboration and information sharing between users online through things like social media platforms and wikis. Web 3.0 extended on these social aspects and aimed to provide location-aware and moment-relevant experiences across multiple devices. Web 4.0, still in development, envisions a symbiotic relationship between humans and machines through technologies like ambient intelligence and mind-controlled interfaces. Each generation brought new interactive capabilities to the internet and how people engage with online information.
Web 1.0 to Web 3.0 - Evolution of the Web and its Various ChallengesSubhash Basistha
The document discusses the evolution of the World Wide Web from Web 1.0 to Web 3.0. Web 1.0 allowed only read-only access to static web pages. Web 2.0 enabled user-generated content and interaction through features like blogs and social media. Web 3.0, also called the Semantic Web, will feature an intelligent web that can understand the meaning of information through standards like XML, RDF, and OWL that structure and define relationships in data. This intelligent web of linked and integrated databases will enable more advanced searches and interactions that go beyond just keywords.
This is the material of my technical training about "Fundamentals of Web" to non-developers, especially to business people. In this presentation, I tried to cover concepts with details that everyone can understand. Even though most of the information I mention verbally in the training, the slides could help the ones who are not very familiar with web and web applications.
The ARPANET was a network created in the 1960s by the US Department of Defense to enable resource sharing between universities and research centers. It connected 4 major universities using packet switching technology over interconnected nodes. This allowed the network to remain operational even if some nodes failed. The ARPANET pioneered internet technology and expanded to include more nodes, eventually evolving into today's internet.
The document provides an overview of basic web concepts including definitions of a network, the internet, the world wide web, web pages, home pages, splash pages, types of internet connections, web browsers, basic web design principles, essential elements of web content, and steps for planning a website. It defines key terms like network, internet, www, web page, and home page. It also lists different types of internet connections, web browsers, and basic principles of web design.
The document discusses XHTML 1.0, which is an XML-based markup language that extends HTML. It defines XHTML as a family of current and future document types that reproduce, subset, and extend HTML 4. The document outlines the rules for XHTML documents, provides an example of valid XHTML code, and describes various elements and tags that can be used in XHTML such as links, images, lists, and tables.
The document summarizes changes between older HTML standards and HTML5. It outlines updates to document type declarations, HTML tags, character encoding metadata, page structure elements, new semantic elements, multimedia tags, form input types, use of semantic HTML5 tags to provide structure and meaning instead of non-semantic divs, new JavaScript APIs, tools to check browser compatibility, HTML5 game development resources, and recommended references for learning more about HTML5.
The document provides an overview of learning HTML and CSS. It discusses HTML topics like DOCTYPE declarations, the HTML DOM, elements, attributes, and comments. It also covers CSS topics such as what CSS stands for, inserting stylesheets, the cascade order, external stylesheets, syntax, and examples of CSS code and selectors. The document includes code snippets of HTML boilerplate, elements, and an external CSS stylesheet.
This document provides an introduction to web standards. It discusses that web standards are formal specifications that describe the World Wide Web. The main standards organizations are the World Wide Web Consortium (W3C) which makes recommendations for technologies like HTML, CSS, XML; and the Internet Engineering Task Force (IETF) which publishes RFC documents. It then gives examples of specific W3C recommendations including XHTML, CSS, XML, and how they are used to structure web pages and apply styles.
The document provides an introduction to the Internet, including how data is transmitted via packet switching using the Internet Protocol (IP). Packets are broken into smaller units of information at the sender and reassembled at the receiver as the packets travel between routers. Domain Name System (DNS) maps human-readable domain names to IP addresses for easier identification of network locations. The World Wide Web is a system for accessing hyperlinked documents over the Internet using HTTP and HTML. URLs provide the location and protocol for retrieving web resources.
This document provides an introduction to web standards. It discusses that web standards are formal specifications that describe the World Wide Web. The main standards organizations are the World Wide Web Consortium (W3C) which makes recommendations for technologies like HTML, CSS, XML; and the Internet Engineering Task Force (IETF) which publishes RFC documents. It then gives examples of specific web standards like XHTML, CSS, XML, and how they are used to structure documents and separate content from presentation.
Girl Develop It Cincinnati: Intro to HTML/CSS Class 1Erin M. Kidwell
Here is some basic HTML code with <html>, <body>, <h1>, <h2>, and <p> tags:
<!DOCTYPE html>
<html>
<head>
<title>My First Webpage</title>
</head>
<body>
<h1>This is a Main Heading</h1>
<h2>This is a Subheading</h2>
<p>This is a paragraph of text.</p>
</body>
</html>
This document provides information about HTML elements and CSS properties. It discusses the different DOCTYPE declarations for HTML, XHTML, and HTML5. It also covers using ID and class attributes, headings, tables, and div elements. The document compares tables and div elements and provides tips for using tables. Finally, it defines margin, padding, transparency and ends with a cross-browser transparency example.
Lee Lundrigan is giving a lecture on introducing HTML and CSS. He discusses XML, the foundation of HTML, and basic HTML tags like paragraphs, headings, lists and links. The class will cover HTML and CSS basics but not advanced topics like HTML5, CSS3 or cross-browser compatibility. Students are assigned homework to create an HTML page with images, text and links and read about well-formed XML.
This document provides an introduction to JavaScript. It discusses that JavaScript is an object-oriented scripting language based on ECMAScript standards. The document outlines JavaScript's history and versions. It describes how JavaScript can be used to add interactivity to HTML pages through dynamic HTML, event handling, validation, and more. Examples of JavaScript uses include AJAX-based sites and Google Web Toolkit. The document concludes with a discussion of JavaScript compatibility issues and possibilities.
The document defines several JavaScript variables including x, y, and z and assigns them values. It then performs basic math operations on the variables like addition, subtraction, multiplication, and division. The results of the operations are written to the document using document.write to output the variable names and values.
This document provides an overview of HTML and web development using HTML. It covers topics such as what HTML is, HTML5, text editors for writing HTML code, basic HTML tags like headings, paragraphs, links and images, HTML tables, lists, and more. The document is intended as teaching material for a class on HTML and contains examples and explanations of HTML elements and tags.
This document summarizes a slideshow presentation on the Sustainable Livelihood Framework. It includes metadata about the presentation such as the title, description, author, categories, and embed code. The presentation contains 32 slides and was uploaded by user Srinivasan Rengasamy to introduce the concept of sustainable livelihoods to students in community development. It also contains scripts for embedding advertisements on the page.
The document discusses JavaScript and the Document Object Model (DOM). It begins with an introduction to JavaScript, including what it is, examples of basic JavaScript code, and how it is used for client-side scripting. It then covers the DOM and how JavaScript can be used to access and manipulate elements in an HTML document. Finally, it discusses several JavaScript libraries and techniques, including the YUI library and how it can be used for drag-and-drop and animation effects.
The document discusses JavaScript and the Document Object Model (DOM). It begins with an introduction to JavaScript, including what it is, examples of simple JavaScript code, and how it is used with HTML. It then covers the DOM and how it allows programming access to the structure of web documents. Several JavaScript DOM examples are provided, such as accessing and manipulating DOM elements. Finally, it briefly discusses JavaScript libraries and frameworks like YUI that can be used to add interactivity and dynamic behavior to web pages.
HTML stands for Hyper Text Markup Language, which is the most widely used language on Web to develop web pages. and dummies guide to html5 and complete html guide pdf
This document is a HTML page for a presentation on SlideShare titled "Eclampsia 4 Real". It includes metadata such as the title, description, and author of the presentation. It also contains scripts and code for features like comments, sharing options, and advertisements on the page.
Esoft Metro Campus - Diploma in Web Engineering - (Module III) Coding HTML for Basic Web Designing
(Template - Virtusa Corporate)
Contents:
Introduction to HTML
HTML Versions
HTML Standards
Creating a Simple HTML Document
Document Type Declaration
Comments in HTML
HTML Attributes
Paragraphs
Line Break
Headings
Text Formatting
Font Formatting
Images
Hyperlinks
Page Body
Lists
Tables
Cell Merging in a Table
Table Attributes
Horizontal Rule
Iframes
HTML Blocks
Division
Span
Audio
Video
Youtube Videos
Forms and Input
Introduction to CSS
Advantages of Using CSS
CSS Syntax
CSS Comments
How to Insert CSS?
CSS Tag, ID and Class Selectors
Grouping and Nesting Selectors
CSS Backgrounds
CSS Text
CSS Fonts
CSS Links
CSS Lists
CSS Tables
CSS Box Model
CSS Dimension
CSS Display - Block and Inline
CSS Positioning
CSS Float
CSS Alignment
Navigation Menu in CSS
This document provides an introduction to JavaScript including:
- JavaScript is an object-oriented scripting language that is a dialect of ECMAScript.
- It was originally designed to add interactivity to HTML pages through dynamic HTML, reacting to events, and data validation.
- JavaScript is now heavily used in AJAX-based sites to asynchronously retrieve and display data without reloading pages.
- The document discusses JavaScript compatibility issues and provides examples of basic JavaScript concepts like variables, comparisons, repetition, and popup boxes.
The document discusses XML transformations using PHP. It describes drawbacks of XSLT including that it is domain specific, verbose, and difficult to learn. It then presents an alternative approach of transforming XML using PHP templates which defines rules for each XML tag and traverses the document recursively. Specific libraries that can be used for PHP XML transformations are also mentioned, including patXMLRenderer.
The document provides an overview of the School of Computer Science programs at a university, including graduate programs (PhD, MS/PhD, MS), undergraduate programs (BS and BA in Computer Science, minor in CS), and a new Informatics program. It describes the research focus and opportunities for undergraduate and graduate students, including research labs, independent studies, honors programs, and paid REU and internship opportunities. Course requirements and tracks are outlined for the BS and BA in Computer Science. Transfer advising is also available to help students strategize their course plans.
The document summarizes a group advising meeting for computer science students at UMass. It discusses courses students are currently taking and will take in the future, including the 200-level core courses. It provides tips on meeting with advisors, maintaining tracking forms, considering study habits and involvement opportunities. It concludes by providing contact information for students to ask additional questions or have holds released on their accounts.
This document provides an overview of basic SQL concepts including attribute ambiguity, aliasing, tuple variables, missing WHERE clauses, selecting all attributes with *, tables as sets, and set operations. It discusses how SQL allows duplicate tuples, qualifying attribute names, and retrieving distinct vs all values. Examples are provided for common SQL queries. The goal is to help students understand how to create and manipulate relational databases using SQL.
The document is a lecture on the SQL language given at Trinity College. It introduces SQL as the standard language for relational databases and describes it as declarative, meaning the user specifies the desired results without specifying how to retrieve them. It then discusses some basic SQL statements like CREATE TABLE to define the structure of tables and import data types for attributes.
This document contains notes from a Java review lecture. It discusses the Java API and various classes and interfaces in the java.util package for common data structures like lists, maps, and sets. It explains that these are interfaces, not classes, and describes some common implementations like LinkedList, ArrayList, HashMap, and HashSet. It also covers generics and how to define parameterized types to avoid casting. Finally, it discusses the for-each loop as a cleaner way to iterate over elements in collections compared to a traditional for loop.
The document discusses constraints in the relational model of databases. It covers domain constraints, which require that the value of each attribute in a tuple must be within the defined domain for that attribute. Key constraints are also discussed, which ensure that tuples within a relation are unique. Key constraints can be expressed in data definition language by specifying that no two tuples can have the same combination of values for a subset of attributes called a super key. A super key is a minimal set of attributes where no duplicate values are allowed.
Here are the steps to read a line of input from System.in:
1. Wrap System.in in an InputStreamReader
2. Wrap the InputStreamReader in a BufferedReader
3. Use the BufferedReader's readLine() method to read a full line of input as a String
So something like:
BufferedReader br = new BufferedReader(new InputStreamReader(System.in));
String line = br.readLine();
This will read the input as a String rather than individual bytes.
1. Trinity College
Markup Languages
Timothy Richards
Trinity College, Hartford CT • Department of Computer Science • CPSC 225
2. HTML
Hypertext Markup Language
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 2
3. HTML
Hypertext Markup Language
A Family of Related Languages
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 3
4. HTML
Hypertext Markup Language
A Family of Related Languages
Most documents communicated
on the web are written using HTML.
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 4
5. HTML
After the next few lectures
you should be able to...
• Create standards-compliant static HTML documents
• Know where to find the reference definitions of HTML and
XML and be able to understand (most of) these defns.
• Determine if an XHTML document is syntactically correct
by consulting an XML document type definition or schema.
• Describe the history of HTML and relationship between
HTML, XML, and XHTML.
• Discuss pros and cons of following standards.
• Explain the new additions to the next version: HTML 5
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 5
6. HTML Example
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 6
7. HTML Example
Every HTML document contains two types of information
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 7
8. HTML Example
The markup information (tags)
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 8
9. HTML Example
The character data of the document (not tags)
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 9
10. HTML Example
Document Type Declaration (more later)
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 10
11. HTML Example
Document Instance
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 11
12. HTML Example
Each tag is either a start tag or end tag
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 12
13. HTML Example
The “word” in a tag is called the element name
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 13
14. HTML Example
This is called the content of the head element.
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 14
15. HTML Example
Each document has a root element
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 15
16. HTML Example
Each document has a root element
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body> This is always
<p>Hello World!</p> html in HTML
</body>
documents
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 16
17. HTML Example
This document strictly conforms
to the XHTML 1.0 standard
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 17
18. HTML Example
When viewed as a tree, XHTML 1.0 Documents always
have two children: head and body
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
<body>
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 18
19. HTML Example
When viewed as a tree, XHTML 1.0 Documents always
have two children: head and body
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
The head element is
<body>
used to provide certain
<p>Hello World!</p>
instructions to the browser
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 19
20. HTML Example
When viewed as a tree, XHTML 1.0 Documents always
have two children: head and body
<!DOCTYPE html
PUBLIC “-//W3C//DTD XHTML 1.0 Strict//EN”
“http://www.w3.org/1999/xhtml”>
<html xmlns=”http://www.w3.org/1999/xhtml”>
<head>
<title>HelloWorld</title>
</head>
The body element defines
<body>
the content of the page.
<p>Hello World!</p>
</body>
</html>
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 20
21. HTML Example
This document as a tree.
html
head body
title p
“HelloWorld” “Hello World!”
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 21
22. HTML History
• Tim Berners-Lee (CERN, 1990)
• CERN - Physics Research Center
• Originally designed with science and
engineering interest in mind.
• •1992 Elements:
title
• paragraph
• hyperlinks
• headings
• simple lists
• glossaries
• monospace text
• address blocks & search terms in URL
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 22
23. HTML History
• Tim Berners-Lee (CERN, 1990)
• CERN - Physics Research Center
• Originally designed with science and
engineering interest in mind.
• •1992 Elements:
title
• paragraph
• hyperlinks That was it!
• headings
• simple lists
• glossaries
• monospace text
• address blocks & search terms in URL
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 23
24. HTML History
• Marc Andreessen, Eric Bina
• National Center for Supercomputer Applications (NCSA)
• Graphical Browser: Mosaic (1993)
• Key Developers Left...
• To form Netscape Communications!
• Microsoft
• Created a team to develop Internet Explorer.
• The “Browser Wars”!
• 1993-1997 HTML was defined by browser support
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 24
25. HTML History
• Marc Andreessen, Eric Bina
• National Center for Supercomputer Applications (NCSA)
• Graphical Browser: Mosaic (1993)
• Key Developers Left...
• To form Netscape Communications!
• Microsoft
• Created a team to develop Internet Explorer. This was
BAD!
• The “Browser Wars”! Why?
• 1993-1997 HTML was defined by browser support
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 25
26. HTML History
• HTML Developers
• Required to “code” to each browser’s idiosyncrasies
• World Wide Web Consortium (W3C)
• Launched in October of 1994 (16 years ago this month!)
• Tim Berners-Lee
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 26
27. HTML History
• HTML Developers
• Required to “code” to each browser’s idiosyncrasies
• World Wide Web Consortium (W3C)
• Launched in October of 1994 (16 years ago this month!)
• Tim Berners-Lee
• Goal: Produce Web Standards!
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 27
28. HTML History
• Standards lagged behind de facto standards
• 2.0 was a standard 6 months after draft for 3.0 released
• 3.0 was never a standard
• 3.2 was adopted as a standard by W3C in 1997
• 3.2 specification captured “practice” of 1996 (year behind)
• HTML 4 released in December 1997
• HTML 4.01 is the “standard”
• HTML 5 is up and coming!
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 28
29. HTML History
HTML standards are now being
adopted from W3C rather than
browser manufactures.
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 29
30. HTML History
HTML standards are now being
adopted from W3C rather than
browser manufactures.
There are two important aspects
of standardization for HTML.
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 30
31. HTML History
HTML standards are now being
adopted from W3C rather than
browser manufactures.
There are two important aspects
of standardization for HTML.
Syntax
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 31
32. HTML History
HTML standards are now being
adopted from W3C rather than
browser manufactures.
There are two important aspects
of standardization for HTML.
Syntax Semantics
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 32
33. HTML History
The Syntax
Defines the strings of characters that can be
used to represent an HTML document and
those that cannot.
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 33
34. HTML History
The Syntax
Defines the strings of characters that can be
used to represent an HTML document and
those that cannot.
< > A-Z a-z / * & % $ @ ! 0-9
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 34
35. HTML History
The Semantics
A description of what the various elements of
a syntactically correct document mean.
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 35
36. HTML History
The Semantics
A description of what the various elements of
a syntactically correct document mean.
The p element represents a paragraph
The a element represents an anchor
The href attribute represents a hyperlink
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 36
37. HTML History
The Semantics
Formal methods do exist for defining
semantics, however, often a language is defined
using natural-language descriptions.
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 37
38. HTML History
The Semantics
Formal methods do exist for defining
semantics, however, often a language is defined
using natural-language descriptions.
For the syntax of computer languages,
however, we use a metalanguage to describe
components of the language.
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 38
39. HTML History
For languages such as Java, a formal notation
known as Backus-Naur Form (BNF) is used.
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 39
40. HTML History
For languages such as Java, a formal notation
known as Backus-Naur Form (BNF) is used.
BNF could be used to define HTML...
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 40
41. HTML History
For languages such as Java, a formal notation
known as Backus-Naur Form (BNF) is used.
BNF could be used to define HTML...
But, SGML
(Standard Generalized Markup Language)
is used for HTML 4.01
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 41
42. HTML History
For languages such as Java, a formal notation
known as Backus-Naur Form (BNF) is used.
BNF could be used to define HTML...
Turns out SGML is VERY complex!
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 42
43. HTML History
For languages such as Java, a formal notation
known as Backus-Naur Form (BNF) is used.
BNF could be used to define HTML...
Turns out SGML is VERY complex!
W3C introduced XML in 1998 to describe
HTML...
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 43
44. HTML History
For languages such as Java, a formal notation
known as Backus-Naur Form (BNF) is used.
BNF could be used to define HTML...
Turns out SGML is VERY complex!
W3C introduced XML in 1998 to describe
HTML...
This resulted in XHTML 1.0, which is
syntactically identical to HTML 4.01
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 44
45. HTML History
For languages such as Java, a formal notation
known as Backus-Naur Form (BNF) is used.
BNF could be used to define HTML...
Turns out SGML is VERY complex!
W3C introduced XML in 1998 to describe
With Some HTML...
Restrictions
This resulted in XHTML 1.0, which is
syntactically identical to HTML 4.01
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 45
46. HTML History
• XHTML 1.0
• Semantically identical to HTML 4.01
• Restricts from of HTML 4.01 generality
• Abstract Syntax Trees (AST)
• Representation of HTML elements “abstractly” as trees
• Concrete Syntax Trees (CST)
• Representation of HTML elements as characters in trees
• XHTML 1.0 AST == HTML 4.01 AST
• XHTML 1.0 CST != HTML 4.01 CST
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 46
47. HTML History
• XHTML 1.0 Differences
• Omitted tags are not allowed
• All element and attribute names must be lowercase
(HTML 4.01 names are case insensitive)
• All attribute values must be quoted (not always necessary
in HTML 4.01)
• Differences are not burdensome
• They make it easier to write software to process HTML
documents
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 47
48. Digging into XHTML
More on this next time!
Any questions?
Trinity College, Hartford CT • Department of Computer Science • CPSC 225 48