ToS v. SLA?

@kinlane was sharing similar relevant thoughts about whether there should be SLAs for government APIs and suggested something more akin to a 'service accord' [in a recent post of his](http://apievangelist.com/2014/03/14/api-service-accord/).

Some other thoughts from that conversation are below, but a basic question is - does this conversation below with the [ToS conversation going on here](https://github.com/GSA/API-Resources/issues/1) or as a standalone effort?
#
- Suggested Terms
- Operational Understanding
- Operational Accord
- Service Accord
- Wikipedia
- [Service Level Agreement](http://en.wikipedia.org/wiki/Service-level_agreement)
- [Operational Level Agreement](http://en.wikipedia.org/wiki/Operational-level_agreement)
- News
- ['What You Should Know About SLAs'](http://www.techopedia.com/2/29356/it-business/it-management/what-you-should-know-about-service-level-agreements)
- Outline - 1
- Definition of services
- Performance measurement
- Problem management
- Customer duties
- Warranties
- Disaster recovery
- Termination of agreement
- Outline - 2
- Description of Services
- Payment For Services
- Term
- Work Product Ownership
- Confidentiality
- Indemnification
- Warranty
- Remedies
- Entire Agreement
- Severability
- Amendment
- Governing Law
- Notice
- Assignment
- Other
- SLA negotiation
- SLA monitoring
- SLA enforcement