Child pages
  • 2022-01-20 OIMT Meeting notes

Versions Compared


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






2 minAdminAll

Core Info Model github

  • The Papyrus files have been downloaded, loaded to PC, and checked. Looks fine.
  • created.

OIMT 2022 Vitrual F2F in 2022. 

10 minAction itemsAll


Actions completed

Re-dated items

The following are proposed dates for the past actions. The action list has been updated to reflect this. The actions can be reverted/adjusted as necessary. Only actions that have been moved are listed.

Note that now provided in the bullet under each action item is the link to the source minutes that created the action item.

  •  Nigel Davis   Discuss the intent grammar, spec grammar. Explore mechanism converting explicit property sentence into constraint statements.
  •  Nigel Davis   Discuss with the TAPI and Wireless transport: Moving away from simple packaging, e.g., object class, datatype, to a much deeper structure. This will not work with the uml2yang tool. Therefore the model will need to be refactored into object/datatype for uml2yang tool.
 minTemporal expressionCH & ND

Updates on Temporal Expression discussion and refactored model

  • CH T73
    • Slides 9, 10, 11, created 12 (Decarator -2)
        • ND: Public holidays
        • ND: Lunch hour closure
  • ND:
    • Radical refactoring, No subclassing, just simple composition, with natural union and intersection. This is work in progress.
    • In PhasingTe, the Real (1) should be Real (0..1)
    • ND to post the diagram as ppt prior to next weeks call (after correcting several errors spotted as the overview was provided and completing the model)

  •  Nigel Davis Create temporal examples and check how the updated refactored temporal model can fit
  minEquipment model KL, ND

Equipment spec model and modeling of equipment properties 


  • Need to define the model patterns. Multiple patterns, such as up/low thresholds, water marks, guages, (e.g., those defined in ITU-T G.7710).
  •  Aim to have the pattern available to any property. 
  • Then to use the Spec model to apply that partten for a particular property into a object class. 
  • In the case of Equipment, there are the physical properties. Such as temporature: thresholding, controlling, monitoring, measuring, reporting, 
  • For control, there could be a number control strategies to choose from. Once one is chosen, it will then dictate the structure of the attribute properties and also the name.
  • For measure, there could be a number measurement strategies. E.g., high warning threshold, high fail threshold, low warning threshold, low fail threshold, ...
    • Then apply the threshold strategy to a property, temperature say.
  • Property names, Threshold strategy names, 
  • Need name consistency
  • Vision: Tooling support
  • The Equipment spec defines what equipment has which property, measurement capability, ...; brings together the patterns.
  • The properties need to be modulated. Enable per type augment.
  • Next step: try manually.

 minAggregrate stererotype ND

Experiment with application of the aggregate stereotype to the core model.

  • Casc: 3 types
  • missing LpSignalesCasc
  • To post PNG diagram
 minTAPI and Wireless transportND, AM, MS


 minIntent/Spec grammarND


 2 minNext calls


  • Temporal expression model and examples and document (ND)
  • Equipment property model (KL, ND)
  • TAPI and Wireless transport: Moving away from simple packaging (ND, AM, MS)
  • Discuss the intent grammar, spec grammar. Explore mechanism converting explicit property sentence into constraint statements. (ND) 
  • Example for separate occurrence (as per action item) (ND)

Future calls agenda items

  • TIP/MUST papers (CH, ND)
  • Catalog / inventory storage application (CH, ND)
  • MEF W130 device physical & environmental specification. OIMT may need to engage MEF on that. (CH)
  • IETF work on physical inventory model (ND)
  • RBAC vs ABAC (June 2021 F2F meeting Tue 1.2 ) 
  • Finalize the write up on Multi-point Media Channel (later call) (Candidate for v1.6)
  • To recap the previous OIMT discussion on synchronization management IM (later call)
  • YANG augmenting 
  • Leo on location model