Saturday, 2 October 2010

24 hour comics day

It's 24 hour comics day, and I am IN.

The deal is - 24 pages in 24 hours. That's it.

I've chosen to heighten the stakes a little - 24 pieces of paper (no spares), and really really bad pencils. Because I can't find my pencil case. (Great start, hey?)

Follow it all here:

www.zoedoesa24hourcomic.blogspot.com

Monday, 27 September 2010

Non-text search is hard...

As far as I can see, there are basically two types of searchable object:

1. Text objects - such as a web page
2. Non-text objects - such as an image

These two require two different search functions:

1. Text-based search - searches the object itself
2. Metadata search - searches descriptive metadata

In my opinion, all content *should* have descriptive metadata (date written, author, so on). But only non-text objects actually require it - you can't search for 'picture of a horse' unless someone has actively tagged a picture with the word 'horse'.

The problem lies in the subjective nature of descriptive metadata, because tagging/taxonomy-ing/controlled vocabulary-ing is HARD. Really hard. And collecting that data is even harder, and utilising that data is harder again.

Case in point: I have a bunch of hobbies. One of them is perfumes.

If ever there was a set of content that didn't meet with text-based search criteria, it's scent. English doesn't even have scent words, or flavour words - we rely on 'smells like' and 'tastes like' because, outside of sweet/salt/bitter/sour/umami, there are no words (and 'umami', a taste-enhancement molecule found in MSG and parmesan cheese, is stolen from Japanese anyhow).

Because of this, perfumes are the perfect place to examine the efficacy of non-text search. How can I, as a perfume enthusiast and buyer, find new scents?

With difficulty.

