Ontology

Ontology and Semantic Connectivity

Industrial semantic view for SI-schema: interface-centric modeling with explicit predicates for connectivity and signal behavior.

Ontology Visualization

1) UML view

classDiagram
    class Function {
      +id: string
      +name: string
      +component_id: ref
      +modes: string[]
      +input_signals: Signal[]
      +output_signals: Signal[]
      +parameters: Parameter[]
      +function_description: string
    }

    class Component {
      +id: string
      +name: string
      +modes: Mode[]
      +ports: Port[]
    }

    class Mode {
      +id: string
      +name: string
      +description: string
    }

    class Port {
      +id: string
      +direction: enum
      +port_type: enum
      +protocol: enum
    }

    class Connection {
      +id: string
      +from_port_ref: ref
      +to_port_ref: ref
      +connection_type: enum
      +signal: ref
    }

    class Signal {
      +id: string
      +name: string
      +signal_type: enum
      +category: enum
    }

    Function "many" --> "1" Component : component_id
    Component "1" *-- "many" Port : exposes
    Component "1" *-- "many" Mode : publishes
    Connection "many" --> "1" Port : from_port_ref
    Connection "many" --> "1" Port : to_port_ref
    Connection "many" --> "1" Signal : signal
    Port "many" --> "many" Signal : actUpon

2) RDF-style view

graph LR
  A[component.autopilot.port.DO01] -- connectedTo --> B[component.propulsion.port.cmd_in]
  B -- actUpon --> C[signal.engine_speed_cmd]
  C -- isActedUponBy --> B
  D[function.fn.rcs_vfd_start] -- component_id --> E[component.RCS]
  D -- modes[*] --> F[component_mode.remote]
  D -- modes[*] --> G[component_mode.power]

3) Ontology predicates

Relation	Domain	Range	Bound in schema	Intent
`connectedTo`	`Port`	`Port`	`connections[].from_port_ref`/`connections[].to_port_ref`	Connectivity edge between interface endpoints.
`actUpon`	`Port`	`Signal`	`Port.attributes.actUpon`	Port transmits, consumes, or processes the signal.
`isActedUponBy`	`Signal`	`Port`	derived inverse of `actUpon`	Read-only inverse view for tools and visualisation.

4) Schema bindings used with the ontology layer

Binding	From	To	Bound in schema	Intent
`component_id`	`Function`	`Component`	`Function.component_id`	Allocated component for the vendor-authored function.
`modes[*]`	`Function`	`Component Mode ID`	`Function.modes[*]`	Subset references to allowed canonical component modes.
`from_port_ref`	`Connection`	`Port`	`connections[*].from_port_ref`	Source endpoint of a connectivity edge.
`to_port_ref`	`Connection`	`Port`	`connections[*].to_port_ref`	Target endpoint of a connectivity edge.
`signal`	`Connection`	`Signal`	`connections[*].signal`	Single signal transmitted by this connection.

5) Schema-oriented examples

connection_ontology.yaml

YAML

connections:
  - id: conn.cmd_speed
    from_port_ref: component.autopilot.port.DO01
    to_port_ref: component.propulsion.port.cmd_in
    connection_type: control
    signal: engine_speed_cmd

port_ontology.yaml

YAML

port:
  id: component.propulsion.port.cmd_in
  direction: in
  port_type: analog
  protocol: 0-10V
  attributes:
    actUpon: signal.engine_speed_cmd
    terminal: X1-12
    sampling_interval_ms: 100

function_mode_binding.yaml

YAML

function:
  id: fn.rcs_vfd_start
  component_id: RCS
  modes:
    - remote
    - power
  function_description: |
    Remote start/stop arbitration profile for RCS to command VFD.