Bug: optional links not following metamodel

[nicu1989]

Description

Metamodel from docs-as-code requires optional_links like realizes or complies to follow the patterns from: https://github.com/eclipse-score/docs-as-code/blob/main/src/extensions/score_metamodel/metamodel.yaml

With docs-as-code v1.3.0 these non-compliances are exposed as info during docs build.

Example:

process_areas/platform_management/platform_management_workproducts.rst:33: wp__project_mgt.complies (['std_req__aspice_40__iic-08-53', 'std_req__aspice_40__iic-14-10', 'std_req__aspice_40__.

does not follow regex:
^std_(wp__iso26262|wp__isosae21434|wp__isopas8926|iic_aspice_40)__.*$

from metamodel: https://github.com/eclipse-score/docs-as-code/blob/edc9f4e421132939921d7d3be7530b914b86ccd4/src/extensions/score_metamodel/metamodel.yaml#L177

Analysis results

process_description repo will be uplifted with DAC v1.3.0 and non-compliances will be visible. Correct the warnings-as-info from docs build log.

Solution

Correct optional links in .rst files.

Error Occurrence Rate

Reproducible

How to reproduce

check CI run for docs build.

Supporting Information

No response

Classification

minor

Affected Version

pre-0.5

Expected Closure Version

0.5

Category

• Safety Related
• Security Related

ASIL classification

No response

[masc2023]

Will be discussed in Process Meeting, 30.09, 9-10, @AlexanderLanin, would good if you could join, as we discussed already yesterday not to lift up, until we have clarified, where todo changes