PipingConnection¶

Overview¶

Abstract class

An elementary connection between two piping items.

Subtypes

Attributes (reference)

Name	Multiplicity	Type
SourceItem	0..1	PipingSourceItem
SourceNode	0..1	PipingNode
TargetItem	0..1	PipingTargetItem
TargetNode	0..1	PipingNode

Implementation in Proteus Schema

Implementation is subclass-specific.

Example

As PipingConnection is abstract, we consider Pipe as an arbitrary concrete subclass.

Implementation in Proteus Schema

<PipingNetworkSegment
    ID="pipingNetworkSegment1"
    ComponentClass="PipingNetworkSegment"
    ComponentClassURI="http://data.posccaesar.org/rdl/RDS267704">
  ...
  <!--
    Only  a <CenterLine> whose parent is a <PipingNetworkSegment>
    implements a DEXPI Pipe.
  -->
  <CenterLine ...>
    ...
  </CenterLine>
  ...
</PipingNetworkSegment>

SourceItem¶

Attribute (reference)

The PipingSourceItem at which the PipingConnection starts.

Multiplicity: 0..1

Type: PipingSourceItem

Opposite multiplicity: 0..1

Implementation in Proteus Schema

Implementation is subclass-specific.

SourceNode¶

Attribute (reference)

The PipingNode at which the PipingConnection starts. The SourceNode must belong to the SourceItem.

Multiplicity: 0..1

Type: PipingNode

Opposite multiplicity: 0..1

Implementation in Proteus Schema

Implementation is subclass-specific.

TargetItem¶

Attribute (reference)

The PipingTargetItem at which the PipingConnection starts.

Multiplicity: 0..1

Type: PipingTargetItem

Opposite multiplicity: 0..1

Implementation in Proteus Schema

Implementation is subclass-specific.

TargetNode¶

Attribute (reference)

The PipingNode at which the PipingConnection ends. The TargetNode must belong to the TargetItem.

Multiplicity: 0..1

Type: PipingNode

Opposite multiplicity: 0..1

Implementation in Proteus Schema

Implementation is subclass-specific.