Wow, another cool idea introduced at Chirp (was it?). Honestly, I'd
just love a free (beer) geocoding service that didn't force me to use
google maps.
Twitter has helped me make $10 so far (woohoo!); perhaps as I make more
with it I'll actually be able to afford going to Chirp! 8-)))
All,
Re. annotations has anyone seen this example re. compact 3-part
(tuple) statements:
http://semantictwitter.appspot.com/
Kingsley
On Apr 14, 5:05 pm, James Teters jtet...@gmail.com wrote:
Just curious if there is any documentation on how annotations will be
implemented?
Any ideas on
- Jud jvale...@gmail.com wrote:
On Apr 14, 5:05 pm, James Teters jtet...@gmail.com wrote:
Any ideas on size limitations or restrictions for this meta data?
good question; I have the same one.
simple math based on average tweet status byte size (of status
structure coming through the
please feel free to point us to standards that you would like us to
consider. we are really attempting to make this insanely simple by
literally just having a triple of items to store (namespace, key, value) --
so, we are just really talking about representation, i assume.
On Thu, Apr 15, 2010
Will annotations be indexed and searchable? Will I be able to search
for all tweets with a certain annotation namespace, or namespace:key?
I think this would be key to truly creating agreeable standards for
metadata that can be utilized by many clients.
On Apr 15, 9:05 am, Raffi Krikorian
I'm thinking of something like the RFC process for Internet protocols.
By the way, on a related note, once the Twitter link shortener I've
been hearing rumors about is in place, can we have all the links in
tweets sent from the API shortened with it? Profile images, user
object URLs, etc. ;-)
Will annotations be indexed and searchable? Will I be able to search
for all tweets with a certain annotation namespace, or namespace:key?
I think this would be key to truly creating agreeable standards for
metadata that can be utilized by many clients.
the plan is yes - we will be working
I'm thinking of something like the RFC process for Internet protocols.
really - i think that's just too formal. just mail the list, or hit
me/marcel up over email.
Part of this stems from my concern over something I thought I heard
yesterday about Twitter building its own place database.
+1!! ;)
On Apr 15, 2010 7:09 a.m., zn...@comcast.net wrote:
- Jud jvale...@gmail.com wrote: On Apr 14, 5:05 pm, James Teters
jtet...@gmail.com wro...
In addition to size constraints, I'd like to *strongly* suggest that
wherever possible, annotations use *existing* open standards! Please,
honestly, of all the place databases out there, none of them fit our needs.
none of them have the combination of unrestrictive licensing + data and IDs
for countries going down to neighborhoods (arbitrarily sized things) + have
the ability for creation, updating, etc. we are building
Thanks for that info. Will try to gather a few and send them later.
So you're ruling out concepts w/ multiple properties? Like a vcard?
This seems similar to what axschema.org have for openid. Namespaces have to
be uris, obviously.
Cheers,
André Luís
On Apr 15, 2010 1:09 p.m., Raffi Krikorian
a way to think about this is analogous to geo. people used to put geo
information in the 140 characters -- but now, we allow you to put it out of
band in a machine-readable way. we want to extend that functionality to all
types of meta data (links to URLs, etc.).
2010/4/15 André Luís
Why shorten links that won't count for 140 limit and are not viewed by user?
It will only add un-needed requests and waste values on the twiter
shortener.
André Luís
On Apr 15, 2010 2:18 p.m., M. Edward (Ed) Borasky zzn...@gmail.com
wrote:
I'm thinking of something like the RFC process for
I guess I need to look at the protocol buffers spec again. And some
of the binary JSON formats. While we're dreaming, how about sending
Streaming data *compressed*? ;-)
On Apr 15, 7:49 am, Raffi Krikorian ra...@twitter.com wrote:
a way to think about this is analogous to geo. people used to put
My impression was that the Open Street Map project was attempting to
solve this. At least that's what I picked up in the aftermath of the
Haiti earthquake. If you haven't already, check out http://maps2.humaninet.org/
and http://www.humaninet.org/maps2/maps2-geo-usability-2010-1-12.pdf
We've got
I guess I need to look at the protocol buffers spec again. And some
of the binary JSON formats. While we're dreaming, how about sending
Streaming data *compressed*? ;-)
How about keeping a new way of talking to Twitter human readable during its
initial implementation? Premature optimization.
probably not - we're just going to stick with JSON and XML for a bit now.
On Thu, Apr 15, 2010 at 8:52 AM, M. Edward (Ed) Borasky zzn...@gmail.comwrote:
I guess I need to look at the protocol buffers spec again. And some
of the binary JSON formats. While we're dreaming, how about sending
tell them to hit me up.
On Thu, Apr 15, 2010 at 8:49 AM, M. Edward (Ed) Borasky zzn...@gmail.comwrote:
My impression was that the Open Street Map project was attempting to
solve this. At least that's what I picked up in the aftermath of the
Haiti earthquake. If you haven't already, check out
On Apr 14, 5:05 pm, James Teters jtet...@gmail.com wrote:
Any ideas on size limitations or restrictions for this meta data?
good question; I have the same one.
simple math based on average tweet status byte size (of status
structure coming through the streaming or REST interface) tells us
that
we're not sure on the sizes we are going to initially launch with, but i
suspect we will launch with something small and ramp it up. i think the
limit will also be the total sum of stuff, as opposed to number of keys,
length of keys, etc.
On Wed, Apr 14, 2010 at 5:43 PM, Jud jvale...@gmail.com
Raffi,
Is the planning for everyone's annotations to be available to everyone
else, or will there be private namespaces accessible only to the
source application?
--
To unsubscribe, reply using remove me as the subject.
completely public, except for protected tweets in which case they would be
private.
On Wed, Apr 14, 2010 at 7:54 PM, Dewald Pretorius dpr...@gmail.com wrote:
Raffi,
Is the planning for everyone's annotations to be available to everyone
else, or will there be private namespaces accessible
22 matches
Mail list logo
