[from now] 2013/06/28 18:29:45

diff --git a/guide/webServices/REST/versioningResources.gdoc b/guide/webServices/REST/versioningResources.gdoc
index bf86914..e716926 100644
--- a/guide/webServices/REST/versioningResources.gdoc
+++ b/guide/webServices/REST/versioningResources.gdoc
@@ -1,15 +1,21 @@
-A common requirement with a REST API is to expose different versions of the REST API. There are a few ways this can be achieved in Grails.
+{hidden}A common requirement with a REST API is to expose different versions of the REST API. There are a few ways this can be achieved in Grails.{hidden}
+REST APIの一般的な要件として、REST APIの異なるバージョンの公開があります。
+Grailsでこれを実現するにはいくつかの方法があります。

-h4. Versioning using the URI
+{hidden}h4. Versioning using the URI{hidden}
+h4. URIを使ったバージョンニング

-A common approach is to use the URI to version APIs (although this approach is discouraged in favour of Hypermedia). For example, you can define the following URL mappings:
+{hidden}A common approach is to use the URI to version APIs (although this approach is discouraged in favour of Hypermedia). For example, you can define the following URL mappings:{hidden}
+一般的な方法は、各バージョンのAPIへのURIを使うことです（しかし、この方式よりはハイパーメディを使った方式をお勧めします）。
+例えば、以下のようにURLマッピングを定義できます:

 {code}
 "/books/v1"(resources:"book", namespace:'v1')
 "/books/v2"(resources:"book", namespace:'v2')
 {code}

-That will match the following controllers:
+{hidden}That will match the following controllers:{hidden}
+これは以下のコントローラに対応付きます:

 {code}
 package myapp.v1
@@ -25,27 +31,35 @@ class BookController {
 }
 {code}

-This approach has the disadvantage of requiring two different URI namespaces for your API.
+{hidden}This approach has the disadvantage of requiring two different URI namespaces for your API.{hidden}
+この方法は、APIに対して異なる2つのURIのネームスペースが必要となるという欠点があります。

-h4. Versioning with the Accept-Version header
+{hidden}h4. Versioning with the Accept-Version header{hidden}
+h4. Accept-Versionヘッダを使ったバージョンニング

-As an alternative Grails supports the passing of an @Accept-Version@ header from clients. For example you can define the following URL mappings:
+{hidden}As an alternative Grails supports the passing of an @Accept-Version@ header from clients. For example you can define the following URL mappings:{hidden}
+代わりに、Grailsはクライアントからの@Accept-Version@ヘッダによる制御をサポートしています。
+例えば以下のようにURLマッピングを定義できます:

 {code}
 "/books"(version:'1.0', resources:"book", namespace:'v1')
 "/books"(version:'2.0', resources:"book", namespace:'v2')
 {code}

-
-Then in the client simply pass which version you need using the @Accept-Version@ header:
+{hidden}Then in the client simply pass which version you need using the @Accept-Version@ header:{hidden}
+そして、クライアントからは@Accept-Version@ヘッダを使ってバージョンを渡すだけです:

 {code}
 $ curl -i -H "Accept-Version: 1.0" -X GET http://localhost:8080/myapp/books
 {code}

-h4. Versioning using Hypermedia / Mime Types
+{hidden}h4. Versioning using Hypermedia / Mime Types{hidden}
+h4. ハイパーメディア/Mimeタイプを使ったバージョニング

+{hidden}
 Another approach to versioning is to use Mime Type definitions to declare the version of your custom media types (see the section on "Hypermedia as the Engine of Application State" for more information about Hypermedia concepts). For example in @Config.groovy@ you can declare a custom Mime Type for your resource that includes a version parameter (the 'v' parameter):
+{hidden}
+他のバージョニング方法は、宣言したバージョン Mimeタイプの定義を使うことです。

 {code}
 grails.mime.types = [