BACM 1.2b1 RTF Avatar
  1. OMG Issue

BACM12 — Reconsider the packaging and namespace conventions

  • Key: BACM12-1
  • Status: closed  
  • Source: Thematix Partners LLC ( Mr. James Rhyne)
  • Summary:

    The justification for namespaces is to permit parts of the model to be used independently. The current packaging is close, but crossmaps between value stream and capability are defined in Capability and crossmaps between ValueItem and Outcome are defined in Customer. Customer mixes together Journeys and Value Streams. Consider repackaging to eliminate crossmaps from the core packages and add new packages with just the crossmaps. This would also benefit use of the OWL as a group of ontologies instead of one large one.

  • Reported: BACM 1.0b2 — Tue, 28 Nov 2023 22:21 GMT
  • Disposition: Deferred — BACM 1.2b1
  • Disposition Summary:

    Lack of time and resources to create a proposal

    Other issues were judged to be more important than this one. There does not appear to be either time or resources to create a meaningful proposal prior to the end of the RTF.

  • Updated: Thu, 17 Sep 2026 01:13 GMT