# content
@eyeinthesky Thanks. In your description, does "primary resource" refer to https://enigmatick.social/user/jdt#main-key or https://enigmatick.social/user/jdt?

That matters since the latter is not known as accurate until the resolution is complete.

Practically speaking, it's clear that I can retrieve the Actor resource using the fragment ID (https://enigmatick.social/user/jdt#main-key) and then retrieve the owner field from the publicKey field of that object to arrive at the Actor ID. Although since the leap to look in the publicKey field doesn't seem like it's specified by LD-JSON, I suppose just pulling the id from the returned Actor object directly might be as valid.

# source.content
@eyeinthesky@mastodon.social Thanks. In your description, does "primary resource" refer to `https://enigmatick.social/user/jdt#main-key` or `https://enigmatick.social/user/jdt`?

That matters since the latter is not known as accurate until the resolution is complete.

Practically speaking, it's clear that I can retrieve the Actor resource using the fragment ID (`https://enigmatick.social/user/jdt#main-key`) and then retrieve the `owner` field from the `publicKey` field of that object to arrive at the Actor ID. Although since the leap to look in the `publicKey` field doesn't seem like it's specified by LD-JSON, I suppose just pulling the `id` from the returned Actor object directly might be as valid.