Semantic Web Technologies
• Brief Readings Discussion
• Class work: Projects discussion
• Research Presentations
What is Web 2.0?
- Are we sure what Web 1.0 is (was)?
• Web 1.0 is the read only Web
• Web 2.0 is the read + write Web
• Web 2.0 is the lightweight semantics web
- First use of Web Services
- Lightweight Semantics are proving their worth
• Do we need Users 2.0?
- How many users will understand Web 2.0?
- Does it matter if they use the functionality?
O’Reilly’s view of Web 1.0 vs. 2.0
The Web as a Platform
Who’s Web 2.0?
• Google is 2.0, not Netscape
- The victory of data over applications?
- Does good data make application interfacing easy?
• Sun & Netscape (& ORACLE?)
- All you need is a PC, broadband & a Web broswer
• Is Web 2.0 back to 3270 terminals?
• Where is the innovation at Google now?
- Small companies purchased by Google
• With engineers too
• SXSW might say that Web 2.0 is small companies
building small pieces that can be loosely joined.
• Users might say that Web 2.0 is the ease of use and
replacement of client applications.
- Client applications without doing all the data entry?
Web (2.0) Services
• Google was born as a service
- Its value is “is proportional to the scale and
dynamism of the data it helps to manage”
• Users can be fickle, does Web 2.0 mean
constant innovation & keeping users happy?
• Continual improvement, no releases like “2.0”
• Google doesn’t host the content (oh yes it
does)
• It’s a collection of APIs, both internal &
external
• “A Platform beats an Application every time”?
Web as participation…
• Not publishing
• “The Web 2.0 lesson: leverage customer-self
service and algorithmic data management to
reach out to the entire web, to the edges and
not just the center, to the long tail and not just
the head.”
• Is it all about being a middleman?
- How much intermediation do we need?
- What about control?
Harnessing Collective Intelligence
• Links make it all work
- Links are very lightweight semantics
• Oh, so people make it all work
• Google uses links, Yahoo wouldn’t exist without them
• More users make a service more useful (eBay,
Amazon)
• Wikipedia, Flickr & Delicious all depend on
participation
• The software they all run on is also collectively built
• “Network effects from user contributions are the key
to market dominance in the Web 2.0 era”
How do blogs make a difference?
•
•
•
•
•
The format
The users (& growth)?
RSS?
More about (perma)links
Systems that enable a conversation are not
new, but now easier & growing
• Is is more about the change in society or the
technology?
Data is the new “Intel Inside”
• Google, Mapquest, Amazon, eBay
- Old data - new data - new formats
• People come for the data, not the experience?
• Mashups are finding new uses that no
company could code
- “Innovation in Assembly”
• Mashups on the browser like Greasemonkey
- It may be your data, but I’m going to look at & use
it my way
• Folksonomies are my (& our) views of data
Building Web 2.0
• Operations are key
- But may become more outsourced
• Users are part of the development team
• Lightweight Programming Models
- Scripting languages have massive power on the
user’s view
• Syndication over Coordination
- How about sync?
• Perpetual Beta
• Rights management
• Connectivity everywhere on anything
Core Competencies
• Services, not packaged software, with cost-effective
scalability
• Control over unique, hard-to-recreate data sources
that get richer as more people use them
• Trusting users as co-developers
• Harnessing collective intelligence
• Leveraging the long tail through customer selfservice
• Software above the level of a single device
• Lightweight user interfaces, development models,
AND business models
• Is this the Semantic Web?
Are You Ready for Web 2.0?
• "Web 1.0 was commerce. Web 2.0 is people," Ross
Mayfield
• Is there enough talent to make user-created media
worthwhile?
• Connectivity means not worrying about the Computer
Science of user experience or application
development
• How many half steps are there to 2.0?
-
Microformats
Structured Blogging
XML
Web Services
AJAX
• When do we know we’re at 2.0, then 3.0?
AJAX
• Pushing desktop software functionality into the
browser
- Interactive, state-dependent controls & functionality
- “Save As…” inside the browser
• Jesse James Garrett says:
- standards-based presentation using XHTML and CSS;
- dynamic display and interaction using the Document Object
Model;
- data interchange and manipulation using XML and XSLT;
- asynchronous data retrieval using XMLHttpRequest;
- JavaScript binding everything together.
AJAX Model
The AJAX Engine
• Sits hidden on the client to manage data &
interface
• Transforms browser into an asynchronous
client
• Data comes in blocks
-
Good default data sets
Interface manages expectations
Subsequent requests are small
REST (Roy Thomas)
XMLHttpRequest
How AJAX is different
What makes AJAX work?
• Broadband
• New(er) browsers
• Javascript is here to stay
- Functionality only beginning to be exposed &
explored
• Users expectations are growing
• More time on the Web than in applications
now (?)
• How can you imagine AJAX improving?
Projects & papers discussion
• Write a blog entry about the project or paper
you are considering or working on
- If you would like collaborators, ask for some
- Link to resources that are inspiring or are building
blocks