|
Dag 1: Dinsdag 7 Mei 2002 | 08:30 - 17:00
|
Michael Benedikt
Mary Fernandez
Juliana Freire
Arnaud Sahuguet
|
TF1 - XML and Data Management
As Web applications manipulate an increasing amount of XML data,
there is growing interest on how to manage this data. Because XML is
extensible and flexible, it can be used in applications with radically
differing needs. This flexibility also implies that one cannot expect
to find out-of-the-box solutions for all different applications; given
the scope of the problem, the immaturity of existing tools, and the
evolving standards environment, building these solutions is a
challenging task.
The objective of this tutorial is to give an overview of XML data
management, presenting both the major issues involved in managing such
data and solutions for them. Topics covered in this tutorial include:
storing, querying, updating, and publishing XML data. Special emphasis
will be given to concrete techniques for developers, making clear how
properties of an application area influence the solution.
|
|
Dag 2: Woensdag 8 Mei 2002 | 08:30 - 10:00
|
- Opening Ceremony
- Opening Address
Hoyt Zia, Pacific Telecommunications Council
- Opening Remarks
Wendy Hall, IW3C2
- Welcome Address
Mazie Hirono, Lieutenant Governor of Hawaii
- Opening Keynote
Tim Berners-Lee, World Wide Web Consortium
|
Opening ceremony
- Opening door een Hawaiiaanse zangeres
- Welkoms woord door Wendy Hall (IW3C2)
- "aloha" door Marie Hirono, gouverneur van Hawaii
- Keynote sessie door Tim Berners-Lee: "bits mean something"
Opening Keynote
- Tim
Berners-Lee - Specs Count
De openings speech van Tim Berners-Lee, de man die in 1989 aan de
basis stond van het World Wide Web,
was nogal ongebruikelijk. Hij begon met een opmerking over spammers
"it's fraudulent -- they should be behind bars". Hij had het
verder nu eens niet over de toekomst van
het web maar sprak over de verschillende onderdelen ervan en hoe de verschillende specificaties en protocollen,
die het web mogelijk maken, van andere specificaties en protocollen
afhangen, tot op de laagste laag, de fysieke laag in het OSI model. Het
belang van het correct gebruiken van de talloze specs wordt nog eens
onderstreept. Verder maakte Tim zich sterk voor royalty-free
standaarden voor het web zonder het belang van patenten uit het oog te
verliezen. Hij wees nog eens uitdrukkelijk op het belang dat de
hedendaagse web technologie open en vrij implementaarbaar zal moeten
blijven. uit de media:
In his opening keynote today at the Twelfth World
Wide Web Conference in Honolulu, Hawaii, Tim Berners-Lee made a strong
appeal for the development of the web to continue unencumbered by
patent royalties.
In a talk entitled “Specs Count”, Berners-Lee outlined how important it
was that today's web technology specifications remain open and freely
implementable. He described how accessing a web page today involved
many layers of standards -- ethernet, IP, TCP, HTTP, MIME, XML,
Namespaces, XHTML -- each layer of which relies critically on the layer
below. As Berners-Lee is fond of noting, the web is “not done yet”,
therefore it is not unreasonable to imagine a future with a similar
number of layers built upon the existing ones. For that reason, it is
still highly critical that the "communal" nature of the specifications
is preserved.
Berners-Lee took off his hat as W3C Director for his speech, stressing
that it was delivered as personal opinion: he was highly pointed in his
support of royalty free licensing for web technology, a position that
doesn't meet universal approval within the consortium. The W3C has
itself had a difficult journey through issues of licensing its own
standards. Reacting to a large amount of dissent from the web and free
software community, it reversed plans to allow RAND ("reasonable and
non-discriminatory") licensing terms on its specifications. The new
patent policy is that every working group will aim to achieve royalty
free licensing terms by the time a spec reaches the final
Recommendation stage at the W3C.
Outlining both the pros and cons of enforcing royalties on open
specifications, Berners-Lee speculated that if the specifications
driving the web had not been royalty-free, then none of the 900-strong
audience would actually be at the conference. Enforcing royalties
discourages adoption both by the open source community, who simply
cannot pay royalties, however "reasonable", and other companies who
will shy away from the issues associated with licensing the technology.
In closing, Berners-Lee encouraged the delegates to get involved in the
patent and licensing debate. He mentioned the effect that the large
amount of public feedback on the W3C RAND debate had had, which
included a change in W3C patent policy and the invitation to the table
of representatives from the open source world. He encouraged continued
involvement and contribution to the debate, stressing that thoughtful
contribution to the ongoing debate was important.
Presentatie slides:
|
|
Dag 2: Woensdag 8 Mei 2002 | 10:30 - 12:00
|
W3C-1 W3C's Achievements and
Expectations
-
Introduction
by Steve Bratt
-
TAG working perspectives
by Tim Berners-Lee and TAG members
-
P3P 1.0
by Rigo Wenning
|
P3P 1.0
Het W3C heeft eindelijk het Platform for Privacy Preferences (P3P)
1.0 goedgekeurd. Het W3C is er meer dan vijf jaar mee bezig geweest.
Maar omdat de bescherming van privacy op het wereldwijde web
waarschijnlijk altijd een 'hot item' zal blijven, lijkt het op xml
gebaseerde systeem nog niet ingehaald door de hedendaagse realiteit.
Het W3C heeft P3P als een 'aanbeveling' gekwalificeerd, wat betekent
dat het grondig is geanalyseerd en geschikt bevonden voor wereldwijde
adoptie door websites en software-ontwikkelaars.
Veel van het aanvankelijke enthousiasme rond P3P is inmiddels geluwd,
vooral omdat vijf jaar wel een érg lange tijd is. P3P is in potentie
een oplossing waarmee individuele internetgebruikers informatie kunnen
krijgen over het privacy-beleid van een website, waarna hij/zij kan
beslissen of hij met die site in zee wil. In wezen bestaat het systeem
uit een gestandaardiseerde set meerkeuzevragen waarmee het
prvacy-beleid van de site wordt 'afgedekt'. De antwoorden op de vragen
zijn in xml gecodeerd, zodat het beleid door de computer kan worden
gelezen. Webbrowsers die geschikt zijn gemaakt voor P3P kunnen
automatisch het 'privacy-plaatje' van een site oproepen, dat
vergelijken met de voorkeuren van de gebruiker en vaststellen of die
met elkaar overeenkomen.
Gerelateerde links:
Presentatie slides:
|
|
Dag 2: Woensdag 8 Mei 2002 | 13:30 - 15:00
|
W3C-2 Web Services
Session Chair: Hugo Haas,
W3C Web Services Activity Lead.
|
Web services
Web Services zijn een
nieuwe soort Webapplicaties. Het zijn objecten die platform- en
programmeeromgeving onafhankelijk zijn. Eens ontwikkeld, kunnen andere
applicaties (en andere Web Services) ze ontdekken en aanroepen. Ze
hoeven dus op slechts 1 plaats in een netwerk (of het Internet)
bijgehouden worden om vanaf een andere plaats in het netwerk gebruikt
te kunnen worden.
One possible definition of the term "Web
service": a web service is an autonomous piece of software uniquely
identified by an URI that can interact with peer web services via
messages using WWW specific standards and protocols, such as HTTP, XML
or SOAP.
W3C Web service activities
3 working groups supervised by the Web services coordination
group:
- Web services architecture working group
-
XML
protocol working group
- Web services description working group
Web services architecture working group:
- started january 2002
- the Web services architecture requirements working draft covers
the following topics:
- interoperability
- reliability
- Web-friendly (consistent with the existing Web, uses XML,
aligned with semantic Web)
- security (authentication, authorization, confidentiality,
data integrity, privacy protection)
- scalability and extensibility (simple, modular, extensible)
- set of team goals for the working group (july 2002: more
complete and stable requirements document; october 2002: first
recommendations)
- there is also a usage scenarios working draft
XML protocol working group (XMLP):
- started september 2000
- chartered to provide:
- 1) an envelope for encapsulating XML data
- a serialization based on XML schema
- an instance of a transport mechanism, namely HTTP
- a convention for representing RPC in the envelope
- achieved in the following documents:
- SOAP 1.2 part 0: primer
- SOAP 1.2 part 1: messaging framework (required):
- processing model
- envelope
- protocol binding framework
- SOAP 1.2 part 2: adjuncts (optional):
- data model
- encoding
- RPC convention
- binding and feature description convention
- message exchange pattern (MEP)
- HTTP binding
- other documents:
- SOAP 1.2 test collection
- SOAP binding to email
- "Application/soap+xml" Internet draft
- attachment feature
Web services description working group:
- started january 2002
- goal: design a description language based on the submission
WSDL 1.1 reason: need for a standard format for describing Web
services:
- URI
- messages accepted and generated
- access protocol
- message encoding
- standard format based on XML
- first working draft of description language in june 2002
- the working group will also provide a primer, a test suite and
a mapping to RDF
Presentatie slides:
|
|
Dag 2: Woensdag 8 Mei 2002 | 15:30 - 17:00
|
W3C-3 Semantic Web
Session Chair: Eric Miller,
W3C Semantic Web Activity Lead
-
Introduction to Semantic Web
by Eric Miller
-
RDF Architecture
by Brian McBride
-
Web Ontology
by Jim Hendler
-
Semantic Web
Advanced Development
by Ralph Swick
-
Semantic Web Demonstration
by Eric Miller and Tim Berners-Lee
|
W3C the semantic Web
Het Semantic Web is de volgende generatie van het web zoals
we dat nu kennen, waarin via technieken als RDF, DAML en OIL
structuur is aangebracht in de inhoud van web-pagina's. Daarmee gaat
ontsluiten van informatie over van presentatie naar begrip. Tim
Berners-Lee meent dat als het Semantic Web op de juiste wijze
ontwikkeld is, het de mens kan assisteren in de evolutie van haar
kennis.
"The Semantic Web is an extension of the current web in which
information is given well-defined meaning, better enabling computers
and people to work in cooperation. It will
allow you to find, share, and combine information more easily."
The semantic web is the logical extension of the current web that
will allow you to find, share and combine information more easily.
the current web is alright for humans, but difficult for machine
processing. the semantic web relates objects in a more descriptive
way than just links.
-
Goals of the Semantic Web Activity
-
Define conventions for applications that exchange metadata on the Web
-
Enable vocabulary semantics to be defined by communities of expertise,
not W3C
-
Provide for the fine-grained mixing of diverse metadata
-
Making it cost-effective for people to effectively record their
knowledge.
RDF architecture
- Resource Description Framework
- a data model
- a representation of metadata
- an XML language
- RDF schema for defining vocabularies
- the foundation of the semantic Web
The RDF working group is chartered to:
- fix, clarify and improve the RDF specifications
- complete the specifications of the RDF schema
Web ontology
- started november 2001
- Web Ontology Language (OWL)
Semantic Web advanced development
- demonstrate the feasibility and utility of the semantic web
concepts
- develop components that can form the basis for widely deployed
semantic web infrastructure
- explore leading edge issues necessary for semantic web but not
ready for deployment
Gerelateerde links:
Presentatie slides:
|
|
Dag 3: Donderdag 9 Mei 2002 | 8:30 - 10:00 |
VEN-1 Netscape
Session Co-Chairs:
Peter Plamondon, Microsoft
Karey Patterson, N-Tech Media.
-
W3C Standards and
Netscape 6
by Katsuhiko Momoi,
Netscape
-
Web Applications,
Web Services, and Extensions - Some Directions
In Web Development With Netscape Gecko
by Arun Ranganathan,
Netscape
|
Netscape 6
Netscape 6 based on Mozilla engine, so version of
this Gecko engine is important.
Unified W3C DOM: Dynamic HTMl with W3C DOM
Legacy problems for DHTML in version 4 browsers. Now Unified DOM for
Mozilla/Netscape 6,
IE 5/6, Opera 5/6 browsers.
- API for both XML and HTML
- Compatible and Cross-Platform
- Preserve some old DHTML
Tools available at
http://developer.netscape.com/:
- JS debugger
- DOM inspector
- Web Site Tune Up wizard
- XBStyle-Cross Browser Style API
- xbDebug
- xbDOM
Demo: Mysidebar Tab addition of W3C Doc Lookup
CSS/XML International Content Demos
Additional list styles via Mozilla to possible CSS3 inclusion for
multilingual language types.
XML format
Mozilla Japan TOP 50 web compatibility test project.
Browser detection issues:
-
Gecko tag in browser string
Netscape/Mozilla common problems:
-
many pages have old legacy codes
-
NN6 does not support IE4/NN4 private extentions
-
NN6 is not destinguised from NN4
In conclusion:
-
How does a new generation browser get accepted by users?
-
A variety of methods are being used to evangelized NN6 features and how
web devellopers can write standards rather than to specific browsers
-cross over strategies
-
Code samples publications are critical
SOAP Enveloppes
Netscape/Gecko gives you building blocks
- HTML 4.01, XHTML: markup languages
- CSS: styling system for HTML and XML
- DOM+JS; manipulate content and style
- XML: multi-purpose markup, e.g. data, RPC
Dynamic Web
Content: Web Applications and Services - Arun Ranganathan
Web Standards in User-Agents
HTML 4.01 and CSS
DOM and Javascript
XML
Demo:
- 2 images mbv DIV
- Case Study: theKompany.com
- XML in a browser
SOAP and Web Services
- SOAP is on the verge of standardization (W3C)
- Remote procedure calls via XML and Javascript
- Javascript as a language to script
Gerelateerde links:
Presentatie slides:
|
|
Dag 3: Donderdag 9 Mei 2002 | 10:30 - 12:00 |
VEN-2 Microsoft
Session Co-Chairs:
Peter Plamondon, Microsoft
Karey Patterson, N-Tech Media
-
SOAP Tutorial
- Henrik Frystyk Nielsen, Microsoft
|
Wat is SOAP?
SOAP is een
lichtgewicht protocol, gebaseerd op XML, om software componenten en
applicaties te laten communiceren met gebruik van standaard Internet
HTTP.
- SOAP staat voor Simple Object
Access Protocol.
- is een communicatie protocol.
- is voor communicatie tussen applicaties.
- is een formaat voor het zenden van berichten.
- is ontworpen voor communicatie over het
Internet
- is platform onafhankelijk.
- is taal onafhankelijk.
- is gebaseerd op XML.
- is makkelijk en uitgebreidt.
- is ontworpen als een W3C standaard.
Design Principles and examples
A simple protocol for exchanging data in a decentralized environment
- It is based on XML technologies
- provide an extensible message envelope that
can be exchanged over a variety of underlying protocols
- ..it is a protocol
Design principles
- modular
- General purpose
- Federated
- Heterogeneous
SOAP 1.2 Status
- We are really close to last call
- We are officially at zero issues
- Working Group will then make the call for enter last call
What changed between SOAP 1.1 and 1.2?
- more than 200 issues has been brought up
- New Protocol Binding Framework
- Clearly defined processing model
- Described in terms of XML Infoset
- Better fault handling
- Primer has a list of changes as well
- but is not backward compatible!
SOAP Processing model
- Provides extensibility framework
- Extensibility through Modularity
- Dynamic composition of data
- Dynamic composition of process
- Simplicity and Extendibility at the core
- Modules complement each other
|
|
Dag 3: Donderdag 9 Mei 2002 | 13:30 - 15:00 |
Afternoon Plenary Session
Session Chairs:
Dave De Roure,
University of Southampton
Arun Iyengar,
IBM T.J. Watson Research Center
|
The Grid -
enabling resource sharing within virtual organizations
- Grid Vision:
resource sharing and coordinated problem solving in dynamic,
multi-institutional virtual
organizations
- need to manage dynamic distributed infrastructures, services and
applications
example: Grid for multiplayer games
- state of the art globus toolkit
- small standards based set of protocols for distributed system
management
- information centric design
- open source implementation
- successful enabler of higher-level quality labels
- gridprojects in e-science are there (eurogrid..)
- Open Grid services Architecture
defines WDSL
delivery via open source Toolkit 3.0
- the Grid Service = interfaces/behaviors + service data
- maintains a set of service data elements (XML fragments in
standard containers
- findServiceData that uses this elements
- Lifetime Management
- GS interface supports
- GT3: an open source OGSA-compliant globus toolkit
- global grid Forum
Keynote Address
Alfred Spector,
IBM Research
- text analysis technologies and techniques seldom work together
well
- Explosive growth of data
- all the techniques come to a plateau fast
- we need a new quality of text technology
- we have to add knowledge to the search
- He argues that a combination of information
retrieval grammatical
statistical advanced statistical and semantic technologies will prove
needed to achieve quality
- database analogy
the relational theory was nice and complicated and succeeded
- Outline
we have to cross the semantic barrier
integrate many technology (many are so different, do we know the
right storage structure)
Organization (we need advanced motivational techniques)
- Example:
Customer Claim Mining
- UIMA Project (Framework for abstract data structures)
- common KM Architecture
- upside: many
- downside: any standardization imposes some constraints
Presentatie slides:
|
|
Dag 3: Donderdag 9 Mei 2002 | 15:30 - 17:00 |
W3C-6 Cool Web
Session Chair: Philipp Hoschka,
W3C Interaction Domain Leader.
- Introduction
by Philipp Hoschka
-
SMIL 2.0
by Thierry Michel
- SVG 1.1
by Dean Jackson
- Mobile SVG profiles
by Chris Lilley
|
SMIL 2.0
SMIL 2.0 specificeert interactieve multimedia voor het Web. Het is
onlangs door W3C als 'recommendation' aangenomen. De omvang van het document met de
specificaties is 15 keer zo groot als van de voorganger SMIL 1.0 SMIL
2.0 biedt veel nieuwe, rijkere mogelijkheden en een rijkere
taalconstructies. Het kan rekenen op de ondersteuning van de belangrijke
industriële spelers, zoals RealNetworks, Microsoft en Oratrix. SMIL 1.0
neemt al een belangrijke plaats in op het Web als het integratie
formaat voor de RealPlayer media browser. Het wordt ondersteund door
Quicktime 4.1, de GRiNS editor en speler, tezamen met diverse andere
spelers.
- Multimedia element description
- SMIL has different possibilities to define the manner
multimediastreams have to be displayed
- Layout options
- Timing features (Sequential Composition, Parallel Composition,
Exclude Composition..)
- Content Control
- Basic Hyperlinks
- Temporal / Spacial Hyperlinks
- Animation(http://www.w3.org/2002/Talks/www2002-smil20/media/animw3c.svg
- Players:
- Players:
Capabilities
- Modularisation and Profiling for different applications
- Extends SMIL 1.0 functionalities
- Animation facilities
- Event handling, (much) more detailed timing semantics
- New time container (exclusive)
- Extended positioning capabilities (e.g., several top level windows,
nested regions)
- Content Adaptation: preload media objects
- Visual transition effects
- More accessibility, internationalization, and metadata
- Some of the modules may (and are) reused by other XML
applications.
- The Idea is to bring graphical stuff also to pda's
- SVG 1.1 supports mobile devices (intermediate version)
- SVG 1.2 is the next proper version
- SVG basic vs. SVG full
- New SVG tiny
- lookout - many wishes are in pipeline
Presentatie slides:
|
|
Dag 4: Vrijdag 10 Mei 2002 | 08:30 - 10:00 |
Morning Plenary Session
Session Chairs:
Dave De Roure,
University of Southampton
Arun Iyengar,
IBM T.J. Watson Research Center.
|
New foundations
for Trust and the Web
Richard DeMillo - V.P. Technology Strategy, Hewlett Packard Co.
- Internet is in trouble (!)
- steel doors in paper walls
- ad hoc leads to patch and fill
- security management doesn't scale
- privacy protection is not embedded
in technology
- sept. 11
- chain of trust must be grounded in
infrastructure
- IT is agnostic (?)
- a common thread for success is ...
trust (as table stakes)
-
http://news.bbc.co.uk/hi/english/sci/tech/newsid_1860000/1860241.stm
- Web-services
new e-commerce frontier
big players
- the grid - the matrix?
- --> chain of trust worth well
defined trust levels is needed
- a chain of trust begins with a
component
- if a skilled hacker gets in
physical contact with your machine it's toast
- linux and open source is a great
principle
- Itanium processor family "industry
standard basis for secure platform architecture"
limits I/O access to the firmware (protects hardware)
builds from designed-in security
- secure platform architecture as
basement (it is open source to)
- privacy:
user choice
assurance
embedded in corporate practices (!!!)
embedded in technology
- trust (hope?) that applications
enabling accessibility will remain royalty free
Toward a
New Politics of Intellectual Property
Pamela Samuelson -
University of California at Berkeley
- copyright is a mayor issue everywhere!!
- people think copyright doesn't apply to their ordinary activities
- there is a need of information environment definition
- There's a "holing bill" at FCC - if it passes, US
Government
will impose Digital Rights Management
- US seems to fall back to the wild wild west..
- http://www.digitalconsumer.org/
Some bullets:
- In the 1950s "environmentalism" wasn't in the vocabulary. Change
can happen, but slowly, in the public mind.
- Some content businesses seriously want to outlaw general purpose
computers because they easily enable hackers to circumvent protection
mechanisms.
- Businesses have obtained too much power from the legislative
government.
Presentatie slides:
|
|
Dag 4: Vrijdag 10 Mei 2002 | 10:30 - 12:00
|
|
GC-5
Making information useful with metadata
Session Chair: Stu Weibel
OCLC
|
Making information useful with metadata
Jane Hunter - Rights Markup Extensions for
the Protection of Indigenous Knowledge
-
Indicuous Knowledge
-
Customary Laws
-
Access Restrictions
-
Markup Languages - Customary Constraint
-
Application of constraints
-
User Profile
Smithsonian Collaboration
-
Interoperable Metadatamodel
Acces to different resources depents on type of user: male female,
tribal member etc.
Demo: multimedia presentations
Dynamic generation of SMIl presentations
Australian Applications
-
N.F. nelson report
-
Oodgeroo Nunukal Archives
Universal Directories: Web Services
as Human Services
POP: Power Of Presence
....
Data and Image Standards of the Open Archive Initiative
A How and Why for Small Collections
.....
Gerelateerde links:
Presentatie slides:
|
|
Dag 4: Vrijdag 10 Mei 2002 | 13:30 - 15:00
|
W3C-8 Device Independence
Session Chair: Philipp Hoschka,
W3C Interaction Domain Leader
- Introduction
by Philipp Hoschka
- Voice and Multimodal Interaction
by Dave Ragett
-
CC/PP
by Kazuhiro Kitagawa
-
XForms 1.0
by Steven Pemberton
|
Wat is interoperabiliteit en waarom is het
belangrijk?
In de afgelopen jaren is een rijke hoeveelheid technologieën
ontstaan die we samen nog steeds het web noemen: allerlei vormen van
markuptalen, scripting, plugins en andere applicaties. In deze
stortvloed aan ontwikkelingen lag er weinig nadruk op onderlinge
afstemming. Heeft u ook wel eens te maken gehad met een website die het
ineens niet deed op een andere versie van dezelfde browser? Kent u
applicaties die bedoeld waren om over het internet te draaien, maar die
op een of andere manier bij sommige collega's maar niet aan de gang te
krijgen zijn? Of geprobeerd om uw eigen website met behulp van een voor
blinden aangepaste browser te bekijken, en gemerkt dat die Flash-animatie
op uw homepage voor hen de toegang blokkeert? De usability van websites
heeft vaak te lijden onder het scala van elkaar wederzijds uitsluitende
technologieën.
Met de komst van XML en daaruit voortvloeiende internationale
standaarden als SVG, XForms, SMIL, SOAP en CSS kunnen
veel van de genoemde problemen eindelijk achter de rug gelaten worden.
Door de interoperabiliteit van deze open webtechnologieën, die
voortkomen uit de internationale not-for-profitorganisatie W3C, wordt
het maken van toepassingen voor het internet veel simpeler, goedkoper
en betrouwbaarder dan voorheen. Interoperabiliteit houdt in dat
specificaties voor webtalen en protocollen op dusdanige wijze rekening
met elkaar houden dat gebruikers ervan op aan kunnen dat het gewoon
altijd werkt. Dat betekent dat men niet zoals nu sterk afhankelijk is
van een bepaalde combinatie van hardware en software om toegang te
krijgen tot bepaalde delen van het WWW. Met de opkomst van bijvoorbeeld
mobiel internet en borstzakcomputers is een dergelijke verhoging van de
betrouwbaarheid en gebruiksvriendelijkheid zeker geen overbodige luxe.
Presentation slides:
|
|
Dag 4: Vrijdag 10 Mei 2002 | 15:30 -
17:00
|
W3C-9 - Leading the Web to its full potential
Session Chair: Steve Bratt,
W3C Chief Operating Officer
-
Integrated W3C
Technologies in Amaya
by Vincent Quint and Irène Vatton
-
Town Meeting: Leading the Web to its full
potential
This session provides attendees with an opportunity to ask questions
on any W3C Activity, and to engage in group discussions on topics
related to Web development.
|
Integrated W3C
Technologies in Amaya
Amaya provides an environment for testing new Web technologies.
These technologies are designed to be combined
-> http://www.w3.org/Amaya/
Presentation slides:
|
|
Dag 4: Vrijdag 10 Mei 2002 | 17:00 -
17:30
|
Closing Plenary Session
Session Chair: David Lassner,
University of Hawaii
-
Closing Ceremony
-
Awards Presentation
|
The 12th WWW conference (WWW2003)
- will be held in budapest, hungary, may 20..24, 2003
- see the official website
for details
|
|
Dag 5: Zaterdag 11 Mei 2002 | 09:00 -
16:00
|
D1 - Track: Protocols, the Web, and Web Services
- 9:00 - 10:30
Does HTTP have a future?
Chair: Tim Bray (Antarti.ca)
Panel: Mark Baker (Planet Fred), Edd Dumbill (XML.com), Henrik
Frystyk Nielsen (Microsoft)
- 11:00 - 12:30
Do Web Services Change Anything?
Chair: Tim Bray (Antarti.ca)
Panel: Mark Baker (Planet Fred), Edd Dumbill (XML.com), Rohit Khare (KnowNow),
Henrik Frystyk Nielsen (Microsoft), Stuart Williams (HP)
|
Does HTTP have a future?
There's a lot of muttering about whether HTTP is "broken" as the
community keeps wielding the same hammer to solve new problems, such as
Web Services. Possible directions HTTP could go include:
- remaining the dominant web protocol,
more or less as it is now
- being gradually replaced by other
protocols
evolving and being extended (really, not just on paper)
HTTP
- 3rd most important protocol, by volume
- 2nd most important by most real world measures
- most important by hype, journalism and investment
- in its second decade
Panel: Questions
- Why did HTTP (the web) succeed?
- What can we learn from its succes?
- Where is HTTP today
- What is the actual deployment status of the various features of HTTP
1.1?
- Do we need any future major versions of HTTP?
- What's the right way to build session and transaction semantics on
top of HTTP?
- Are there any big outstanding il8n problems?
- Do we need to worry about IRI's?
Do Web Services Change Anything?
The level of hype around Web Services
has reached a point where we can't ignore it. So, even assuming that
the Web Services Future comes to pass, what are the impacts at the
protocol level? In particular, we will address issues raised in IETF
RFC 3025, particularly security.
As a fraction of total Internet
traffic, HTTP is by far the dominant application layer protocol, but
classical protocols for email and file transfer aren't going away; and
nor will emerging protocols for voice, video, gaming, and other novel
uses. New meta-protocols such as SOAP even claim to be HTTP-independent
so they can migrate to new application-layer protocols. This panel will
compare the prospects for new developments such as BEEP, WebDAV, WAP2,
SOAP Routing, and more.
Web Services
- What is a web Service?
- What do Web Services have to do with the Web?
- What Web Services have actually been deployed in production as of
now?
- Where do we think that Web Services will be important?
- Does BEEP (bxxp, etc) make a difference?
- Does WebDAV make a difference?
- Are Web Services a security thread?
- Is the open-ness of port 80 at risk?
- What do the firewall configurations of the future look like?
- What security protocols are missing?
Discussion about Webservices Do they change
anything?
- It seems, that after a year of soap only about 141
Services are online.(1 google and 140 calculators..) ...
- SOAP has to grow up and have an own protocol
(maybe BEEP)
- I see the problem in the not existing ability of
viewing XML directly - so there is not a direct use of it (lack of
browsers)
- security: how about
http://project.honeynet.org/
?
- it's classical, that the protocol track is at the
same time as the secutity track --> application architects are
seperate from security-networkers
- SOAP is used only in very simple applications
|
