package uprotocol

Get desktop application:
View/edit binary Protocol Buffers messages

Service topic definition

Used in: core.udiscovery.v3.ServiceTopicInfo

• uint32 id = 1

  Topic id (0x8000 - 0xFFFF). The topic id **MUST** be unique within the containing service scope.

• string name = 2

  Topic name. The topic name **MUST** be unique within the containing service scope.

• string message = 3

  The topic message (defines the data passed in the topic). Both absolute and relative message names can be used, following the [Protobuf type name resolution rules](https://protobuf.dev/programming-guides/proto3/#name-resolution): 1. **Relative name:** partially-qualified name, resolved starting from the innermost scope to the outermost scope. 2. **Absolute name:** fully-qualified name with a leading `'.'`, resolved starting from the outermost scope instead. For example, with respect to a concrete service *foo.bar.Service*, the following topic message references are all equivalent: - *foo.bar.Topic* - *bar.Topic* - *Topic* <br> **_NOTE:_** If the topic message is defined in a separate proto file, then this proto file must be explicitly imported into the proto file in which it is referenced, otherwise the message reference will not be resolved.

• repeated string resources = 4

  One or more enumerated resource values that can be used to generate corresponding list of topics: <p>&emsp;&emsp;&emsp;[* resource_enum *] : [* resource_value *]</p> Both absolute and relative resource enum names can be used, following the [Protobuf type name resolution rules](https://protobuf.dev/programming-guides/proto3/#name-resolution). If the resource name is relative, it will be resolved relative to the topic message. The *resource_enum* part is optional, and if omitted will default to "Resources". For example, with respect to a concrete topic message *foo.bar.Topic*, the following topic resource references are all equivalent: - *foo.bar.Topic.Resources* : \* - *bar.Topic.Resources* : \* - *Topic.Resources* : \* - *Resources* : \* - \* <br> Topics can be defined automatically using the `"\*"` wildcard (e.g., `"Resources:*"`). This will create a separate topic per each resource instance, using the resource code/value to generate the topic id/uri. Topics with multiple resources can be defined using an array (e.g., `["front_left", "front_right"]`). The `"\*"` wildcard can also be used in this context (e.g., `["*"]`). This can be used to define a single topic that is triggered by a combination of multiple resources. **_NOTE:_** If a topic resource is defined in a separate proto file, then this proto file must be explicitly imported into the proto file in which it is referenced, otherwise the resource reference will not be resolved.

• optional uint32 permission_level = 5

  Code Access Permission (CAP) Level for the topic