Message Element Interoperability Concerns

[dlemire60]

Currently the definition of message elements in Table 3-1 only limits the format of From, To, and Message_ID to "string". Failing to define a more specific format for those message elements will almost certainly lead to compatibility / interoperability issues among different implementations of OpenC2 messaging.

(source: HII software team)

[dlemire60]

Discussed at 8/10 working meeting. @davaya clarified that the message tables in the LS define content needed but are not format definitions, since the manifestation of the header content may or may not be handled using protocol features, as specified in a transfer specification. @TobyConsidine reminded the group of the previous debates about the most concise possible message, with reliance on transfer protocol features, vs. an atomic, strongly-typed message structure that would of necessity be larger, and stated he doesn't think we've done anything "to resolve strong message typing vs. parsimonious transmission". Issue deferred to the future.