Files
frappy/doc/source/protocol/issue_2.rst
Markus Zolliker 8663501150 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>
2017-11-03 08:46:20 +01:00

785 B

SECoP Issue 2: Equipment ID in Describing Message (under discussion)

The equipment ID is a SEC node property, and it is therefore redundant to put it as the second item of the describe message.

However as the describe/describing message might be extended later, for example to get the description of single modules only, we should specify a fixed word for the second item of the describe message, for example the keyword "ALL" or "All".

At the meeting in Berlin (2017-05-30) this was discussed, but it was not yet decided the the keyword should be exactly. Until a final decision, SECoP clients should ignore the second item.

Opinions

We should use key keyword ALL (Markus Zolliker)

Decision