Neil McKechnie

I'd be willing to provide an example in the future but first want to incorporate all the 1.0 udpates Tim recently published to ensure it is compliant. I have provided...

I like the precision these changes introduce, in general. I do agree that retaining the parent_name and maybe adding parent_id is useful. The current spec calls for including the entire...

@timgdavies , I agree with @klambacher. I prefer your second approach of "taxonomy_link". But since 1.1 is approved I would think this would need to be in a future rev...

Upon further thinking, we should consider creating a new object type that is well-structured for these kinds of geographical hierarchies and can be a child of the service object.

Excellent points @klambacher and you and I have had many great conversations on this topic. But we do need to find some approach that maximizes interoperability. For that reason I...

Yes I've seen @klambacher 's geographic taxonomy for Canada but it does have the "issues" (from my perspective, sorry Kate) I note above. Also I don't believe it is grounded...

Thanks @greggish but this fails the "colloquially known" test. No one knows what census track they live in, except the tiny percentage of people who work with them. Or am...

All valid points Kate. I think the decision for HSDS is going to come down to "what maximizes interoperability between heterogeneous systems" and "what is the most flexible structure for...

@timgdavies thank you for the very thoughtful response. Your recommendation is certainly getting there but you've essentially chosen the approach the venerable @klambacher has put forward, which is a hierarchically...

Hey this is pretty interesting @JordanLyons . Have you looked closely to see to what degree it has a similar data structure and elements as HSDS?