Child pages
  • 2022-08-25 OIMT Meeting notes
Skip to end of metadata
Go to start of metadata





  • Admin (none)
  • Other TE examples
  • Document progress update
  • AOB

Discussion items








Action items completed

Action items discussed

Action items re-dated 

Re-dated according to the review plan. See the call plan below for the document review plan 

TE ExamplesChris

Chris summarized challenge with providing examples and requested that Nigel provides examples to test IncorporatedTe.

  • Nigel Davis Provide an example showing how IncorporatedTE is used to produce compound TE expressions within a TeElement with many IncorporatedTE and also how many IncorporatedTE can relate to a TemporalExpression.
  • Nigel Davis Add union/intersection roles to association names where possible.
  • Nigel Davis Add full description union/intersection behavior for all cases.

Document progress update

Nigel ran through the control task model work (which is being prepared to be included in TR-512.8).

The main discussion was on the diagram below which show the ControlTask terminology overlaid on the Component-System diagram. 

Nigel noted that the multiplicity at the System end of the SystemIsAssemblyOfComponents association is probably 1 not * for the ControlTask model and that the orientation of the association may be better reversed (a simple refactoring of the model) due to the purpose of the ControlTaskTransferFunction as a description of the ControlTask (exposing descriptive detail as opposed to emergent abstraction from an assembly). The same is true for the orientation of the SystemViewedAsComponent association. 

Chris noted that in general, for the component system pattern, it may be beneficial to use the occurrence pattern (sketched in green below) to help deal with the many-many complexity. Nigel agreed that this may be helpful and will explore this although it was agreed that this may not be necessary in the simpler form of the task model.

The PortBindsToPort association was explored briefly. Nigel explained the purpose of the portRole with respect to this association and used the analogy of broadcast for the ENVIRONMENT role. Nigel noted that this allowed for a task to be triggered by an unknown source (listening for an event) and for a task to provide output with no defined recipient. After some discussion it was agreed that there was a distinction of explicit binding v implicit binding. This aspect will be worked on more.

  • Nigel Davis Upload a new version of Task Model slides.

Nigel noted that the schedule for reviews had been updated to account for the missed meeting last week and current rate of progress.

0 minNext calls

Individual's vacation plan: MB (August 11-31; Sept 19-30), AM (August 15-19), KL (August 22-26; Sept 19-Oct 12) 

  • Meeting planning proposal (where each meeting will deal with the corresponding actions (with the date of the meeting)):
      • ControlTask document overview
      • Document progress update
      • ControlTask document overview
      • Spec document draft overview
      • Equipment discussion/resolution and preparation for delivery of document
      • Validate progress and plan model and documentation development
        • Review all relevant minutes/action resolution and draft document progress against plan including
          • Streaming (T65)
          • Task (T57)
          • Temporal (T73)
          • Spec (T56)
          • OAM (T5)
          • Views/Context (11b)
          • Media multipoint addition to .A.4 (T77)
          • Equipment (T8a) (??)
          • Aggregate (T64b)
        • Consider progress on and plan for delivery of
          • Compute and storage (T36)
        • Construct detailed action plan for delivery on target date  
  • At each meeting we should check that we are on track for the planned items

Future calls agenda items for consideration

  • TIP/MUST papers (CH, ND)
  • Catalog / inventory storage application (CH, ND)
  • IETF work on physical inventory model (ND)
  • RBAC vs ABAC (June 2021 F2F meeting Tue 1.2 ) 
  • To recap the previous OIMT discussion on synchronization management IM (later call)
  • YANG augmenting 
  • Leo on location model