General TOSCA question. Is there anything in the spec that requires attributes to be values rather than functions? IOW, is there anything in there that prevents an orchestrator from representing an attribute read as more of a "getter", rather than a database fetch? I ask because I've run across a case where I'd prefer an attribute reference to return a calculated value. Seems more flexible if allowed, and if not allowed, it should be allowed.
DeWayne
