Project Title	API Versioning
Target Release
Epic
Document Status	DRAFT
Document Owner
Document Sign-Off
Subject Matter Expert(s)
Technical Expert(s)

Background & Business Value

How API Versioning will be standardized on, but ... how do we handle the change management for this? How do we communicate this out? Where should information be listed? WIll clients be contacted and how?

Goals

Assumptions

Out of Scope

Requirements

Ticket(s)	Title	User Story	Priority	Notes

User Interaction, Design & Architecture

Examples and References

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome	Decision Date
Ian Lessing (Unlicensed) - How do other universities handle this?

Browser not supported