Now that we have a TypeDefinition/AttributeDefinition metadata at the Instance level, it is possible to extend each Resource in arbitrary ways, so the use of a set of Characteristics (which provide the same function) seems superfluous. This becomes clear when you lay an ABAC rules engine across the API in which case characteristics and attributes have to be expressed differently even though the characteristics are really just a set of extensible attributes.