📜 ⬆️ ⬇️

OExchange got support

The new protocol, designed to “fumble” content, received support from large companies such as Microsoft, Google, LinkedIn.
On the one hand, content sites need the ability to allow visitors to exchange links to this content in different systems. On the other hand, every google buzz wants to be integrated into the list of systems for sharing with its users. Between them there are still exchange tools, which in the simplest case are different web widgets that work on the page in the browser. The OExchange protocol unifies the solution of these problems.

How it works

Everything is very similar to OpenID.

The service provider (Service Provider, a service where links can be published) on the user page displays
<link rel="http://oexchange.org/spec/0.8/rel/related-target" type="application/xrd+xml" href="http://www.example.com/linkeater/oexchange.xrd"/>
It also defines a list of points for posting in a special root document. hostname/.well-known/host-met
The XRD meta-data document (host-meta) indicates the point of publication (offer endpoint) and optionally a number of other properties.
The publish point is the HTTP address where the resource is located, capable of simply accepting the url parameter and a number of other optional parameters (such as content type).
Personal user XRD can also be in any other ways available to the link exchange tool.

Now, to any content (text, pictures, video) on different pages, buttons for telling about it to all-all-all on ten different sites will begin to be massively stuck. And under this one modest protocol will work.
')
UPD: Clearspring Technologies Press Release .

Source: https://habr.com/ru/post/95383/


All Articles