Transcript W3C and Web Standards









Stands for the World Wide Web Consortium
Was created in October 1994
Was created by Tim Berners-Lee
Was created by the Inventor of the Web
Is organized as a Member Organization
Is working to Standardize the Web
Creates and maintains WWW Standards
Standards are called W3C Recommendations

The World Wide Web (WWW) began as a project at the
European Organization for Nuclear Research (CERN), where
Tim Berners-Lee developed a vision of the World Wide Web.

Tim Berners-Lee - the inventor of the World Wide Web - is
now the Director of the World Wide Web Consortium (W3C).

W3C was created in 1994 as a collaboration between the
Massachusetts Institute of Technology (MIT) and the
European Organization for Nuclear Research (CERN), with
support from the U.S. Defense Advanced Research Project
Agency (DARPA) and the European Commission.

W3C is working to make the Web accessible to all users
(despite differences in culture, education, ability, resources,
and physical limitations)

W3C also coordinates its work with many other standards
organizations such as the Internet Engineering Task Force,
the Wireless Application Protocols (WAP) Forum and the
Unicode Consortium.

W3C is hosted by three universities:
 Massachusetts Institute of Technology in the US.
 The French National Research Institute in Europe
 Keio University in Japan

Because the Web is so important (both in scope and in
investment) that no single organization should have control
over its future, W3C functions as a member organization.

Some well known members are:
 IBM
 Microsoft
 America Online
 Apple
 Adobe
 Macromedia
 Sun Microsystems

The Full List of Member Organizations includes a variety of
software vendors, content providers, corporate users,
telecommunications companies, academic institutions,
research laboratories, standards bodies, and governments.

The most important work done by the W3C is the
development of Web specifications (called
"Recommendations") that describe communication
protocols (like HTML and XML) and other building blocks of
the Web.

Each W3C Recommendation is developed by a work group
consisting of members and invited experts. The group
obtains its input from companies and other organizations,
and creates a Working Draft and finally a Proposed
Recommendation. In general the Recommendation is
submitted to the W3C membership and director, for a formal
approval as a W3C Recommendation.

The W3C standards approval process includes up to
7 different steps.
When W3C is publishing a new Web standard, the specification has worked
its way from an idea through a lot of refining processes including the
following:







W3C receives a Submission
W3C publishes a Note
W3C creates a Working Group
W3C publishes a Working Draft
W3C publishes a Candidate Recommendation
W3C publishes a Proposed Recommendation
W3C publishes a Recommendation

Any W3C member can submit a suggestion for a Web
standard to the consortium. Most W3C Recommendations
started as a submission to the consortium.

If a submission is within the W3C work area (or charter), the
W3C will decide if they should start working to refine the
suggestion.

Often a submission to the W3C becomes a Note. A Note is a
description of a suggestion refined as a public document.

A Note is made available by the W3C for discussion only.
Publication of a Note indicates no endorsement by W3C. The
content of a Note is edited by the member that submitted
the Note, and not by the W3C. A Note may be updated,
replaced, or rendered obsolete at any time. The publication
of a Note does not indicate that the W3C has started any
work related to the Note.

When a submission is acknowledged by the W3C, a Working
Group consisting of members and other interested parties is
formed.

The Working Group will normally define a time schedule and
issue a Working Draft of the proposed standard, describing
the work in progress.

W3C Working Drafts are normally posted on the W3C Web
site, along with an invitation for public comments.

A Working Draft indicates work in progress, but should not
be used as reference material. The content may be updated,
replaced, or rendered obsolete at any time.

Some specifications are more complex than others, and might require
more input, more time, and more testing from members and software
vendors. Sometimes these specifications are published as Candidate
Recommendations.

A Candidate Recommendation is also a "work in progress" and should not
be used as reference material. The document may be updated, obsolete,
and replaced at any time.

A Proposed Recommendation represents the final stage of
the work in the Working Group.

A Proposed Recommendation is still a "work in progress" and
may still be updated, obsolete, and replaced. But even if it
does not imply any official endorsement by the W3C, most
often a Proposed Recommendation is close to the final
Recommendation both in content and in time.

W3C Recommendations have been reviewed by the W3C
members, and have the W3C's director's stamp of approval.

