TL;DR (from [1]). Guidelines for the "best" URIs: * Simplicity: Short, mnemonic URIs will not break as easily when sent in emails and are in general easier to

TL;DR (from [1]). Guidelines for the "best" URIs: * Simplicity: Short, mnemonic URIs will not break as easily when sent in emails and are in general easier to remember. * Stability: Once you set up a URI to identify a certain resource, it should remain this way as long as possible ("the next 10/20 years"). Keep implementation-specific bits and pieces such as .php out, you may want to change technologies later. * Manageability: Issue your URIs in a way that you can manage. One good practice is to include the current year in the URI path, so that you can change the URI-schema each year without breaking older URIs. 1: https://www.w3.org/TR/cooluris/#cooluris https://www.w3.org/TR/cooluris/#cooluris