issue-241 descriptively defining some qualifiers

I've been talking with Susan and Rob and Chris P. about some text regarding issue-239. This text is in progress and any mistakes in it are surely mine, but I thought it was worth getting something out to the group since we might want to discuss it on today's call.

Thanks,
Nick

This text would be added after the definition of the qualifiers field in the tracking status resource section. Comments and improvements most welcome.

> While different compliance regimes can define requirements and uses of certain qualifiers, and a particular compliance regime may not require the use of qualifiers for particular activities to be permitted, the following qualifiers have the defined, descriptive meanings.
> 
> "1": the resource is designed for usage in first-party contexts
> "3": the resource is designed for usage in third-party contexts
> 
> "f": tracking data collected about this resource may be used for frequency capping purposes
> "l": tracking data collected about this resource may be used for financial logging purposes
> "s": tracking data collected about this resource may be used for security and anti-fraud purposes
> "d": tracking data collected about this resource may be used for debugging purposes
> "m": tracking data collected about this resource may be used for audience measurement purposes