Use of oslc:range, especially for enumerations, is unclear

Add Section "Defining Enumerations" to core-vocab.html.

Update the Shape Resources Overview section to start with:

"A resource shape is a resource that describes the contents of, and constraints on, the RDF representation of other resources. These constraints are intended to be applicable to OSLC core and domain vocabularies in order to express the domains sufficiently to support interoperability between clients and servers that use and support them. Resource shapes specify the minimum an implementation needs to do be considered compliant. Specifically:

• All compliant implementations MUST do what the spec says when they get data that conforms to the shape.
• Compliant implementations MAY also do something sensible when they get other data.

That is, the intention is not that an OSLC implementation would reject a message if it violated shape constraints, rather the intention is that implementations do what is specified by an OSLC spec when they get data that conforms to the shapes."

Add the following clause at the end of section 6.2 Associating and Applying Shapes:

"If a resource satisfies its applicable shapes, client and server implementations MUST behave as described in the defining OSLC specifications. If a resource does not satisfy its applicable shapes, implementations SHOULD attempt to complete the operation with the given data if possible. Otherwise implementations MAY reject the operation."

Specify oslc:range for most oslc:Property constraints in the core shapes.

This would specify the "likely" type of the property, but would not prevent servers from using other types.

For oslc;Property shape for oslc:range, change the dcterms:description from "For object properties, an allowed object resource type." to: "For object properties, specifies what the target resource type is expected to be, but that is not necessarily the case."

Ensure that the description of the property in the specification is consistent with this shape description.