...
| Name | Company | Phone Number | TIme Zone | |
|---|---|---|---|---|
| AT&T | dw2049@att.com | (561) 371-7619 | EST | |
| AMDOCS | sharon.chisholm@amdocs.com | EST | ||
| Huawei | Christopher.Donley@huawei.com | |||
| AT&T | gg2147@att.com | (847) 420-8459 | ||
| Mark Ho | AT&T | mh574f@att.com | (781) 791-4345 | EST |
| VMware | ramkik@vmware.com | |||
| ARM (OAM Technologies) | adolfo.perez-duran@oamtechnologies.com | 720.560.2659 | MT | |
| Intel | alex.vul@intel.com | |||
| Huawei | Parviz.Yegani@huawei.com |
...
- SHALL (mandatory)is used to indicate a requirement that is contractually binding, meaning it must be implemented, and its implementation verified.
- SHOULD (non-mandatory) is used to indicate a goal which must be addressed by the design team, but is not formally verified.
Item | What | Notes |
|---|---|---|
| 1 |
Resources
- REST APIs Must be Hypertext-Driven: Blog post where Roy Fielding argues that not any HTTP-based interface is a REST API
http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven