Web Technology 2ID60

Dr. Katrien Verbert Dr. ir. Natasha Stash Dr. George Fletcher

Today

•  Overview assignments •  Your input: what do YOU want to learn? •  Tutorial: querying DBpedia

Overview assignments Web Technology 2ID60 14 November 2013

Dr. Katrien Verbert Dr. ir. Natasha Stash Dr. George Fletcher

Overview

•  Team project (70%) •  Individual assignments (30%)

• Mini-project • report assignment

•  Questions

Overview

•  Team project •  Individual assignments

• Mini-project • Paper assignment

•  Questions

Team project: a dynamic web application

•  Groups of 3 – 4 •  Limited number of restrictions •  Be creative!

Team project: some guidelines

•  Result of the project has to be a dynamic Web application that: •  uses web data in some interesting way, •  provides a user interface for users to interact with the application.

•  User interactions with the web app have to be tracked and used. •  Examples include:

•  Automatic tailoring of content based on user interests. •  Recommendations based on interests of like-minded users. •  Visualisations of how users interact with the application.

Team project: example data sources

•  http://dbpedia.org/About •  http://doc.metalex.eu/ •  http://last.fm

Team project: very basic examples

•  http://www.programmableweb.com/ •  http://dbpedia.org/Applications#h80-3 •  Check the reading list of this week on Sakai

Very basic examples that use DBpedia data

http://www.rapidmonkey.com/birdsoftheworld/index.do

http://www.programmableweb.com/api/wikipedia/mashups

Very basic examples that use DBpedia data ht

tp://

mus

ic.c

amar

is.b

e/cl

ouds

ervl

et?

artis

t=M

adon

na

Examples that use DBpedia data http://www.aboutthisday.com/

Team project: time schedule

•  As indicated in previous lecture: team proposals due today •  Intermediate presentation: 3 and 5 December •  Final presentation: 14 and 16 January •  Final report

Team project: intermediate presentation

•  5 mins presentation •  Include:

• motivation • which datasets you will use • which tools you will use • current status. If already available, you can show first designs. • problems

Team project: final presentation

•  10 mins •  Must include a demo •  What is your project about? •  What have you learned when implementing your project? •  What would be interesting extensions?

Team project: screencast

•  Make a 5 mins screencast of your web app •  What is your project about? •  What can end-users do with your application? •  Tools: for instance Camtasia studio

Team project: final report guidelines

•  What was the project motivation? •  Which use cases did you implement? •  Which datasets did you use? •  What does the technical architecture of your application look

like? •  Which user data do you track and how do you use this data? •  How is your work related to the topics taught in this course? •  How much effort did it take to implement the project and how

did you distribute it in your group? •  Template will be provided

Team project: summary two basic requirements

•  Result of the project has to be a dynamic Web application that: •  uses web data in some interesting way, •  provides a user interface for users to interact with the application.

•  User interactions with the web app have to be tracked and used.

Overview

•  Team project •  Individual assignments

• Paper assignment • Mini-project

•  Questions

Paper assignment

•  Questions will be posted on 21 November, 18:00 •  Report due by 28 November, 18:00

Mini-project: Developing a Web Service for Room Thermostat

•  Within the Human-Technology Interaction course given in quartile 4 the students get an assignment to design and develop a graphical user-interface for a (mobile) room thermostat

•  Within our course we will develop the back-end of the thermostat app – the Web service that pretends to be the heating system. A thermostat can both send data to the heating system and retrieve data from the heating system

Example Thermostat App

Example Thermostat App

API of the Web Service Pretending to be the Heating System

String getDay() void setDay(String dayName) String getTime() void setTime(String time) String getCurrentTemperature() void setCurrentTemperature(String temp) // note that this overides the week-program //(i.e., weekProgram is in the off state) String getDayTemperature() void setDayTemperature(String dayTemp) // note that this potentially affects the current // target temperature, as defined by the week // program String getNightTemperature() void setNightTemperature(String nightTemp) // note that this potentially affects the current // target temparature, as defined by the week // program

void setWeekProgramOnOff(String onOrOff) String getWeekProgramState() String getWeekProgram() String setWeekProgram(String xml) // setWeekProgram accepts an XML representation of the // week-program and also does validation of the program, // to ensure that exactly 5 day switches and 5 night // switches are included for each day of the week. // setWeekProgram returns a string that indicates whether // the operation was successful ("Status=OK") or an error // message in case the week program is not valid.

Output Generated by the Web Service

<xml> <current_day></current_day> <!– one of Monday, Tuesday, …, Sunday --> <time></time> <!– of the format 12:30 --> <current_temperature></current_temperature> <!– of the format 21.0 --> <day_temperature></day_temperature> <!-- 21.0 --> <night_temperature></night_temperature> <!-- 16.0 --> <week_program state="on" > <!-- state on/off; all days must be present --> <day name="Monday”> <switch type= "day" state= "on"></switch> <!-- 12:00 --> <switch type= "night" state= "on"></switch> <!-- 13:00 --> ... <switch type= "day" state= ”off"> </switch><!-- 17:00 --> <switch type= "night" state= "on"></switch> <!-- 22:00 -->

<!– must specify exactly five night and five day switches --> </day> <day name="Tuesday"></day> <day name="Wednesday"></day> <day name="Thursday"></day> <day name="Friday"></day> <day name="Saturday"></day> <day name="Sunday"></day> </week_program>

</xml>

Capabilities and limitations

•  There are (exactly) two temperatures, called day and night, which the user can set (to arbitrary values in the range of 5 to 30 degrees centigrade, accurate up to 0.1 degrees). These two temperatures apply to all days of the week at once.

•  There is one week-program. Each day may have different times for switching between day and night temperature.

•  Each day has exactly five changes to night-mode and five changes to day-mode. Midnight is always an extra (is not counted) switch to the night temperature, unless this is the start of a day period (i.e., there is a day-mode switch at 00:00). Unused switches cannot be transferred to another day.

Capabilities and limitations

•  Each switch can be active xor inactive.

•  All temperature changes should happen with some observable delay.

•  Turning off vacation mode (i.e., changing the WeekProgram state from “off” to “on”) should set the temperature based on the week program (i.e., to the most recent temperature in the week program).

•  The server should use a clock that may be based on the computer’s clock (but need not be) and that runs 300 times faster: every second of real time is 5 minutes of simulated time elapse. In this way we can test the thermostat.

Mini-project

•  Individual assignment •  Due date: 12 December •  Detailed instructions will be posted on Sakai

Summary

•  Team project (70%) • Dynamic web app: be creative • Intermediate and final presentation • Screencast and final report

•  Individual assignments (30%) • Report assignment (15%) • Mini-project (15%)

Questions?

5-minute paper

•  What do YOU expect from this course?

k.verbert@tue.nl n.v.stash@tue.nl g.l.fletcher@tue.nl