Rob Redpath

@greggish I've reordered the menu as we've discussed. Please can you review [this branch on ReadTheDocs](http://docs.openreferral.org/en/add-project-docs/) and let me know if there's any other changes that you'd like - and...

@greggish @odscjames eligibility is now handled by the other_attribute mechanism, with `link_type` = `eligibility`. I can see how that's not clear from the docs, so that's something we should improve...

@MikeThacker1 @greggish HSDS 2.0 supports use of informal tagging or free text, because it doesn't specify what a `taxonomy_term` should be - you can just have a row in `taxonomy_term`...

(I clearly need to update http://docs.openreferral.org/en/latest/hsds/classifications/ with an example!)

Hi @japrogramer Thanks for this; we're addressing the missing unique constraints in the [2.0 upgrade](https://github.com/openreferral/specification/pull/219) The mention of UUIDs there is confusing; I've removed it in the 2.0 draft as...

MINOR for publishers; risk of breaking if data consumers rely on only values in codelist

Obviously, doing this by hand makes sense for now, but I don't think it'd be hard to automate. I doubt I'll get a chance to do it any time soon,...

@MikeThacker1 is this something you'd be able to reflect on wrt your work in England?

I'm bringing this into scope for the Spring 2020 upgrade as I'm hoping that we can agree on a mechanism by which we can describe and share the additional information...

This has started in a very informal way in http://docs.openreferral.org/en/latest/hsds/extending/ I've steered clear of suggesting technical mechanisms, because I think that it's more important for people to share their work...