Adding os.build_id resource attribute and discussion why os.sdk.version isn't required

CHANGELOG.md

@@ -59,6 +59,8 @@ release.
   ([#252](https://github.com/open-telemetry/semantic-conventions/pull/252))
 - Simplify HTTP metric briefs.
   ([#276](https://github.com/open-telemetry/semantic-conventions/pull/276))
+- Added `os.build` and `os.sdk_version` resource attributes.
+  ([#293](https://github.com/open-telemetry/semantic-conventions/pull/293))
 
 ## v1.21.0 (2023-07-13)
 

CONTRIBUTING.md

@@ -21,18 +21,18 @@ key, but non-obvious, aspects:
 - All descriptions, normative language are defined in the `docs/`
   directory.
   - We provide tooling to generate Markdown documentation from the formal
-    YAML definitons.  See [Yaml to Markdown](#yaml-to-markdown).
+    YAML definitons. See [Yaml to Markdown](#yaml-to-markdown).
   - We use Hugo to render [semantic conventions on our website](https://opentelemetry.io/docs/specs/semconv/).
     You will see `<!--- Hugo front matter used to generate ...` sections
-    in markdown.  See [Hugo frontmatter](#hugo-frontmatter) for details.
+    in markdown. See [Hugo frontmatter](#hugo-frontmatter) for details.
 - All changes to existing attributes, metrics, etc. MUST be allowed as
   per our [stability guarantees](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.20.0/specification/versioning-and-stability.md#semantic-conventions-stability) and
-  defined in a schema file.  As part of any contribution, you should
+  defined in a schema file. As part of any contribution, you should
   include attribute changes defined in the `schema-next.yaml` file.
   For details, please read [the schema specification](https://opentelemetry.io/docs/specs/otel/schemas/).
 - After creating a pull request, please update the [CHANGELOG](CHANGELOG.md) file with
   a description of your changes.
-  
+
 Please make sure all Pull Requests are compliant with these rules!
 
 ### Hugo frontmatter

docs/resource/os.md

@@ -14,7 +14,9 @@ In case of virtualized environments, this is the operating system as it is obser
 | `os.type` | string | The operating system type. | `windows` | Required |
 | `os.description` | string | Human readable (not intended to be parsed) OS version information, like e.g. reported by `ver` or `lsb_release -a` commands. | `Microsoft Windows [Version 10.0.18363.778]`; `Ubuntu 18.04.1 LTS` | Recommended |
 | `os.name` | string | Human readable operating system name. | `iOS`; `Android`; `Ubuntu` | Recommended |
-| `os.version` | string | The version string of the operating system as defined in [Version Attributes](/docs/resource/README.md#version-attributes). | `14.2.1`; `18.04.1` | Recommended |
+| `os.version` | string | The major version string of the operating system.  Additionally, build numbers can be added in os.build attribute. | `14.2.1`; `18.04.1` | Recommended |
+| `os.build` | string | Unique identifier for a particular build or compilation of software. | `TQ3C.230805.001.B2`; `20E247` | Recommended |
+| `os.sdk_version` | string | Identifies the set of development tools and APIs used for building the software. | `26`; `6.1.1` | Recommended |
 
 `os.type` has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.
 

model/resource/os.yaml

@@ -60,6 +60,14 @@ groups:
       - id: version
         type: string
         brief: >
-          The version string of the operating system as defined in
-          [Version Attributes](/docs/resource/README.md#version-attributes).
+          The major version string of the operating system. 
+          Additionally, build numbers can be added in os.build attribute.
         examples: ['14.2.1', '18.04.1']
+      - id: build
+        type: string
+        brief: 'Unique identifier for a particular build or compilation of software.'
+        examples: ['TQ3C.230805.001.B2', '20E247']
+      - id: sdk_version
+        type: string
+        brief: 'Identifies the set of development tools and APIs used for building the software.'
+        examples: ['26', '6.1.1']