A Start: "Schema Ideas"

[Michael Bleigh]

To get things started, I have created a list of a few schema ideas for
discussion. What are your ideas? Feel free to contribute and I'll do
my best to keep the list current with the latest ideas.

Click on http://groups.google.com/group/twitter-meta/web/schema-ideas
- or copy & paste it into your browser's address bar if that doesn't
work.

[dhavaln]

I would suggest to have a priority\critical\importance tag like a
panic button.
a tag whose value describes the criticality of the tweet.
the reason for this is that twitter is a global communication medium
different agencies can use this tag to circulate important news and on
the otherside its really easy to find out these tweets depending on
their level.

On Apr 18, 7:52 am, Michael Bleigh <mble...@gmail.com> wrote:
> To get things started, I have created a list of a few schema ideas for
> discussion. What are your ideas? Feel free to contribute and I'll do
> my best to keep the list current with the latest ideas.
>

> Click onhttp://groups.google.com/group/twitter-meta/web/schema-ideas

[Justyn]

Didn't see a way to edit the Schema Ideas page, so I'll add a few
here;

- Check-In: A flag to indicate if the tweet is intended to mark
arrival at a location, or about a specific location.
- URL info in meta-data: URL's currently take way too much of the
allotted 140 characters - even after shortened. Would be great if we
could adopt a universal way to add links which showed a simple (link)
on the client side.

Not sure if anyone else would find these useful, but I imagine a lot
of innovation could stem from these two.

On Apr 17, 9:52 pm, Michael Bleigh <mble...@gmail.com> wrote:
> To get things started, I have created a list of a few schema ideas for
> discussion. What are your ideas? Feel free to contribute and I'll do
> my best to keep the list current with the latest ideas.
>

> Click onhttp://groups.google.com/group/twitter-meta/web/schema-ideas

[x5315]

Would another flag to have a link to an image also? Similar to the URL
info, but only used to images.


--
Subscription settings: http://groups.google.com/group/twitter-meta/subscribe?hl=en

[Justyn]

I've seen some examples floating around where they are handled as one
item. As in;

1 'annotations':
2 {
3 'links':
4 {
5 'web': 'http://www.xyz.com',
6 'image' : 'http://www.abc.com',
7 'video' : 'http://www.foo.com/'
8 }
9 }

[Raffi Krikorian]

how would you store more than one of each?

--
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi

[Justyn]

More than one of each? That's ambitious :)

It's going to be really exciting to see how the platform evolves with
Annotations! Which opportunities are you most excited about Raffi?

Justyn

[Jeremy McAnally]

Great idea about URL info.

I don't know why this hasn't been discussed much, too: simply adding a
"(more)" annotation (i.e., attach the extended text as a "more"
annotation or something).

--Jeremy

[harrisj]

I have a few ideas I'm kicking around and will probably also blog
about, but I figured I'd add them here:

- A 'meta' namespace for annotations about the annotations. It's
unlikely the annotation payload will be much, much larger than the
tweets, so a mechanism for linking to things like meta:complete => url
or meta:truncated => true.
- The mediaRSS standard (http://video.search.yahoo.com/mrss) seems
natural for any twitpic-like services. Provide the short URL in the
tweet, but the mediaRSS in the annotations.
- similarly, the Dublin Core might excite MLA nerds tweeting about
texts (oh, I kid)
- actually, just look over this site and some other ideas spring to
mind (http://rss-extensions.org/wiki/Main_Page). Bear in mind, most
annotations make sense in terms of describing the "target" of the
tweet link, rather than the actual tweet.
- linked data is very exciting to me, but I think there might be some
issues with how big those URLs can get.
- I like the idea of presenting the canonical URL in the annotations
(even if the shortened URL is used in the tweet). Makes for a good way
to present the destination in the client without expansion (although
it also creates a fun phishing opportunity).

Jacob

[harrisj]

Forgot one:

- CSS; finally, I will be able to tweet with "css:font-family: Comic
Sans". ;)

[Laurie Voss]

This is really interesting stuff.

One of the things we at awe.sm are particularly interested in is the
idea of providing canonical metadata about links. So for a tweet that
reads "Archer is awesome! http://awe.sm/54H8s" we could add the
canonical link (http://www.hulu.com/watch/136115/archer-dial-m-for-mother).
This allows the tweet to work in simple contexts, while providing
richer clients and third-party services valuable. I see two major
use-cases:

1. Visual cues: a link could be accompanied by a suggested preview
icon and a short description (like Facebook's stream.publish API
allows) to show some attractive pre-click information.

2. Aggregation help: services like Tweetmeme, Backtweets et al, which
currently have to follow redirects to discover their destination,
could save themselves millions of HTTP fetches (and redirection
services millions of hits) by using the canonical data direct from the
tweet.

We are in general all about the idea of attaching structured metadata
to social media content, so the idea of being able to do so directly
is very exciting.

L.

[Michael Bleigh]

JSON array would be my vote. It would be interesting (though difficult from a technical standpoint) for Twitter to support "native" JSON in annotations such that it would all be parsed naturally rather than having a dividing barrier at the annotation value level that required a second parse.