You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Person.identifier was added in #427 in pursuit of alignment with the OCDS Beneficial Owners extension. However, we omitted adding a disclaimer like the one in the extension documentation:
to use this extension, the laws in your jurisdiction must permit the publication of personal identifiers.
I think that we should add a similar disclaimer to the reference documentation for the Person subschema.
To reduce the chances of implementers unnecessarily publishing personal identifiers, I think that we should also include a clarification that Person.identifer is only relevant in the context of Organization.beneficialOwners (the Person subschema also appears in the context of Organization.people, relating to the CoST IDS element 'Contract officials and roles', for which personal identifiers are not relevant).
At the same time, we can update the changelog entry for #427, which presently only mentions Organization.beneficialOwners, to include Person.identifier and the other fields added to the Person subschema.
Person.identifier
was added in #427 in pursuit of alignment with the OCDS Beneficial Owners extension. However, we omitted adding a disclaimer like the one in the extension documentation:I think that we should add a similar disclaimer to the reference documentation for the
Person
subschema.To reduce the chances of implementers unnecessarily publishing personal identifiers, I think that we should also include a clarification that
Person.identifer
is only relevant in the context ofOrganization.beneficialOwners
(thePerson
subschema also appears in the context ofOrganization.people
, relating to the CoST IDS element 'Contract officials and roles', for which personal identifiers are not relevant).At the same time, we can update the changelog entry for #427, which presently only mentions
Organization.beneficialOwners
, to includePerson.identifier
and the other fields added to thePerson
subschema.@jpmckinney sound good?
The text was updated successfully, but these errors were encountered: