@cda/adapter-xma 0.1.0 → 0.3.0

package/README.md

@@ -88,7 +88,7 @@ interface XmaSerializeOptions {
 
 This is **initial, evidence-backed XMA serialization support** — not a
 complete, universal XMA converter. Everything below was confirmed against
-two reference `.archimate`/`.xma` fixture pairs (see
+four reference `.archimate`/`.xma` fixture pairs (see
 [`tests/fixtures/README.md`](tests/fixtures/README.md)); nothing here is
 extrapolated beyond that evidence.
 
@@ -98,13 +98,28 @@ extrapolated beyond that evidence.
   Application, Technology, Physical, Motivation, Implementation & Migration,
   Composite), with confirmed scheme/collection placement and default icon
   decoration presence.
+- `Junction`/`OrJunction` — a root-level `Connectors` container, confirmed
+  distinct graphical form (no fill/line color, `mm_graphicType="3"`). See
+  `tests/fixtures/README.md`.
 - Element and view names, and documentation (as RTF profile values).
-- A single ArchiMate view per model: node geometry (exact ×3 scale),
-  default per-category fill colors, line color, opacity, and font.
+- **Multiple ArchiMate views per model** (up from exactly one) — each gets
+  its own `GraphicalModule`, all nesting under one shared `AbstractViews`
+  container. Confirmed against 38-view and 3-view real-world fixtures. Node
+  geometry (exact ×3 scale), default per-category fill colors, line color,
+  opacity, and font are unaffected by view count.
 - Notes and Groups (as `ArchiMate:ViewGraphic`), including Group
   documentation.
-- Three confirmed semantic relationship mappings and their graphical
-  representation:
+- **90 confirmed exact-triple semantic relationship mappings** (up from 3),
+  spanning all eight schemes, plus **3 confirmed generic (type-independent)
+  forms** — `AssociationRelationship`, a `Grouping` endpoint (Composition,
+  Specialization, Influence, Use), and a `Junction`/`OrJunction` endpoint
+  (Realisation, Influence) — see `src/mapping/relationship-mapping.ts` and
+  `src/mapping/generic-relationship-mapping.ts` for the tables, and
+  `tests/fixtures/README.md` for how each was derived and verified. The
+  original 3 exact-triple mappings additionally have their graphical
+  `MM_DirectedRel` representation confirmed end-to-end; the rest were
+  confirmed at the semantic layer only (the same generic serializer code
+  path, not independently fixture-checked for the graphical layer):
   - `AssignmentRelationship` `BusinessActor` → `BusinessProcess`
   - `ServingRelationship` `ApplicationService` → `BusinessProcess` (XMA
     calls this `...Use`, not `...Serving`)
@@ -119,12 +134,21 @@ extrapolated beyond that evidence.
 
 ### Not yet guaranteed
 
-- Relationship type/source/target combinations beyond the three confirmed
-  above (reported as a diagnostic, not silently dropped or guessed).
-- More than one view per model (reported as a diagnostic).
+- Relationship type/source/target combinations beyond the 90 confirmed exact
+  triples and the 3 confirmed generic forms (reported as a diagnostic, not
+  silently dropped or guessed) — e.g. a `Grouping`/`Junction` endpoint paired
+  with a verb outside the confirmed set for that endpoint kind.
+- A handful of concrete types that collapse to a coarser XMA category
+  specifically for relationship naming, distinct from their own element
+  mapping — confirmed and implemented for `TechnologyCollaboration` →
+  `TechnologyNode`, `BusinessCollaboration` → `BusinessRole`, and
+  `SystemSoftware` → `TechnologyNode`. `Constraint` → `MotivationRequirement`
+  remains circumstantial (one otherwise-unexplained count mismatch, no
+  direct confirmation) and is **not** implemented. See "Generic and
+  collapsed forms" in [`tests/fixtures/README.md`](tests/fixtures/README.md).
 - Nested diagram objects, `DiagramModelReference` ("insert view as
   reference"), and purely visual (non-semantic) connections.
-- Junctions, profiles/specializations, and arbitrary model properties.
+- Profiles/specializations and arbitrary model properties.
 - Explicit font size, bold/italic, line width, font color, or connector
   line color overrides (reported as diagnostics; the confirmed defaults are
   used instead).
@@ -152,7 +176,8 @@ src/
 
   mapping/                    immutable mapping DATA (never switch statements)
     element-mapping.ts           60 confirmed Archi type -> XMA type/scheme/collection
-    relationship-mapping.ts      3 confirmed (type, source, target) -> XMA relationship
+    relationship-mapping.ts      90 confirmed (type, source, target) -> XMA relationship
+    generic-relationship-mapping.ts  3 confirmed type-independent forms (Association, Grouping, Junction)
     scheme-mapping.ts            scheme container / folder-nesting metadata
     visual-mapping.ts            default fill/line colors, font, opacity
 

package/dist/mapping/generic-relationship-mapping.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Generic (type-independent) relationship forms — confirmed to exist, but
+ * structurally different from `relationship-mapping.ts`'s exact-triple
+ * table: these apply *regardless* of the concrete source/target type, not
+ * for one specific pair. See `tests/fixtures/README.md` for the full
+ * derivation evidence.
+ *
+ * All three forms serialize into the root-level `<ArchiMate:Relations>`
+ * container (a sibling of `AbstractSchemes` under `ArchiMateComponent`),
+ * never inside a layer scheme — confirmed directly in both fixtures
+ * (`sabsa.xma`, `agile-manifesto.xma`): every generic-form relation appears
+ * there, never nested in `BusinessScheme`/`ApplicationScheme`/etc.
+ */
+export interface GenericRelationshipMapping {
+    xmaType: string;
+}
+export declare function lookupGenericRelationshipMapping(archiRelationshipType: string, sourceArchiType: string, targetArchiType: string): GenericRelationshipMapping | undefined;
+//# sourceMappingURL=generic-relationship-mapping.d.ts.map

package/dist/mapping/generic-relationship-mapping.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"generic-relationship-mapping.d.ts","sourceRoot":"","sources":["../../src/mapping/generic-relationship-mapping.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAkCH,MAAM,WAAW,0BAA0B;IACzC,OAAO,EAAE,MAAM,CAAC;CACjB;AAED,wBAAgB,gCAAgC,CAC9C,qBAAqB,EAAE,MAAM,EAC7B,eAAe,EAAE,MAAM,EACvB,eAAe,EAAE,MAAM,GACtB,0BAA0B,GAAG,SAAS,CA4BxC"}

package/dist/mapping/generic-relationship-mapping.js

@@ -0,0 +1,68 @@
+/**
+ * Generic (type-independent) relationship forms — confirmed to exist, but
+ * structurally different from `relationship-mapping.ts`'s exact-triple
+ * table: these apply *regardless* of the concrete source/target type, not
+ * for one specific pair. See `tests/fixtures/README.md` for the full
+ * derivation evidence.
+ *
+ * All three forms serialize into the root-level `<ArchiMate:Relations>`
+ * container (a sibling of `AbstractSchemes` under `ArchiMateComponent`),
+ * never inside a layer scheme — confirmed directly in both fixtures
+ * (`sabsa.xma`, `agile-manifesto.xma`): every generic-form relation appears
+ * there, never nested in `BusinessScheme`/`ApplicationScheme`/etc.
+ */
+/** Archi relationship type -> its confirmed "verb" suffix (see relationship-mapping.ts). */
+const VERB_BY_ARCHI_TYPE = {
+    AssignmentRelationship: 'Assignment',
+    AccessRelationship: 'Access',
+    RealizationRelationship: 'Realisation',
+    FlowRelationship: 'Flow',
+    TriggeringRelationship: 'Triggering',
+    InfluenceRelationship: 'Influence',
+    SpecializationRelationship: 'Specialization',
+    CompositionRelationship: 'Composition',
+    ServingRelationship: 'Use',
+};
+/**
+ * Verbs confirmed (directly, not inferred) to produce the generic
+ * `{Verb}Relation` form when a `Junction`/`OrJunction` is an endpoint:
+ * `RealizationRelationship` (`RealisationRelation`, sabsa + agile-manifesto)
+ * and `InfluenceRelationship` (`InfluenceRelation`, agile-manifesto). Not
+ * extended to other verbs without fixture evidence for that specific verb —
+ * a relationship type absent from this set is still reported unsupported.
+ */
+const JUNCTION_CONFIRMED_VERBS = new Set(['Realisation', 'Influence']);
+/**
+ * Verbs confirmed to produce the `{Grouping|Element}{Grouping|Element}{Verb}`
+ * generic form when a `Grouping` is an endpoint (sabsa + agile-manifesto):
+ * `CompositionRelationship`, `SpecializationRelationship`,
+ * `InfluenceRelationship`, `ServingRelationship`. Same "no evidence, no
+ * guess" rule as Junction above.
+ */
+const GROUPING_CONFIRMED_VERBS = new Set(['Composition', 'Specialization', 'Influence', 'Use']);
+export function lookupGenericRelationshipMapping(archiRelationshipType, sourceArchiType, targetArchiType) {
+    // Confirmed universal: every AssociationRelationship instance across dozens of
+    // distinct source/target type pairs (sabsa + agile-manifesto) serializes as this
+    // one generic tag — never a type-specific one.
+    if (archiRelationshipType === 'AssociationRelationship') {
+        return { xmaType: 'ElementElementAssociation' };
+    }
+    const verb = VERB_BY_ARCHI_TYPE[archiRelationshipType];
+    if (!verb) {
+        return undefined;
+    }
+    const sourceIsJunction = sourceArchiType === 'Junction';
+    const targetIsJunction = targetArchiType === 'Junction';
+    if ((sourceIsJunction || targetIsJunction) && JUNCTION_CONFIRMED_VERBS.has(verb)) {
+        return { xmaType: `${verb}Relation` };
+    }
+    const sourceIsGrouping = sourceArchiType === 'Grouping';
+    const targetIsGrouping = targetArchiType === 'Grouping';
+    if ((sourceIsGrouping || targetIsGrouping) && GROUPING_CONFIRMED_VERBS.has(verb)) {
+        const sourcePart = sourceIsGrouping ? 'Grouping' : 'Element';
+        const targetPart = targetIsGrouping ? 'Grouping' : 'Element';
+        return { xmaType: `${sourcePart}${targetPart}${verb}` };
+    }
+    return undefined;
+}
+//# sourceMappingURL=generic-relationship-mapping.js.map

package/dist/mapping/generic-relationship-mapping.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"generic-relationship-mapping.js","sourceRoot":"","sources":["../../src/mapping/generic-relationship-mapping.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;GAYG;AAEH,4FAA4F;AAC5F,MAAM,kBAAkB,GAAqC;IAC3D,sBAAsB,EAAE,YAAY;IACpC,kBAAkB,EAAE,QAAQ;IAC5B,uBAAuB,EAAE,aAAa;IACtC,gBAAgB,EAAE,MAAM;IACxB,sBAAsB,EAAE,YAAY;IACpC,qBAAqB,EAAE,WAAW;IAClC,0BAA0B,EAAE,gBAAgB;IAC5C,uBAAuB,EAAE,aAAa;IACtC,mBAAmB,EAAE,KAAK;CAC3B,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,wBAAwB,GAAG,IAAI,GAAG,CAAC,CAAC,aAAa,EAAE,WAAW,CAAC,CAAC,CAAC;AAEvE;;;;;;GAMG;AACH,MAAM,wBAAwB,GAAG,IAAI,GAAG,CAAC,CAAC,aAAa,EAAE,gBAAgB,EAAE,WAAW,EAAE,KAAK,CAAC,CAAC,CAAC;AAMhG,MAAM,UAAU,gCAAgC,CAC9C,qBAA6B,EAC7B,eAAuB,EACvB,eAAuB;IAEvB,+EAA+E;IAC/E,iFAAiF;IACjF,+CAA+C;IAC/C,IAAI,qBAAqB,KAAK,yBAAyB,EAAE,CAAC;QACxD,OAAO,EAAE,OAAO,EAAE,2BAA2B,EAAE,CAAC;IAClD,CAAC;IAED,MAAM,IAAI,GAAG,kBAAkB,CAAC,qBAAqB,CAAC,CAAC;IACvD,IAAI,CAAC,IAAI,EAAE,CAAC;QACV,OAAO,SAAS,CAAC;IACnB,CAAC;IAED,MAAM,gBAAgB,GAAG,eAAe,KAAK,UAAU,CAAC;IACxD,MAAM,gBAAgB,GAAG,eAAe,KAAK,UAAU,CAAC;IACxD,IAAI,CAAC,gBAAgB,IAAI,gBAAgB,CAAC,IAAI,wBAAwB,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC;QACjF,OAAO,EAAE,OAAO,EAAE,GAAG,IAAI,UAAU,EAAE,CAAC;IACxC,CAAC;IAED,MAAM,gBAAgB,GAAG,eAAe,KAAK,UAAU,CAAC;IACxD,MAAM,gBAAgB,GAAG,eAAe,KAAK,UAAU,CAAC;IACxD,IAAI,CAAC,gBAAgB,IAAI,gBAAgB,CAAC,IAAI,wBAAwB,CAAC,GAAG,CAAC,IAAI,CAAC,EAAE,CAAC;QACjF,MAAM,UAAU,GAAG,gBAAgB,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,SAAS,CAAC;QAC7D,MAAM,UAAU,GAAG,gBAAgB,CAAC,CAAC,CAAC,UAAU,CAAC,CAAC,CAAC,SAAS,CAAC;QAC7D,OAAO,EAAE,OAAO,EAAE,GAAG,UAAU,GAAG,UAAU,GAAG,IAAI,EAAE,EAAE,CAAC;IAC1D,CAAC;IAED,OAAO,SAAS,CAAC;AACnB,CAAC"}

package/dist/mapping/relationship-mapping.d.ts

@@ -2,10 +2,36 @@
  * Archi relationship mapping, resolved by (relationship type, source
  * semantic type, target semantic type) — never by relationship type alone.
  *
- * Only THREE mappings are proven, all confirmed directly against
- * `tests/fixtures/relationships/relaciones.{archimate,xma}`. Every other
+ * 90 exact-triple mappings are proven: the original 3 confirmed against
+ * `tests/fixtures/relationships/relaciones.{archimate,xma}`, 64 more
+ * confirmed against `tests/fixtures/sabsa/sabsa.{archimate,xma}`, 20 more
+ * confirmed against `tests/fixtures/agile-manifesto/agile-manifesto.{archimate,xma}`,
+ * and 3 confirmed "...Collaboration collapses to its singular active-structure
+ * counterpart" instances (see below) — see each fixture pair's entry in
+ * `tests/fixtures/README.md` for the full derivation method. Every other
  * relationship type/source/target combination is unsupported for v0.1 and
  * must be diagnosed, never guessed (see `serializer/relationship-writer.ts`).
+ *
+ * `scheme` is always the scheme of the *source* type (confirmed even across
+ * schemes, e.g. `WorkPackage -> BusinessFunction` lives in `IMScheme`, the
+ * source's scheme, not `BusinessScheme`).
+ *
+ * Three "...Collaboration" entries collapse to their singular active-structure
+ * counterpart for relationship naming only (their own element mapping is
+ * unaffected — see `element-mapping.ts`): `BusinessCollaboration` collapses
+ * to `BusinessRole`, `TechnologyCollaboration` collapses to `TechnologyNode`.
+ * Verified directly against raw relation instances in both fixtures, not
+ * inferred.
+ *
+ * NOT modeled here as exact triples — genuinely type-independent, so they
+ * live in `generic-relationship-mapping.ts` instead:
+ *   - `AssociationRelationship` always serializes as the generic
+ *     `ElementElementAssociation`, regardless of source/target type.
+ *   - A `Grouping` endpoint (for the confirmed verbs Composition,
+ *     Specialization, Influence, Use) or a `Junction`/`OrJunction` endpoint
+ *     (for the confirmed verbs Realisation, Influence) uses a generic form
+ *     (e.g. `GroupingElementComposition`, `RealisationRelation`) instead of a
+ *     type-specific one.
  */
 export interface RelationshipMappingEntry {
     archiRelationshipType: string;

package/dist/mapping/relationship-mapping.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"relationship-mapping.d.ts","sourceRoot":"","sources":["../../src/mapping/relationship-mapping.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,MAAM,WAAW,wBAAwB;IACvC,qBAAqB,EAAE,MAAM,CAAC;IAC9B,eAAe,EAAE,MAAM,CAAC;IACxB,eAAe,EAAE,MAAM,CAAC;IACxB,qFAAqF;IACrF,OAAO,EAAE,MAAM,CAAC;IAChB,oGAAoG;IACpG,MAAM,EAAE,MAAM,CAAC;CAChB;AAED,eAAO,MAAM,qBAAqB,EAAE,SAAS,wBAAwB,EAwBpE,CAAC;AAaF,wBAAgB,yBAAyB,CACvC,gBAAgB,EAAE,MAAM,EACxB,eAAe,EAAE,MAAM,EACvB,eAAe,EAAE,MAAM,GACtB,wBAAwB,GAAG,SAAS,CAEtC"}
+{"version":3,"file":"relationship-mapping.d.ts","sourceRoot":"","sources":["../../src/mapping/relationship-mapping.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAkCG;AAEH,MAAM,WAAW,wBAAwB;IACvC,qBAAqB,EAAE,MAAM,CAAC;IAC9B,eAAe,EAAE,MAAM,CAAC;IACxB,eAAe,EAAE,MAAM,CAAC;IACxB,qFAAqF;IACrF,OAAO,EAAE,MAAM,CAAC;IAChB,oGAAoG;IACpG,MAAM,EAAE,MAAM,CAAC;CAChB;AAED,eAAO,MAAM,qBAAqB,EAAE,SAAS,wBAAwB,EA+oBpE,CAAC;AAaF,wBAAgB,yBAAyB,CACvC,gBAAgB,EAAE,MAAM,EACxB,eAAe,EAAE,MAAM,EACvB,eAAe,EAAE,MAAM,GACtB,wBAAwB,GAAG,SAAS,CAEtC"}