SOPES 1.0 FTF Avatar
  1. OMG Issue

SOPES — Annex A - The Navigation Constraint example in diagram A.8 could benefit from further explanation

  • Key: SOPES-39
  • Legacy Issue Number: 15245
  • Status: closed  
  • Source: Advanced Systems Management Group Ltd. ( Michael Abramson)
  • Summary:

    The Navigation Constraint example in diagram A.8 could benefit from further explanation

  • Reported: SOPES 1.0b1 — Wed, 5 May 2010 04:00 GMT
  • Disposition: Resolved — SOPES 1.0
  • Disposition Summary:

    The clarification of the example Navigation Constraint in Figure A.8 is to be added in section A.1.7.6 . Though this concern was not specifically mentioned in discussion of issue SOPES-00026, it is included for clarification as SOPES-00041.

    Clarifications:

    For all instances of the constrained navigation the initial element 'self' is the enclosing Transactional,
    and in the case of the example from diagram A.8 self refers to ‘InformationTransactional_1’.

    The second element of the constraint is the Wrapper instance which must be a directly subtended element of the enclosing Transactional,
    and in this case the Wrapper instance is 'Wrapper_1'.

    The third element is the named Wrapper Attribute featured on the specified Wrapper,
    and in this case this element is 'catCode'.

    The final element is evaluated against the constraint, and in this case the value is 'domainValue'

  • Updated: Fri, 6 Mar 2015 23:15 GMT