A W3C Recommendation is considered a stable document
and may be used as reference material.
HTML is the universal markup language for the Web.

HTML 2.0 was developed by the Internet Engineering Task
Force HTML Working Group in 1996.

HTML 2.0 is an outdated version of HTML. For a Web
developer there is no need to study the HTML 2.0 standard.

HTML 3.2 became a W3C Recommendation 14. January 1997.
HTML 3.2 contained new features such as fonts, tables,
applets, superscripts, subscripts and more, to the existing
HTML 2.0 standard.

One of the elements added to the HTML 3.2 standard, was
the <font> tag. This tag introduced unnecessary complexity
to the important task of separating HTML content (text)
from its presentation (style). The <font> tag became
deprecated in HTML 4.0.

HTML 4.0 became a W3C Recommendation 18. December
1997. A second release was issued on 24. April 1998 with only
some editorial corrections.

The most important feature of HTML 4.0 was the
introduction of style sheets (CSS).

HTML 4.01 became a W3C Recommendation 24. December
1999.

HTML 4.01 was a minor update of corrections and bug-fixes
from HTML 4.0.

XHTML 1.0 reformulates HTML 4.01 in XML.

XHTML 1.0 became a W3C Recommendation 20. January
2000.

On January 22nd, 2008, W3C published a working draft for
HTML 5.

HTML 5 improves interoperability, and reduces development
costs, by making precise rules on how to handle all HTML
elements, and how to recover from errors.

Some of the new features in HTML 5 are functions for
embedding audio, video, graphics, client-side data storage,
and interactive documents.

HTML 5 also contains new elements like <nav>, <header>,
<footer>, and <figure>.

The HTML 5 working group includes AOL, Apple, Google,
IBM, Microsoft, Mozilla, Nokia, Opera, and many hundred
other vendors.
Specification
HTML 3.2
HTML 4.0
HTML 4.01
HTML 5
Recommendation
14. January 1997
24. April 1998
24. December 1999
19. October 2010
(latest draft)
XHTML is a stricter and cleaner version of HTML.
XHTML 1.0
 XHTML 1.0 became a W3C Recommendation 20. January
2000.
XHTML 1.0 Second Edition
 XHTML 1.0 Second Edition became a W3C Recommendation
1. August 2002. The second edition was not a new version,
but an update and a "bug-fix".

XHTML 1.0 was the first major change to HTML since 1997.

XHTML was an important step for creating a standard that
provided richer web pages on a wider range of user agents
(browsers), like desktop PCs, mobile (wireless) devices, and
cell phones.

XHTML 1.0 reformulates HTML 4.01 in XML. XHTML 1.0
relies on HTML 4.01 for the meanings of the HTML tags.

W3C's next step included modularization of XHTML into
smaller element collections, to make it easier to combine
XHTML with other markup languages, like vector graphics or
multimedia.

Modularization of XHTML reduced development costs,
improved cooperation with other applications (like
databases), easier communication with different user
agents, and cleaner integration between HTML and different
XML standards.

XHTML 1.0 is a reformulation of HTML 4.01 in XML.

Small devices cannot support all XHTML functions, therefore
XHTML 1.1 divides the specification into modules with
limited functionality.

Small browsers can reduce their complexity by supporting
only selected modules

XHTML 1.1 is a strict language. XHTML 1.1 is not backward
compatible with HTML 4.

XHTML Basic is a small subset of XHTML 1.1.
It contains only the basic XHTML features like
text structure, images, forms, and tables. It is
designed for small browsers (like in handheld
devices).

With support for the DOM in XHTML, event
handlers can be attached to XHTML elements
so that parent elements can handle events
before and after child elements.


XHTML-Print is a part of XHTML 1.1.
XHTML-Print is designed for mobile devices
and low-cost printers that generally print
from top to bottom of a page with no printing
buffer and without a device-specific printer
driver.

XForms are the successors of HTML forms.
XForms provides a richer and presentation
independent way of handling interactive Web
transactions. Designed to be integrated with
XHTML, we can expect that future ecommerce applications will demand the use
of XForms.

XHTML 2.0 is expected to remain similar to
XHTML 1.1, but the markup language may be
altered to conform to the requirements
of XML standards like XML Linking and XML
Schema.

