In practice, I use a slight enhancement. Not only does the url contain the ID to the element, but changing a part of it can tell the site how to display the dat

In practice, I use a slight enhancement. Not only does the url contain the ID to the element, but changing a part of it can tell the site how to display the data. For example: http://www.shellcompanyfinder.com/ShellCompanies/7845/11/NathanMyhrvoldsIntellectualVentures http://www.shellcompanyfinder.com/ShellCompanies/7845/11/Nat... Is a url that shows the data for a human. http://www.shellcompanyfinder.com/ShellCompanies/7845/35/NathanMyhrvoldsIntellectualVentures http://www.shellcompanyfinder.com/ShellCompanies/7845/35/Nat... or http://www.shellcompanyfinder.com/ShellCompanies/7845/json/NathanMyhrvoldsIntellectualVentures http://www.shellcompanyfinder.com/ShellCompanies/7845/json/N... Will show the data in JSON format. Or you can get it in CSV if you prefer: http://www.shellcompanyfinder.com/ShellCompanies/7845/csv/NathanMyhrvoldsIntellectualVentures http://www.shellcompanyfinder.com/ShellCompanies/7845/csv/Na... Makes it easy to show human forms and also keep it accessible to automation and integration in an easy and consistent manner.