[kEv] Topics for the Summit

["JG Rae" <jgr@xxxxxxxxxxxxxxxxx>]

I was wondering how people think we should structure the day on the 9th. I
have four business questions and I think if went through them in order, we
could focus people's energy and get something quite productive going. I'm
floating this as a possible idea, would be very interested to know what
others think.

Q1 What kinds of things do we want to do, that better quality metadata could
help us with?

I'd like to start here, because it's a chance to remind ourselves of our
common purpose before we get too geeky. As I said in my post yesterday,
metadata is for answering "have you got..." and "may I have..." type
questions. The invitation to the summit did a good job of flagging up the
business issues that Kendra is trying to solve.  

Ideally I would like to ask people to think about this before the 9th;
orperhaps we could hand out cards during registration that people could
write an idea on and drop them into a bucket?

Q2 What tags do we need to support those activities?

This is the meatiest topic. There are some good examples on the Kendra wiki,
and I like the way you flag up that Kendra has a more ambitious scope than
Gracenote. The answers to Q1 should help frame the discussion here. 

It may prove helpful to split into smaller groups, but I don't whether it's
good or bad to divide people along industry lines, or to have a content
discovery group, a licensing group, e-commerce group, maybe. What do others
think?

Business Q3 Who is going to populate the tags?
Business Q4 What controls do we need to restrict people changing some tags?

I think maybe we could handle Q3 and Q4 together. I'd like to stimulate a
social media / mashup agenda, in which some tags are completed by fans a la
Wikipedia, some have to be policed by the content owners (e.g. publisher,
collection society, royalty rate) and some can be filled in by software
translating from other metadata schema. 

I was at a conference on web 2.0 and social media last week, and one idea
that came out was that you can use metadata to tag metadata. This really
helps if you want a standard that interoperates well with other industry
initiatives, because it lets you say that "Kendra-title is the equivalent of
CDDB-track-name". 

If we're not all exhausted by this point we could talk about exposing our
metadata through API's, and getting some dialogue going between software
developers and users:
Q5 What tools will help us leverage the value of metadata?
Q6 What tools will help us populate metadata, improve it, validate it, etc?

I'd love to know what other people think. Please evolve, warp, edit, mutate
and improve it.

Gordon