Why Web Standard Are Important: An Overview of W3C, Its Operation and Current Technical Directions
Why Web Standard Are Important: An Overview of W3C, Its Operation and Current Technical Directions
W3C is international…
W3C Hosts (in red) and W3C Offices (in blue) around the Globe
W3C members
W3C Members ensure the strength of W3C
they influence the strategic direction of Web Standard Development
each member is represented in the Advisory Committee (AC)
the AC has regular meetings (twice a year) where issues are discussed
the community of key players on the Web
Recommendations are developed by the Members’ experts
documents are developed in Working Groups staffed by the Members’ representatives
altogether, they form a community of more than 600 experts
the keyword is consensus building
W3C staff
More than 50 researcher and engineers
Very international team (residence in 9 countries, around 12
nationalities…)
Their role is:
provide directions to W3C
coordinate the activities of W3C
facilitate active member participation
communicate the results of W3C
So, what do we do ?
The “horizontals”…
What is “mobile”?
Currently W3C concentrates on mobile/cell phones and
network aware PDA-s
but a workshop on Ubiquitous Web took place earlier this year!
Question: what does W3C contribute to this environment?
Characteristics of mobile
Extremely dynamic market
Big business in Europe and Asia, with US catching up fast
extremely dynamic market: ≈800M units sold in 2005, 63% of installed phones are Web capable (est.)
Potentially huge number of users
40 Million new users per year in China alone!
future: one PC per family, but one (or more!) mobile per person…
Potentially huge number of users in developing countries (where, for many people, mobile is the only gateway
to the Web/Internet!)
It is multipolar World
Variety of hardware architectures
Nokia, HP, Samsung, Palm, Motorola, DoCoMo, Sharp, SonyEricsson, KDDI, Sony, Dell, Sagem, Fujitsu, …
they represent different architectures, processors, displays, user interface styles, …
Operating systems evenly spread the field
proprietary, Symbian, PalmOS, Windows Mobile/CE, Linux, …
none of them dominates!
Thriving software industry for all variants
A World of varieties
Source: T-Mobile
The players
Lots of hardware and software vendors (of course)
Two main industry consortia outside W3C:
Open Mobile Alliance (OMA):
integrated some older consortia (WAP Forum, SyncML Initiative, …)
specifies interoperable technical specification for Mobile devices
3rd Generation Partnership Project (3GPP)
specifies technical specification for 3rd Generation GSM networks
roughly: 3GPP is the radio, OMA is the application level
but there are overlaps; they try to cooperate and synchronize
Position of W3C
OMA and 3GPP often integrate existing technologies (when available and possible)
only if the technology does not exist, do they define it themselves
W3C’s expertise lies in the development of the basic Web architecture
W3C provides already a number of “building blocks”; these are integrated in 3GPP/OMA specifications
Bottomline: there is good cooperation among W3C, OMA, and 3GPP
Example: XHTML/CSS
XHTML Basic: a “minimized” profile of XHTML
no frames, scripting; only simple tables (no colgroup, tbody/thead/tfoot,
justification in cells)
had an early adoption for WAP 2
CSS Mobile: under development
Important for simple devices
For higher end devices, XHTML Basic may not be that relevant any
more…
there are browsers that can manage XHTML 1.1+CSS
Example: SVG
SVG has two “Mobile profiles”: Tiny and Basic
Newer phones come with SVG built in (122 different types end of June 2006)
some Web Browsers have SVG Tiny built in (Opera, NetFront, …)
W3C is working on SVG 1.2 Tiny (in strong synchrony with 3GPP)
SVG Mobile becomes the vector graphics tool for Mobile!
Example: XForms
XForms aims at an enhancement of traditional HTML forms
XForms (full) is a W3C Recommendation
XForms Basic should become a Rec later this year
e.g., very restricted requirements on XML Schemas
(courtesy of solidapp.com)
Complements the work of OMA and 3GPP and the work done elsewhere at W3C
Launched in May 2005 with a separate set of directed sponsorship
The general approach:
solve interoperability and usability issues for end users and content providers
not geared at new technology
explain how to use existing technology and improve implementations
Best practices
Studied existing “tips and tricks” (W3C Accessibility, iMode, Opera, Openwave, Nokia,…)
60 “Best Practices”; examples:
thematic consistency/“One Web”
no table for layout, no spacers-GIFs, no frames
screen estate constraints: small top navigation, avoid large graphics
has an overview of the typical current set of devices
keep URI-s for sites short
scrolling should be in one direction
…
Close-to-final release issued last week!
Semantic Web…
What is needed?
Data should be available on the Web for further processing by other machines and
programs
Data should be possibly merged, connected, combined on a Web scale
Sometimes, data may describe other data (e.g, using metadata)…
… but sometimes the data is to be exchanged by itself, like a calendar or travel preferences
Machines may also need to reason about that data
The “Semantic Web” is an infrastructure extending the current Web for the interchange and
the integration of data on the Web,
RDF triples
We said “interchange” and “connection” of data… ie, resources have to be connected
But a simple connection is not enough… it should be named somehow
a connection from me to my calendar is not the same as the connection from me to my CV (even if all of these
are on the Web)
the first connection should somehow say “myCalendar”', the second “myCV”
Hence the RDF Triples: a labelled connection between two resources
This triple connects my home site with my calendar, using a myCalendar “predicate”
note that URIs are also used to name the connection itself
RDF is a general model for such triples
… with machine readable formats (RDF/XML, Turtle, n3, RXR, …), where RDF/XML is the “official” format
<rdf:Description rdf:about="http://www.ivan-herman.net">
<foaf:name>Ivan</foaf:name>
<abc:myCalendar rdf:resource="http://…/myCalendar"/>
<foaf:surname>Herman</foaf:surname>
</rdf:Description>
URI-s: merging
It becomes easy to merge data
e.g., applications may merge the SVG annotations
Merge can be done because statements refer to the same URI-s
nodes with identical URI-s are considered identical
Merging is a very powerful feature of RDF
metadata may be defined by several (independent) parties…
…and combined by an application
one of the areas where RDF is much handier than pure XML in many applications
Ontologies
The Semantic Web needs a support of ontologies:
“defines the concepts and relationships used to describe and represent an area of
knowledge”
Example: portals
Vodafone's Live Mobile Portal
search application (e.g. ringtone, game, picture) using RDF
page views per download decreased 50%
ringtone up 20% in 2 months
Sun’s SwordFish: public queries for support, handbooks, etc, go through an
internal RDF engine for White Paper Collections and System Handbook
collections
Nokia has a somewhat similar support portal
Further information
More information about W3C:
http://www.w3.org/Consortium/
Mail me:
[email protected]