Clarify that service.* conventions apply to all telemetry sources (op…

…en-telemetry#630)

Co-authored-by: Joao Grassi <[email protected]>

CHANGELOG.md

@@ -18,6 +18,9 @@ release.
 
 ### Fixes
 
+- Clarify that `service.*` attributes apply to all telemetry sources.
+  ([#630](https://github.com/open-telemetry/semantic-conventions/pull/630))
+
 ## v1.24.0 (2023-12-15)
 
 ### Breaking

docs/resource/README.md

@@ -77,7 +77,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet
 
 **type:** `service`
 
-**Description:** A service instance.
+**Description:** A telemetry source. OpenTelemetry has adopted a broad interpretation such that every telemetry source is a service. Examples include, but are not limited to: web services, hosts, mobile applications, browser application, edge computing devices, functions as a service, databases, message brokers, etc. Specific types of telemetry sources may have additional conventions defining domain specific information, but the `service` conventions are applicable to all telemetry sources.
 
 <!-- semconv service -->
 | Attribute  | Type | Description  | Examples  | Requirement Level |
@@ -94,7 +94,7 @@ as specified in the [Resource SDK specification](https://github.com/open-telemet
 
 **type:** `service`
 
-**Description:** Additions to service instance.
+**Description:** Experimental additions to service.
 
 <!-- semconv service_experimental -->
 | Attribute  | Type | Description  | Examples  | Requirement Level |

model/resource/service.yaml

@@ -3,7 +3,12 @@ groups:
     prefix: service
     type: resource
     brief: >
-      A service instance.
+      A telemetry source. OpenTelemetry has adopted a broad interpretation such that every
+      telemetry source is a service. Examples include, but are not limited to: web services,
+      hosts, mobile applications, browser application, edge computing devices, functions as
+      a service, databases, message brokers, etc. Specific types of telemetry sources may have
+      additional conventions defining domain specific information, but the `service`
+      conventions are applicable to all telemetry sources.
     attributes:
       - id: name
         type: string

model/resource/service_experimental.yaml

@@ -3,7 +3,7 @@ groups:
     prefix: service
     type: resource
     brief: >
-      A service instance.
+      Experimental additions to service.
     attributes:
       - id: namespace
         type: string