Interaction Flow Modeling Language Avatar
  1. OMG Specification

Interaction Flow Modeling Language — Closed Issues

  • Acronym: IFML
  • Issues Count: 76
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Summary

Key Issue Reported Fixed Disposition Status
IFML-77 Fig. 5 - ContentModel references UML Element IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-76 DI and DD specifications need to be fixed based on the changes to the MM IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-74 Figure 3 - wrong diagram IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-75 Class Expression description to be fixed IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-73 Wrong associations in Class Form IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-72 Class Form - wrong description text IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-71 Change content-model in domain-model IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-69 rewrite In ConditionalExpression (8.3.6) IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-70 Replace ContentAccess with DataBinding IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-68 viewelementevent can be associated with 0..1 viewelements IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-67 Conditional expression can have outgoing flow IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-66 ViewComponentPart: association with interactionflow is missing IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-65 viewelementevent cannot be associated with viewcomponentpart IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-63 Description of some association ends IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-62 system event IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-64 isLandmark IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-61 triggeringExpression [1..*] IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-60 parameterBinding [0..*] IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-59 History and default context are not defined IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-58 Fig. 53 and all others that include a XOR IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-57 Dangling actions IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-54 Add SetContext event IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-55 context variables IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-53 An event can have at most one incoming and one outgoing flow IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-56 Outgoing flows from actionevents IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-52 Add Default value to parameters IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-51 Rename submit and select events IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-49 extensibility IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-50 content model IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-48 modules in UML profile IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-47 actions IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-45 view components in examples IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-46 connection to BPMN IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-43 symbol of submit event IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-44 throwing and catching events IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-42 ports in modules IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-41 data access typo IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-40 Form class description IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-38 parameter direction IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-39 parameters of field IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-37 misplaced img IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-36 MessageReader in example IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-34 throwing events in examples IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-33 wrong component in figure 54 IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-35 MessageWritter typo IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-31 Action description IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-32 Menu ViewContainer IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-30 An List - fix typo IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-29 Fix Figure 64 IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-28 add event type onLoad IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-27 Modality in Table 1 IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-26 Add Window in table 1 IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-24 module defs IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-25 Default container IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-23 actions in containers IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-22 Parameter scope IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-21 Fix Figure 50 IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-20 Content of Field Class IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-19 Low resolution images in specification IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-18 Section 6.3: IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-17 Chapter 11: IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-16 Section 11.3 IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-14 Section 8.4.9: IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-13 Section 8.4.4: SubmitEvent property must be removed in text (not there in metamodel) IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-15 Section 9.2 - 9.3: IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-12 Section 8.3.32 - 8.3.33: IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-11 Section 8.4.4: IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-10 Section 8.3.28 IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-8 Section 8.3.24: IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-7 Section 8.1.6 IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-6 Section 8.1.7 IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-9 Section 8.3.27: IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-5 Section 8.1.4: IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-4 Section 6.4: acknowledgements IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-3 Section 1: scope IFML 1.0b1 IFML 1.0b2 Resolved closed
IFML-2 Two of the XMI files use the XMI 2.1 namespace instead of XMI 2.4 IFML 1.0b1 IFML 1.0b2 Resolved closed

Issues Descriptions

Fig. 5 - ContentModel references UML Element

  • Key: IFML-77
  • Legacy Issue Number: 19206
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    The content model (aka Domain Model) should reference a generic modeling element (e.g., DomainElement), so as to enable any kind of domain model to be used with IFML.
    UML element can be associated to it.
    DomainElement should be extensible.

  • Reported: IFML 1.0b1 — Thu, 6 Feb 2014 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Created new class in IFML Metamodel: DomainElement. All the classes describing the domain elements (DomainConcept, FeatureConcept, BehavioralFeatureConcept, BehaviorConcept) now extend the DomainElement class, instead of NamedElement. Association from DomainModel is to DomainElements and not to UML::Element.
    Fixed Figure 5 by adding the new DomainElement class and its 4 subclasses.
    Added new clause describing the DomainElement. Fixed generalization text in the 4 subclasses.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

