James (ODSC)

I know this is even older now, but to add you can also do this without the file: bit in the reference. ```` aaa@aaa:~/work/gazpachoking-jsonref$ cat test.json { "cat":"woof" } aaa@aaa:~/work/gazpachoking-jsonref$...

Thanks!

https://github.com/openreferral/specification/commit/b02e50d05dff13103388c0e3b0eda1be669accd7#diff-85b9548466eda4168e93923c9559cce6492b416971e27ed0f0b07e102bb11419 This commit removes it

Ah I see, so we are moving from Eligibility being a free text field to Eligibility being described as a term from the Taxonomy? So if a service had Eligibility...

(BTW fixing https://github.com/openreferral/specification/issues/270 may help make this clearer)

Actually, I'm guessing from the schedule description the intention is that a schedule can be attached to a location, which might run many services. But in that case it seems...

Ok I've had a deeper look and I think this is important. * http://docs.openreferral.org/en/latest/hsds/reference/#schedule * http://docs.openreferral.org/en/latest/hsds/schedules/ # Until & valid_to I'm not clear why we have both set of fields....

> "+05:30" would be 5.5. True, but that's a very unusual representation of offset data that I've not seen before. Most time tools I've seen work in the "+05:30" format,...

Done commit. This changes from GitHub to the files included in the docs. This is important because it means that if the docs use older versions of the API Standard...

This should also be more robust against breakages in the future - the reason this was broken was that the api-spec directory layout had been changed and the docs hadn't.