This repository is the home of all Tango Open Specification.
The process to add or change an RFC is the following:
- An RFC is created and modified by pull requests according to the Collective Code Construction Contract (C4).
- The RFC life-cycle SHOULD follow the life-cycle defined in the Consensus-Oriented Specification System (COSS).
| Short Name | Title | Type | Status | Editor |
|---|---|---|---|---|
| RFC-1 | The Tango control system | Standard | Draft | Lorenzo Pivetta |
| RFC-2 | The device object model | Standard | Draft | David Erb |
| RFC-3 | The command model | Standard | Draft | Sergi Blanchi-Torné |
| RFC-4 | The attribute model | Standard | Draft | Sergi Blanchi-Torné |
| RFC-5 | The property model | Standard | Draft | Gwenaelle Abeillé |
| RFC-6 | The database system | Standard | Draft | |
| RFC-8 | The server model | Standard | Draft | |
| RFC-9 | The class model | Standard | Draft | |
| RFC-10 | The Request-Reply protocol | Standard | Draft | |
| RFC-11 | The Request-Reply protocol - CORBA implementation | Standard | Draft | |
| RFC-12 | The Publisher-Subscriber protocol | Standard | Draft | |
| RFC-13 | The Publisher-Subscriber protocol - ZeroMQ implementation | Standard | Draft | |
| RFC-XX | The dynamic attribute and command | Standard | Draft | |
| RFC-XX | Logging service | Standard | Draft | |
| RFC-XX | Cache system | Standard | Draft | |
| RFC-XX | Memorised attribute service | Standard | Draft | |
| RFC-XX | Authorisation system | Standard | Draft | |
| RFC-XX | High Level API | Standard | Draft | |
| RFC-XX | High Level API - Python implementation | Standard | Draft | |
| RFC-XX | High Level API - Java implementation | Standard | Draft |