Stovepipes are incredibly effective constructs for isolating information and routing to another location without, necessarily, preserving the context. When used in software and systems integration, stovepipes are an effective way to create (and sustain) vendor-lock, or, the sole-reliance on a single vendor for all future changes.
Industry has attempted to eliminate vendor-lock by creating well-defined standards that allow for integration via commonality. This works reasonably well as long as there are common things to be defined. However, vendors often want to obscure proprietary data or optimize their implementations.
These factors work against a common, standardized definition. As a result, while open is goal, stovepipe is the unintended result.
The mission of Open Stovepipe is to:
actively hope that this standard is never implemented,
to publish a "15th standard," and
champion a better way of integrating.