Fixes #7

liqian19891011 · liqian19891011 · commit ef5f29f1154a · 2015-05-18T16:59:37.000+08:00
diff --git a/pages/abnf.html b/pages/abnf.html
@@ -4,6 +4,7 @@
 date: 2014-02-20 08:09:31.000000000 +08:00
 permalink: /documentation/odata-version-3-0/abnf/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h1 id="abnfforodata">ABNF for OData</h1>
 <p>Current Revision: 4/27/2012</p>
 <p>The following Augmented BackusNaur Form (ABNF) details the construction rules for OData Uris that target OData services that follow the Uri Conventions specified in this document.<br />
diff --git a/pages/atom-format-v2.html b/pages/atom-format-v2.html
@@ -4,6 +4,7 @@
 date: 2014-02-28 03:35:17.000000000 +08:00
 permalink: /documentation/odata-version-2-0/atom-format/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h2>Introduction</h2>
 <p>OData supports two formats for representing the resources (Collections, Entries, Links, etc) it exposes: the XML-based Atom format and the JSON format. This document describes how OData resources are represented in Atom (plus additional elements defined in AtomPub) and <a href="../json-format">[OData-JSON]</a> describes the JSON representation. The <a href="../operations#RepresentationFormatAndContentTypeNegotiation"> content type negotiation</a> section of the <a href="../operations">[OData-Operations]</a> document describes how clients can use standard HTTP content type negotiation to tell an OData service which format it wants to use.</p>
 <h2><a id="Background" name="Background"></a>1. Background</h2>
diff --git a/pages/atom-format-v3.html b/pages/atom-format-v3.html
@@ -4,6 +4,7 @@
 date: 2014-02-20 08:13:13.000000000 +08:00
 permalink: /documentation/odata-version-3-0/atom-format/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h1 id="overview">1. Overview</h1>
 <p>The OData protocol is comprised of a set of specifications for representing and interacting with structured content. This document describes the OData Atom Format returned from an OData Service when requesting the <code>application/atom+xml</code> mime type.</p>
 <p>An OData payload may represent:</p>
diff --git a/pages/batch-processing-v2.html b/pages/batch-processing-v2.html
@@ -4,6 +4,7 @@
 date: 2014-02-28 03:34:09.000000000 +08:00
 permalink: /documentation/odata-version-2-0/batch-processing/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h2>Introduction</h2>
 <p>The OData protocol exposes a uniform service interface to operate on collections of structured and unstructured data. <a href="../operations">[OData-Operations]</a> enumerates the set of operations supported by the uniform interface and describes a means to send one operation per HTTP request.</p>
 <p>This document builds on the <a href="../operations">[OData-Operations]</a> document and describes how an OData implementation can optionally support executing multiple operations sent in a single HTTP request through the use of Batching. This document covers both how Batch operations are represented and processed.</p>
diff --git a/pages/batch-processing-v3.html b/pages/batch-processing-v3.html
@@ -4,6 +4,7 @@
 date: 2014-02-20 08:11:24.000000000 +08:00
 permalink: /documentation/odata-version-3-0/batch-processing/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h1 id="opendataprotocolodatabatchprocessing"></h1>
 <h1 id="introduction">1. Introduction</h1>
 <p>The OData protocol defines a way to query and manipulate data (described using an EDM model) using a simple set of operations. This document builds on the ‘Interaction Semantics’ section of the core OData specification document and describes how an OData implementation MAY support executing multiple operations sent in a single HTTP request through the use of Batching. This document covers both how Batch operations are represented and processed.</p>
diff --git a/pages/common-schema-definition-language-csdl.html b/pages/common-schema-definition-language-csdl.html
@@ -4,6 +4,7 @@
 date: 2014-02-20 08:01:53.000000000 +08:00
 permalink: /documentation/odata-version-3-0/common-schema-definition-language-csdl/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h1 id="introduction">Introduction</h1>
 <p>OData services are described by an Entity Data Model (EDM). Common Schema Definition Language (CSDL) defines an XML-based representation of the entity model exposed by an OData service. CSDL is based on standards defined in [<code><a href="http://www.w3.org/TR/2006/REC-xml11–20060816/">XML 1.1</a></code>] and [<code><a href="http://www.w3.org/standards/techs/xmlschema#w3c_all">XML Schema</a></code>].</p>
 <p>An OData service SHOULD provide a CSDL description of its entity model when a client requests a description of the entity model by sending a <code>GET</code> request to <code>&lt;serviceRoot&gt;/$metadata</code>. <code>$metadata</code> MUST wrap the CSDL document in an EDMX wrapper.</p>
diff --git a/pages/json-format-v2.html b/pages/json-format-v2.html
@@ -4,6 +4,7 @@
 date: 2014-02-28 03:36:01.000000000 +08:00
 permalink: /documentation/odata-version-2-0/json-format/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h2>Introduction</h2>
 <p>OData supports two formats for representing the resources (Collections, Entries, Links, etc) it exposes: the XML-based AtomPub format and the JSON format. This document describes how OData resources are represented in JSON and <a href="../atom-format">[OData-Atom]</a> describes the AtomPub representation. The <a href="../operations#ContentTypeNegotation">content type negotiation</a> section of the <a href="../operations">[OData-Operations]</a> document describes how clients can use standard HTTP content type negotiation to tell an OData service which format it wants to use.</p>
 <h2><a id="Background" name="Background"></a>1. Background</h2>
