René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Fix Storage naming to (mostly) match API Schema","articleBody":"- [x] Renaming noun \"key\" to \"object\" or close relative (#560).\n- [x] Remove `boto` aliases (#568)\n- [x] Address other concerning naming conventions\n\n(Above added by @dhermes on 1/19/2014)\n\n---\n\nThe naming conventions appear to be modeled around s3's boto library, but the library is not compatible with S3. It seems like it might be more useful to use the JSON API resource names. \nThe major difference here is the use of \"key\" to represent an \"object\" resource.  The Cloud Storage API JSON docs typically use the word \"key\" to refer to an API key or a service account private key file, never to a cloud object resource.  Of course \"object\" is a reserved name in Python, but there are other possibilities.\nWith the hierarchy of connection/bucket/key, this looks a lot like boto without actually supporting s3, which could confuse users.\n\n/cc @thobrla\n","author":{"url":"https://github.com/silvolu","@type":"Person","name":"silvolu"},"datePublished":"2015-01-14T19:10:46.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":11},"url":"https://github.com/544/google-cloud-python/issues/544"}