Fix attributes names in Google Cloud Logging mapping

Vendor-specific attribute names must be prefixed
with reverse FQDN, see recommendation here
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/common/attribute-naming.md#recommendations-for-application-developers

CHANGELOG.md

@@ -36,6 +36,9 @@ release.
 
 ### Logs
 
+- Fix attributes names in Google Cloud Logging mapping.
+  ([#2093](https://github.com/open-telemetry/opentelemetry-specification/pull/2093))
+
 ### Resource
 
 ### Semantic Conventions

specification/logs/data-model.md

@@ -979,8 +979,8 @@ severity         | LogSeverity        | The severity of the log entry.
 trace            | string             | The trace associated with the log entry, if any.        | TraceId
 span_id          | string             | The span ID within the trace associated with the log entry. | SpanId
 labels           | map<string,string> | A set of user-defined (key, value) data that provides additional information about the log entry. | Attributes
-http_request     | HttpRequest        | The HTTP request associated with the log entry, if any. | Attributes["google.httpRequest"]
-All other fields |                    |                                                         | Attributes["google.*"]
+http_request     | HttpRequest        | The HTTP request associated with the log entry, if any. | Attributes["com.google.httpRequest"]
+All other fields |                    |                                                         | Attributes["com.google.*"]
 
 ## Elastic Common Schema