DI and DD specifications need to be fixed based on the changes to the MM

  • Key: IFML-76
  • Legacy Issue Number: 19203
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Update definition of diagrams by adding the new concepts and fixing the updated ones.

    Replace:
    "actionExpression:" --> "activationExpression:"

    In listing of 10.6 remove rules for [modal] and [modeless], and for [clientSide]; Fix radius of the event element to static value. Add port and throwing events

  • Reported: IFML 1.0b1 — Fri, 31 Jan 2014 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    No Data Available

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Figure 3 - wrong diagram

  • Key: IFML-74
  • Legacy Issue Number: 19195
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    iagram in Fig. 3 is wrongly repeating the Albums containers twice. It should appear only once, and the arrow should go back to it after exiting from the Action.

  • Reported: IFML 1.0b1 — Tue, 28 Jan 2014 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Figure fixed as requested

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Class Expression description to be fixed

  • Key: IFML-75
  • Legacy Issue Number: 19200
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    reference to the context in the descriptive text to be removed.
    Replace a "." with a "," in first sentence.
    In the metamodel, remove the association with Parameter [0..1].

  • Reported: IFML 1.0b1 — Thu, 30 Jan 2014 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Text fixed as requested and as reported below. Metamodel fixed by removing association with Parameter

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Wrong associations in Class Form

  • Key: IFML-73
  • Legacy Issue Number: 19066
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    (8.4.4) submitEvent [0..1]: SubmitEvent - Event that triggers a navigation, which passes the Field's values as Parameters to the target InteractionFlowElement. --> revise text. multiplicity is max N

  • Reported: IFML 1.0b1 — Tue, 5 Nov 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    submitEvent association completely removed, to address issue 19160. No change needed for this issue.
    Disposition: Closed, no change

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Class Form - wrong description text

  • Key: IFML-72
  • Legacy Issue Number: 19065
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Replace: Order in which the ValidationRules are going to be applied to the Fields of the ViewComponent. with correct description (8.4.4)

  • Reported: IFML 1.0b1 — Tue, 5 Nov 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Disposition: See issue 19158 for disposition

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Change content-model in domain-model

  • Key: IFML-71
  • Legacy Issue Number: 19064
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Change content-model in domain-model
    rename in domain-model

  • Reported: IFML 1.0b1 — Tue, 5 Nov 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    ContentModel has been renamed as DomainModel throughout the whole specification document and machine-readable files.
    Content Model has been replaced with Domain Model (matching the needed case) throughout the whole specification document.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

rewrite In ConditionalExpression (8.3.6)

  • Key: IFML-69
  • Legacy Issue Number: 19058
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    In ConditionalExpression (8.3.6): rewrite the following: When a ConditionalExpression has an incoming NavigationFlow it means that the DataBinding is queried with the query expression represented by the ConditionalExpression for retrieving content.

  • Reported: IFML 1.0b1 — Thu, 31 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    The wording of the description has been changed as follows

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Replace ContentAccess with DataBinding

  • Key: IFML-70
  • Legacy Issue Number: 19059
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    "ContentBinding is specialized in two concepts, DataBinding and DynamicBehavior. A DataBinding references a UML Classifier that may represent an object, an XML file, a table in a database etc. A *ContentAccess* is associated with a ConditionalExpression, which determines the specific content to be obtained from the content source. A DynamicBehavior represents a content access such as a service or method that returns content after an invocation, as represented by a UMLBehavioralFeature for representing it." (8.1.8)

    *ContentAccess* – replace with DataBinding

  • Reported: IFML 1.0b1 — Thu, 31 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Disposition: See issue 18936 for disposition

  • Updated: Sat, 7 Mar 2015 01:10 GMT

viewelementevent can be associated with 0..1 viewelements

  • Key: IFML-68
  • Legacy Issue Number: 19057
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    viewelementevent can be associated with 0..1 viewelements.

    should be 1

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    ViewElementEvent can be associated with 1 ViewElement. Metamodel and textual descriptions updated accordingly.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Conditional expression can have outgoing flow

  • Key: IFML-67
  • Legacy Issue Number: 19056
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Conditional expression can have outgoing flow. Correct? The text says it only supports incoming flows. Constraint missing?

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    A conditional expression should not have an outgoing flow. The issue is closed
    Disposition: Closed, no change

  • Updated: Sat, 7 Mar 2015 01:10 GMT

ViewComponentPart: association with interactionflow is missing

  • Key: IFML-66
  • Legacy Issue Number: 19055
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    ViewComponentPart: association with interactionflow is missing. Correct?

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    It’s correct. ViewComponentPart inherits the association from InteractionFlowElement. No action needed.
    Disposition: Closed, no change

  • Updated: Sat, 7 Mar 2015 01:10 GMT

