@lizzi, @rrlevering is there any particular use case you have in mind for Person.identifier?

https://developers.google.com/search/docs/appearance/structured-data/profile-page#profile-target-specification

Reason I ask is that when thinking about it, while taking the GDPR into account, I realized there really are no identifiers I can think of that do not potentially cause (legal) issues.

So surely there must be something particular (and not privacy sensitive) you had in mind when adding this property.

Profile Page (ProfilePage) Schema Markup | Google Search Central  |  Documentation  |  Google for Developers

You can use profile page structured data to help provide information about the people and organizations on your website.

Google for Developers
@JarnoVanDriel @lizzi That is a little vague, I agree... It's mostly for sites that have their own unique id for people if something like name or alternateName is not unique. Maybe we should clarify that we don't want social security numbers anywhere.
@rrlevering @JarnoVanDriel good point. i would also like an example ๐Ÿ‘€ by not unique, do you mean something like โ€œuser456โ€ that only has meaning within that site? like internal id?
@lizzi @JarnoVanDriel Some sites allow people to change their handle and the most stable id we can get is ideal so we don't lose the person over time, just within that website...so a database id is really what we want