From a2fef915e3b961b389433c09bc74b40269f292b9 Mon Sep 17 00:00:00 2001 From: Ashwin Kumar Date: Sun, 8 Oct 2017 17:02:21 +0200 Subject: [PATCH] Updating link to Twitter API Link to Twitter API was broken, put in the correct link --- lessons/restfulresourcenaming.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lessons/restfulresourcenaming.html b/lessons/restfulresourcenaming.html index 16edf03..918437e 100644 --- a/lessons/restfulresourcenaming.html +++ b/lessons/restfulresourcenaming.html @@ -115,7 +115,7 @@

By now you can see how the hierarchy concept works. There aren't any hard and fast rules, only make sure the imposed structure makes sense to consumers of your services. As with everything in the craft of Software Development, naming is critical to success.

Look at some widely used APIs to get the hang of this and leverage the intuition of your teammates to refine your API resource URIs. Some example APIs are: