Remove kuksa.val and VSC references

content/en/docs/about/_index.md

@@ -35,7 +35,7 @@ Eclipse _Velocitas™_ is an open source project providing an end-to-end, scalab
 - **Project lifecycle management** to update _Vehicle App_ repositories via CLI.
 - **Vehicle abstraction support** helps to focus on business logic by using a generated vehicle model _on code level_ with type safety and auto-completion. The vehicle model is generated from a standardized API that hides the details of vehicle-specific signals and E/E architecture, allowing _Vehicle Apps_ to be portable across different electronics and software architectures.
 - Microsoft **Visual Studio Code integration** with DevContainer helps to install everything required to start the local development immediately, while tasks and launch configurations help to launch runtime services, other apps, and tests.
-- **_Vehicle App_ skeleton and examples** helps to understand easily how to write a _Vehicle App_ using the KUKSA.VAL runtime services.
+- **_Vehicle App_ skeleton and examples** helps to understand easily how to write a _Vehicle App_ using the KUKSA runtime services.
 - Ready-to-use **CI/CD workflows** that build (for multi architectures), test, document and deploy a containerized _Vehicle App_ with no dependencies to E/E architecture help saving setup time.
 
 ## Language Support

content/en/docs/about/repository-overview/_index.md

@@ -21,7 +21,7 @@ description: >
 | [vehicle-model-cpp](https://github.com/eclipse-velocitas/vehicle-model-cpp)                       | Basic vehicle model for C++ is generated from [VSS](https://github.com/COVESA/vehicle_signal_specification/tree/master/spec) with addition of some specialized vehicle services.                                                                                                                                                                                                                                                       |
 | [kuksa-databroker](https://github.com/eclipse-kuksa/kuksa-databroker)                    | Is a part of the _Vehicle Abstraction Layer (VAL)_ of the [Eclipse KUKSA project](https://github.com/eclipse-kuksa) and provides the KUKSA Databroker. The KUKSA Databroker offers data points available in the vehicle to the _Vehicle Apps_ semantically aligned to a data model like the [Vehicle Signal Specification (VSS)](https://covesa.github.io/vehicle_signal_specification/).                                               |
 | [kuksa-can-provider](https://github.com/eclipse-kuksa/kuksa-can-provider)               | The KUKSA CAN Provider is a generic data feeder that reads data from the vehicle's [CAN bus](https://en.wikipedia.org/wiki/CAN_bus) defined by a DBC file, maps them to a set of data points (e.g. according to the VSS) and feeds it into the Databroker.                                                                                                                                                                           |
-| [kuksa.val.services](https://github.com/eclipse/kuksa.val.services)                               | Provides exemplary vehicle services and respective implementations that illustrates how to interact with in-vehicle components and services via an unified access that is semantically described e.g. in the [Vehicle Service Catalog (VSC)](https://github.com/COVESA/vehicle_service_catalog).                                                                                                                                    |
+| [kuksa-incubation](https://github.com/eclipse-kuksa/kuksa-incubation)                               | Provides exemplary vehicle services and respective implementations that illustrates how to interact with in-vehicle components and services via an unified access.                                                                                                                                    |
 | [release-documentation-action](https://github.com/eclipse-velocitas/release-documentation-action) | GitHub Action to generate a release documentation from the CI workflow output by rendering it to markdown files so that this can be easily published with GitHub Pages.                                                                                                                                                                                                                                                             |
 | [license-check](https://github.com/eclipse-velocitas/license-check)                               | GitHub Action to collect the licenses of the used components and can be configured to fail with an error message on invalid licenses.                                                                                                                                                                                                                                                                                               |
 | [vehicle-model-generator](https://github.com/eclipse-velocitas/vehicle-model-generator)           | Provides basic functionality to create a vehicle model from the given vspec specification for the target programming                                                                                                                                                                                                                                                                                                                |

content/en/docs/concepts/development_model/_index.md

@@ -44,10 +44,6 @@ Vehicle data is stored in the KUKSA Databroker conforming to an underlying [Sema
 
 The Vehicle Signal Specification ([VSS](https://covesa.github.io/vehicle_signal_specification/)) provides a domain taxonomy for vehicle signals and defines the vehicle data semantically, which is exchanged between _Vehicle Apps_ and the Databroker.
 
-The Vehicle Service Catalog ([VSC](https://github.com/COVESA/vehicle_service_catalog#vehicle-service-catalog)) extends VSS with functional remote procedure call definitions and semantically defines the gRPC interfaces of Vehicle Services and _Vehicle Apps_.
-
-As an alternative to VSS and VSC, vehicle data and services can be defined semantically in a general IoT modelling language like Digital Twin Definition Language ([DTDL](https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v2/dtdlv2.md)) or BAMM Aspect Meta Model [BAMM](https://github.com/OpenManufacturingPlatform/sds-bamm-aspect-meta-model) as well.
-
 The Velocitas SDK is using [VSS](https://covesa.github.io/vehicle_signal_specification/) as the semantic model for the Vehicle Model.
 
 ### Communication Protocols