Here are some comparisons of my favourite perfumes (I stress: despite what you're about to read, I love these scents), compared against their marketing blurbs.


Hermes Eau de Merveilles

They say:

An enchanting fragrance that encapsulates the spirit of wood, the memory of oceans and the sparkle of a constellation.

I say:

Smells like cake, only sexy. Exactly like I think spice would smell like. (Gentlemen: this is the one you want to buy your lady. You will love this so much.)


Guerlain Samsara

They say:


It was in China and Tibet that Jean-Paul Guerlain sought the inspiration necessary to create Samsara.
Samsara is a Sanskrit word that has its roots in Hinduism. It signifies the cycle of birth and rebirth, the perpetual voyage from one existence to the next, the wheel of life that keeps on turning.

Samsara is an invitation to serenity and harmony, with oneself and with the world. It is a voyage between East and West, Orient and Occident, an homage to the woman who is ever in search of serenity.


I say:

Smells like sand. No organic content, apart from one element - it's sexy (more civet than musk). Exactly like what I think Arrakis would smell like.


Shiseido Zen

They say:

Something to do with amber and 'wood breath'.

I say:

I only bought it because it has space rose in it. Not sexy.


Hermes Kelly Caleche

They say:

The unexpected caress of leather among flowers. Mimosa, iris, tuberose, and climbing rose. A floral perfume touched by leather.

I say:

A wood fire that just went out, and someone dropped some fresh/wet herbs on it. And some booze. Probably gin. Not sexy.


Jardin sur le Nil

They say:

A perfume of light and life, generous and sparkling. A bottle reflecting the shimmering green and ochre tints of the banks of the Nile River appreciated by women and men alike.

I say:

Smells like orange peel and mud, on a very hot day. Not sexy.


Chanel No 5

They say:

Femininity is timeless

I say:

Smells like perfume. Ur-perfume. Super-sexy.


The thing is, I would never search 'orange peel' when looking for a new scent, but neither would I search 'femininity is timeless' or 'cycle of birth and rebirth'. And I know that the results from using a frangrance wheel (yes, that's a Thing) are mid-lame to very-lame.

If I looked for a 'sexy' perfume I would get something vile and musk-ridden (don't fret, it's all synthetic now) with a celebrity branding attached, not something that smelled like cake. Similarly, a search for 'not-sexy perfumes' wouldn't take me to the best not-sexy perfume sources - Japanese houses like Shiseido and Kenzuo and Issey Miyake. (The cultural reasons for this are extensive and, for this post, irrelevant. But Japanese perfumes are amazing.)

Scents - they just don't translate to text.

And yet, a little part of me thinks - hopes - that this is a solvable problem. There will be a way to search for scent. One day.

...and to be honest, pretty much this whole post is to announce how thrilled I am to see that Hermes' new Eau Claire des Merveilles is now out.

Mmmmmmm... fresh cake. Delicious.

Thursday, 9 September 2010

I am so glad this exists: Monocle

I found out about this over a week ago (thank you for making it *and* telling me about it, @josephpearson), so it's about time I posted a synopsis about this potentially excellent new ebook tool.

I haven't played with it yet, but I like the sound of it: it's the Monocle ebook reader. http://inventivelabs.com.au/weblog/post/announcing-monocle/

Monocle is a new - and in my opinion, overdue - development in ebookery. It could be revolutionary, for one reason: it works in browsers. Which is to say, you access your eBook content through the internet.

Fundamentally, there are two ways to access content using machines:

1. Content lives on the user's own device. This is a download-based model.
Example: iTunes.

2. Content lives on external servers which are accessed by the user's device. This is a web-based model.
Example: Spotfiy.

There's a user-facing difference between the two, and a difference in the deployment of IP. In both cases I think the no-download (like Monocle) model will eventually have the upper hand.

For content publishers, the download model is terrifying for a simple reason - once the file is downloaded, it's fate is entirely out of your hands. No matter how much DRM it's wrapped in, someone, someday, will crack it. It will always have the opportunity to go wild, and when it does, there go (some of) the profits.

Similarly, once a file is downloaded, you can't track the usage well. Is it popular? Do people actually use it after they've bought it? It's hard to say (unless the content is software dependant, like iTunes, and that's not much fun).

For content users, the download model is the more annoying option, because it's tethered to a device. We hear people grumble all the time about iTunes, but never about spoftify - spotify is a smoother experience, because there's no fiddling (or protecting) downloaded files to get in the way of accessing the music.

To (shamelessly) use my husband as an example: he works from home some days, from the office others, but he does the same job in both locations. He's an academic, so he uses professionally published academic book content a *lot*.

At work and at home, he uses different machines. They're powerful desktops, so physically lugging them about is not a good option. Because of this, Aadevice-tethered eBook is no use to him.

But he always has an internet connection. He can always log on to a website.

There's a developing trend of people using multiple machines to access their content, instead of the trusty old family PC. My household isn't unusual - it has two people, a desktop, two laptops, an ipad, and an iphone. Matching that trend on the other side, we can also see internet access growing exponentially - it's quite likely (if not inevitable) that ubiquity is just around the corner.

Which is more likely? A future where people use the same device all the time, or a future where people have internet access all the time?

In choosing between browser-based and download-based content models, these respective trends point to an access-it-through-the-internet model as being where the smart money is.

A browser-based service naturally has to rely on a logon. This for me is a double-bonus, because (unless I've misinterpreted) Monocle can support the standard university logon services such as Raven and Shibboleth. That's great for universities, because that opens up the ability for a university library to buy browser-based eBooks and make them accesssible to all staff and faculty using their own, normal logon - no mess, no fuss, all access.

Monocle is also (hooray!) completely open source. I hope it does really, really well.

Tuesday, 24 August 2010

Vroom vroom iPad!

Last week, my husband caved. I knew it was going to be one of us, but to be honest, I always thought it would be me.

He bought an iPad.

It became part of our day-to-day immediately - I love the sweet little thing (especially 'Plants vs Zombies'). It's so easy! So fast! So many cute little apps, look at them, they're adorable!

I was reminded of an analogy I thought of months ago, but didn't realise was true until now (because I was busy *talking* about iPads rather than *using them and learning about them properly*, naturally):
  • Desktop (and laptop) computers are like geared cars.
  • iPads (and their tablety kin) are like automatics.
Here's the thinking behind that:
  • Desktops give you more control, but they're harder to use
  • Tablets give you less control, but they're easier to use
I prefer PCs myself (stop laughing), and I'm quite happy to wander off into the more bewildering realms of 'My Computer' and tinker with what I find. Sometimes I mess things up terribly, and often I get confused. It's hard territory in there, and sometimes, when the task is boring or fiddly (installing new software for example) I'd really rather not. But I do have a huge amount of control - if I want to have a poke around the program files, I can.

With a tablet, you don't have to know much about anything to make them work, and nothing is boring or fiddly or a chore. It's all smooth. What you give up is the ability to wander around places like 'My Computer', because there isn't one - or at least, not one you can ever find to access.

I think, in a couple of years' time, the current (but starting to fade) idea that all computer users - from the highly skilled to the I-just-want-it-to-work types - should use the same machines will emerge as having been a bad call. The same machines that bewilder the less-skilled irritate the life out of the highly-skilled, so why should they be the same? No happy middle-ground has emerged (yes, pipe down Mac users) and the odds are good that that's because there isn't one. The two groups have different needs, why should they use the same machines?

We have different tools for different tasks for different users in almost all fields of life, and I can't see why computers should be any different - or how they've stayed different for so long.

And until the division becomes clearer, I'm just going to keep playing 'Plants vs. Zombies'.

Thursday, 19 August 2010

Explaining the structure of XML

I thought of a good way to explain the structure of XML to someone who hadn't seen it before today:

XML is like Russian dolls.



Each doll has two halves, just like each XML element has two tags.

Each doll needs both halves to match up to be complete.

The dolls have to match up in order - the littler ones must always go inside the bigger ones.


(NB. I haven't managed to stretch this out to schemas yet, but I'm working on it...)

Saturday, 14 August 2010

Inception: I think I've cracked it

Ok. I could be wrong, but I *think* I've worked out Inception. Which is to say - there is an answer, and this might just be it. Naturally, the following contains spoilers.

If you can prove me wrong, please do.


Here we go...

1. Cobb is dreaming for the entire movie.

2. Cobb is not the protagonist. Mal is.

3. Because we are watching Cobb's dream, we never actually meet Mal. This is a movie where we never meet the main character.

4. All the characters but Cobb - including Cobb's version of Mal - are dreamed by Cobb. All the things that happen are events dreamed by Cobb. Consequently - the entire movie is a McGuffin.

5. No, all of it. It's all a McGuffin.

6. It's a McGuffin because it's the story Cobb's unconscious has made up to protect itself. But one real thing did happen -

7. Cobb and Mal were indeed stuck in limbo together.

8. She got out.

9. He didn't - he's still there.

10. (Brace yourselves)

11. He didn't plant the suicide idea in her. She planted it in him. She did the inception.

11.5 Consider - on whose word do we have it that Cobb did the inception? Cobb's. We see them both reciting the lines about waiting for a train, but we never see anyone say it for the first time.

12. It didn't work.

13. Because inception doesn't work.

14. It's because Cobb's drive to be the protagonist was so strong that he couldn't accept the incepted idea, or with it, the truth that she was right the whole time, and that he was the one living in the not-real world. The story was made up by his subconscious as a way to protect him from the idea that he wasn't the protagonist.

15. That drive - to be the protagonist - was, in the story-pattern used by mainstream movies, masculine.

16. The movie was pulling an act of inception on you - planting the idea that the woman might be the agent, the protagonist. Female agents do not happen in our mainstream movies, our stories. The movie is a story about our stories and our stories are gendered. The story world were the men are always the protagonists, that is a not-real world. Those stories are not good for us. They're keeping us stuck in not-real thinking. We need better stories now.

17. It won't work.

18. Because inception doesn't work.

Thursday, 12 August 2010

Embedded learning materials

Here is an example of how common cartridge materials can embed in websites like blogs.


This quiz material (it's QTI 1.2, standards fans) is actually hosted on cloud.icodeon.com by the good people at Icodeon, who are the only folk who are making a non-VLE-dependent Common Cartridge player at the moment (if you know of another, please let me know!)

It's embedded here the same way that a youtube video embeds - the content isn't present on this site at all.

It looks pretty shmick, but the key point here is that the content isn't present on this site. Publishing people I know you've spotted this already - that means it can't be copied, which means in turn, it can't be pirated.

Sweet, eh?

(Common Cartridge is a new educational content packaging standard by IMS global. More about Common Cartridge can be found here.)