Skip to content

Commit 6e63d2b

Browse files
authored
Move up the easy read
1 parent 7dafc17 commit 6e63d2b

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

Guidelines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -128,14 +128,14 @@ These guidelines aim to achieve the following:
128128
### 3.1 Recommended reading
129129
Understanding the philosophy behind the REST Architectural Style is recommended for developing good HTTP-based services. If you are new to RESTful design, here are some good resources:
130130

131+
[REST on Wikipedia][rest-on-wikipedia] -- Overview of common definitions and core ideas behind REST.
132+
131133
[REST Dissertation][fielding] -- The chapter on REST in Roy Fielding's dissertation on Network Architecture, "Architectural Styles and the Design of Network-based Software Architectures"
132134

133135
[RFC 7231][rfc-7231] -- Defines the specification for HTTP/1.1 semantics, and is considered the authoritative resource.
134136

135137
[REST in Practice][rest-in-practice] -- Book on the fundamentals of REST.
136138

137-
[REST on Wikipedia][rest-on-wikipedia] -- Overview of common definitions and core ideas behind REST.
138-
139139
## 4 Interpreting the guidelines
140140
### 4.1 Application of the guidelines
141141
These guidelines are applicable to any REST API exposed publicly by Microsoft or any partner service. Private or internal APIs SHOULD also try to follow these guidelines because internal services tend to eventually be exposed publicly. Consistency is valuable to not only external customers but also internal service consumers, and these guidelines offer best practices useful for any service.

0 commit comments

Comments
 (0)