viewelementevent cannot be associated with viewcomponentpart

  • Key: IFML-65
  • Legacy Issue Number: 19054
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    viewelementevent cannot be associated with viewcomponentpart, is it correct?

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    The association ViewComponentPart – ViewElementEvent already exists. However, it is not shown in any high level metamodel picture. Now added in Figure 10. Events.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Description of some association ends

  • Key: IFML-63
  • Legacy Issue Number: 19052
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Description of some association ends is missing and not listed

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    all the lists of association ends, attributes and ocl constraints have been checked. Missing elements added throughout the spec. Association ends names have been set to plural (adding “s”) when maximum multiplicity is bigger than 1.
    Fixes applied throughout the specification and the metamodel

  • Updated: Sat, 7 Mar 2015 01:10 GMT

system event

  • Key: IFML-62
  • Legacy Issue Number: 19051
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    system event: chech difference between activation expression, triggering expression, interactionflow expression

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    The three concepts have different meaning. No action required in the specification.
    Disposition: Closed, no change

  • Updated: Sat, 7 Mar 2015 01:10 GMT

isLandmark

  • Key: IFML-64
  • Legacy Issue Number: 19053
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    "• isLandmark: Boolean - If true, the ViewContainer is directly reachable from any ViewElement. It represents an implicit link between all the other ViewElements and the ViewContainer."[8.3.34]

    – > replace: from any ViewElement contained, directly or indirectly, in the same ViewContainer

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    proposed text change applied

  • Updated: Sat, 7 Mar 2015 01:10 GMT

triggeringExpression [1..*]

  • Key: IFML-61
  • Legacy Issue Number: 19050
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    "triggeringExpression [1..*]: Expression - Expressions that determines when or under what conditions the SystemEvent should be triggered." (8.3.31)

    should be 0..*

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Multiplicity of association fixed.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

parameterBinding [0..*]

  • Key: IFML-60
  • Legacy Issue Number: 19049
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    parameterBinding [0..*]: ParameterBinding - The ParameterBindings composing the ParameterBindingGroup.(8.3.29)

    should be 1..*

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Multiplicity of association (and plural name of association) fixed.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

History and default context are not defined

  • Key: IFML-59
  • Legacy Issue Number: 19048
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    In these sentences (9.3): ʺIf the computation semantics of the ViewContainer is without history, default contexts are considered in point 3. if the computation semantics is with context history, components may draw their input values either from default contexts or from the past context existing prior to the last flow navigation.ʺ

    history and default context are not defined. Simplify this part.

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Disposition: See issue 16162 for disposition

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Fig. 53 and all others that include a XOR

  • Key: IFML-58
  • Legacy Issue Number: 19047
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Fig. 53 and all others that include a XOR: add a ʺ...ʺ for showing that there are more elements in the xor

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Figures have been fixed by adding “…”

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Dangling actions

  • Key: IFML-57
  • Legacy Issue Number: 19046
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Define that dangling actions by default return back to the container containing the starting component (in Action sections)

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Added appropriate text in description of Class Action. Removed ActionEventType from SystemEventType

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Add SetContext event

  • Key: IFML-54
  • Legacy Issue Number: 19043
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Add SetContext event

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    SetContextEvent added for describing the happening of the setting of a ContextVariable value.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

context variables

  • Key: IFML-55
  • Legacy Issue Number: 19044
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Context: context variables are pointers to the corresponding element in the data model.

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Added ContextVariable, SimpleContextVariable, and DataContextVariable metaclasses and respective descriptions.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

An event can have at most one incoming and one outgoing flow

  • Key: IFML-53
  • Legacy Issue Number: 19042
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    An event can have at most one incoming and one outgoing flow

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Ocl constraint added to the Event metaclass

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Outgoing flows from actionevents

  • Key: IFML-56
  • Legacy Issue Number: 19045
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Outgoing flows from actionevents can only end in viewcomponents o viewcontainers

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    No Data Available

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Add Default value to parameters

  • Key: IFML-52
  • Legacy Issue Number: 19041
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Add Default value to input parameters. It can be an OCL expression?

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    new attribute defaultValue (of type IFML::Core::Expressoin) added to Parameter

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Rename submit and select events

  • Key: IFML-51
  • Legacy Issue Number: 19040
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Rename submit and select events
    Call them OnSubmit and OnSelect

  • Reported: IFML 1.0b1 — Wed, 30 Oct 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    SubmitEvent and SelectEvent have been renamed as OnSubmitEvent and OnSelectEvent. Names have been replaced in the metamodel and in the text.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