XLink is a language for creating hyperlinks in
XML documents. XLink is similar to HTML
links - but it is a lot more powerful.

HLink is an extension to XLink, and it
specifies which attributes of elements
represent hyperlinks in XHTML, and specifies
how hyperlinks should be traversed.
Specification
XHTML 1.0
Draft/Proposal
Recommendation
26. Jan 2000
XHTML 1.0 Revision
XHTML 1.1
XHTML Modules
XHTML Modules 1.1
01. Aug 2002
31. May 2001
10. Apr 2001
08. Oct 2008
XHTML Basic
XHTML Basic 1.1
19. Dec 2000
29. Jul 2008
XHTML Events
14. Oct 2003
Specification
XHTML Print
Draft/Proposal
Recommendation
20. Sep 2006
XHTML Media Types (SE) 16. Jan 2009
XHTML 2.0
26. Jul 2006
XForms 1.0
XForms 1.0 (Third Edition)
14. Oct 2003
29. Oct 2007
XForms 1.1
XLink
18. Aug 2009
27. Jun 2001
HLink
13. Sep 2002

XML was designed to transport and store data.
XML 1.0
 XML 1.0 became a W3C Recommendation 10.
February 1998.
XML 1.0 (Second Edition)
 XML 1.0 (SE) became a W3C
Recommendation 6. October 2000. The
second edition is not a new version, but an
update and a "bug-fix“.
XML 1.0 (Third Edition)
 The third edition is not a new version, but an
update and a "bug-fix".
XML 1.1
 XML 1.1 was released as a Working Draft 13.
December 2001, and became a Candidate
Recommendation 15. October 2002. XML 1.1
allows almost any Unicode characters to be
used in names.
XML Namespaces
 In XML, element names are defined by the
developer. This often results in a conflict
when trying to mix XML documents from
different XML applications.
 XML Namespaces provide a method to avoid
element name conflicts.
XML Linking (XLink, XPointer, and XML Base)
 XLink allows you to insert links into XML
documents.
 XPointer allows the links to address into
specific parts of an XML document.
 XML Base is a standard for defining a default
reference to external XML resources (similar
to <base> in HTML).
XInclude
 XInclude is a mechanism for merging XML
documents using elements, attributes, and
URI references.
Specification
XML 1.0
Draft/Proposal Recommendation
10. Feb 1998
XML 1.0 (2.Ed)
XML 1.0 (3.Ed)
XML 1.0 (5.Ed)
XML 1.1
06. Oct 2000
04. Feb 2004
26. Nov 2008
04. Feb 2004
XML (2.Ed)
XML 1.0 Namespaces
16. Aug 2006
14. Jan 1999
XML 1.0 Namespaces (2.Ed)
16. Aug 2006
Specification
XML 1.1 Namespaces
Draft/Proposal Recommendation
04. Feb 2004
XML 1.1 Namespaces (2.Ed)
XML Infoset
XML Infoset (2.Ed)
XML Base
16. Aug 2006
24. Oct. 2001
04. Feb. 2004
27. Jun 2001
XML Base (2.Ed)
Xlink 1.0
28. Jan 2009
27. Jun 2001
Specification
XPointer Framework
Draft/Proposal Recommendation
25. Mar 2003
XPointer element() scheme
XPointer xmlns() scheme
XInclude 1.0
XInclude 1.0 (2.Ed)
XML Processing Model
XMLHttpRequest Object
25. Mar 2003
25. Mar 2003
20. Dec 2004
15. Nov 2006
05. Apr 2004
19. Nov 2009

CSS defines HOW HTML elements are to be
displayed.
CSS1
 CSS1 became a W3C Recommendation 17.
December 1996.
CSS2
 CSS2 became a W3C Recommendation 11.
January 1999. CSS2 has added support for
media (printers and aural devices),
downloadable fonts, element-positioning and
tables.
CSS3
 CSS3 is about breaking CSS into smaller
