Ubiquity fun (at the Scripting Challenge)

The PSW command I told you about in the previous post was my entry for the Scripting Challenge at the Scripting and Development for the Semantic Web Workshop, which took place on Sunday, in Crete, collocated with ESWC 2009. The challenge idea is to create a < 1000 lines script which uses the Semantic Web to create real-world applications.

I couldn't go there to present it, so I created a screencast / demo to replace my live presentation:



Unfortunately I didn't win, it was the Researchers map that took the prize this year, but I got quite nice feedback (thanks everybody!) and new Twitter friends :). Also, it was very fun from one end to the other: from creating the script, to the paper describing the script, to creating the screencast (interesting experience, long live recordMyDesktop and mencoder) and getting feedback about it almost live on Twitter and Facebook, as the scripts were presented at the workshop and I was home having (late) lunch.

I'm now working on advancing the idea, to also have it a part of my MSc (that's why blogging takes a while, because MSc takes the other whiles in my life :) ).

Please, don't send me .doc attachments!

.doc as in Microsoft Word's proprietary format file

I know, thousands of MBytes have been written on this subject, but
beside the fact that it's a proprietary format and all those points that I support:

• Microsoft Word documents cannot always be read by other word processors.




• Documents produced with one version of Microsoft Word cannot always be read by other versions of Microsoft Word.




• Microsoft Word documents are not guaranteed to look and print the same way on every computer and printer.




• Microsoft Word documents are extremely large compared to other file formats.




• Sending Microsoft Word files can violate your privacy.




• Microsoft Word files are a security hazard.

I'd like to highlight one more aspect: if it's not a DOCUMENT then you should not send it as an attachment at all: just copy the bloody text in the email body. Or, at least, attach it as a text file that most email readers can parse and print in the email body.
Why am I so mad?
I received, a few hours ago, a simple table (1 page long) where I had to lookup my name and confirm some data written there. But guess what, it was an attached .doc instead of plain csv in the email message. And I had to go through all the mess of downloading it and opening the editor to read it.
I also received announcements (like "some papers are due until day x, 12:00 PM") in .doc attachments, or even empty emails that gave no sign about their purpose until you opened the attached .doc.
I cannot see the rationale behind these kind of actions: I mean, I know, it was probably easier for that person to attach the .doc she created for HER OWN PURPOSE then re-format that for the rest of the world, but you don't speak your native language that the other one does not understand just because it's easier FOR YOU. If you knew what you are doing and still did it for YOUR OWN COMFORT then you're a stupid lazy bastard and you fully deserve my eternal hate!
I can't imagine that people that send .doc attachments don't now that:

• it is so damn annoying to have to download things (where to store it (damn, the desktop is full)? oh, and now I have to wait for that to download?, etc, etc)




• the office editor (either MS's or OpenOffice) takes some time to load and this gets really annoying if you have some other applications running (you must now this, don't you?)

Imagine how much time this takes compared to just reading a piece of text in an email! I'd probably ignore that email if it didn't concern me too, and this is actually what you were counting on, isn't it? You devil! The next time I will send the response in hexa, because it concerns you and you're the one responsible of reading it and making communication between us possible!

For all these reasons,
PLEASE, DON'T SEND .DOC ATTACHMENTS!