[twitter-dev] Twitter Annotation Potential Article
All, Should be interesting to this mailing list: http://www.semanticweb.com/on/semantic_wave_hits_ecommerce_part_2_current_innovation_161798.asp Twitter Annotation implications are towards the end of the article, best you read the entire article for context. -- 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
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
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: Introduce yourself!
Hi All, I am Kingsley Idehen, Founder CEO, OpenLink Software. Somewhat unconventional re. conventional CEO's, I am still actively involved in the technical aspects of my company's products. Background: I've been involved with Data Access (ODBC, JDBC, OLEDB, ADO.NET, XMLA), Data Integration, and Data Management (Relational, Graph, Document) technology since the late '80's (I am only 44 btw!). More recently, I've been actively involved with the burgeoning Web of Structured Linked Data (using GData, OData, and RDF etc..). My main interest here is to contribute to the conversation that ultimately leads Twitter realizing its full potential via its evolution into a powerful Linked Data Space on the burgeoning Web of Linked Data. The opportunities are boundless and the sole requirement is structured data (which makes Linking much easier). Links: 1. http://www.openlinksw.com/blog/~kidehen -- Blog 2. http://bit.ly/cA0zxw -- Recent Data 3.0 Manifesto Post re. Structured Data Construction and Dissemination via HTTP using EAV Data Model. -- Regards, Kingsley Idehen President CEO OpenLink Software Web: http://www.openlinksw.com Weblog: http://www.openlinksw.com/blog/~kidehen Twitter: @kidehen -- 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
