Add a Shutdown() method to *Provider

Author: XSAM

specification/metrics/api.md

@@ -358,6 +358,12 @@ other libraries.  The name of the `Meter` is explicitly not intended
 to be used as part of the instrument name, as that would prevent
 instrumentation libraries from capturing metrics by the same name.
 
+### Shutdown
+
+Exporting pending metrics.
+
+The `Shutdown` API MAY be implemented by invoking `Shutdown` within internal processors.
+
 ### Global Meter provider
 
 Use of a global instance may be seen as an anti-pattern in many

specification/trace/api.md

@@ -91,11 +91,12 @@ number of `TracerProvider` instances.
 
 ### TracerProvider operations
 
-The `TracerProvider` MUST provide functions to:
+The `TracerProvider` MUST provide the following functions:
 
 - Get a `Tracer`
+- Shutdown the provider (exporting pending spans)
 
-That API MUST accept the following parameters:
+That `Tracer()` API MUST accept the following parameters:
 
 - `name` (required): This name must identify the [instrumentation library](../overview.md#instrumentation-libraries)
   (e.g. `io.opentelemetry.contrib.mongodb`) and *not* the instrumented library.
@@ -125,6 +126,8 @@ the tracer could, for example, do a look-up with its name+version in a map in
 the `TracerProvider`, or the `TracerProvider` could maintain a registry of all
 returned `Tracer`s and actively update their configuration if it changes.
 
+The `Shutdown` API MAY be implemented by invoking `Shutdown` within internal processors.
+
 ## Tracing Context Utilities
 
 `Tracing Context Utilities` contains all operations within tracing that