extensibility

  • Key: IFML-49
  • Legacy Issue Number: 18945
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Extensibility of the language should be made more explicit. The set of extensible concepts should be listed.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    No Data Available

  • Updated: Sat, 7 Mar 2015 01:10 GMT

content model

  • Key: IFML-50
  • Legacy Issue Number: 18946
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    The supported content model is only UML. This should be generalized to any content model, and UML should be left as an example

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Added classes to the metamodel: FeatureConcept and DomainConcept, UMLStructuralFeature and UMLDomainConcept, BehavioralFeatureConcept and BehaviorConcept, UMLBehavioralFeature and UMLBehavior.
    Content can now be referenced through the FeatureConcept and DomainConcept classes. Behavior can now be referenced through the BehavioralFeatureConcept and BehaviorConcept classes. UML becomes one specific case of binding.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

modules in UML profile

  • Key: IFML-48
  • Legacy Issue Number: 18944
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    The Module concept is missing in the UML profile.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Module has been added in the UML profile. Corresponding text fixed.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

actions

  • Key: IFML-47
  • Legacy Issue Number: 18943
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Actions must have a Name property. They must also appear in the UML Profile.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Action now is now also a specialization of a NamedElement.
    Action added in the UML Profile

  • Updated: Sat, 7 Mar 2015 01:10 GMT

view components in examples

  • Key: IFML-45
  • Legacy Issue Number: 18941
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Some view components in example images appear outside the containers (figs. 40, 43, 58). Add containers to avoid misunderstandings.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Containers added to all images when needed

  • Updated: Sat, 7 Mar 2015 01:10 GMT

connection to BPMN

  • Key: IFML-46
  • Legacy Issue Number: 18942
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Modules should include a reference to a BPMN Activity (optional) to represent the fact that a module could implement a business activity.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    ModuleDefinition (not Module) now contains a reference to a BPMN Activity

  • Updated: Sat, 7 Mar 2015 01:10 GMT

symbol of submit event

  • Key: IFML-43
  • Legacy Issue Number: 18938
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    The symbol of the submit event should be changed from simple big rightwards arrow ( ➡ ) to an arrow similar to the Return button in keyboards (↵ )

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    The symbol of the event has been changed and all the figures where it was used updated accordingly.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

throwing and catching events

  • Key: IFML-44
  • Legacy Issue Number: 18939
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Events should be subtyped by two specializations: throwing event and catching event, which allows explicit understanding of the role of the event. Corresponding icons should be designed (e.g., one negative and one positive, as in BPMN).

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    added CatchingEvent and ThrowingEvent. Hierarchy of events restructured accordingly. Added the text clauses describing the new events. Event description has been modified as from below.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

ports in modules

  • Key: IFML-42
  • Legacy Issue Number: 18937
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Min cardinality of relation Module--Port must be 0: a Module may have 0 Ports.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    fixed minimum cardinality for associations in the metamodel, both for Module/Port and ModuleDefinition/PortDefinition and text updated. Constraint onlyOnePortPerPortDefinition added for describing relation between Ports and PortDefinitions.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

data access typo

  • Key: IFML-41
  • Legacy Issue Number: 18936
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    In page 26, section 7.1.8, DataAccess (old term) must be replaced with DataBinding

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    typo fixed. ContentAccess replaced with DataBinding in clause 8.1.8

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Form class description

  • Key: IFML-40
  • Legacy Issue Number: 18935
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    The description of Form class in section 8.4.4 is wrong (it is actually a definition of another class). Replace with correct definition.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Fixed description of Form Class in Section 8.4.4

  • Updated: Sat, 7 Mar 2015 01:10 GMT

parameter direction

  • Key: IFML-38
  • Legacy Issue Number: 18933
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    the property "kind" of Parameter must be renamed as Direction.

    Direction of parameter is described as one of:

    direction ::= 'in' | 'out' | 'inout'

    and defaults to 'in' if omitted.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Property kind changed to direction. ParameterKind enumeration changed to Direction. Direction values fixed as requested. Text in Clauses 8.1.5, 8.2.1 and 8.3.27 has been fixed.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

