4 added 1 characters in body
source | link

I'm all for opening up oneboxing, but not for creating yet another standard.

There are already several competing standards for onebox-like functionality and semantic representation of web page data:

If Stack Exchange is going to do this, they should adopt one of those instead of re-inventing the wheel. My preference is for oEmbed, with a secondary preference of Open Graph.

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shoot.

Note 1: what you're proposing is pretty close to Open Graph anyway.

I'm all for opening up oneboxing, but not for creating yet another standard.

There are already several competing standards for onebox-like functionality and semantic representation of web page data:

If Stack Exchange is going to do this, they should adopt one of those instead of re-inventing the wheel. My preference is for oEmbed, with a secondary preference of Open Graph.

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shoot.

Note 1: what you're proposing is pretty close to Open Graph anyway.

I'm all for opening up oneboxing, but not for creating yet another standard.

There are already several competing standards for onebox-like functionality and semantic representation of web page data:

If Stack Exchange is going to do this, they should adopt one of those instead of re-inventing the wheel. My preference is for oEmbed, with a secondary preference of Open Graph.

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shoot.

Note 1: what you're proposing is pretty close to Open Graph anyway.

3 The rabbit hole goes deeper; added 45 characters in body
source | link

I'm all for opening up oneboxing, but not for creating yet another standard.

There are already twoseveral competing, widespread standards for onebox-like functionality: oEmbed and Facebook's Open Graph1.semantic representation of web page data:

If Stack Exchange is going to do this, they should adopt one of those instead of re-inventing the wheel. My preference is for oEmbed, with a secondary preference of Open Graph.

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shoot.

Note 1: what you're proposing is pretty close to Open Graph anyway.

I'm all for opening up oneboxing, but not for creating yet another standard.

There are already two competing, widespread standards for onebox-like functionality: oEmbed and Facebook's Open Graph1. If Stack Exchange is going to do this, they should adopt one of those instead of re-inventing the wheel.

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shoot.

Note 1: what you're proposing is pretty close to Open Graph anyway.

I'm all for opening up oneboxing, but not for creating yet another standard.

There are already several competing standards for onebox-like functionality and semantic representation of web page data:

If Stack Exchange is going to do this, they should adopt one of those instead of re-inventing the wheel. My preference is for oEmbed, with a secondary preference of Open Graph.

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shoot.

Note 1: what you're proposing is pretty close to Open Graph anyway.

2 Link to Open Graph standard proposal page instead of Facebook's implementation; added 56 characters in body; added 40 characters in body; added 9 characters in body
source | link

I'm all for opening up oneboxing, but not for creating yet another standard:

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shoot..

There are already two competing, widespread standards for onebox-like functionality: oEmbed and Facebook's Open GraphOpen Graph1. If Stack Exchange is going to do this, they should adopt one of those, not instead of re-inventinventing the wheel.

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shoot.

Note 1: what you're proposing is pretty close to Open Graph anyway.

I'm all for opening up oneboxing, but not for creating yet another standard:

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shoot.

There are already two competing, widespread standards for onebox-like functionality: oEmbed and Facebook's Open Graph. If Stack Exchange is going to do this, they should adopt one of those, not re-invent the wheel.

I'm all for opening up oneboxing, but not for creating yet another standard.

There are already two competing, widespread standards for onebox-like functionality: oEmbed and Facebook's Open Graph1. If Stack Exchange is going to do this, they should adopt one of those instead of re-inventing the wheel.

Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB? Shoot.

Note 1: what you're proposing is pretty close to Open Graph anyway.

1
source | link