[editorial] Add missing READMEs to section (#2559)

specification/README.md

@@ -9,7 +9,7 @@
   - [Package/Library Layout](library-layout.md)
   - [General error handling guidelines](error-handling.md)
 - API Specification
-  - [Context](context/context.md)
+  - [Context](context/README.md)
     - [Propagators](context/api-propagators.md)
   - [Baggage](baggage/api.md)
   - [Tracing](trace/api.md)

specification/baggage/README.md

@@ -0,0 +1 @@
+# Baggage

specification/baggage/api.md

@@ -101,7 +101,7 @@ REQUIRED parameters:
 ## Context Interaction
 
 This section defines all operations within the Baggage API that interact with
-the [`Context`](../context/context.md).
+the [`Context`](../context/README.md).
 
 If an implementation of this API does not operate directly on the `Context`, it
 MUST provide the following functionality to interact with a `Context` instance:
@@ -110,11 +110,11 @@ MUST provide the following functionality to interact with a `Context` instance:
 - Insert the `Baggage` to a `Context` instance
 
 The functionality listed above is necessary because API users SHOULD NOT have
-access to the [Context Key](../context/context.md#create-a-key) used by the
+access to the [Context Key](../context/README.md#create-a-key) used by the
 Baggage API implementation.
 
 If the language has support for implicitly propagated `Context` (see
-[here](../context/context.md#optional-global-operations)), the API SHOULD also
+[here](../context/README.md#optional-global-operations)), the API SHOULD also
 provide the following functionality:
 
 - Get the currently active `Baggage` from the implicit context. This is

specification/common/README.md

@@ -1,3 +1,6 @@
+<!---
+aliases: [/docs/reference/specification/common/common]
+--->
 # Common specification concepts
 
 **Status**: [Stable, Feature-freeze](../document-status.md)

specification/compatibility/README.md

@@ -0,0 +1 @@
+# Compatibility

specification/context/context.md → specification/context/README.md

@@ -1,3 +1,6 @@
+<!---
+aliases: [/docs/reference/specification/context/context]
+--->
 # Context
 
 **Status**: [Stable, Feature-freeze](../document-status.md).

specification/metrics/README.md

@@ -27,7 +27,7 @@ important to understand the goals of OpenTelemetry’s metrics effort:
 
 * **Being able to connect metrics to other signals**. For example, metrics and
   traces can be correlated via exemplars, and metrics attributes can be enriched
-  via [Baggage](../baggage/api.md) and [Context](../context/context.md).
+  via [Baggage](../baggage/api.md) and [Context](../context/README.md).
   Additionally, [Resource](../resource/sdk.md) can be applied to
   [logs](../overview.md#log-signal)/[metrics](../overview.md#metric-signal)/[traces](../overview.md#tracing-signal)
   in a consistent way.

specification/metrics/api.md

@@ -298,15 +298,15 @@ asynchronous:
   inline with application/business processing logic. For example, an HTTP client
   could use a Counter to record the number of bytes it has received.
   [Measurements](#measurement) recorded by synchronous instruments can be
-  associated with the [Context](../context/context.md).
+  associated with the [Context](../context/README.md).
 
 * Asynchronous instruments (e.g. [Asynchronous Gauge](#asynchronous-gauge)) give
   the user a way to register callback function, and the callback function will
   be invoked only on demand (see SDK [collection](sdk.md#collect) for reference). For example, a piece of embedded software
   could use an asynchronous gauge to collect the temperature from a sensor every
   15 seconds, which means the callback function will only be invoked every 15
   seconds. [Measurements](#measurement) recorded by asynchronous instruments
-  cannot be associated with the [Context](../context/context.md).
+  cannot be associated with the [Context](../context/README.md).
 
 Please note that the term *synchronous* and *asynchronous* have nothing to do
 with the [asynchronous

specification/metrics/sdk.md

@@ -646,7 +646,7 @@ This interface SHOULD have access to:
 
 - The `value` of the measurement.
 - The complete set of `Attributes` of the measurement.
-- The [Context](../context/context.md) of the measurement, which covers the
+- The [Context](../context/README.md) of the measurement, which covers the
   [Baggage](../baggage/api.md) and the current active
   [Span](../trace/api.md#span).
 - A `timestamp` that best represents when the measurement was taken.
@@ -663,7 +663,7 @@ The "offer" method SHOULD accept measurements, including:
 
 - The `value` of the measurement.
 - The complete set of `Attributes` of the measurement.
-- The [Context](../context/context.md) of the measurement, which covers the
+- The [Context](../context/README.md) of the measurement, which covers the
   [Baggage](../baggage/api.md) and the current active
   [Span](../trace/api.md#span).
 - A `timestamp` that best represents when the measurement was taken.

specification/overview.md

@@ -342,7 +342,7 @@ All of OpenTelemetry cross-cutting concerns, such as traces and metrics,
 share an underlying `Context` mechanism for storing state and
 accessing data across the lifespan of a distributed transaction.
 
-See the [Context](context/context.md)
+See the [Context](context/README.md)
 
 ## Propagators
 

specification/resource/README.md

@@ -0,0 +1 @@
+# Resource

specification/trace/README.md

@@ -0,0 +1 @@
+# Trace

specification/trace/api.md

@@ -153,7 +153,7 @@ association.
 ## Context Interaction
 
 This section defines all operations within the Tracing API that interact with the
-[`Context`](../context/context.md).
+[`Context`](../context/README.md).
 
 The API MUST provide the following functionality to interact with a `Context`
 instance:
@@ -162,10 +162,10 @@ instance:
 - Insert the `Span` to a `Context` instance
 
 The functionality listed above is necessary because API users SHOULD NOT have
-access to the [Context Key](../context/context.md#create-a-key) used by the Tracing API implementation.
+access to the [Context Key](../context/README.md#create-a-key) used by the Tracing API implementation.
 
 If the language has support for implicitly propagated `Context` (see
-[here](../context/context.md#optional-global-operations)), the API SHOULD also provide
+[here](../context/README.md#optional-global-operations)), the API SHOULD also provide
 the following functionality:
 
 - Get the currently active span from the implicit context. This is equivalent to getting the implicit context, then extracting the `Span` from the context.

specification/trace/sdk.md

@@ -238,7 +238,7 @@ Returns the sampling Decision for a `Span` to be created.
 
 **Required arguments:**
 
-* [`Context`](../context/context.md) with parent `Span`.
+* [`Context`](../context/README.md) with parent `Span`.
   The Span's SpanContext may be invalid to indicate a root span.
 * `TraceId` of the `Span` to be created.
   If the parent `SpanContext` contains a valid `TraceId`, they MUST always match.