feature: upgrade knowledge agent references according to TX/CX 2412 versions.

docs-kits/kits/knowledge-agents/development-view/api.md

@@ -131,7 +131,7 @@ curl --location '${KA-MATCH}/agent/skill?asset=urn%3Acx%3ASkill%3Aconsumer%3ALif
 --data-raw 'PREFIX xsd:           <http://www.w3.org/2001/XMLSchema#> 
 PREFIX rdf:           <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
 PREFIX rdfs:          <http://www.w3.org/2000/01/rdf-schema#>
-PREFIX cx:            <https://github.com/catenax-ng/product-knowledge/ontology/cx.ttl#>
+PREFIX cx:            <https://github.com/big-data-spaces/knowledge-agents-deployment/ontology/cx.ttl#>
 
 ############################################################################################
 #                  Catena-X Knowledge Agents Sample Federated Skill           
@@ -166,8 +166,8 @@ VALUES (?vin ?troubleCode) { ("@vin"^^xsd:string "@troubleCode"^^xsd:string) }.
         cx:hasConnector ?oemConnector.
 
 ?oemConnector cx:offersAsset ?diagnoseAsset.
-?diagnoseAsset rdf:type <https://raw.githubusercontent.com/catenax-ng/product-knowledge/main/ontology/cx_ontology.ttl#GraphAsset>;
-                rdfs:isDefinedBy <https://raw.githubusercontent.com/catenax-ng/product-knowledge/main/ontology/diagnosis_ontology.ttl>.
+?diagnoseAsset rdf:type <https://raw.githubusercontent.com/big-data-spaces/knowledge-agents-deployment/main/ontology/cx_ontology.ttl#GraphAsset>;
+                rdfs:isDefinedBy <https://raw.githubusercontent.com/big-data-spaces/knowledge-agents-deployment/main/ontology/diagnosis_ontology.ttl>.
 
 ####
 # 3. The CONSUMER delegates the following logic to the OEM (connector)
@@ -214,7 +214,7 @@ SERVICE ?oemConnector {
                     ].           
 
     ?tieraConnector cx:offersAsset ?prognosisAsset.
-    ?prognosisAsset rdfs:isDefinedBy <https://raw.githubusercontent.com/catenax-ng/product-knowledge/main/ontology/prognosis_ontology.ttl>.
+    ?prognosisAsset rdfs:isDefinedBy <https://raw.githubusercontent.com/big-data-spaces/knowledge-agents-deployment/main/ontology/prognosis_ontology.ttl>.
 
     ####
     # 4. The OEM (and not the CONSUMER) delegates to the SUPPLIER (connector)
@@ -277,7 +277,7 @@ curl --location '${KA-BIND}/agent' \
 --data-raw 'PREFIX xsd:           <http://www.w3.org/2001/XMLSchema#> 
 PREFIX rdf:           <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
 PREFIX rdfs:          <http://www.w3.org/2000/01/rdf-schema#>