modules.
Specification
CSS 1
Draft/Proposal Recommendation
17. Dec 1996
CSS 1 (Revised)
CSS 2
CSS 2.1
CSS Mobile Profile 2.0
11. Apr 2008
12. May 1998
08. Sep 2009
10. Dec 2008
CSS TV Profile 1.0
CSS Print Profile
14. May 2003
13. Oct 2006
Specification
CSS 3
CSS 3 Namespace
CSS 3 User Interface
Draft/Proposal Recommendation
23. May 2001
23. May 2008
11. May 2004
CSS 3 Selectors
CSS3 Fonts
CSS3 Colors
CSS 3 TV
CSS 3 Backgrounds and
borders
10. Mar 2009
18. Jun 2009
21. Jul 2008
14. May 2003
10. Sep 2008
Specification
CSS 3 Text
Draft/Proposal Recommendation
06. Mar 2007
CSS 3 Lists
CSS 3 Line
CSS 3 Box model
CSS3 Multi column
07. Nov 2002
15. May 2002
09. Aug 2007
30. Jun 2009
CSS3 Ruby
CSS 3 Speech
14. May 2003
16. Dec 2004
Specification
CSS 3 Paged Media (PM)
Draft/Proposal Recommendation
10. Oct 2006
CSS 3 Generated PM
CSS 3 Print
CSS 3 Values
CSS3 Cascade
04. May 2007
13. Oct 2006
19. Sep 2006
15. Dec 2005
CSS3 Template Layout
CSS 3 Media Queries
02. Apr 2009
15. Sep 2009


W3C started to develop XSL because there
was a need for an XML-based Stylesheet
Language.
The XSL language consists of three parts:
XSLT, XPath, and XSL Formatting Objects.

XML Schema is an XML-based alternative to
DTD.


XPath is a language for selecting parts of an
XML document.
XPath is designed to be used by XSLT,
XQuery, and XPointer.

XQuery is a language for extracting data from
XML documents.

The Document Object Model (DOM) is a
platform and language neutral Application
Programming Interface (API) that allows
programs to access and update the content,
structure, and style of a document.
SOAP is a simple XML-based protocol to let
applications exchange information over
HTTP.
 Or more simply: SOAP is a protocol for
accessing a Web Service.
SOAP
 SOAP stands for Simple Object Access
Protocol, and is a format for sending
messages.

WSDL is an XML-based language for
describing Web services and how to access
them.
WSDL
 WSDL stands for Web Services Description
Language, and is an XML-based language for
describing Web Services.

RDF and OWL are two important Semantic
Web technologies.
The Semantic Web
 The Semantic Web is a framework for sharing
data between companies, applications,
enterprises, communities, and people,
independent of platform and software.
 RDF and OWL are key Semantic Web
technologies.

RDF - Resource Description Framework
 RDF is a language for describing Web
resources, such as the title, author,
modification date, content, and copyright
information of a Web page.
OWL - Web Ontology Language
 OWL is built on top of RDF, and is a language
for processing information on the internet.
SPARQL - Query Language for RDF
 SPARQL offer developers a way to write
queries across the wide range of RDF
information on the internet.
SMIL is a language for describing audiovisual
presentations on the web.
SMIL
 SMIL (Synchronized Multimedia Integration
Language) was designed to enable
multimedia presentations on the web.
 A SMIL presentation can be composed of
audio, video, images, text, and other media
types.

The Web Accessibility Initiative (WAI)
 WAI define guidelines for how to make Web
content accessible to people with disabilities.
 WAI is working for "Web accessibility for all"
through technology, guidelines, tools,
education, research, and development
projects.
Mathematical Markup Language (MathML)
 MathML is an XML-based language for
describing mathematical notation.
 The goal of MathML is to enable
mathematics to be served, received, and
processed on the Web, just as HTML has
enabled this functionality for text.
Scalable Vector Graphics (SVG)
 SVG is an XML-language for describing 2Dgraphics and graphical applications.
 SVG graphics do NOT lose any quality if they
are zoomed or resized.
Ink Markup Language (InkML)
 InkML is an XML data format for representing
digital ink data that is input with an electronic
pen or stylus as part of a multimodal system.
Internationalization
 The W3C Internationalization Activity has the
goal of proposing and coordinating any
techniques, conventions, guidelines and
activities within the W3C and together with
other organizations that allow and make it
easy to use W3C technology worldwide, with
different languages, scripts, and cultures.
Voice Browser Activity
 W3C Voice Browser Activity is about
expanding the Web to allow people to
interact via spoken commands and synthetic
speech.