I think this belongs on the -new list, so I'm forwarding from -discuss.
--
Scott Reynen
MakeDataMakeSense.com
Begin forwarded message:
From: Michael Smethurst <[EMAIL PROTECTED]>
Date: June 15, 2007 3:26:17 AM MDT
To: Microformats Discuss <[EMAIL PROTECTED]>,
"For discussion of new microformats." <microformats-
[EMAIL PROTECTED]>
Subject: Re: [uf-discuss] Using org in vcard in haudio
Reply-To: Microformats Discuss <[EMAIL PROTECTED]>
Hi Scott
I was thinking along the same lines but couldn't decide on the
demarcation
between people and people AS organisations. Is a function of
production or
fame? Would the same rules apply to Tony Blair, Andy Warhol? Is
there a
difference between Mark E Smith the person and Mark E. Smith the
""singer""?
Or Tony Blair the person and Tony Blair the politician. Anyway, for
now I'm
keeping it simple and leaving out org cos I don't know from the db
if it's a
group or a person... So just fn it is
Anyway, my first shot at combining hevent and haudio to describe a
tracklist is in the wild(ish) here:
http://bbc-hackday.dyndns.org:2822/programmes/shaunkeaveny/episodes/
43n8r
If we can reach some consensus it'll be rolling out across all the
bbc music
radio and tv programme pages soon(ish). That's a /lot/ of pages so
any help
in getting it right would be much appreciated
KNOWN ISSUES
- each track played is both an event and audio. Because hevent uses
summmary
for it's title and haudio uses fn there's some duplication
- because each event ( a programme segment) doesn't have a url but
the
contributor / contact hcard does both operator and tails parse out
this url
as the url of the event (see also
http://microformats.org/discuss/mail/microformats-discuss/2007-June/
009789.h
tml)
- the way contributors are added in haudio seems to differ from how
contacts
are added in hevent. In hevent the hcard can live on the same
element as
contact; the haudio examples seem to suggest that the hcard lives
on a child
element of contributor. This might make the layout of a tracklist
in a table
difficult if the track has 2 contributors (performer + composer)
- music brainz links. Both the bbc and another newer more 2.0 radio
service
are committed to making music resources (artists, releases, tracks)
addressable thru urls using musicbrainz ids. But we don't want
these to be
our public facing canonical urls. We also don't wanna expose links to
musicbrainz to users in tracklists (cos they'd get confused). So
I've added
empty links to musicbrainz artists (where available). These are
definitely
designed for machines first and humans not at all - apologies - I /
know/
it's bad
Anyway, help, tips, corrections, clarifications, rants all appreciated
Thanks
michael
On 14/6/07 23:28, "Scott Reynen" <[EMAIL PROTECTED]> wrote:
I'm cross-posting this to the -new list, as it might also be relevant
to the hAudio work happening on -new.
On Jun 14, 2007, at 10:48 AM, Michael Smethurst wrote:
What should you do if you don't have the data to
determine whether a "contact" is a group or an individual?
I think it depends on the context. If it's just a generic contact
that you know nothing about, I'd say just use fn, as adding org is
potentially incorrect information. But if you know it's a music act,
I think it makes sense to consider even an individual performer's
name to be an organization name in that context. I'd say there's a
difference, for example, between Norah Jones the person, who would be
<span class="fn">Norah Jones</span>, and Norah Jones the musical act,
which would be <span class="fn org">Norah Jones</span>.
Peace,
Scott
_______________________________________________
microformats-discuss mailing list
[EMAIL PROTECTED]
http://microformats.org/mailman/listinfo/microformats-discuss
http://www.bbc.co.uk/
This e-mail (and any attachments) is confidential and may contain
personal views which are not the views of the BBC unless
specifically stated.
If you have received it in error, please delete it from your system.
Do not use, copy or disclose the information in any way nor act in
reliance on it and notify the sender immediately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
_______________________________________________
microformats-discuss mailing list
[EMAIL PROTECTED]
http://microformats.org/mailman/listinfo/microformats-discuss
_______________________________________________
microformats-new mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-new
