views:

22

answers:

1

I have a database where various student musicians have their specialisms and departments listed (for example somebody could specialise in violin in the Historical Performance department). Also for example, consider Johann Sebastian Bach - he is a musician and composer in the Baroque style. Logically perhaps I'd want his specialism to fall under "Composition" and his department to be "Baroque".

I think that 'department' could be covered happily by the "category" property, but what to make of 'specialism'? That's a kind of category, too. The hCard spec says that it's cool to use 'category' twice, but it seems kind of dirty since department and specialism are so semantically unrelated.

What about the 'notes' property? Or 'role'? Thoughts?

+1  A: 

Hey,

I think I'd be inclined to use the category for 'Composition' and 'Baroque' either into role or as part of his faculty address. I'm not entirely clear on whether 'Baroque' would be an addressable part of your school, but if that would be the case then that'd work. Maybe think about it in terms of how you would describe them - would Johann be a 'Composer of Baroque' (role) or a 'resident of Baroque department' (adr).

vCards aren't that super detailed, unfortunately.

Phae
Hm, interesting it's not a residential school, so adr is out for the student contacts at least, but as far as I can see at the moment, role is the most interesting / likely possibility. I did think that 'class' would also be a good one but it turns out that's something to do with security, go figure ;-)
hollsk