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
We have a few data sources where we use the Sanction schema to describe non-sanction adverse information, such as a procurement debarment, a criminal record or a regulatory penalty. We should have a new schema type - of which Sanction is maybe a sub-type - for those sorts of facts.
The text was updated successfully, but these errors were encountered:
I've been facing this a bit and agree, that some form of 'fine' 'rebuke' 'penalty' or more broadly 'assessment', but in most cases (due to our work) negative assessment/judgement/resolution ... I feel we are in thesaurus territory.
I guess we just need a name, and figure out if we want Sanction to be a sub-type of it. Perhaps it also helps to clarify what's really broken about this. In my mind, it's the fact that while we use the term "this company got sanctioned for defrauding the World Bank" it's a different meaning of "sanction" than the US gov coming down on them. The broadest thing is Punishment, I guess.
We'll also have to think about a migration story here, allowing our data re-users to adopt the new schema before we remove the old.
We have a few data sources where we use the
Sanction
schema to describe non-sanction adverse information, such as a procurement debarment, a criminal record or a regulatory penalty. We should have a new schema type - of which Sanction is maybe a sub-type - for those sorts of facts.The text was updated successfully, but these errors were encountered: