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).
Read more here.
The table below summarises all available or expected specifications. For the current "work in progress status", please check either PRs or Wiki.
| Short Name | Title | Status | Editor |
|---|---|---|---|
| RFC-1 | The Tango control system | Raw | Lorenzo Pivetta |
| RFC-2 | The device object model | Draft | Vincent Hardion |
| RFC-3 | The command model | Draft | Sergi Blanchi-Torné |
| RFC-4 | The attribute model | Draft | Sergi Blanchi-Torné |
| RFC-5 | The property model | Draft | Gwenaelle Abeillé |
| RFC-6 | The database system | Draft | Gwenaelle Abeillé |
| RFC-7 | The pipe model | Raw | |
| RFC-8 | The server model | Raw | Lorenzo Pivetta |
| RFC-9 | Data types | Raw | Gwenaelle Abeillé |
| RFC-10 | The Request-Reply protocol | Raw | Reynald Bourtembourg |
| RFC-11 | The Request-Reply protocol - CORBA implementation | Raw | |
| RFC-12 | The Publisher-Subscriber protocol | Raw | Vincent Hardion |
| RFC-13 | The Publisher-Subscriber protocol - ZeroMQ implementation | Raw | |
| RFC-14 | Logging service | Raw | Sergi Blanchi-Torné |
| RFC-15 | The dynamic attribute and command | Raw | Reynald Bourtembourg |
| RFC-16 | Cache system | Raw | |
| RFC-17 | Memorised attribute service | Raw | |
| RFC-18 | Authorisation system | Raw | |
| RFC-XX | High Level API | Raw | |
| RFC-XX | High Level API - Python implementation | Raw | |
| RFC-XX | High Level API - Java implementation | Raw |