Miłowski — things I do

• markup since the 1990 ...
• math ...
• all things XML ...
• the Web ...
• standards — XML, XSLT, XProc, RDFa ...
• open source — WebKit (MathML), Poster, Green Turtle, XProclet, ... and many others
• lots of code ...
• lots of running

Miłowski — recent

• Enabling Scientific Data on the Web — PhD, Informatics (2014) — University of Edinburgh, School of Informatics, ILCC
• How to survive the coming namespace winter — Balisage 2014
• XML on the Web — HTML5 & XML pre-conference Seminar — Balisage 2014
• Scientific Computing in the Open Web Platform — XML Prague 2014
• Local Knowledge for In Situ Services (slides) (paper) — XML Prague 2013

Miłowski — one more thing

I taught here in 2004 and 2005: XML and Related Technologies.

It was a different time. XML was as a good thing.

I'm older, wiser...

XML is still a good thing and so is the Web.

Malhotra — things I do

• try and keep up with this guy!
• struggle through iSchool...
• JAVA!
• JavaScript, HTML, CSS, fun API stuff, web service thingamajig, PHP (yeah, i'm one of those...)
• just enough code...
• not enough running...

Malhotra — recent

• Stairway to (Integration) Heaven — Netapp, Inc - Software Developer Intern (May-August) — Salesforce based project
• MIMS, 1st year — many projects through last year (some through this very class)
• Becoming I Foundation — internationally recognized non profit (cofounded, 2010) — expanded to 5th city in India!
• MUN Cafe! — startup experiential learning venture (Hyderabad, 2012)
• eBay, India — Java developer aka coding monkey

Class Introductions

• You'll get a chance during the pitches to introduce yourself.

• Quick polls:

  • web geeks, technology geeks, design geeks, don't categorized me, man!
  • MIMS 2015, MIMS 2016, other

The Approach

• We want to use the modern Web —
• the Open Web Platform —
• using current technologies,
• without ignoring the successes of the past,
• or declarative approaches,
• for organizing, retrieving, and searching information.

Overall Goals

In this course we explore:

• technologies that align and support 202: Information Organization and Retrieval,
• homework and a final project that do so as well,
• general introduction to various technologies of the Web,
• architectures that support information organization, search, and retrieval.

If you aren't in 202, that's OK. The everything works on its own as well.

There is overlap with 253: Web Architecture but you should find this course organized differently and focused at a different level. That said, you probably don't want to take both at the same time.

Technology Goals

• a quick sprint through the Open Web Platform,
• enough about JavaScript so that you are dangerous,
• some bits on visualization and mapping,
• serious bits about architecture and tools for organizing information,
• some XML and search technologies you might not get elsewhere.

Course Website

http://courses.ischool.berkeley.edu/i290ta/f14/

• everything you need is on it,
• if not, that's a mistake,
• it is a living document,
• we'll adjust it to make sure you have everything you need,
• check it often.

Note: Everything is done on the Web using common Web formats (i.e. not PDF). All you should need is a browser. I'll even try to make it work on your phone.

Class Meeting Structure

A rough breakdown of class time:

1. any pressing issues or questions,
2. a variety of lectures with slides on each topic (hint: look at them before class),
3. some time for discussion and/or lab time,
4. and we'll try to address your questions too.

There will be open topic where we will agree in advance what we will cover. These sessions will be your chance to cover additional topics you want to hear about.

Homework

The purpose of homework is to explore a technology and not to punish you.

You must:

• make a valiant attempt to accomplish the task,
• contact an instructor if you get stuck,
• collaborate with your classmates and colleagues for solutions,
• turn in your assignment before the class meeting on the date it is due.

If you feel an assignment is too much, let's chat.

There are eight homework assignments: four independent and two 2-part.

Projects

There is a final project divided into:

• milestones that track your project,
• delivery of the final project.

You or your team must present something, briefly, at each stage.

You may do projects independently or as a team of 2-3 people.

Projects must scale to the size of the team.

Projects can span classes. For example, maybe you are in 202 and want to do one project that can satisfy both classes. Also, maybe you want to collaborate with another team of people in 213 for the UI design.

If you do, please let us know so we can help coordinate with the instructor for the other class.

Project Pitches

Don't worry! We'll make this easy as you can:

1. pick something that we pitch to you all,
2. pitch a project idea (or two) to the class,
3. pitch yourself (i.e. your skills).

You must do (2) or (3). If you can't find something to do or someone to partner with, we can get you sorted.

Again, don't worry.

Find something fun to do that interests you and a team of people with whom you want to work.

Grading

• 10% class participation — yes, you must show up!
• 30% homework — each is graded on a 10 point scale and not in a draconian way
• 20% project milestones
• 40% final project

Upcoming Dates

• Homework #1 — Get Setup!— due ~ 09/04
• Homework #2 — Back to the Future with CSS3 — due 09/11

Questions?

Questions, comments, suggestions?

Jokes?

Don't run for the door yet...