Purpose Specification

[smartopian]

We have two items related to the purpose specification field, which is an ongoing list discussion in the WG.

1. is to make it extensible - Add Optional field to a single purpose specification field +

Example [service name, purpose (selected from list), Add Option - with a specified list of options]

• . option A - service description
• option B - is a link to the purpose description, this would be a URI
• option C - preference on/off

1. To use a purpose list with an “other” option, that would need to be defined when calling to the API.
   2a. the use of a purpose list would also require it to be posted somewhere. This would need to be addressed in this issue.
   2b. There is space, in the Appendix B, reserved for this list
   2c. Examples for the use of this should be listed and added to the best practice examples, i.e. marketing, newsletters, mail chimp,

(note: this creates an action to create a Best Practice Document on the CISWG Wiki for the MVCR which has purpose specification in it. with examples)