some general structure

REST_Intro/intro.md

@@ -45,6 +45,16 @@ headers: --headers
 data: -d property1 = value1
 Query parameters?
 
+- Concept of a state machine GET reads state. POST and PUT modify state
+- Statelessness. No client context is stored on the Server
+- Client-Server architecture. You don't know how the data is stored
+- Layered System: Client cannot tell wether it is directly connected to the server
+- Uniform Interface:
+  - Resource Identification in requests
+  - Resource Manipulation through representation
+  - Self-Descriptive Messages
+  - Hypermedia as the engine of application: a REST client should be able to use server-provided links dynamically
+
 Do we need that?
 # POST procedures... Create an issue at gitlab?
 Go to requestbin.com
@@ -64,4 +74,4 @@ We use our JupyterHub, today at http://wthp008.physik.uni-wuerzburg.de:31476
 
 # Outlook
 - jq: cli parsing of json formatted data.
-- OPTIONS method -> see RALPH example
+- OPTIONS method -> see RALPH example -> discoverable API
\ No newline at end of file