Right now, we have two stabilized "resource"s in semantic conventions.

• service - includes service.name, service.namespace, etc.
• telemetry.sdk

However the service.instance.id field is NOT stable, but marked as required and an identifying field.

I propose two options:

1. We stabilize service.instance.id and make it identifying on service.
2. We create a new entity service.instance. There would be a "has-a" relationship between service and service.instance. Initially, service.instance would only consist of its id. service would be identified by namespace and name.

UPDATE:

We will take option (2) and open in semconv.