-PREFIX cx:            <https://github.com/catenax-ng/product-knowledge/ontology/cx.ttl#>
+PREFIX cx:            <https://github.com/big-data-spaces/knowledge-agents-deployment/ontology/cx.ttl#>
 
 # Sample Graph Context that is Delegated/Instantiated to a Binding Agent Call
 SELECT ?partType ?description WHERE {

docs-kits/kits/knowledge-agents/development-view/modules.md

@@ -193,7 +193,7 @@ The Federated Catalogue is an RDF data storage facility for the Matchmaking Agen
 
 The Federated Catalogue should initially download the complete Semantic Model that has been released for the target environment. It should also contain a list of business partners and their roles which form the surrounding dataspace neighborhood of the tenant. For that purpose, It could use GPDM (Business Partner Data Management) and Self-Description Hub services in order to lookup EDC addresses and additional domain information (sites, geo addresses). It should then be frequently updated with “live” information by invoking the EDC data management API to regularly obtain catalogue information.
 
-The portion of the Semantic Model describing these meta-data (Business Partners, Sites, Addresses, Use Cases, Use Case Roles, Connectors & Assets) is called the Common domain ontology and is mandatory for all releases/excerpts of the Semantic Model (<https://raw.githubusercontent.com/catenax-ng/product-knowledge/main/ontology/common_ontology.ttl>).
+The portion of the Semantic Model describing these meta-data (Business Partners, Sites, Addresses, Use Cases, Use Case Roles, Connectors & Assets) is called the Common domain ontology and is mandatory for all releases/excerpts of the Semantic Model (<https://raw.githubusercontent.com/big-data-spaces/knowledge-agents-deployment/main/ontology/common_ontology.ttl>).
 
 ## Virtualization Layer (Non-Standard Relevant)
 
@@ -268,8 +268,8 @@ There are two main components whose interplay implements the AAS-KA bridge:
 * A flexible SQL/JSON engine, such as Dremio or in parts also Postgresql which is able to mount raw data in various
 formats from remote filesystems and APIs. This engine is used to build flat relational views onto a hierarchical
 json structure that may originate in the value-only-serialization of the AAS. Typically there will be one table/view
-per json-schema/submodel template. As an example, see these [scripts](https://github.com/big-data-spaces/knowledge-agent-deployment/tree/main/infrastructure/resources/dremio)
-* A graph engine (such as [ontop](https://ontop-vkg.org/guide/) ) that is able to bind/translate SPARQL queries into SQL. As an example, see these [bindings](https://github.com/big-data-spaces/knowledge-agent-deployment/tree/main/infrastructure/oem/resources/trace.obda)
+per json-schema/submodel template. As an example, see these [scripts](https://github.com/big-data-spaces/knowledge-agents-deployment/tree/main/infrastructure/resources/dremio)
+* A graph engine (such as [ontop](https://ontop-vkg.org/guide/) ) that is able to bind/translate SPARQL queries into SQL. As an example, see these [bindings](https://github.com/big-data-spaces/knowledge-agents-deployment/tree/main/infrastructure/oem/resources/trace.obda)
 
 Of course, if the data is available in a native SQL-schema, the SQL/JSON-engine can be omitted. Likewise, even the graph engine
 can be left out if a sparql-capable database holds its data in conformance to the CX-ontologies.

docs-kits/kits/knowledge-agents/operation-view/agent_edc.md

@@ -49,7 +49,7 @@ Add a helm dependency to your umbrella/infrastructure Chart.yaml (this example u
 - name: agent-plane
   alias: my-agent-plane
   repository: https://eclipse-tractusx.github.io/charts/dev
-  version: 1.13.22
+  version: 1.14.24
 ```
 
 Then configure the connector in the values.yaml

docs-kits/kits/knowledge-agents/operation-view/deployment.md

@@ -241,7 +241,7 @@ Deployed as "provider-agent-plane"
 project: project-knowledge
 source:
   repoURL: 'https://eclipse-tractusx.github.io/charts/dev'
-  targetRevision: 1.13.22
+  targetRevision: 1.14.24
   plugin:
     env:
       - name: HELM_VALUES
@@ -458,7 +458,7 @@ Deployed as "consumer-agent-plane"
 project: project-knowledge
 source:
   repoURL: 'https://eclipse-tractusx.github.io/charts/dev'
-  targetRevision: 1.13.22
+  targetRevision: 1.14.24
   plugin:
     env:
       - name: HELM_VALUES
@@ -587,7 +587,7 @@ Deployed as "consumer-agent"
 project: project-knowledge
 source:
   repoURL: 'https://eclipse-tractusx.github.io/charts/dev'
-  targetRevision: 1.13.22
+  targetRevision: 1.14.24
   plugin:
     env:
       - name: HELM_VALUES
@@ -679,7 +679,7 @@ Therefore, some of the following settings are specific to stable and will not be
 project: project-knowledge
 source:
   repoURL: 'https://eclipse-tractusx.github.io/charts/dev'
-  targetRevision: 1.13.22
+  targetRevision: 1.14.24
   plugin:
     env:
       - name: HELM_VALUES
@@ -754,7 +754,7 @@ For simplicity, the remoting agent exposes a simply public API as a graph.
 project: project-knowledge
 source:
   repoURL: 'https://eclipse-tractusx.github.io/charts/dev'
-  targetRevision: 1.13.22
+  targetRevision: 1.14.24
   plugin:
     env:
       - name: HELM_VALUES