Marcel Molina wrote:
I've talked to the analytics team. Three main metrics we're going to
work to surface on something like dev.twitter.com
<http://dev.twitter.com> initially (and maybe even an API so you all
can build experiences/explorers around annotations):
1) All time most used namespaces/keys.
2) Trending namespace/keys.
3) Most widely adopted namespace/keys (i.e. not necessarily the most
used but the ones used by the highest number of different client
applications)
On Fri, Apr 16, 2010 at 1:43 PM, Marcel Molina <[email protected]
<mailto:[email protected]>> wrote:
This is a great idea for how to bootstrap and fuel the adoption
and consensus on namespaces and key names. I'm going to talk to
our analytics team and see if we can surface analytics on the most
used namespaces and those namespace's most used keys.
On Fri, Apr 16, 2010 at 1:05 PM, Jaanus <[email protected]
<mailto:[email protected]>> wrote:
Another 2c: you should think about publishing numbers/stats for
annotations. Easiest to start on the level of namespaces. Publish
stats about popularity of namespaces: how many tweets and how many
users use which namespaces. And don't do "that's a good idea
and there
are still many moving parts and we are thinking of it for the
future,"
do "this is absolutely vital for the community from day 1" :) This
would be a good measure for community to inform what namespaces to
support, what works and what doesn't, etc.
J
--
Subscription settings:
http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
--
Marcel Molina
Twitter Platform Team
http://twitter.com/noradio
--
Marcel Molina
Twitter Platform Team
http://twitter.com/noradio
Marcel,
Please take a look at this blog post which covers the issue of
Structured Data [1].
At the end of the day, every Tweet is a uniquely identifiable data
object (entity). Annotations ultimately come down to making simple
statements about the attributes of a Tweet, thus the
Entity-Attribute-Value (EAV) works here as it does everywhere else re.
data representation flexibility (XML, JSON, and other data
representation formats).
Links:
1. http://bit.ly/cA0zxw -- Data 3.0 Manifesto (all about Structured Data
and the EAV Model)
2. http://semantictwitter.appspot.com/ -- an example of compact EAV
style 3-tuple approach to annotations
3. http://smob.me/ -- ditto .
--
Regards,
Kingsley Idehen
President & CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen
