Add attribute 'revisionAware' to cas:Link

Author: odungern

design/CASCaRA-Reference-Implementation/1_Source/CASCaRA-Reference-Implementation.archimate

@@ -1255,5 +1255,12 @@ Major requirements (capabilities and characteristics) must be satisfied:
 - Extend the software using a documented, if possible standardized plug-in mechanism.
 
 This model is authored with [Archi](https://www.archimatetool.com/) using the ArchiMate 3.2 notation, then transformed to [SpecIF](https://specif.de) via ArchiMate Open Exchange file format and then transformed to HTML. The CASCaRA App will support a similar workflow (among others) for the source data formats chosen.
+
+The [ArchiMate notation](https://www.opengroup.org/sites/default/files/docs/downloads/n221p.pdf) uses the following background colors per model element:
+- **Motivation** level: light violet for stakeholders, goals, outcomes etc.
+- **Strategy** level: beige for competencies, course of action, value streams etc.
+- **Business** level: light yellow for roles, business functions and processes etc.
+- **Application** level: light blue for applications, data objects etc.
+- **Technology** level: light green for operating resources etc.
 </purpose>
 </archimate:model>

design/CASCaRA-Reference-Implementation/1_Source/CASCaRA-Reference-Implementation.archimate.bak

@@ -1179,10 +1179,10 @@ Subject to validation:
         <sourceConnection xsi:type="archimate:Connection" id="id-0ab77cac46bc43e7983e3fefee837b46" source="id-8cc0074b463f4f88a18267283aad6c53" target="id-d6149b2c7eee47628c886d8e16fe69b6" archimateRelationship="id-99bca21995b44ac69efe740eb45e3f8f"/>
         <sourceConnection xsi:type="archimate:Connection" id="id-5d56e776a24f49e388212edf1eac0ea3" source="id-8cc0074b463f4f88a18267283aad6c53" target="id-fc4f087f0c51477b819afe8a9d36b7a4" archimateRelationship="id-5c87f59b40c44dc587feaff9eae59077"/>
         <child xsi:type="archimate:DiagramObject" id="id-d6149b2c7eee47628c886d8e16fe69b6" targetConnections="id-0ab77cac46bc43e7983e3fefee837b46" textPosition="1" archimateElement="id-8b0a9929440147a2b4aa7b8d4e6cdd40">
-          <bounds x="16" y="144" width="120" height="37"/>
+          <bounds x="36" y="144" width="120" height="37"/>
         </child>
         <child xsi:type="archimate:DiagramObject" id="id-fc4f087f0c51477b819afe8a9d36b7a4" targetConnections="id-5d56e776a24f49e388212edf1eac0ea3" textPosition="1" archimateElement="id-d6d5d5dd3f5647fc96608825d21ed329">
-          <bounds x="16" y="192" width="120" height="37"/>
+          <bounds x="36" y="192" width="120" height="37"/>
         </child>
       </child>
       <child xsi:type="archimate:DiagramObject" id="id-a6a9637228594a229c2a179aea290f38" font="1|Segoe UI|12.0|0|WINDOWS|1|-16|0|0|0|400|0|0|0|0|3|2|1|34|Segoe UI" textPosition="1" archimateElement="id-38c956c5b33947c88f70acd9dd92acf9">
@@ -1255,5 +1255,12 @@ Major requirements (capabilities and characteristics) must be satisfied:&#xD;
 - Extend the software using a documented, if possible standardized plug-in mechanism.&#xD;
 &#xD;
 This model is authored with [Archi](https://www.archimatetool.com/) using the ArchiMate 3.2 notation, then transformed to [SpecIF](https://specif.de) via ArchiMate Open Exchange file format and then transformed to HTML. The CASCaRA App will support a similar workflow (among others) for the source data formats chosen.&#xD;
+&#xD;
+The [ArchiMate notation](https://www.opengroup.org/sites/default/files/docs/downloads/n190p_5.pdf) uses the following background colors per model element:&#xD;
+- **Motivation** level: light violet for stakeholders, goals, outcomes etc.&#xD;
+- **Strategy** level: beige for competencies, course of action, value streams etc.&#xD;
+- **Business** level: light yellow for roles, business functions and processes etc.&#xD;
+- **Application** level: light blue for applications, data objects etc.&#xD;
+- **Technology** level: light green for operating resources etc.&#xD;
 </purpose>
 </archimate:model>

public/assets/jsonld/Link.json

@@ -77,6 +77,10 @@
         "$ref": "#/$defs/idObject"
       }
     },
+    "cas:revisionAware": {
+      "type": "boolean",
+      "description": "Indicates whether the link is version-aware. If true, instances must specify identifier and revision of the endpoints."
+    },
     "sh:minCount": {
       "type": "integer",
       "minimum": 0

src/common/schema/pig/json/pig-schemata.ts

@@ -256,6 +256,7 @@ class PigSchemaFactory {
                     minItems: 1,
                     items: { $ref: '#/$defs/idString' }
                 },
+                revisionAware: { type: 'boolean' },
                 minCount: { type: 'integer', minimum: 0 },
                 maxCount: { type: 'integer', minimum: 1 },
                 revision: { type: 'string' },

src/common/schema/pig/ts/pig-metaclasses.ts

@@ -41,8 +41,8 @@
  * - Programming errors result in exceptions, data errors in IMsg return values.
  * - The namespace prefixes are defined in definitions.ts and used consistently in the code; it was initially 'pig:'
  *   and is now pfxNsMeta: 'cas:' for the metamodel and pfxNsSemi: 'cas:' for the semantic infrastructure.
- * - CASCaRA (PIG) classes (as derived from the ontology) get version information it their URL path.
- * - All others must at least specify the 'modified' attribute to capture the version history of the item;
+ * - CASCaRA (PIG) classes (as derived from the ontology) get revision information it their URL path.
+ * - All others must at least specify the 'modified' attribute to capture the revision history of the item;
  *   it is recommended to maintain revision and priorRevision as well for better configuration management and traceability.
  *
  * @ToDo:
@@ -51,6 +51,8 @@
  * - allow packages to be nested
  * - implement 'composes' (formerly composedProperty) for Property and aProperty
  * - implement the inheritance of enumeratedProperty, enumeratedSourceLink, enumeratedTargetLink and enumeratedEndpoint
+ * ✅ implement 'revisionAware' for Link.
+ * - Consequently aSourceLink and aTargetLink must specify the endpoints by identifier and revision, if their class specifies revisionAware=true.
  * - Check use of PigItem.normalizeId() in the setJSONLD() thread
  *   PigItem.normalizeId() shortly before validate() in set() ?
  * ✅ Check the result of PigItem.normalizeId in the setXML() thread in case of enumerated values
@@ -1133,11 +1135,13 @@ export class Property extends Identifiable implements IProperty {
 }
 export interface ILink extends IIdentifiable {
     enumeratedEndpoint: TPigId[]; // must be URI of an Entity or Relationship (class)
+    revisionAware?: boolean; // optional, default is false
     minCount?: number;
     maxCount?: number;
 }
 export class Link extends Identifiable implements ILink {
     enumeratedEndpoint!: TPigId[];
+    revisionAware?: boolean;
     minCount?: number;
     maxCount?: number;
     constructor() {
@@ -1172,6 +1176,7 @@ export class Link extends Identifiable implements ILink {
         if (this.lastStatus.ok) {
             super.set(_itm);
             this.enumeratedEndpoint = _itm.enumeratedEndpoint;
+            this.revisionAware = _itm.revisionAware;
             this.minCount = _itm.minCount;
             this.maxCount = _itm.maxCount;
         }
@@ -1181,6 +1186,7 @@ export class Link extends Identifiable implements ILink {
         return LIB.stripUndefinedAndNull({
             ...super.get(),
             enumeratedEndpoint: this.enumeratedEndpoint,
+            revisionAware: this.revisionAware,
             minCount: this.minCount,
             maxCount: this.maxCount
         }) as ILink;

src/common/schema/pig/ts/pig-package-constraints.ts

@@ -45,6 +45,7 @@
  *      - a subClass has all properties and links of its superClass
  *      enumeratedProperty references
  *      Link endpoint compliance
+ *      aLink must specify identifier and revision of the endpoints, if its class has revisionAware set to true
  * Phase 3 (useful):
  *      No cyclic composition of properties
  *      Relationship structure