A credential can influence how the public interprets expertise, so its ownership should be precise. If an individual professional earned a license, certification, degree, or other qualification, the credential belongs to that professional. An employer may accurately state that the professional is part of its team, but the organization should not accidentally absorb the credential as if the company itself earned it.
Structured vocabularies reinforce this distinction. Schema.org provides a hasCredential property for a Person or Organization, allowing the credential to be modeled with the entity that actually holds it. That may seem like a technical detail, but it reflects an important communication principle: authority should travel through explicit relationships rather than vague association.
This becomes especially important when people change organizations. If the professional leaves, the historical fact that the person worked there may remain true, but the company should not continue presenting the person’s current credential as if it were a permanent corporate asset. Likewise, an article authored by the professional remains authored by that professional even after employment changes.
A well-structured authority record therefore separates credential ownership, current affiliation, historical affiliation, authorship, and organizational claims. The public can then understand why the credential is relevant without being misled about who possesses it.
This approach also improves maintenance. Verification can occur at the credential record, and all dependent public pages can reference the same verified fact instead of storing inconsistent copies.