RSD

RFC: Really Simple Discoverability 1.0

movabletype을 보다가 index template에 RSD file이 들어있는걸 봤습니다. 도대체 RSD는 또 뭐야??

구글에서 찾아보다가 위의 사이트를 발견했는데 RSD에 대해 자세히 설명 되어있더군요.

대충읽어본걸 요약해보면...
RSD는 Really Simple Discoverability의 약자로 blog client가 blog system의 설정등을 쉽게 찾아낼 수 있도록 해주는 XML포맷의 파일입니다.

여러 블로깅 툴들이 XML-RPC를 이용하여 remote publishing, 관리 기능들을 제공하고 있는데 각 툴마다 RPC URL들이 제각기 다르고 설령 안다고 하더라도 사람이 입력하는한 잘못 입력할 수도 있습니다.
이러한 설정등에 대한 정보를 가지고 있는 파일이 RSD파일이고 블로그 클라이언트 툴에서는 이 RSD파일을 보고 이용할 블로그 시스템에 대한 정보를 얻어올 수 있습니다.

위치
RSD파일은 HTML파일내에 다음과 같은 형식으로 링크 되어있습니다.

<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://whereever the rsd.xml lives." />

RSD파일의 형식
is a container element. It's a hedge against the future.

Sub-elements of

* a string that is the name of the engine that is providing the services being described.
* is the URL to the home of the engine.
* is the URL of the users homepage.
* is a container element.

Sub-elements of

* has 4 required attributes. "name" is a string that is the name of the api. There is a list of "well-known" names below. A name does not need to be listed here or elsewhere to be valid. (see below). Multiple api elements are allowed.
o "preferred" is a boolean and takes either "true" or "false". The point is to allow weblog software to list all the APIs supported, but choose which one to "recommend" to the client software. Only one API should set as prefered.
o "apiLink" is the URL for this API. The location the client should speak to.
o "blogID" is a common bit of data that most APIs currently require. It can be specified here. If your system doesn't require it, include the attribute, but leave it blank like so blogID="" (this is demonstrated in the example.)

Optional sub-elements of

The api element doesn't require these elements. Information required by more flexible or capable systems can be expressed here.

is a container element and is required if you are going to include the following optional sub-elements.

* is a URL that points to the documentation for this API.
* is text that should be used to explain features and their settings. Intended to be human readable.
* requires a single attribute "name" a string which refers to the name of the "service-specific-setting". The value is the service setting. Multiple setting elements are allowed.