Skip to content

Allow SpanRefinement to override name.note in definition/2 #1402

@lmolkova

Description

@lmolkova

A Span defines name.note (how to build the span name). A SpanRefinement can't override it — refinements just inherit, with no way to express a provider-specific format.

Many conventions explicitly allow this. From GenAI:

gen_ai.inference.client: Span name SHOULD be {gen_ai.operation.name} {gen_ai.request.model}. Semantic conventions for individual GenAI systems and frameworks MAY specify different span name format.

Proposal

Add an optional name: SpanName to SpanRefinement. Resolution: use the refinement's name.note if set, otherwise inherit from the referenced base.

Complements #1401 (which fixes name.note preservation for top-level spans but leaves refinements emitting the type id).

Metadata

Metadata

Labels

resolution engineIssues relating to behavior of resolving raw schema files into a cohesive model
No fields configured for Feature.

Projects

Status
V2 Schema

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions