[Model Deprecation]: urn:bamm:io.catenax.pcf:3.0.0

[bs-jokri]

Update Reason

The model is neither used in a standard document or triangle document, which indicates that the model is not used anymore.

If there are still reasons to still have this model in the repository, please provide a short rationale in the comments. If not, please indicate with a "+1" that you are OK with deprecating the model.

Deprecating a model means, that it will be removed after two Tractus-X releases from the repository. For details, please refer to the GOVERNANCE process.

MS1 Criteria

• [ ] The model that should be deprecated exists and is not deprecated already
• [ ] The respective model does not affect existing use cases (aspect is either used in higher versions or replaced by a different aspect)
• [ ] A shared aspect, which will be deprecated, is not used by any released aspect model

[bs-jokri]

@SMaierTSI please check this request

[SMaierTSI]

Methodological viewpoint: the validity of a PCF is specified in the Catena-X PCF Rulebook. As a result, a PCF can be valid for a longer time period. For consistency, a specific PCF data model version needs to be supported at least as long as there is a valid PCF. This must be considered when we want to deprecate a data model.

Technical viewpoint: in order to meed the specification in the PCF Rulebook the PCF Exchange applications support different PCF data models concurrently. It needs to be aligned with the application providers which PCF data model versions can be deprecated.