1. Pages
2. …
3. OIMT
4. Core Model
5. OIMT minutes
6. 2021 OIMT Minutes

2021-03-04 OIMT Meeting notes

• From March 11, OIMT call will resume the normal IM-D time, i.e., 0300-0400 Pacific Time 
• Daylight Saving Time
  • DST USA will start next Sunday 14th March
  • See https://www.timeanddate.com/time/dst/2021a.html for other location

TR-512.17 Foundation (State) has been created. It 

• took the version of TR-512.3 Foundation (Identifiers, naming and state) that we worked on in last year as the base,
• removed the part of Identifiers and naming.
• accepted most of the comments
• some comments/notes have been added

Main changes/notes

• 3.1.2.2 LifecycleState
  • "plan" could be in different stages, e.g, tentative, firm, committed; need discussion. 
  • pending removal → pending withdrawal
  • potential not installed  → potential planned

Keep LifecycleState as a flat Enumeration, not to create substate

Will update the figures to align with the changes in the Enumeration.

It will be posted as oimt2021.MB.001-draft-TR-512.17 for discussion next week.

Nigel noted the off-line discussion on Leo's comments and propsoal

• May pull properties back to the Equipment class from the grouping classes
• May refactor the model for practical reason
• The core model is not intended to be implemented as it is. It is intended as the source of attributes and structure that would then be refactored - lightly or heavily, for implementation. Like TAPI.
• The core model is for representation of information exchanged across interfaces, not to represent information stored in device. It doesn't dictate the internal model. 
• CH: Will present the principles next week.
• LN: In a particular API (e.g., JSON), might prefer to have the equipment type attribute of equipment be an UUID so that to avoid repeating the equipment type information in each equipment instance.
• CH: Will need to have equipment type library
• CH: Should revisit the physical model to clear up, in particular the Spec.
• ND: Not just instance data in the Spec, it includes type and instance
• LN: The spec model needs detailing, avoid repicating information of other instance.
• CH: Need to clarify the backbone model, options, decoration, augmentation, ...
• On the spec model, step back, start from simple, take equipment to rework on