Use datatype string for profile:gender property #71
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Change the datatype for the profile:gender property to string. Previously, the datatype was enum(male, female), which made it effectively impossible to encode genders other than male or female. In the EU, you are required by law (Article 16 GDPR, Right to rectification) to correct incorrect information. Due to the standard, it was either not permitted to encode gender in some jurisdictions (e.g., Germany), where more genders than male or female are legally recognized, or you needed to ignore the standard. The decision to use a string, instead of expanding the enum to include more gender descriptions, was based on the fact that different jurisdictions legally recognize different genders. To keep the standard simple, this implementation was chosen. Also, not explicitly mentioning non-binary genders will make this change less prone to attacks from TERFs, Trump supporters, or other assholes. This is, first and foremost, a political commit. Any technical content you encounter is a byproduct of political acts and should be considered as such.
This comment was marked as duplicate.
This comment was marked as duplicate.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change the datatype for the profile:gender property to string. Previously, the datatype was enum(male, female), which made it effectively impossible to encode genders other than male or female.
In the EU, you are required by law (Article 16 GDPR, Right to rectification) to correct incorrect information. Due to the standard, it was either not permitted to encode gender in some jurisdictions (e.g., Germany), where more genders than male or female are legally recognized, or you needed to ignore the standard.
The decision to use a string, instead of expanding the enum to include more gender descriptions, was based on the fact that different jurisdictions legally recognize different genders. To keep the standard simple, this implementation was chosen. Also, not explicitly mentioning non-binary genders will make this change less prone to attacks from TERFs, Trump supporters, or other assholes.
This is, first and foremost, a political commit. Any technical content you encounter is a byproduct of political acts and should be considered as such.