Define file configuration parse and create operations

CHANGELOG.md

@@ -64,6 +64,8 @@ release.
 - Move `sdk-configuration.md` and `sdk-environment-variables.md`
   to `/specification/configuration/`.
   ([#3434](https://github.com/open-telemetry/opentelemetry-specification/pull/3434))
+- Define file configuration parse and configure operations.
+  ([#3437](https://github.com/open-telemetry/opentelemetry-specification/pull/3437))
 
 ### Telemetry Schemas
 

specification/configuration/file-configuration.md

@@ -10,7 +10,10 @@
 - [Configuration file](#configuration-file)
 - [SDK Configuration](#sdk-configuration)
   * [In-Memory Configuration Model](#in-memory-configuration-model)
-  * [Operations](#operations)
+    + [Parse File to Configuration](#parse-file-to-configuration)
+  * [ConfigurationProvider](#configurationprovider)
+    + [Create ConfigurationProvider](#create-configurationprovider)
+    + [Get TracerProvider, MeterProvider, LoggerProvider](#get-tracerprovider-meterprovider-loggerprovider)
 - [References](#references)
 
 <!-- tocstop -->
@@ -60,12 +63,52 @@ to provide this in-memory representation in a manner that is idiomatic for their
 language. If an SDK needs to expose a class or interface, the
 name `Configuration` is RECOMMENDED.
 
-### Operations
+#### Parse File to Configuration
 
-TODO: define how to parse configuration file to configuration model
+SDKs MUST provide an API to parse and validate
+a [configuration file](#configuration-file) and return a
+corresponding [Configuration Model](#in-memory-configuration-model).
 
-TODO: define how to apply configuration model to produce configured sdk
-components
+The API MUST accept the following parameters:
+
+* `file`: The [configuration file](#configuration-file) to parse. This MAY be a
+  file path, or language specific file class, or a stream of a file's content.
+
+The API MAY return an error if:
+
+* The `file` doesn't exist or is invalid
+* The parsed `file` content does not conform to
+  the [configuration model](#configuration-model) schema.
+
+### ConfigurationProvider
+
+`ConfigurationProvider` is responsible for
+interpreting [Configuration](#in-memory-configuration-model) and producing
+configured SDK components.
+
+It MUST be possible to [create](#create-configurationprovider)
+multiple `ConfigurationProvider`s with different configurations. It is the
+caller's responsibility to ensure the
+resulting [SDK components](#get-tracerprovider-meterprovider-loggerprovider) are
+correctly wired into the application and instrumentation.
+
+#### Create ConfigurationProvider
+
+Create a `Configurationprovider` from a configuration model.
+
+The API MUST accept the following parameters:
+
+* `configuration` - The [configuration model](#in-memory-configuration-model).
+
+#### Get TracerProvider, MeterProvider, LoggerProvider
+
+Interpret `configuration` and return SDK components (`TracerProvider`,
+`MeterProvider`, `LoggerProvider`). The SDK components MUST strictly reflect
+the `Configuration` and ignore
+the [environment variable configuration scheme](./sdk-environment-variables.md).
+
+// TODO: Extend ConfigurationProvider with ability to update SDK components with
+// new configuration for usage with OpAmp
 
 ## References