Create a basic demo, and perhaps some standards, around enabling semantic information in the map yaml to label places:

• point and size,
• pixels,
• polygons
• others?

With info like:

• name string
• class type
• geometric information
• other properties?

Then capabilities to load that information, and some capabilities enabled on top of it.

Ex:

• navigate to a label (go to dishwasher)
• avoid a label (stay out of conference room)
• get distance to label (are you within 10ft of the front door?)
• where are you (in the Steve’s cubicle)

As such I propose we discuss the following, in this order

• File formats for points, lines, and areas: YAML, XML, OSM-XML, or other
• What we want out of masks and how to embed that information: pgm/png, XML, or other
• A couple potential designs for multi-floor mapping to come to the consensus on how it makes most sense to represent the multiple maps and the "gateways" between them. The goal of this will be only to determine if the multi-map work is a consumer of this semantic work, or a direct member of it needing to be fully designed in tandem.
• A couple of potential designs around using the major classes of objects: point, area, mask (e.g. dock or waypoint or elevator; zoom or section; speed or keepout) to motivate the design of tools or servers required for this development.
• Tools: server to read like map server, services to get all or some of the semantic information, wrappers for calling to get it and parsing the result for the specific objects it wants, IO tools.
• Once we have some pretty good understandings of how we want the data formatted and how we want them to be used, we can then discuss the GUI element of this. Though I think we're all in agreement here.