René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Docstring Conventions","articleBody":"This Issue follows up https://github.com/ODM2/ODM2PythonAPI/pull/105#discussion_r141936709.\r\n\r\nWe need a set of conventions that we should follow when writing docstring within the functions and classes:\r\n- [X] Follow the google style documentation as discussed in #97. Official example [here](http://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_google.html) (and for reference, [here's a comparison to the numpy style](http://sphinxcontrib-napoleon.readthedocs.io/en/latest/index.html#google-vs-numpy))\r\n- [X] Don't say \"defaults to ____\" unless it needs further explanation. The default value is already available in the method/function definition.\r\n- [X] If function needs to be instantiated, explicitly show in example. See [here for discussion of class vs instance methods.](https://stackoverflow.com/questions/17134653/difference-between-class-and-instance-methods)\r\n- [X] Provide link to Controlled Vocabulary if it needs CV as value.\r\n- [X] **Other code comments besides docstrings** must use `#` rather than triple quotes, because all triple quotes, regardless of where they're found will be interpreted as doctrings by Sphinx.\r\n\r\nCurrently (10/1) one of the best docstrings available as an example is in [ReadODM2.getAffiliations](https://github.com/ODM2/ODM2PythonAPI/blob/master/odm2api/ODM2/services/readService.py#L545)\r\n\r\ncc @emiliom \r\n\r\nPlease add more as necessary.","author":{"url":"https://github.com/lsetiawan","@type":"Person","name":"lsetiawan"},"datePublished":"2017-09-29T19:32:39.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/106/ODM2PythonAPI/issues/106"}