Skip to content

chore: Remove redundant 'View name' entry from compliance matrix#5043

Merged
reyang merged 3 commits intoopen-telemetry:mainfrom
cijothomas:cijothomas/remove-redundant-view-name-entry
Apr 23, 2026
Merged

chore: Remove redundant 'View name' entry from compliance matrix#5043
reyang merged 3 commits intoopen-telemetry:mainfrom
cijothomas:cijothomas/remove-redundant-view-name-entry

Conversation

@cijothomas
Copy link
Copy Markdown
Member

@cijothomas cijothomas commented Apr 21, 2026

The compliance matrix entry "The name of the View can be specified" is misleading and redundant:

  1. The spec defines name as a stream configuration parameter that renames the output metric stream — there is no concept of naming a View itself.
  2. This capability is already covered by the existing entry: "The View allows configuring the name, description, attributes keys and aggregation of the resulting metric stream."
  3. The redundancy caused contradictory compliance statuses in some languages (e.g. Go marked - for the removed entry but + for the broader one).

Changes:

  • Remove "The name of the View can be specified" from spec-compliance-matrix/template.yaml and all 12 language YAML files
  • Regenerate spec-compliance-matrix.md

@cijothomas cijothomas requested review from a team as code owners April 21, 2026 23:51
@cijothomas cijothomas changed the title Remove redundant 'View name' entry from compliance matrix chore: Remove redundant 'View name' entry from compliance matrix Apr 21, 2026
Comment thread spec-compliance-matrix/dotnet.yaml
@reyang reyang added the editorial Editorial changes only (typos, changelog, ...). No content-related changes of any kind. label Apr 23, 2026
@reyang reyang added this pull request to the merge queue Apr 23, 2026
Merged via the queue into open-telemetry:main with commit 49e7fc4 Apr 23, 2026
10 checks passed
hilmarf pushed a commit to apeirora/opentelemetry-specification that referenced this pull request Apr 23, 2026
…n-telemetry#5043)

The compliance matrix entry "The name of the `View` can be specified" is
misleading and redundant:

1. The spec defines `name` as a [stream
configuration](./specification/metrics/sdk.md#stream-configuration)
parameter that renames the output metric stream — **there is no concept
of naming a View itself.**
2. This capability is already covered by the existing entry: "The `View`
allows configuring the name, description, attributes keys and
aggregation of the resulting metric stream."
3. The redundancy caused contradictory compliance statuses in some
languages (e.g. Go marked `-` for the removed entry but `+` for the
broader one).

**Changes:**
- Remove "The name of the `View` can be specified" from
`spec-compliance-matrix/template.yaml` and all 12 language YAML files
- Regenerate `spec-compliance-matrix.md`

Co-authored-by: Alex Boten <223565+codeboten@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

editorial Editorial changes only (typos, changelog, ...). No content-related changes of any kind.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants