...
| No. | R5 Project Names | API Subcommittee member assignment | Status | Notes |
| 1 | Brower | |||
| 2 | Brower | |||
| 3 | ||||
| 4 | Brower | |||
| 5 | ||||
| 6 | Brower | |||
| 7 | Brower | |||
| 8 | Brower | |||
| 9 | Brower | |||
| 10 | ||||
| 11 | Micro MEC Ferenc Székely | Brower |
| |
| 12 | Brower | |||
| 13 | Brower | |||
| 14 | 5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint | Brower | ||
| 15 | Brower | |||
| 16 | ||||
| 17 | Brower | |||
| 18 | Brower | |||
| 19 | Brower | No changes from R5, per e-mail from HaiHui Wang | ||
| 20 | ||||
| 21 | Brower | |||
| 22 | ||||
| 23 | Brower | |||
| 24 | Brower | |||
| 25 | Brower | |||
| 26 | ||||
| 27 | Brower | |||
| 28 | Brower | Per e-mail from Colin Peters , blueprint consumes Kubernetes and EdgeX APIs API info form uploaded 14 Scheduled for review by API subcommittee | ||
| 29 | Robot Basic Architecture Based on SESS | Brower | Per e-mail from Inoue Reo blueprint does not export or consume APIs | They are uploading an API info form indicating no APIs, along with comments about possible future API usage |
...