parameters of field

  • Key: IFML-39
  • Legacy Issue Number: 18934
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    The class field must have an association with parameter, to allow input and output of values from the field when it has no slots.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Instead of defining an association between Field and Parameter, the class Field has been defined as extension of Parameter. In this way, a Field automatically acts as a parameter.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

misplaced img

  • Key: IFML-37
  • Legacy Issue Number: 18932
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    A misplaced image appears at the bottom of page 81 of the PDF version of the spec. Remove

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    This was a problem in the generation of the PDF. The image has been anchored in the right position in the document, so misplacement disappears when the PDF is generated in the new version of the spec.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

MessageReader in example

  • Key: IFML-36
  • Legacy Issue Number: 18931
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Description of examples in pages 82-91 sometimes still mention the component MessageReader, while the correct label is Message Details.

    (also be sure to set all the names in italics format)

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Names of components in examples always shown in italics. MessageReader component references removed. Description of Figure 54 modified as below.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

throwing events in examples

  • Key: IFML-34
  • Legacy Issue Number: 18929
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    remove throwing events after each action in the examples of appendix A.3.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Throwing events are left there because they have an important role. However, a more precise textual explanation has been written.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

wrong component in figure 54

  • Key: IFML-33
  • Legacy Issue Number: 18928
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    In Figure 54: Message Full Search viewcomponent must be replaced by <<Form>> Message Writer view component. The send event must be a submit event.

    Also fix the description of Figure 54 accordingly (and mention MessageWriter as a view container, not component)

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Figure fixed by replacing the <<Form>> component as requested. “Message Full Search” text in <<Form>> has been replaced with “Message Writer”. Send Event changed to Submit event. “Message Keyword Search” in <<Details>> replaced with “Message Details”.
    Caption of Figure 53 fixed: MessageReader ? MessageDetails

  • Updated: Sat, 7 Mar 2015 01:10 GMT

MessageWritter typo

  • Key: IFML-35
  • Legacy Issue Number: 18930
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    MessageWritter appears in figure 56 and others. Replace with MessageWriter all over the document.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    MessageWritter has been replaced with MessageWriter in all the figures containing it.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Action description

  • Key: IFML-31
  • Legacy Issue Number: 18926
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Action Description (page 30): replace InteractionViewElement with InteractionFlowElement.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Typo fixed and sentence specified better, for clarity reasons.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Menu ViewContainer

  • Key: IFML-32
  • Legacy Issue Number: 18927
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Add a new viewcontainer called Menu in the metamodel, as an extension, together with Window.

    Peculiarity: only contains events, no sub-containers or components

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Menu class added as a specialization of ViewContainer, with OCL constraint and describing text.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

An List - fix typo

  • Key: IFML-30
  • Legacy Issue Number: 18925
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Fix at page 88: An List --> A List

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    typo corrected

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Fix Figure 64

  • Key: IFML-29
  • Legacy Issue Number: 18924
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Figure 64 contains a RED [H] tag. Make it black and add the stereotype <<Window>> to all the containers.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    This and other figures still contained colored elements. All figures have been transformed in black and white (with grayscale filling of ViewComponents and Modules).

  • Updated: Sat, 7 Mar 2015 01:10 GMT

add event type onLoad

  • Key: IFML-28
  • Legacy Issue Number: 18923
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Add a new event type onLoad, applicable to containers and components.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    added onLoadEvent metaclass. Correspondingly, all the other catching events have been renamed by adding the “On” prefix in front.
    Specific events are discussed in Clause 8.1.6. Events, and therefore their discussion is removed from Clause 8.1.10 Specific Events and ViewComponents

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Modality in Table 1

  • Key: IFML-27
  • Legacy Issue Number: 18922
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Modal and Modeless containers must be tagged as <<Window>> in Table 1.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Resolution:
    Instead of adding tag Window, they must be stereotypes themselves

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Add Window in table 1

  • Key: IFML-26
  • Legacy Issue Number: 18921
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Add Window in the list of main concepts in Table 1.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Added new row in Table 2 (not Table 1) with Window, respective symbol, description and example

  • Updated: Sat, 7 Mar 2015 01:10 GMT

