Should we introduce a domain-reference object?

[rocketstack-matt]

The 2024-08 draft introduces a domain model.

• The design allows new domains to be defined, as can be seen in the control-specification example.
• We then declare instances of a domain, as can be seen in the control-instance example.
• Domain instances can then be specified in CALM instance documents either at either the architecture (document), node or relationship level, as can be seen with the cbom example in one-node-wonder

e.g.

"domains": {
        "cbom": [
          {
            "unique-id": "ci-arch-001",
            "description": "Evidence of Pre Production Review",
            "requirement-schema": "control-specification.json",
            "requirement-instance": "control-instance.json",
            "evidence": [
              {
                "evidence-link": "https://evidence.com/12345",
                "evidence-id": "12345"
              }
            ]
          }
        ]
      }

The implementation requires the author to specify the domain specification a specific domain should adhere to and the instance being referenced, but we also duplicate the unique-id and description. Could we reduce duplication and make the document more readable by creating a new domain-reference object (open to different names) which would be the schema/instance and evidence container rather than referencing the domains themselves?

Tag: @jpgough-ms, @willosborne