diff --git a/pages/json-verbose-format-v3.html b/pages/json-verbose-format-v3.html
@@ -4,6 +4,7 @@
 date: 2014-02-20 08:15:04.000000000 +08:00
 permalink: /documentation/odata-version-3-0/json-verbose-format/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <p>OData is released under the <a href="http://www.microsoft.com/openspecifications/en/us/programs/osp/default.aspx">Open Specification Promise</a> to allow anyone to freely interoperate with OData implementations.<br />
 Current Revision: 4/27/2012</p>
 <h1 id="overview">Overview</h1>
diff --git a/pages/odata-version-3-0-core-protocol.html b/pages/odata-version-3-0-core-protocol.html
@@ -4,6 +4,7 @@
 date: 2014-02-20 07:50:09.000000000 +08:00
 permalink: /documentation/odata-version-3-0/odata-version-3-0-core-protocol/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h1 id="overview">1. Overview</h1>
 <p>The OData Protocol is an application-level protocol for interacting with data via RESTful web services. The protocol supports the description of data models and the editing and querying of data according to those models. It provides facilities for:</p>
 <ul>
diff --git a/pages/operations.html b/pages/operations.html
@@ -4,6 +4,7 @@
 date: 2014-02-28 03:32:08.000000000 +08:00
 permalink: /documentation/odata-version-2-0/operations/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h2>Introduction</h2>
 <p>The OData protocol exposes a uniform service interface to operate on collections of structured and unstructured data. Most of the semantics of operations in OData come from the AtomPub protocol [RFC5023], which in turn builds on top of HTTP <a href="http://www.ietf.org/rfc/rfc2616.txt">[RFC2616]</a>.</p>
 <p>This document describes the operation model for the protocol, specifying the interactions between clients and servers for retrieving and manipulating data in an OData service. It builds on the <a href="../overview">[OData-Core]</a> document for core concepts, <a href="../uri-conventions">[OData-URI]</a> for URI conventions and on the formats specifications for Atom <a href="http://www.odata.org/developers/protocols/atom-format"> [OData-Atom]</a> and JSON <a href="../json-format">[OData-JSON]</a> for the description of data representations.</p>
diff --git a/pages/overview.html b/pages/overview.html
@@ -4,6 +4,7 @@
 date: 2014-02-28 03:27:38.000000000 +08:00
 permalink: /documentation/odata-version-2-0/overview/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <p>The Open Data Protocol (OData) enables the creation of HTTP-based data services, which allow resources identified using Uniform Resource Identifiers (URIs) and defined in an abstract data model, to be published and edited by Web clients using simple HTTP messages. OData is intended to be used to expose and access information from a variety of sources including, but not limited to, relational databases, file systems, content management systems, and traditional Web sites.</p>
 <p>OData is made up of a group of specifications. This specification describes OData's core concepts and the following specifications define optional extensions to the foundations defined in this document:</p>
 <div>
diff --git a/pages/terminology.html b/pages/terminology.html
@@ -4,6 +4,7 @@
 date: 2014-02-28 03:28:21.000000000 +08:00
 permalink: /documentation/odata-version-2-0/terminology/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h2>Summary of References:</h2>
 <div>
 <table border="1" cellspacing="0" cellpadding="0">
diff --git a/pages/uri-conventions.html b/pages/uri-conventions.html
@@ -4,6 +4,7 @@
 date: 2014-02-28 03:30:31.000000000 +08:00
 permalink: /documentation/odata-version-2-0/uri-conventions/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h2>Introduction</h2>
 <p>The Open Data Protocol (OData) enables the creation of REST-based data services, which allow resources, identified using Uniform Resource Identifiers (URIs) and defined in a <a href="../overview#ODataBasics">data model</a>, to be published and edited by Web clients using simple HTTP messages. This specification defines a set of recommended (but not required) rules for constructing URIs to identify the data and metadata exposed by an OData server as well as a set of reserved URI query string operators, which if accepted by an OData server, MUST be implemented as required by this document.</p>
 <p>The <a href="../atom-format">[OData:Atom]</a> and <a href="../json-format">[OData:JSON]</a> documents specify the format of the resource representations that are exchanged using OData and the <a href="../operations">[OData:Operations]</a> document describes the actions that can be performed on the URIs (optionally constructed following the conventions defined in this document) embedded in those representations.</p>
diff --git a/pages/url-conventions.html b/pages/url-conventions.html
@@ -4,6 +4,7 @@
 date: 2014-02-20 09:14:47.000000000 +08:00
 permalink: /documentation/odata-version-3-0/url-conventions/
 ---
+<h5 class="alert alert-warning">Note: <a href="/documentation/" title="" class="alert-link">OData Version 4.0</a> is the current recommended version of OData. OData Version 4.0 has been standardized by OASIS and has many features not included in old OData versions.</h5>
 <h1 id="url1">1. Introduction</h1>
 <p>The Open Data Protocol (OData) enables the creation of REST-based data services, which allow resources, identified using Uniform Resource Identifiers (URLs) and defined in a data model, to be published and edited by Web clients using simple HTTP messages. This specification defines a set of recommended (but not required) rules for constructing URLs to identify the data and metadata exposed by an OData service as well as a set of reserved URL query string operators, which if accepted by an OData service, MUST be implemented as required by this document.</p>
 <p>The [OData:Atom] and [OData:JSON] documents specify the format of the resource representations that are exchanged using OData and the [OData:Operations] document describes the actions that can be performed on the URLs (optionally constructed following the conventions defined in this document) embedded in those representations.</p>
