revision of SECoP documentation

- created secop_v2017-09-14.rst, based on the GoogleDocs
  SECoP Preliminary V2016-11-30 (rc 2)
- this Document is supposed to contain the full SECoP standard
- created SECoP issues
- moved everything else to "outdated" (kept for reference)

Change-Id: I87d69d1846fc4ed55f1c78b22fd4650d8550152b
Reviewed-on: https://forge.frm2.tum.de/review/16573
Reviewed-by: Enrico Faulhaber <enrico.faulhaber@frm2.tum.de>
Tested-by: JenkinsCodeReview <bjoern_pedersen@frm2.tum.de>

doc/source/protocol/issue_5.rst

@@ -0,0 +1,34 @@
+SECoP Issue 5: Definition of the term 'Property' (under discussion)
+===================================================================
+
+The definition as in SECoP V2016-11-30 draft is not very consistent.
+
+As decriptive data we have:
+
+- SEC node properties
+- module properties
+- parameters properties
+- command properties
+
+Live data may be:
+- value
+- timestamp 't'
+- sigma 'e'
+
+It is confusing to use the same term 'property' for live data and for
+descriptive data.
+
+The section with the definition of properties has to be rewritten.
+
+Opinions
+--------
+
+Enrico proposed to name live data like timestamps and sigma 'qualifiers'.
+
+Markus supports this. He would be happy also with an other term than
+'qualifiers', but definitely does not like the terms 'live properties' and
+'descriptive properties', as two different things share the same name.
+
+
+Decision
+--------