Follow-up: Standing Technical Meetup (2025-04-09)
Discussion points and actions
UK Update
- New UK site and validator is live and supports original UK version 1 (JSON) and 3.0. * Stricter than previous so things are failing that weren’t before.
- Access to beta development of the tool for testing. Skyler has an endpoint that can be used.
- TPXimpact contract has been extended for 6 months.
- They are hoping for closer alignment and knowledge sharing with the global community.
- Feedback on the ‘crude export to spreadsheet’ tool is being used to revamp it and an MVP for a potential new tool is being mapped out.
Actions
- @skyleryoung to provide endpoint and API key
- @MikeThacker to check with UK if able to test full HSDS endpoint with API endpoint in dev
- @bloom @skyleryoung to discuss a blog post on UK progress
Validator use cases
- Discussed the distinction between schema and data compliance.
- Data quality use cases raised. Determined that these have been covered within the existing use cases.
Actions
- @mrshll (others are welcome) to meet with Greg and Sasha to input on use cases
- @skyleryoung to input on the offline validation user stories
Confidentiality
- Discussed specific use cases i.e. DV shelters and generalized use cases i.e. privacy and permissions
- Considered a framing question for a dedicated session and how this related to consent and liability considerations.
Action
- @bloom to put out a forum post with an invite to a dedicated session
Metadata API
- Disucssed David’s work tracking extensive metadata and potential scalability and efficiency concerns.
- Identified a need to feed this Skyler’s technical insights into ongoing strategic discussions about effective federation and move Katherine’s metadata proposal forward.
- Feedback from David is that the current metadata table is quite robust/flexible.
- Discussed the potential for guidelines on how to use the metadata table rather than change the specification.
- Skyler suggested an extension for multi-tenant architecture
Action
- @bloom to check-in with @klambacher and get her input on provenance
How-to documentation for database deployment
- Airtable documentation will not be added to the main documentation as implementation details are very specific and cannot be standardized.
- Potential for tutorials or how-to-documentation for alternative methods (e.g., SQL dump, PHP/Python library) to help get people started. But not for providing implementation-specific details.
- Matt shared knowledge on how other standards approach this. Generally with a strict line around reference documentation, maybe a tools library which includes publishing and development tools and then they either use their blog or website where they provide guidance on how to bootstrap a system that speaks their standard.
- Agreed there’s a demand for solutions to help small organizations that can’t afford large build-outs.
- A resource information exchange layer was proposed for small organizations to trade data using plug-and-play solutions.
- Raised that concept of a messaging platform needs further discussion.
- Acknowledged the need for deploying modular datasets with exchange infrastructure, which is a bigger issue than just documentation.
Action:
- @Dan-ODS Table for next meeting with a view to deciding whether we agree on any concrete actions
Rendering documentation in Markdown – for LLMs – is this useful?
- Docs already in markdown but presented in HTML. No action required.