Add more details regarding research process (#7)

* add more details regarding research process

* adjust section based on recent meeting discussions

Author: Ethan-Arrowood

README.md

@@ -10,7 +10,13 @@ A research analysis on the usage of `package.json` throughout the entire JavaScr
 
 Within the `research` directory are a collection of markdown files each containing the analysis for one or more top-level `package.json` properties. The file, [package-json.md][package-json], contains a property research index.
 
-To contribute new research:
+Research should primarily focus on a property's existing rule-set and use-cases. Details should be presented in such a way to not infer bias to any single tool; however, since many tools share the same behavior, those details can be presented as fact.
+
+For example, the `dependencies` property has a number of ways a dependency can be specified. From using SemVer, workspace syntax, or even specifying a git link, many package manager tools will resolve the value in a similar way (though the lockfile output may be unique).
+
+Research should accurately and clearly declare when it is presenting tool-specific behavior about a certain package.json property.
+
+### Contributing New Research:
 - Make sure that an analysis has not already been conducted on the property or properties you are analyzing.
   - Check the index in [package-json.md][package-json].
   - Check in progress pull requests.
@@ -24,7 +30,7 @@ To contribute new research:
   - The PR title should follow the format: `[research] Property: <property>` or `[research] Properties: <property-1>, <property-2>`.
 - Once your research is complete, mark the PR as "ready to review".
 
-To contribute to existing research:
+### Contributing to Existing Research:
 - Open a PR with the title `[research] Edit: <file-name.md>`.
 
 [package-json]: <./research/package-json.md>