Re: [twitter-dev] Re: Early look at Annotations
Raffi Krikorian wrote: Not to be glib, but they are more than welcome to join in on the conversation in the community. We plan to let the community really drive this one. ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that Twitter intends to leave the annotation classification system to be determined by the market. http://bit.ly/csK8Od Although I appreciate that Twitter values keeping the annotation ecosystem open for innovation and adaptation, I hope the conversation on Linked Data metadata standards within Twitter annotations is just beginning. It could be an historic lost opportunity if the hard driving Twitter team doesn�ft step back and consider soliciting the counsel of the W3C, Sir TB-L, Nigel Shadbolt and others in the Linked Data community. After all, Metaweb's Freebase team is just 3 blocks away. Raffi, Is is a Wiki or some other publicly accessible shared document space where the What, Why, and How of Twitter's Structured Annotations is being developed? there will be soon! taylor and i will work on getting a page up. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi Raffi, Great! I think once that's in place, the community process will accelerate. -- Regards, Kingsley Idehen President CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Early look at Annotations
Not to be glib, but they are more than welcome to join in on the conversation in the community. We plan to let the community really drive this one. On Apr 19, 2010, at 8:06 PM, R_Macdonald roger.g.macdon...@gmail.com wrote: ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that Twitter intends to leave the annotation classification system to be determined by the market. http://bit.ly/csK8Od Although I appreciate that Twitter values keeping the annotation ecosystem open for innovation and adaptation, I hope the conversation on Linked Data metadata standards within Twitter annotations is just beginning. It could be an historic lost opportunity if the hard driving Twitter team doesn’t step back and consider soliciting the counsel of the W3 C, Sir TB-L, Nigel Shadbolt and others in the Linked Data community. After all, Metaweb's Freebase team is just 3 blocks away. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Early look at Annotations
Raffi Krikorian wrote: Not to be glib, but they are more than welcome to join in on the conversation in the community. We plan to let the community really drive this one. On Apr 19, 2010, at 8:06 PM, R_Macdonald roger.g.macdon...@gmail.com wrote: ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that Twitter intends to leave the annotation classification system to be determined by the market. http://bit.ly/csK8Od Although I appreciate that Twitter values keeping the annotation ecosystem open for innovation and adaptation, I hope the conversation on Linked Data metadata standards within Twitter annotations is just beginning. It could be an historic lost opportunity if the hard driving Twitter team doesn�ft step back and consider soliciting the counsel of the W3C, Sir TB-L, Nigel Shadbolt and others in the Linked Data community. After all, Metaweb's Freebase team is just 3 blocks away. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en Raffi, Is is a Wiki or some other publicly accessible shared document space where the What, Why, and How of Twitter's Structured Annotations is being developed? -- Regards, Kingsley Idehen President CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter/Identi.ca: kidehen
Re: [twitter-dev] Re: Early look at Annotations
On 04/19/2010 11:21 PM, Raffi Krikorian wrote: Not to be glib, but they are more than welcome to join in on the conversation in the community. We plan to let the community really drive this one. Yes, but, for example, is Sir Tim Berners-Lee even *on* Twitter? I know Marshall Kirkpatrick is, but he's a journalist, not a standards-maker. Of course, there are *lots* of people I'd like to see on Twitter. http://borasky-research.net/2010/04/18/the-top-ten-people-who-should-be-on-twitter-but-arent/ On Apr 19, 2010, at 8:06 PM, R_Macdonald roger.g.macdon...@gmail.com wrote: ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that Twitter intends to leave the annotation classification system to be determined by the market. http://bit.ly/csK8Od Although I appreciate that Twitter values keeping the annotation ecosystem open for innovation and adaptation, I hope the conversation on Linked Data metadata standards within Twitter annotations is just beginning. It could be an historic lost opportunity if the hard driving Twitter team doesn’t step back and consider soliciting the counsel of the W3C, Sir TB-L, Nigel Shadbolt and others in the Linked Data community. After all, Metaweb's Freebase team is just 3 blocks away. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős
Re: [twitter-dev] Re: Early look at Annotations
Not to be glib, but they are more than welcome to join in on the conversation in the community. We plan to let the community really drive this one. ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that Twitter intends to leave the annotation classification system to be determined by the market. http://bit.ly/csK8Od Although I appreciate that Twitter values keeping the annotation ecosystem open for innovation and adaptation, I hope the conversation on Linked Data metadata standards within Twitter annotations is just beginning. It could be an historic lost opportunity if the hard driving Twitter team doesn�ft step back and consider soliciting the counsel of the W3C, Sir TB-L, Nigel Shadbolt and others in the Linked Data community. After all, Metaweb's Freebase team is just 3 blocks away. Raffi, Is is a Wiki or some other publicly accessible shared document space where the What, Why, and How of Twitter's Structured Annotations is being developed? there will be soon! taylor and i will work on getting a page up. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Early look at Annotations
On 04/19/2010 08:06 PM, R_Macdonald wrote: ReadWriteWebs's Co-Editor, Marshall Kirkpatrick, suggests today that Twitter intends to leave the annotation classification system to be determined by the market. http://bit.ly/csK8Od Although I appreciate that Twitter values keeping the annotation ecosystem open for innovation and adaptation, I hope the conversation on Linked Data metadata standards within Twitter annotations is just beginning. It could be an historic lost opportunity if the hard driving Twitter team doesn’t step back and consider soliciting the counsel of the W3C, Sir TB-L, Nigel Shadbolt and others in the Linked Data community. After all, Metaweb's Freebase team is just 3 blocks away. That's *exactly* what I told Marshall! I know him - he lives here in PDX. Sir Tim Berners-Lee got a significant chunk of funding to develop the Semantic Web, and I'd think he'd have a lot to say about Twitter Annotations if we'd only ask him! -- M. Edward (Ed) Borasky borasky-research.net/m-edward-ed-borasky A mathematician is a device for turning coffee into theorems. ~ Paul Erdős -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Early look at Annotations
XML option #2 feels like the best option to me, because it seems the most flexible, most forward compatible, and plays well with AWS: http://docs.amazonwebservices.com/AmazonSimpleDB/latest/DeveloperGuide/SDB_API_GetAttributes.html (that's my $0.02) _s. XML option #2 which is more verbose but allows for namespaces and keys to contain arbitrary data annotations annotation namespaceiso/namespace keyisbn/key value030759243X/value /annotation annotation namespaceamazon/namespace keyurl/key valuehttp://www.amazon.com/Although-Course-You-Becoming-Yourself/dp/030759... /value /annotation /annotations If we went with XML option #2 it may or may not be a problem that it isn't symmetrical with the JSON representation. On the other hand, JSON and XML tend to be culturally at opposite sides of the Pithiness Spectrum. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Early look at Annotations
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 mar...@twitter.com mailto:mar...@twitter.com 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 jaa...@gmail.com mailto:jaa...@gmail.com 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
[twitter-dev] Re: Early look at Annotations
On Apr 16, 10:54 am, Marcel Molina mar...@twitter.com wrote: This isn't final. The payloads could end up wildly different after we noodle around in things like RDF and the semantic web's literature and all that kind of stuff. You can't see me but my hands are waving vigorously. I think there are amazing opportunities in Twitter's new annotation feature. I am awestruck by the potential of developers applying Linked Data / Semantic Web schema and using RDF in Twitter annotations. It would massively scale search effectiveness and distribution opportunities while allowing sophisticated on-the-fly analysis of Twitter's firehose other feeds. The Twitter ecosystem is particularly suited to applying principles of the Semantic Web in that machine interpolated meaning could be continually refined the more humans tweet retweet about the same and related topics (resolved by semantic entity detection; coupled with author, location, hashes, platform, temporal and other information. The vision of Semantic Web is occasionally dismissed as long on dream and short on practice. However, early implementations are gaining significant traction and offering substantive value to early adopters. Thompson Reuters, no slouch in the business of information, was quite visionary in acquiring the now @OpenCalais service. The mostly free service is currently identifying semantic entities in over 5 million documents submitted to it per day. @zemanta is also finding a significant user base among bloggers for its related services. Twitter annotations may well be a turning point in the early practical application of Tim Berners-Lee’s 1999 “dream for the Web [in which computers] become capable of analyzing all the data on the Web – the content, links, and transactions between people and computers.” It is all about the metadata! -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Early look at Annotations
Marcel, I'd strongly urge you to consider a more structured and controlled environment for annotations. Ideally, I think an OAuth app must register a namespace, or subscribe to an existing namespace of another app, before it can create annotations in that namespace. And these registrations and subscriptions must be reviewed and approved before an app can actually contribute to a namespace. Being as open and free as you currently have it, it's fertile soil for the poisoning of any namespace by any rogue or not-so-nice app. It's better to plan and create the controls ahead of time. You're going to save everyone, including yourselves, a lot of effort and time. On Apr 16, 2:54 pm, Marcel Molina mar...@twitter.com wrote: Hey everyone. One of the things we talked about at Chirp is the new Annotations feature we're working on. In short, it allows you to annotate a tweet with structured metadata. We're still working on Annotations, but I wanted to share with a wider audience beyond those I was able to talk to in person at Chirp about how we're thinking of doing Annotations. * What is an annotation more exactly exactly? First off let's be clearer about what an annotation is. An annotation is a namespace, key, value triple. A tweet can have one or more annotations. Namespaces can have one or more key/value pairs. * How do I specify what annotations a tweet should have? Annotations are specified for a tweet when the tweet is created. When submitting a POST to /statuses/update, you'll include an annotations parameter with your annotations. We're thinking we'll provide two mechanisms for specifying what a tweet's annotations are: 1. JSON 2. form encoded parameters * How big can an annotation be and how many annotations can I attach to a tweet? There is no limit on the size of any given namespace, key or value but the entire set of all annotations for a given tweet can not exceed some fixed byte size. That size isn't set in stone yet. We will be starting small (probably 512 bytes) and growing it gradually as we incrementally roll out the feature so we can gauge its scalability at various sizes. We'd like to (no promises) have it end up around 2K. How you use that 2K is up to you. You can attach one honking annotation, or a thousand+ tiny ones. You can attach one namespace with hundreds of key/value pairs, or hundreds of namespaces with just one key/value pair. We want to keep things as flexible and open ended as possible. * What kind of data can go into an annotation? We'd like to allow for any arbitrary data to be stored in an annotation. Arbitrary Unicode? Sure. MIDI? Go for it. Emoji? Yes please! There might be some tricky edge cases though. Skip the rest of this paragraph if you don't care about the details of edge cases... For one, since these annotations will be serialized to, among other formats, XML, and we'd like to keep the XML succinct, the namespace and key components of an annotation triple would likely be an XML tag with its value as, well, its value. If that's the case then the data of the key must be a valid XML tag. This greatly limits what it can contain (not even spaces for example). If allowing all three elements of the triple to contain any arbitrary data is more important than a succinct XML payload then we'll design a more verbose XML payload. Up to you all really. I've included examples of both options below. Make a case for another proposal if you have strong opinions. * What constitutes a valid annotation? Aside from the size and data type restrictions listed above, another requirement is that namespaces and keys be non-empty values. Values, on the other hand, may be empty. In this way the namespace/key pair can be treated like a flag of sorts. It should be noted: I'd encourage everyone to always think of a namespace as a namespace, to think of a key as a key and to think of a value as a value. Don't take the fact that a value can be empty to mean that you can skip out on the whole namespace think and morph the namespace into a key and the key into a value. While open endedness and flexibility is a quality of the Annotations feature that I'm most excited about for the developer community, this kind of approach seems prone to causing confusion by undermining namespaces. * What namespaces can I write to? What namespaces can I read from? Anyone can write to or read from any namespace. We aren't planning on enforcing any policy that restricts someone else from adding an annotation with your namespace or seeing annotations only if they are logged in with a certain account. In the absence of some really compelling reason to do that, we want to err on the side of making this feature as flexible and open ended as possible. Namespaces aren't intended as a way for people to claim their little slice of the tweet space. Rather they are intended to dramatically increase the possible significance of a given key/value pair.
Re: [twitter-dev] Re: Early look at Annotations
I'd strongly urge you to consider a more structured and controlled environment for annotations. Ideally, I think an OAuth app must register a namespace, or subscribe to an existing namespace of another app, before it can create annotations in that namespace. And these registrations and subscriptions must be reviewed and approved before an app can actually contribute to a namespace. Being as open and free as you currently have it, it's fertile soil for the poisoning of any namespace by any rogue or not-so-nice app. It's better to plan and create the controls ahead of time. You're going to save everyone, including yourselves, a lot of effort and time. the same could happen right now - if somebody puts a $ before something, stock twits may try to parse that as a stock market commodity. i don't see us (for some) enforcing anything on the namespaces, and will let the community try to work it out. if there happens to be a rogue app, then users will stop using it. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Early look at Annotations
comments inline... Dewald Pretorius wrote: Marcel, I'd strongly urge you to consider a more structured and controlled environment for annotations. agreed, but... Ideally, I think an OAuth app must register a namespace, or subscribe to an existing namespace of another app, before it can create annotations in that namespace. And these registrations and subscriptions must be reviewed and approved before an app can actually contribute to a namespace. ... not to this extent. twitter becomes app and content police? I vote no. I don't even think they have the manpower to review and approve each app. And I sure don't want that job. -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
Re: [twitter-dev] Re: Early look at Annotations
not necessarily - twitterbots are easy to build. you can't rely on lack of usage by humans to kill a twitter app. Raffi Krikorian wrote: if there happens to be a rogue app, then users will stop using it. -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en
[twitter-dev] Re: Early look at Annotations
Raffi, It's not about people using or not using rogue apps. It's about rogue apps poisoning the annotation data and ruining it for everybody. Rogue apps can continue to refresh their consumer keys with new accounts and OAuth app registrations, as soon as the one currently in use is suspended. Meaning, a new class of rogue app will emerge. Ones with the express purpose of getting their data into the namespaces. To name one example (with reference to Marcel's examples): - A rogue app that creates tweets with an affiliate link in the amazon namespace. On Apr 16, 3:31 pm, Raffi Krikorian ra...@twitter.com wrote: I'd strongly urge you to consider a more structured and controlled environment for annotations. Ideally, I think an OAuth app must register a namespace, or subscribe to an existing namespace of another app, before it can create annotations in that namespace. And these registrations and subscriptions must be reviewed and approved before an app can actually contribute to a namespace. Being as open and free as you currently have it, it's fertile soil for the poisoning of any namespace by any rogue or not-so-nice app. It's better to plan and create the controls ahead of time. You're going to save everyone, including yourselves, a lot of effort and time. the same could happen right now - if somebody puts a $ before something, stock twits may try to parse that as a stock market commodity. i don't see us (for some) enforcing anything on the namespaces, and will let the community try to work it out. if there happens to be a rogue app, then users will stop using it. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Subscription settings:http://groups.google.com/group/twitter-development-talk/subscribe?hl=en- Hide quoted text - - Show quoted text -
Re: [twitter-dev] Re: Early look at Annotations
right now, i could send out a whole bunch of tweets with crappy yfrog URLs (that all return 404s). to end users, again, it seems like yfrog is a bad service. i mean, you have good points - and i hear all of them - its not something we are going to with for now, but i totally understand everything you're saying. On Fri, Apr 16, 2010 at 11:49 AM, Dewald Pretorius dpr...@gmail.com wrote: Raffi, It's not about people using or not using rogue apps. It's about rogue apps poisoning the annotation data and ruining it for everybody. Rogue apps can continue to refresh their consumer keys with new accounts and OAuth app registrations, as soon as the one currently in use is suspended. Meaning, a new class of rogue app will emerge. Ones with the express purpose of getting their data into the namespaces. To name one example (with reference to Marcel's examples): - A rogue app that creates tweets with an affiliate link in the amazon namespace. On Apr 16, 3:31 pm, Raffi Krikorian ra...@twitter.com wrote: I'd strongly urge you to consider a more structured and controlled environment for annotations. Ideally, I think an OAuth app must register a namespace, or subscribe to an existing namespace of another app, before it can create annotations in that namespace. And these registrations and subscriptions must be reviewed and approved before an app can actually contribute to a namespace. Being as open and free as you currently have it, it's fertile soil for the poisoning of any namespace by any rogue or not-so-nice app. It's better to plan and create the controls ahead of time. You're going to save everyone, including yourselves, a lot of effort and time. the same could happen right now - if somebody puts a $ before something, stock twits may try to parse that as a stock market commodity. i don't see us (for some) enforcing anything on the namespaces, and will let the community try to work it out. if there happens to be a rogue app, then users will stop using it. -- Raffi Krikorian Twitter Platform Teamhttp://twitter.com/raffi -- Subscription settings: http://groups.google.com/group/twitter-development-talk/subscribe?hl=en-Hide quoted text - - Show quoted text - -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
[twitter-dev] Re: Early look at Annotations
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
Re: [twitter-dev] Re: Early look at Annotations
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 jaa...@gmail.com 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
Re: [twitter-dev] Re: Early look at Annotations
Thanks for the insight this early into everything. This helps from the communication standpoint. I hope this devolve thought into design by commit on this thread though for the name-spacing. I have a few ideas but I'm reserving them because they may be obvious and not going to hurt me because I can work around anything you make. Now make some annotations. :-) Zac Bowling On Fri, Apr 16, 2010 at 1:43 PM, Marcel Molina mar...@twitter.com 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 jaa...@gmail.com 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
Re: [twitter-dev] Re: Early look at Annotations
I've talked to the analytics team. Three main metrics we're going to work to surface on something like 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 mar...@twitter.com 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 jaa...@gmail.com 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
Re: [twitter-dev] Re: Early look at Annotations
Been following the conversation; very interesting to see, even today, the devlopment of ideas around potential standards from the community of developers. To see the trends, most used, etc will definitely help us work towards the namespaces and keys with the most utility for ourselves and our users. On 16 April 2010 22:17, Marcel Molina mar...@twitter.com wrote: I've talked to the analytics team. Three main metrics we're going to work to surface on something like 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 mar...@twitter.com 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 jaa...@gmail.com 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
[twitter-dev] Re: Early look at Annotations
Thanks for all of the info, Marcel. Cool stuff! How would people feel about a wiki for developers to share thoughts on how to use/standardize on annotations? That would give us a chance to flesh out some of the namespacing issues that have been raised so that we can hit the ground running when Annotations are launched. I'd be happy to set up a PBWorks page or maybe a Google Doc that can be shared with this list. --Robby On Apr 16, 5:17 pm, Marcel Molina mar...@twitter.com wrote: I've talked to the analytics team. Three main metrics we're going to work to surface on something like 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 mar...@twitter.com 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 jaa...@gmail.com 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 Teamhttp://twitter.com/noradio
Re: [twitter-dev] Re: Early look at Annotations
i expect we'll put a page up on dev.twitter.com that will allow people to list out namespaces, keys, etc. all for the community. On Fri, Apr 16, 2010 at 2:41 PM, Robby Grossman ro...@freerobby.com wrote: Thanks for all of the info, Marcel. Cool stuff! How would people feel about a wiki for developers to share thoughts on how to use/standardize on annotations? That would give us a chance to flesh out some of the namespacing issues that have been raised so that we can hit the ground running when Annotations are launched. I'd be happy to set up a PBWorks page or maybe a Google Doc that can be shared with this list. --Robby On Apr 16, 5:17 pm, Marcel Molina mar...@twitter.com wrote: I've talked to the analytics team. Three main metrics we're going to work to surface on something like 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 mar...@twitter.com 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 jaa...@gmail.com 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 Teamhttp://twitter.com/noradio -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Early look at Annotations
I'd say keep it all on dev.twitter.com - minimise sites to visit. On 16 April 2010 22:44, Raffi Krikorian ra...@twitter.com wrote: i expect we'll put a page up on dev.twitter.com that will allow people to list out namespaces, keys, etc. all for the community. On Fri, Apr 16, 2010 at 2:41 PM, Robby Grossman ro...@freerobby.comwrote: Thanks for all of the info, Marcel. Cool stuff! How would people feel about a wiki for developers to share thoughts on how to use/standardize on annotations? That would give us a chance to flesh out some of the namespacing issues that have been raised so that we can hit the ground running when Annotations are launched. I'd be happy to set up a PBWorks page or maybe a Google Doc that can be shared with this list. --Robby On Apr 16, 5:17 pm, Marcel Molina mar...@twitter.com wrote: I've talked to the analytics team. Three main metrics we're going to work to surface on something like 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 mar...@twitter.com 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 jaa...@gmail.com 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 Teamhttp://twitter.com/noradio -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
Re: [twitter-dev] Re: Early look at Annotations
I think this will be a great addition to the platform. I suppose it will be up to each software client to determine how (classic) retweets are handled. The annotations could be copied and edited. I assume new retweets will simply reference the original tweet and its annotations. On Fri, Apr 16, 2010 at 3:12 PM, Nigel Legg nigel.l...@gmail.com wrote: I'd say keep it all on dev.twitter.com - minimise sites to visit. On 16 April 2010 22:44, Raffi Krikorian ra...@twitter.com wrote: i expect we'll put a page up on dev.twitter.com that will allow people to list out namespaces, keys, etc. all for the community. On Fri, Apr 16, 2010 at 2:41 PM, Robby Grossman ro...@freerobby.comwrote: Thanks for all of the info, Marcel. Cool stuff! How would people feel about a wiki for developers to share thoughts on how to use/standardize on annotations? That would give us a chance to flesh out some of the namespacing issues that have been raised so that we can hit the ground running when Annotations are launched. I'd be happy to set up a PBWorks page or maybe a Google Doc that can be shared with this list. --Robby On Apr 16, 5:17 pm, Marcel Molina mar...@twitter.com wrote: I've talked to the analytics team. Three main metrics we're going to work to surface on something like 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 mar...@twitter.com 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 jaa...@gmail.com 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 Teamhttp://twitter.com/noradio -- Raffi Krikorian Twitter Platform Team http://twitter.com/raffi
