resourceState attribute needs clarification

The CAMP spec currently defines a "ResourceState" type and defines a "resourceState" attribute of this type for some, but not all, resources. There are several problems with this:

1.) There is some confusion between the information communicated by this attribute and the state of the application within the application lifecycle. We need to make it clear that "resourceState" is about that particular resource and not the (more abstract) application which is represented by the resource.

2.) The values and semantics of the "ResourceState" type are only listed as exampled (through use of "e.g."). We need to define a enumeration of specific values with specific semantics.

3.) The "resourceState" attribute is only defined for some resources and not others. We either need to define "resourceState" as a common attribute, or explain the criteria for its application to a particular resource type.