Hi all,
Sorry for the delay in getting this out.
Standing Technical Meetup (2025-03-12)
Key takeaways and actions
Validator / Tooling
- Attention was brought to further work on Validation use cases since the last meeting
- A use case centered around checking/ensuring vendor compliance with the standard was discussed.
- It was suggested that the primary use case (post 3.0) is API endpoint validation rather than bulk data
- Reasons for non-compliance and the utility of a pass/fail tool weāre discussed.
- A need to identify or distinguish between types/degrees of pass/fail was identified.
Action:
- @TechnicalCommittee: Please all review the new table linked in the forum post with user stories. We have two questions, and only the first is important now:
-
Is this user story clear and precise?
a. If not, can you offer a clear, concise alternative suggestion? -
(Once weāve landed on the story formulation ā ) How important is it? Letās start on a 5 point scale of ā
a. Need to have this
b. want to have this
c. nice to have this
d. Donāt care about this
e. This should not be built under any circumstances
Proposal to add extra metadata to API feeds
- The approach set out in the proposal is supported (with the addition of some definitions).
- It was then agreed that thereās a need to distinguish between the source of the feed (provenance) and responsibility for the data (stewardship).
Actions:
- @devin: To Vote on the proposal
- @kathrynods: Add definitions for publisher/developer in the proposal
- @kathrynods: Write a ticket for publisher metadata at a record level
Approval and implementation process
- No objections to the use of google forms to vote
- No objections to ODS deciding on an approach to implementation (batching vs standalone upgrades)
Action
- @kathrynods: Move from the ārevision and consensusā to āimplementationā phase once all votes are cast.
Handling Confidential Addresses in HSDS 3.0
- The committee discussed various aspects of privacy/confidentially that were not included in the 3.1 proposal.
- It was agree that due to the complexities and nuances of the subject a dedicated conversation with a broader range of stakeholders is needed to take this froward.
Action
- @TechnicalCommittee is anyone willing to take the lead on this. (If not, GB will take this on after the federation conversation)
- TBD (see above): Setup a separate/dedicated conversation regarding privacy
Versioning
- Update on changes and deprecation of V2.0 documentation
- Backwards compatibility considerations discussed but agreed not be an issue
Action:
- @kathrynods: Final post in the forum and GitHub.
UK Updates
- Update on progress and testing of the UK validator, website and dashboard. Due to launch on 24th March.
- Discussed ways to test other profiles to determine its utility beyond a UK context once live.
- Over the next 6 months there will be work to support, maintain and iterate, align with international group and support UK engagement.
Action
- @MikeThacker: To keep the group updated on further developments
Demo of Taxonomy/Terminology Alignment Tool
- Mike has created a video showing how Info loom Networker relates to Open Referral and how it āProvides the basis for something which somebody might want to develop into a full-blown tool, for both maintaining local taxonomies in a local context and maybe also national taxonomies which can be used for data thatās aggregated from multiple sourcesā
- Unfortunately, we are not in a position to fund the development of this tool
- GB is also connected with another similar tool Open Concept Lab
Resource Data Federation Discussion
- We discussed how a broader discussion around federation could be structured and organized
- This has been scheduled for Tues 3/25 at 11a Eastern
Action:
@everyone: Anyone interested in getting involved with this can reach out for an invite and/or submit questions to shape the agenda.
See -