Adrian Macneil

Related / possible duplicate of https://github.com/foxglove/rosmsg-msgs-common/issues/2

I guess in my mind the message encoding _is_ the mime type, rather than the message encoding being `mime`. The message encoding should tell you what format the binary data...

Yeah - it's probably not clear from the current set of recommended channel/schema encodings, but schemas are intended to be optional. For self-describing messages like json or jpeg there is...

I'm in favor of just dropping the `mime:` / `media:` prefix, and specifying in the spec that implementations should interpret any unknown message encoding as a media type. I think...

They would treat it like an unknown type, same as they do today. If you want to be more specific, we could say that any message encoding containing a `/`...

> I thought x- wasn't a thing anymore 😅 https://www.rfc-editor.org/rfc/rfc6648.html It seems like their answer is `x-` is no longer necessary because we made the registration process easier. So if...

Would it be worth adding to our spec appendix that well known media types are explicitly allowed in the message encoding field? E.g. `image/jpeg` seems like a no-brainer to me....

Are you on windows? The colons `:` are the issue. I have [several open PRs](https://github.com/cruise-automation/webviz/pulls/amacneil) to fix cloning and building this repo on windows. [This commit](https://github.com/foxglove/webviz/commit/dfd069d0fb490e4d7882c53b6fe4e624e86832f8) fixes the migration file...

What format(s) are your data currently in?

This is something we've been thinking about for [foxglove/studio](https://github.com/foxglove/studio) (fork of webviz). We really want to add support for non ROS formats. However, it would really help to understand more...