Issue 19150: Section 1: scope (ifml-ftf) Source: WebRatio Inc (Dr. Marco Brambilla, marco.brambilla(at)webratio.com) Nature: Uncategorized Issue Severity: Summary: Issue: scope not well described Solution: Remove: "; and the distribution of control, data and business logic at the different tiers of the architecture" - not explicitly covered. Add the fact we are only referencing the business logic and not controlling the sequence of actions Resolution: new text formulation, according to suggestion Revised Text: In Section 1, Scope, the description of the scope is now: This specification defines the Interaction Flow Modeling Language (IFML). The objective of IFML is to provide system architects, software engineers, and software developers with tools for the definition of Interaction Flow Models that describe the principal dimensions of an application front-end: the view part of the application, made of view containers and view components; the objects that embody the state of the application and the references to business logic actions that can be executed; the binding of view components to data objects and events; the control logic that determines the actions to be executed after an event occurrence; and the distribution of control, data and business logic at the different tiers of the architecture. Added “view” to containers, and “references to” to business logic. Removed “sequence of” from actions (as IFML does not allow to specify orchestrations of actions). Actions taken: December 9, 2013: received issue July 15, 2014: closed issue Discussion: End of Annotations:===== s is issue # 19150 ISSUE 1: Section 1: scope. Issue: scope not well described Solution: Remove: "; and the distribution of control, data and business logic at the different tiers of the architecture" - not explicitly covered. Add the fact we are only referencing the business logic and not controlling the sequence of actions