Update enduser domain and add enduser.pseudo.id

docs/general/attributes.md

@@ -412,9 +412,9 @@ These attributes may be used for any operation with an authenticated and/or auth
 <!-- END AUTOGENERATED TEXT -->
 <!-- endsemconv -->
 
-These attributes describe the authenticated user driving the user agent making requests to the instrumented
+`enduser.id` describe the authenticated user driving the user agent making requests to the instrumented
 system. It is expected this information would be propagated unchanged from node-to-node within the system
-using the Baggage mechanism. These attributes should not be used to record system-to-system
+using the Baggage mechanism. This attribute should not be used to record system-to-system
 authentication attributes.
 
 Examples of where the `enduser.id` value is extracted from:
@@ -442,10 +442,6 @@ Examples of where the `enduser.id` value is extracted from:
 [JavaEE/JakartaEE Servlet]: https://jakarta.ee/specifications/platform/8/apidocs/javax/servlet/http/HttpServletRequest.html
 [Windows Communication Foundation]: https://docs.microsoft.com/dotnet/api/system.servicemodel.servicesecuritycontext?view=netframework-4.8
 
-Given the sensitive nature of this information, SDKs and exporters SHOULD drop these attributes by
-default and then provide a configuration parameter to turn on retention for use cases where the
-information is required and would not violate any policies or regulations.
-
 Enduser attributes capture end user identity. They are likely to contain PII and should be populated, processed, and stored with caution.
 Information about the end user is usually available on the client side (in a mobile or browser application).
 Enduser attributes are populated by the user application in coordination with OpenTelemetry SDK.