#658 new todo

representation of an OutputDesignation claim

Reported by: Ichthyostega Owned by: Ichthyostega
Priority: normal Milestone: 0integration
Component: lumieraSteam Keywords: session design
Sub Tickets: #647, #657 Parent Tickets: #652, #671

Description

Decide on the proper representation (and possibly code it up).

It is clear by now that, in order for a (global) pipe actually to appear as part of the model, two conditions need to be met

  • the pipe gets mentioned somewhere as an OutputDesignation (typically this happens in the form of a plug within some placement)
  • an object actually claims to root this pipe (typically this should be a child of a BindingMO, i.e. directly within a "timeline")

We need to clarify what this claim is, how it works and how its actually to be represented in the model data.

Change history (2)

comment:1 by Ichthyostega, at 2010-10-02T14:52:30Z

blocking: 652652, 671

comment:2 by Undercover Agent, at 2025-12-25T00:00:00Z

blockedby: 647, 657
blocking: 652, 671
Parent Tickets: 652, 671
Sub Tickets: 647, 657
Note: See TracTickets for help on using tickets.