module defs

  • Key: IFML-24
  • Legacy Issue Number: 18919
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    The spec misses the concept of ModuleDefinition, so one can use a module but not define it.
    Module definitions should come with a packaging mechanism too.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Add ModuleDefinition and Module Package. Module renamed as ModuleDefinition (as a NamedElement); added Element, PortDefinition and ModulePackage in metamodel, with composite pattern. Added respective descriptions. Modules refer to ModuleDefinitions. Flows in PortDefinition can only be connected to elements within the ModuleDefinition. Flows in PortDefinition can only be connected to elements outside the Module. The set of Parameters of the Port is derived from the set of Parameters of the corresponding PortDefinition.
    Created new general clause for describing the new concepts and showing the metamodel fragment. Created all the specific clauses needed for describing the new concepts.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Default container

  • Key: IFML-25
  • Legacy Issue Number: 18920
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    In ClassViewContainer: The property Default can be true only for containers within a XOR container. One and only one Default subcontainer must be defined for a XOR container.

    Consider the option of transforming Default into an association from XOR container to one of its subcontainers.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Added OCL condition on ViewContainer and fixed describing text.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

actions in containers

  • Key: IFML-23
  • Legacy Issue Number: 18918
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    ViewContainers cannot contain Actions. This should be possible.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Add containment relation between ViewContainer and Action. In clause 8.1.3 figure and text have been updated.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Parameter scope

  • Key: IFML-22
  • Legacy Issue Number: 18917
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Define the scope of parameters. It's not clear where parameters can be referenced.

    A sensible rule can be: Scope of the parameter is the component or container where defined, plus everything contained in it.

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Scope and type of parameters are clarified in Clause 8.3.27 in a new piece of text.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Fix Figure 50

  • Key: IFML-21
  • Legacy Issue Number: 18916
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    In figure 50: The model of the interaction flow for moving a message to an existing or newly created tag:

    • the XOR container is not needed
    • add the needed dataflow to the second action CreateTag
    • the missing parent Folder must be added
    • fix the newPage event
  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Figure 50 fixed by: removing the XOR container and adding the missing DataFlow.

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Content of Field Class

  • Key: IFML-20
  • Legacy Issue Number: 18915
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Field can contain any sub-viewcomponentpart, not only slot.

    remove rule from Field Class:

    Constraints
    • viewComponentPartsAreSlots
    self.subViewComponentPart -> forAll(v | v.oclIsTypeOf(Slot))

  • Reported: IFML 1.0b1 — Tue, 17 Sep 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Constraint Removed

  • Updated: Sat, 7 Mar 2015 01:10 GMT

