# DataSet and Communication Channel Association

The diagram below provides a very generic overview of the responsibilities that must be implemented by the UA Application:

![Architecture](/files/-LEUl4qlO0VcaVtFggff)

* `UA Data Networking` - represents a software exchanging the data using protocol compliant with the [UA Part 14 Pub/Sub](/ooi/reactive-communication/readme.pubsubmtf.md) and binding the data with the underlying process.
* `MessageHandler` - represents a selected transport protocol supporting unsolicited data distribution or a middle-ware supporting publication/subscription message exchange communication pattern.
* `DataSet` - represents a preselected collection of process data items transmitted by the `MessageHandler` as one whole and information required to bind with the underlying process.
* `MessageReader` - captures functionality necessary to filter out unwanted messages and decode the data according to provided meta-data
* `MessageWriter` - captures functionality necessary to address the message (provide globally unique identifier) and encode the data using provided meta-data
* `Association` - provides:
  1. one to one association between an entity instance derived from `MessageHandler` and `DataSet`
  2. required addressing information as the `PublisherId`/`DataSetWriterId` couple
  3. meta-data information used to encode/decode the process data into the messages


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://commsvr.gitbook.io/ooi/reactive-communication/semanticdata/readmedatadiscoveryandbinding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.