MikeThacker1

I think I was expecting the free text (lesser) alternative to taxonomy terms to still exist for legacy daat and people who haven't (yet) implemented taxonomies. Mike *Mike Thacker** Porism*...

Actually the text on [Applying a taxonomy term to an object](http://docs.openreferral.org/en/latest/hsds/classifications/#applying-a-taxonomy-term-to-an-object) helps a lot. (Although it raises more questions on taxonomies for me.)

In England so far we've annotated a copy of the Tabular Data Format datapackage to denote what is an extension to Open Referral and what, from the extended schema, is...

My view is that the taxonomy_id (alone or combined with the "vocabulary") should be sufficient to be able to link to the full taxonomy/vocabulary maintained outside of the Open Referral...

First I'd like to concur that: - vocabulary and taxonomy are normally seen as synonymous and "Taxonomy" might be a better term to use. I also see the term "list"...

I've raised this as a more general need for taxonomies for multiple types of entity as [issue 208](https://github.com/openreferral/specification/issues/208).

My best use case is a frontline worker wanting to find services of a particular type for with a particular eligibility criterion. From our illustrative API, [this query](https://api.porism.com/ServiceDirectoryServiceBucks/services/?taxonomy_id=OpenEligibility:20023&link_type=eligibility&vocabulary=OpenEligibility&vocabulary=Bucks:keyword&taxonomy_id=keyword:exercise) returns services...

Yes @greggish adding `taxonomy_type` to `service_taxonomy` would be the simplest approach (although the name `service_taxonomy` would then imply a smaller scope for taxonomies than is supported). Regarding @devinbalkind's point on...

@devinbalkind we have these use-cases for applying standardised taxonomies: - aggregating data from several sources into one consistent directory of services - maintaining extra information pertaining to taxonomy terms centrally...

Ahh yes @greggish. I see the [HSDS tabular data package](https://github.com/openreferral/specification/blob/master/datapackage.json) says this is an enumeration of ["active", "inactive", "defunct", "temporarily closed"]. I'll see how that works. I can imagine people...