# ros-lyrical-type-description-interfaces

**Repository Path**: openkylin/ros-lyrical-type-description-interfaces

## Basic Information

- **Project Name**: ros-lyrical-type-description-interfaces
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: openkylin/huanghe
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2026-10-12
- **Last Updated**: 2026-10-15

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# type_description_interfaces

A package containing message and service definitions for describing and communicating descriptions of other types.

## Messages (.msg)

* [Field](msg/Field.msg): Represents a single field in a ROS Interface Type
* [FieldType](msg/FieldType.msg): Represents the type of a single field in a ROS Interface Type
* [IndividualTypeDescription](msg/IndividualTypeDescription.msg): Represents a single ROS Message Type by itself
* [TypeDescription](msg/TypeDescription.msg): Represents a single ROS Message Type along with all referenced types

## Quality Declaration

See the [Quality Declaration](QUALITY_DECLARATION.md) for more details.

## TODO

* Should we pick limits (bounds) for strings in these types, e.g. type names, default values, etc?
* Should we pick limits (bounds) for sequences in these types, e.g. number of referenced types?
* Consider how to support constants and annotations (currently excluded) and potentially enums in the future.
* Consider using padding in `IndividualTypeDescription.msg` to support back porting efforts.