Child pages
  • IISOMI Work Items

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Area/Topic

  • UML Modeling   
    • Continuation of Associations Discussion (Nigel Davis)
      • Importancy=M and Urgency=M
      • Composition/strictComposite/extendComposite and Association class and multiplicity in abstraction
     
    • MEF MCM – ONF Core Model Alignment (Nigel Davis)
      • Importancy=HH and Urgency=H
     
    • Use of Stereotypes (See 2019-02-20 IISOMI Meeting notes for the decision)
      • In general we should not use stereotypes where user-defined data-types could be used 
      • BitLength (We will not use bitLength stereotype property anymore. Need to be deprecated. Will use a combination of multiplicity and OCL for this purpose.)
  • UML to YANG Mapping 
    • Object Reference Mapping (use of xPath “current()” function) (All)
      • Importancy=M/L and Urgency=L
     
    • Mapping of Abstraction / <specify> relationship of operation (Karthik Sethuraman)
      • Importancy=H and Urgency=H
     
    • Mapping of complex Data Types
      • Mapping to "typedef" statement
     
    • Use of “when” and “must” statements (Karthik SethuramanScott Mansfield)
      • Importancy=H and Urgency=H
      • This is needed for TAPI 2.2
      • Related to translation of <cond>, conditional Pac, 
      • Need to bring Rob Wilton into the discussion (Scott Mansfield's action)
     
    • IETF MW Test Model (Martin Skorupski)
      • Importancy=L and Urgency=L
      • About alignment between the IETF and ONF models
      • I#249
  • Tools  
    • Yang2Uml Mapping Tool updates
      • Importancy=M and Urgency=L
     
    • Use of continuously updated Eclipse/Papyrus versions (Nigel DavisScott Mansfield)
      • From previous (old) minutes documenting earlier decisions that may no longer hold etc.
        • Moving to Photon: Importancy=H and Urgency=H
        • Karthik has been closely using the latest versions, no serious problem in that.
        • Karthik suggest we need to move to the Photon version
        • The TR-512 core model will move to Photon in v1.4.1
        • SG15 will move to Photon in the next version of the models too
     
    • Style template (See
     
    • 2019-02-20 IISOMI Meeting notes)
      • Not to have a universal stylesheet. Every papyrus project should package and auto-apply the stylesheets used by that project.
      • Most of the issues with transferring diagrams between projects could be solved by turning off auto-resizing of class boxes.
     
    • Tool Chains (Augie)