From 3e3b200dad5eca68b9d43f9729ce5446205825ce Mon Sep 17 00:00:00 2001
From: Patrice Chalin <pchalin@gmail.com>
Date: Wed, 20 Nov 2024 18:50:25 -0500
Subject: [PATCH] Fix access to separate OTLP signal statuses

---
 content/en/docs/specs/status.md | 24 +++++++++++++++++-------
 1 file changed, 17 insertions(+), 7 deletions(-)

diff --git a/content/en/docs/specs/status.md b/content/en/docs/specs/status.md
index 82075dad9bb9..8b596a0751cd 100644
--- a/content/en/docs/specs/status.md
+++ b/content/en/docs/specs/status.md
@@ -54,11 +54,12 @@ support for specific features can be found in the
 Note that, for each of the following sections, the **Collector** status is the
 same as the **Protocol** status.
 
-### [Tracing][]
+### Tracing
 
+- [Specification][tracing]
 - {{% spec_status "API" "otel/trace/api" "Status" %}}
 - {{% spec_status "SDK" "otel/trace/sdk" "Status" %}}
-- {{% spec_status "Protocol" "otlp" "Status" %}}
+- {{% spec_status "Protocol" "otlp" "/document-status/.*for.*trace" %}}
 - Notes:
   - The tracing specification is now completely stable, and covered by long term
     support.
@@ -67,11 +68,12 @@ same as the **Protocol** status.
   - OpenTelemetry clients are versioned to v1.0 once their tracing
     implementation is complete.
 
-### [Metrics][]
+### Metrics
 
+- [Specification][metrics]
 - {{% spec_status "API" "otel/metrics/api" "Status" %}}
 - {{% spec_status "SDK" "otel/metrics/sdk" "Status" %}}
-- {{% spec_status "Protocol" "otlp" "Status" %}}
+- {{% spec_status "Protocol" "otlp" "/document-status/.*for.*metric" %}}
 - Notes:
   - OpenTelemetry Metrics is currently under active development.
   - The data model is stable and released as part of the OTLP protocol.
@@ -79,8 +81,9 @@ same as the **Protocol** status.
   - Collector support for Prometheus is under development, in collaboration with
     the Prometheus community.
 
-### [Baggage][]
+### Baggage
 
+- [Specification][baggage]
 - {{% spec_status "API" "otel/baggage/api" "Status" %}}
 - **SDK:** stable
 - **Protocol:** N/A
@@ -90,12 +93,13 @@ same as the **Protocol** status.
     keys and values to a transaction, so that downstream services may access
     them. As such, there is no OTLP or Collector component to baggage.
 
-### [Logging][]
+### Logging
 
+- [Specification][logging]
 - {{% spec_status "Bridge API" "otel/logs/api" "Status" %}}
 - {{% spec_status "SDK" "otel/logs/sdk" "Status" %}}
 - {{% spec_status "Event API" "otel/logs/event-api" "Status" %}}
-- {{% spec_status "Protocol" "otlp" "Status" %}}
+- {{% spec_status "Protocol" "otlp" "/document-status/.*for.*log" %}}
 - Notes:
   - The [logs data model][] is released as part of the OpenTelemetry Protocol.
   - Log processing for many data formats has been added to the Collector, thanks
@@ -112,9 +116,15 @@ same as the **Protocol** status.
     the Event API is intended to be called by end users. The Event API is under
     active development.
 
+### Profiles
+
+- [Specification][profiles]
+- {{% spec_status "Protocol" "otlp" "/document-status/.*for.*profiles" %}}
+
 [baggage]: /docs/specs/otel/baggage/
 [event semantic conventions]: /docs/specs/semconv/general/events/
 [logging]: /docs/specs/otel/logs/
 [logs data model]: /docs/specs/otel/logs/data-model/
 [metrics]: /docs/specs/otel/metrics/
+[profiles]: /docs/specs/otel/profiles/
 [tracing]: /docs/specs/otel/trace/