eclipse-score / eclipse-score/docs-as-code

requirements.rst: arch_linkage_safety table missing real_arc_int_op rows for comp implements/uses

Open
#629 0 comments 0 reactions 1 assignee Claimed by @RolandJentschETAS View on GitHub
Dominant language
Python
Stars
10
Forks
32
Avg merge
23h 52m
Merged PRs (30d)
52

Description

## Context

Follow-up from review discussion on #624 (`tool_req__arch_linkage_safety`).

## Issue

In `docs/internals/requirements/requirements.rst`, the linkage table under `tool_req__arch_linkage_safety` documents:

```
comp, implements, logic_arc_int, no, yes
comp, uses, logic_arc_int, no, yes
```

However, `src/extensions/score_metamodel/metamodel.yaml` allows both `implements` and `uses` from `comp` to target **either** `logic_arc_int` or `real_arc_int_op`:

```yaml
optional_links:
implements: logic_arc_int, real_arc_int_op
uses: logic_arc_int, real_arc_int_op
```

The table only lists `logic_arc_int` as a target, so it doesn't fully mirror the metamodel for these two relations.

## Suggested fix

Either:
1. Add rows for `comp, implements, real_arc_int_op` and `comp, uses, real_arc_int_op`, or
2. If the omission is intentional (table only documents the safety-relevant subset per `gd_req__arch_linkage_safety`), note that explicitly in the table/requirement text.

## Reference

- PR: #624
- Review comment: https://github.com/eclipse-score/docs-as-code/pull/624#issuecomment-4600579672

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.