Low resolution images in specification

  • Key: IFML-19
  • Legacy Issue Number: 19180
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    most images in the spec document are difficult to read, due to low resolution exporting problems.
    Solution: if possible, replace images with vector versions

  • Reported: IFML 1.0b1 — Tue, 14 Jan 2014 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Diagram images have been replaced with vector graphics diagram images where possible. (note: this doesn’t change the content of the images, just the quality of the printing)

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 6.3:

  • Key: IFML-18
  • Legacy Issue Number: 19165
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Issue: Remove: The IFML textual syntax offers a textual syntax for expressing IFML models alternative, but equivalent, to the visual syntax

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Text above removed from Clause 6.3 – IFML artfacts. The reason is that IFML does not specify any textual syntax

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Chapter 11:

  • Key: IFML-17
  • Legacy Issue Number: 19164
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Issue: UML profile: reorganize viewelement UML profile correspondance as classes and components.

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    At the purpose of solving implementability and semantics problems, some stereotypes have been redefined (from UML component to class).
    Furthermore, new stereotypes have been added for the new elements added in the metamodel for addressing the issues filed on IFML Beta 1, and respective descriptions and symbols have been added too

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 11.3

  • Key: IFML-16
  • Legacy Issue Number: 19163
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Figure 29 and figure 32: the nested component notation does not mean packaging but component realization. Fix figure and UML Profile structure. ViewComponents can be classes and not components. Nested component instances, on the other hand, mean composite structure, which is neither component packaging nor component realization!

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    The figures derive from the definition of most of the IFML concepts as stereotypes of the UML Component class. The definition of the profile has been updated to fix this problem, as from resolution of issue 19164.
    The whole clause 11.3 has been restructured by using classes instead of components for defining ViewComponents. Furthermore, events have been stereotyped from UML Ports. Figures and respective descriptions have been fixed.

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 8.4.9:

  • Key: IFML-14
  • Legacy Issue Number: 19161
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Issue: SimpleField expose automatically an output parameter. Slots expose an input parameter.
    Solution: say that in the metamodel. Make simpleField and Slot inherit from Parameter and add OCL expressions? Rephrase Slot definition

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    This applies to 8.4.10 (slot) and 8.4.3 (field).
    Slot description has been rewritten in 8.4.10.
    Slot now inherits from Parameter too.
    Field now inherits from Parameter too

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 8.4.4: SubmitEvent property must be removed in text (not there in metamodel)

  • Key: IFML-13
  • Legacy Issue Number: 19160
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    ISSUE 11:
    Section 8.4.4:
    Issue: SubmitEvent property must be removed in text (not there in metamodel)

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Association end removed from text

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 9.2 - 9.3:

  • Key: IFML-15
  • Legacy Issue Number: 19162
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Issue: Simplify description of history management. Remove references to context and contextual flows

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Rephrasing has been applied throughout Clause 9 for removing the concept of context and contextual flows. Final text reported below.

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 8.3.32 - 8.3.33:

  • Key: IFML-12
  • Legacy Issue Number: 19159
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Issue: lists of ViewComponentParts and SubViewComponentParts

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    added “a” in text of 8.3.33. The rest of the issue does not apply.

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 8.4.4:

  • Key: IFML-11
  • Legacy Issue Number: 19158
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Issue: Text description of Form is incomplete

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    New text describing the form added.

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 8.3.28

  • Key: IFML-10
  • Legacy Issue Number: 19157
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Issue: Parameters in parameterBinding must be characterized as input or output. (in text and metamodel)

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Fixed text and metamodel by characterizing parameters as input or output, through the attribute direction

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 8.3.24:

  • Key: IFML-8
  • Legacy Issue Number: 19155
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Section 8.3.24:
    Issue: Remove the following miselading sentence: Modules may be replaced by other InteractionFlowElements with the same input and output Parameters.

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Sentence removed

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 8.1.6

  • Key: IFML-7
  • Legacy Issue Number: 19154
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Section 8.1.6
    Issue: the URI attribute of ContentBinding must be optional

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    The affected Clause is 8.1.8, not 8.1.6.
    Added “optional” in the textual description and optionality in the metamodel diagram (figure 12).

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 8.1.7

  • Key: IFML-6
  • Legacy Issue Number: 19153
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Section 8.1.7
    Issue: "The Expression's context is any IFML element denoted by Element. The Expression values"- Rewrite.
    Solution: Replace with: "The values". And add: "ConditionalExpressions can be defined only inside a DataBinding ViewComponentPart."

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Text rephrased as below

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 8.3.27:

  • Key: IFML-9
  • Legacy Issue Number: 19156
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Issue: add description of behaviour of data flows related to navigation flows

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Issue actually applies to section 8.3.26. New text added, both in section 8.3.26 and also in 8.3.13 to make DataFlow description compatible with the new description

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 8.1.4:

  • Key: IFML-5
  • Legacy Issue Number: 19152
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Section 8.1.4:
    Issue: Rephrase unclear sentence: "This new window may be a modal blocking interaction in all other previously active containers"

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    sentence rephrased as below

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 6.4: acknowledgements

  • Key: IFML-4
  • Legacy Issue Number: 19151
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • Summary:

    Issue: authors list does not reflect contribution
    Solution: Put Brambilla, Fraternali first as main contributors

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    Applied suggestion. Added Andrea Mauri as further author as he contributed to the finalization work.

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Section 1: scope

  • Key: IFML-3
  • Legacy Issue Number: 19150
  • Status: closed  
  • Source: WebRatio Inc ( Marco Brambilla)
  • 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

  • Reported: IFML 1.0b1 — Mon, 9 Dec 2013 05:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    new text formulation, according to suggestion

  • Updated: Sat, 7 Mar 2015 01:07 GMT

Two of the XMI files use the XMI 2.1 namespace instead of XMI 2.4

  • Key: IFML-2
  • Legacy Issue Number: 18574
  • Status: closed  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    Two of the XMI files use the XMI 2.1 namespace instead of XMI 2.4

  • Reported: IFML 1.0b1 — Thu, 21 Mar 2013 04:00 GMT
  • Disposition: Resolved — IFML 1.0b2
  • Disposition Summary:

    XMI namespace version has been fixed to 2.4

  • Updated: Sat, 7 Mar 2015 01:07 GMT