Data sensitivity tagging for telephone numbers (and possibly other directory info)

Summary of outcomes for Data Standard 2.1

• Problem Addressed: An indication is needed that personal data (address, telephone, and email) may not be published.
• High-level Reasoning: Some personal data is sensitive and should not be provided in rosters.
• Changes Made: Added optional boolean DoNotPublishIndicator to Address, Telephone, and ElectronicMail common types

Original ticket description follows:

Michigan has a need to identify telephone numbers (and possibly addresses) as collected but "unlisted". There is an "unlisted" enum value in the TelephoneNumberType enumeration, but that means one cannot mark a phone number as a mobile number and also unlisted. It may be necessary to look at data sensitivity tagging standards, and identify a mechanism to tag a limited number of data elements as public, non-public, restricted, etc. Also, social sites that protect profile information at different levels of sensitivity might be a decent model (visible to: only me, school, district, region, state, public).

Example use case: teachers want to provide their phone number for SMS alerts from the alert system, but they want to list an entirely different number (e.g., their classroom number) for district/parent/etc. inquiries), and it's important to know that the number is a mobile number (so "unlisted" is not a good solution).