valueflows

commit 1ecd58cfaba1480bba0c9e2b72e4fbbc93486398
parent f0c1df0056c5180a11ffc8bd21414adaad2a8d25
Author: Lynn Foster <foster.j.lynn@gmail.com>
Date:   Tue, 19 Mar 2019 11:21:26 -0500

clarify resource classification and specification (#465)


Diffstat:
M
docs/introduction/resources.md
 | 
6
+++++-

1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/docs/introduction/resources.md b/docs/introduction/resources.md
@@ -26,7 +26,11 @@ So, for example, you may want an apple. Or you may want a green apple. Or you ma
 
 Or, Herb is the parent classification of Anise Hyssop, Goldenrod, Nettles, Red Clover, etc.  Besides its usefulness in understanding taxonomies of resource types, this can be useful when one can define a general recipe that will work for many more specific kinds of resources.
 
-People can use the multitude of existing taxonomies for resources, or can also create their own as needed.
+People can use the multitude of existing taxonomies for resource classifications, or can also create their own as needed.  The references to resource classifications are uri's, and not covered inside ValueFlows.
+
+The ResourceSpecification is part of ValueFlows, and part of the recipe structure. 
+It is used when you need to have more definition and configurability than you can 
+find in a simple taxonomy, whether there is a recipe or not.
 
 #### Identification and Behaviors of Resources