# Standing Technical Meetups

**URL:** <https://forum.openreferral.org/t/standing-technical-meetups/454>\
**Category:** Technical\
**Created:** [November 6, 2023, 10:39am UTC](https://forum.openreferral.org/t/standing-technical-meetups/454 "2023-11-06T10:39:49Z")\
**Posts on this page:** 1\
**Showing post:** 80

<div class="post-metadata">

**Author:** ![bloom](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/bloom/32/103_2.png) [@bloom](https://forum.openreferral.org/u/bloom)\
**Post date:** [July 30, 2025, 3:47pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/80 "2025-07-30T15:47:51Z")

</div>

[Note: this is about the validator user stories referenced above – sorry to be sorting out schedule and agenda issues in the same thread at the same time; we may want to break these into separate threads]

Here are the user stories from the spreadsheet referenced by @Dan-ODS above – we want to see if we can get better language here, I sketched it out on the spot and I think we can probably make it better. @MikeThacker-iStandUK @skyleryoung can we capture the actions and intended results in clearer ways?

| **325** | **publisher** | perform a full validation of my open API endpoint | ensure my API feed is publishing data that is compliant with the HSDS API. |
| --- | --- | --- | --- |
| **718** | **publisher** | perform a full validation of my key-required API endpoint | ensure my API feed is valid before I publish an open feed, use in production, etc. |

---

_[View the full topic](https://forum.openreferral.org/t/standing-technical-meetups/454)._
