Skip to content

Commit 2259aef

Browse files
committed
:
Signed-off-by: Adam Dabrowski <adam.dabrowski@robotec.ai>
1 parent d2eb026 commit 2259aef

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

rep.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -410,13 +410,13 @@ A canonical repository of open-source, compliant simulation assets is to be esta
410410

411411
## Rationale
412412

413-
- **Why OpenUSD?** This REP does not argue against any other formats. OpenUSD is useful for robotics due to:
413+
- **Why OpenUSD?:** This REP does not argue against any other formats. OpenUSD is useful for robotics due to:
414414
- Volume and quality of assets authored and a value such assets have for building robotic simulations.
415415
- Adoption and existing drive for the standard towards robotics.
416416
- Connection to a broad ecosystem and tooling.
417-
- **Extensions** A version of this REP with sensor and control schemas was considered, but the scale of dealing with all of these at once speaks against such an approach. Thus, the REP takes on a core + extensions model, following OpenUSD and glTF 2.0 practice.
418-
- **Scope limit** This REP does not regulate how simulation-level interfaces (such as `/clock` topic) are to be implemented, only that they are not a part of compliant assets. This scope limit is important so that diverse implementations of ROS communication in simulators can be supported.
419-
- **glTF** glTF 2.0 was selected as primary export pathway due to support in multiple ROS simulators, its complementary lightweight nature, and an ongoing development of the format in direction of robotics simulation.
417+
- **Extensions:** A version of this REP with sensor and control schemas was considered, but the scale of dealing with all of these at once speaks against such an approach. Thus, the REP takes on a core + extensions model, following OpenUSD and glTF 2.0 practice.
418+
- **Scope limit:** This REP does not regulate how simulation-level interfaces (such as `/clock` topic) are to be implemented, only that they are not a part of compliant assets. This scope limit is important so that diverse implementations of ROS communication in simulators can be supported.
419+
- **glTF:** glTF 2.0 was selected as primary export pathway due to support in multiple ROS simulators, its complementary lightweight nature, and an ongoing development of the format in direction of robotics simulation.
420420

421421
## How to Teach This
422422

0 commit comments

Comments
 (0)