MokE: a tool for Mobile-ok evaluation of Web Content - Presentation Transcript
MokE: a tool for Mobile-ok evaluation of Web Content Vassilios Stefanis Computer Engineering & Informatics Department University of Patras, Greece Research Academic Computer Technology Institute Patras, Greece
Contents
Introduction
W3C Mobile Best Practices
W3C MobileOK Tests
Hidden Web
Our system
Conclusions and future work
Introduction (1)
Mobile Web
www from mobile devices
Digital Divide
Dot.mobi
One world, one web
Why a new term?
Limitation of mobile devices
Introduction (2)
Limitation of Mobile Devices
Screen size and resolution
Network
Input method
Cost of transferred data
Energy consumption
Computational power and memory
Supported technologies and plug-ins
W3C Mobile Web Best Practices (1)
W3C Mobile Web Initiative (MWI)
Objective
Improve the user experience of the Web when accessed from mobile devices
Recommendations
For the delivered content
User agents
Devices
Other technologies
√ Χ Χ Χ
W3C Mobile Web Best Practices (2)
Best practices grouped in five categories:
Overall Behavior
Navigation and Links
Page Layout and Content
Page Definition
User Input
60 Best Practices
Default Delivery Context (1)
Defined by W3C
Default mobile experience
Hypothetical mobile user agent
DDC is a minimum context necessary for a reasonable experience of the Web
DDC ≠ limitation
Exploit the capabilities of actual devices
Default Delivery Context (2) No support for client side scripting Script HTTP ver1.0 or more recent HTTP ver1.1 HTTP CSS Level 1. In addition, CSS Level 2@media rule together with the handheld and all media types Style Sheet Support 256 Colors, minimum Colors 20 kilobytes Maximum Total Page Weight JPEG and GIF 89a Image Format Support UTF-8 Character Encoding XHTML Basic 1.1 delivered with content type application/xhtml+xml Markup Language Support 120 pixels, minimum Usable Screen Width Value Characteristic
Mobile OK Tests
Basic Tests and Pro Tests
Based on Best Practices
Basic Tests
Machine Verifiable
Subset of Mobile OK Pro Tests
Content passes Mobile OK Basic Tests √ Author has taken basic steps to provide a functional experience for mobile users
Mobile OK Basic Tests (2)
Some examples:
CHARACTER_ENCODING_SUPPORT
NO_FRAMES
PAGE_TITLE
SCROLLING
TABLES_NESTED
Every test may return:
Success
Fail
Warning
W3C MobileOK checker library (1)
Beta version – 2/2008 (Alpha 10/2007)
MobileOK Basic tests against a URI
Open and generic library
W3C help developers
Run private instances
Fix or improve the code
Develop their own tools
W3C MobileOK checker library (1)
Before this...
W3C Best Practices checker (3GWeb Project)
Foundation CTIC – MobileOK checker http://validadores.tawdis.net/mobileok/en/
dotMobi – MobileOK site test http://ready.mobi
Our system - modules Mobile Crawler Hidden Web Checker W_Profiles The Web
Our approach
New mobile crawler
Seek for hidden content
Run MobileOK Basic tests for
Crawling results
Retrieved hidden content
Rate the web site depend on
MobileOK tests results
Weights of importance
Hidden Web - Intro
Web content that typical crawlers can’t reach. Why?
No hyperlinks
Authorization issues
Dynamic content and web forms
Hidden web >>> Classic Web
Typical web crawlers reach the “surface” of the web...
Hidden Web - Forms
Main entry to hidden web
Forms:
Ideal for interaction with the user
Problem for crawler designers
2 type of forms
Predefined input Send every possible input
Free text
Hidden Web – Our module
Free text Create proper queries for every form
Hidden content is auto generated
We seek for the best subset in the “presentation level”
Presentation of our system (1) Main Page Authorized user
Presentation of our system (2) Create new crawler
Presentation of our system (3) Crawling results
Presentation of our system (4) Hidden content
Presentation of our system (5) Results
Presentation of our system ( 6 ) Create profiles
Presentation of our system ( 7 ) Results Rating
Calculating Ratings Rating Weighted rating # pages that return pass for the test t n # pages that return warning for the test t n The number of tests Weight by the user for test t n Total number of tested pages
Conclusions
Crawling web site
Retrieve hidden web content
Run MobileOK Basic Tests for whole content
Rate the whole content based on:
Tests results
Weighted rating/ ask the user!
Future work
Improve:
Hidden web module
Crawler
Experiments with a large number of web sites – impact of hidden content
1 comments
Comments 1 - 1 of 1 previous next Post a comment