Meetings 2012-02-02

RST Release Management

Type Consolidation

Component-specific (non-domain) Data Types

  • How can these be retrieved?
  • Mandatory installation to file system?
  • Other serialization formats than protobuf?

Meeting Planning

  1. Collect additional topics
  2. Determine topic priorities
  3. Roughly assign to meeting slots (~ short-term, mid-term, long-term)


Type Consolidation

  • Add versioning to rst library
  • Add library (simlink) with protobuf version encoded
  • Lists
    • Naming: HeadObject*List* instead of HeadObject*s*
    • No lists in RST, handle it on middleware layer
  • Open topics:
    • Coordinate systems
    • Units
    • Use type definitions for different serialization methods


  • rst/audition/ITD.proto: filename should be full name, not abbreviation (#848)
  • Express units right inside the proto file
    • For first release, check, that units are documented in every proto file
    • For next release, check how to express units (enum?)
  • For geometry/pointcloud types, we should check compliance with PCL
  • For next release: Overwork image type (check ivimage)


  • Ingo cleans up States/StateTransitions in TaskState
  • How to handle platform-specific types
    • Extend generic type (is that feasible with protobuf?)
  • VICON type needs cleanup (e.g. redundant orientations)
    • Should use rst/stable types (translation/orientation/pose)
  • geometry/PointPair into 2DPointPair and 3DPointPair
  • Timestamp lacks specification

sandbox -> stable

  1. TaskState
  2. geometry/*
  3. XOPData (Change package rst.rsb.xml -> rst.xml)
  4. timing/timestamp (after specification)