# 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:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [March 21, 2025, 10:27am UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/63 "2025-03-21T10:27:29Z")

</div>

Hi all,

Sorry for the delay in getting this out.

# Standing Technical Meetup (2025-03-12)

- [Meeting notes](https://docs.google.com/document/d/1SYmsSa_U8uQKZW0zhEq8H6CNttNeWPqP7BAV0HDJa2o/edit?tab=t.0#heading=h.nzjtlht2hdck)
- [Meeting recording & transcript](https://drive.google.com/drive/folders/15OSiMHfdu7kXDyw7h8sQoPp0GqDbWQuB)

## Key takeaways and actions

### Validator / Tooling

- Attention was brought to [further work on Validation use cases](https://forum.openreferral.org/t/validator-and-dashboard-for-hsds-hsda-3-0-and-beyond/415/9)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](https://forum.openreferral.org/groups/technicalcommittee): Please all review the new table linked in t[he forum post with user stories](https://forum.openreferral.org/t/validator-and-dashboard-for-hsds-hsda-3-0-and-beyond/415/9). We have two questions, and only the first is important now:

1. Is this user story clear and precise?  
a. If not, can you offer a clear, concise alternative suggestion?

2. (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](https://forum.openreferral.org/t/proposal-for-3-2-extra-metadata-with-api-feeds/616/7)).
- 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](https://docs.google.com/forms/d/1AEOxC81-2Q2b9kPKf6XQ_8UCX9u27YSFeD_NGjKsiIQ/edit#responses)
- @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](https://forum.openreferral.org/groups/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-iStandUK: To keep the group updated on further developments

### Demo of Taxonomy/Terminology Alignment Tool

- Mike has created [a video](https://www.loom.com/share/e1ef2ff97964403c9d01ddfc8f49f258?sid=c7adebbd-6407-4d39-98b3-012da682255e) showing how [Info loom Networker](https://networker.infoloom.com/)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](https://openconceptlab.org/)

### 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](https://forum.openreferral.org/groups/everyone): Anyone interested in getting involved with this can reach out for an invite and/or submit questions to shape the agenda.

---

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [March 21, 2025, 10:43am UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/64 "2025-03-21T10:43:08Z")

</div>

Things that have progressed since the meeting:

> - @kathrynods: Add definitions for publisher/developer in the proposal

✅ See - [Proposal for 3.2 - Extra metadata with API feeds - #7 by kathrynods](https://forum.openreferral.org/t/proposal-for-3-2-extra-metadata-with-api-feeds/616/7)

> - @kathrynods: Write a ticket for publisher metadata at a record level

✅ See - [Publisher/source metadata at a record level - #3 by kathrynods](https://forum.openreferral.org/t/publisher-source-metadata-at-a-record-level/625/3)

> - @MikeThacker-iStandUK: To keep the group updated on further developments

✅ - [UK website upgrade](https://forum.openreferral.org/t/uk-website-upgrade/626)

---

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [April 7, 2025, 9:31am UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/65 "2025-04-07T09:31:36Z")

</div>

Hi all,

Here’s the proposed agenda for the meeting on Wednesday. Feel free to suggest further items as always.

## Validation

- UK Validator ([Direct link](https://openreferraluk.org/developers/validator) | [Forum thread](https://forum.openreferral.org/t/uk-website-upgrade/626/2))
- Discuss next steps regarding use cases ([sheet](https://docs.google.com/spreadsheets/d/1tszuthH-_xq1vmjOQbUsroGf8R-wScFu6bYhEs9h4eI/edit?gid=482058597#gid=482058597) | [forum thread](https://forum.openreferral.org/t/validator-and-dashboard-for-hsds-hsda-3-0-and-beyond/415/12))

## UK update

- Relevant updates from Mike.

## Confidentiality

- Discuss and establish the scope of this work
- Discuss next steps regarding the [dedicated discussion we agreed at the last meeting](https://docs.google.com/document/d/1SYmsSa_U8uQKZW0zhEq8H6CNttNeWPqP7BAV0HDJa2o/edit?disco=AAABedJiA9M)

## Metadata API

- Discuss the problem(s) we want to solve?
- Agree next steps

## How-to documentation for database deployment

- I.e. Airtable: we have [documentation](https://docs.google.com/document/d/1qwNU8Jp8oMLG5yKc8V3tRgxdVI1ezXms3dKnNA1Cdcc/edit?tab=t.0) now for deploying the 3.1 compatible Airtable.
  - Do we want to check this documentation to see if it’s worth including (or revising to include) in our docs site?
  - Do we want other how-to documentation for alternative methods of deployment (i.e. SQL dump) (as a complement to or alternative to Airtable)
  - Thread [Potential for using AirTable for small API feeds](https://forum.openreferral.org/t/potential-for-using-airtable-for-small-api-feeds/622/5)

## Federation discussion

- Feedback from those that took part ([Forum thread](https://forum.openreferral.org/t/resource-data-federation-lets-discuss/601/9)| [Notes](https://docs.google.com/document/d/1SYmsSa_U8uQKZW0zhEq8H6CNttNeWPqP7BAV0HDJa2o/edit?tab=t.blv4nr28fynh#heading=h.r2n823x9mssj))

## LLM check-in

- Check-in on this and discuss documentation format ([Forum thread](https://forum.openreferral.org/t/hsds-schema-summary-in-markdown-for-llm-inference/627/3))

---

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [April 15, 2025, 11:40am UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/66 "2025-04-15T11:40:24Z")

</div>

# Follow-up: Standing Technical Meetup (2025-04-09)

- [Meeting Notes](https://docs.google.com/document/d/1SYmsSa_U8uQKZW0zhEq8H6CNttNeWPqP7BAV0HDJa2o/edit?tab=t.blv4nr28fynh)
- [Video and transcript](https://drive.google.com/drive/folders/1VJ-ruldKRm5OCe0iwgnyy7X2yBoOa1v1?usp=sharing)

# 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-iStandUK 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.

---

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [May 12, 2025, 9:26am UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/67 "2025-05-12T09:26:50Z")

</div>

Hi all, see the proposed agenda for our meeting on Wednesday. Input and suggestion welcome as always:

## Agenda

### Validator

- UK validator update
  - Hear from developer (David)
  - Testing results

- User stories update ([forum post](https://forum.openreferral.org/t/validator-and-dashboard-for-hsds-hsda-3-0-and-beyond/415/14); [spreadsheet](https://docs.google.com/spreadsheets/d/1tszuthH-_xq1vmjOQbUsroGf8R-wScFu6bYhEs9h4eI/edit?gid=482058597#gid=482058597))

### Federation

- Updates from [breakout session](https://docs.google.com/document/d/1SYmsSa_U8uQKZW0zhEq8H6CNttNeWPqP7BAV0HDJa2o/edit?tab=t.blv4nr28fynh#heading=h.czrrkpv9c6ih)
  - Confidentiality

- Metadata API
  - Relevant updates from[the breakout](https://docs.google.com/document/d/1SYmsSa_U8uQKZW0zhEq8H6CNttNeWPqP7BAV0HDJa2o/edit?tab=t.blv4nr28fynh#heading=h.czrrkpv9c6ih)
  - Data guides
    - [Initial proposal](https://docs.google.com/document/d/1QCBn_oDgH5Wh9FZmCuhPNDhLlPa1LqIhAH6yhRbfyxQ/edit?tab=t.mfc89kmfdrhe#heading=h.ye0dggmm63xe)
    - [Request for comments on the forum](https://forum.openreferral.org/t/request-for-comments-data-guides-for-hsds/643)
    - What would be useful to include in a template?

### How-to documentation and tutorials

- for database deployment
  - Further discussion/decisions ([notes from the last meeting for reference)](https://forum.openreferral.org/t/standing-technical-meetups/454/66#p-1607-how-to-documentation-for-database-deployment-7)

- What other documentation might be helpful?

### FYI notices

- Merging - [Adding information about the MARC 21 standard #552](https://forum.openreferral.org/t/adding-information-about-the-marc-21-standard-to-the-docs/637/1)
- Github issue - [Consider using OpenAPI tags to define required endpoints inside the OpenAPI file #556](https://github.com/openreferral/specification/issues/556)

---

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [June 4, 2025, 10:29pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/68 "2025-06-04T22:29:54Z")

</div>

# Proposed agenda for Standing Technical Meetup (2025-05-11)

Agenda item suggestions welcome as always.

- **UK Validator**

- **[Validation use cases](https://docs.google.com/spreadsheets/d/1tszuthH-_xq1vmjOQbUsroGf8R-wScFu6bYhEs9h4eI/edit?gid=482058597#gid=482058597)**

- **Federation**

- **Metadata API**

- **How-to documentation and tutorials**

- **Confidentiality**

- **FYI notices**

---

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [July 8, 2025, 8:08am UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/69 "2025-07-08T08:08:10Z")

</div>

# June Standing Technical Meetup Follow-up

Hi all,

Sorry for the delay posting this summary but please see below for a summary of key discussion points and actions from the June the meeting.

Also, the meeting recording and transcript can be found [here](https://drive.google.com/drive/folders/1ItHsItpoia-w2w49ZNiXCJ1_B7eUPh1U?usp=sharing)

## Key Discussion Points & Actions

### Metadata & Data Attribution

- KL described a federated system with four source applications and varying data-editing capabilities. KL’s overview of the problem space aligns with the concept of “Data Lineage”; recording and understanding how various fields are the result of operations on other datasets.
- Record-level metadata is critical: it includes the source database, steward organization (via unique three-letter codes), public URLs, and change request links.
- Importance of flexibility in metadata systems due to vendor constraints and lack of standard APIs

#### Registry of Data Sources

- A historical system of unique organization codes allows tracing data origins and enforcing accountability.
- There’s strong community interest in a formal registry of data sources, potentially aligning with federation goals.

#### Record Ownership & Permissions

- Systems need to accommodate many-to-many relationships between data contributors and records.
- Legal agreements often define these relationships and their respective responsibilities.
- Traceability at both feed and record level is important.

#### HSDS Schema Challenges

- The HSDS schema lacks a primary “top-level object” for its records (e.g. every record is a service) and is instead normalized, making it hard to anchor metadata in the model; does it go everywhere or only on a few of the object types?
- Discussion leaned toward adopting per-record metadata, inspired by Katherine’s model.
- Possible evaluation of whether a “parties array” to define organisational roles and relationships would be suitable for HSDS.

#### Data Guides

- Considered complementary to metadata but don’t address the original problems that KL highlighted.
- Provide human-readable guidance for data imports and implementation.
- KL clarified that they’re not a harmful endeavor and wouldn’t work in contradiction to what she’s discussing; but rather helpful for standardization and interpretation.

#### UK Validator

- The UK validator supports HSDS profiles and can flag warnings/errors.
- Differences in how errors are prioritized may stem from compliance pressures.
- Open source and adaptable: instances can be customized to treat all issues as errors, if desired.

#### Use-Case Driven Validation

- Proposal: validation criteria could vary by use case (e.g., replication vs. search).
- A research project is underway to develop a use case description specification, which could help shape this approach.

#### Core Concepts

As highlighted by Matt Marshall:

- Who owns the data feed?
- What does the data look like (human-readable)?
- How to process the data for standardization (machine-readable)?

#### Actions & Follow-ups

- SY to share API key and ensure proper Swagger setup.
- MM to research record-level metadata strategies and validation mechanisms.
- GB & MT to follow up on validator testing with Michigan 211.
- Group to discuss Diataxis documentation framework and revisit federation/how-to/confidentiality next time.
- Poll on validation use case value to be an agenda item for the next meeting.

---

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [July 8, 2025, 8:10am UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/70 "2025-07-08T08:10:26Z")

</div>

# Proposed agenda for tomorrows meeting (2025-07-08)

As always, please feel free to suggest further items either here or at the start of the meeting.

### Main item:

- Collective review of [user stories](https://docs.google.com/spreadsheets/d/1tszuthH-_xq1vmjOQbUsroGf8R-wScFu6bYhEs9h4eI/edit?gid=482058597#gid=482058597) values
  - Poll
  - In-situ review?

### Other items:

- Adding new committee members –
  - Nominating Jen Abels from Inform USA

- UK updates
  - Validator testing
    - Skyler and Michigan API testing
    - Matt’s experiments with running ORUK validator locally

  - Secretariat

- Metadata API / Data Guides
- Federation
- Confidentiality
- How-to documentation and tutorials (Diataxis)

### FYI’s

- Merging - [Adding information about the MARC 21 standard #552](https://forum.openreferral.org/t/adding-information-about-the-marc-21-standard-to-the-docs/637/1)
- Review - [Consider using OpenAPI tags to define required endpoints inside the OpenAPI file #556](https://github.com/openreferral/specification/issues/556)

---

<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 14, 2025, 2:25pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/71 "2025-07-14T14:25:40Z")

</div>

We need to reschedule the meeting on August 13th, because at least one committee member can’t attend and I think we’ll need as many committee members as possible in order to review and decide on two nominations for new members.

Let’s start looking for availability at the same time (11a Eastern) – any other day that week, but let’s aim for Thursday. @klambacher @MikeThacker-iStandUK @SarahP @devin @Dan-ODS @skyleryoung [@TechnicalCommittee](https://forum.openreferral.org/groups/technicalcommittee) **are you able to do Thursday 8/14 at 11a Eastern, and/or that time at any other day that week**?

---

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [July 15, 2025, 11:40am UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/72 "2025-07-15T11:40:28Z")

</div>

# 2025-09-06 - Meeting follow-up (summary & actions)1`

## [Recording and Transcript](https://drive.google.com/drive/folders/14yoTrYolcNjFwNN4jLJ--grs73csyUro?usp=drive_link)

## Membership Updates

- Sarah has stepped back from the group.
- Jen Abels from Inform USA is a strong candidate to join.
- Kate is unavailable on Wednesdays over the summer.
- Devin’s attendance is limited due to new fatherhood.
- The group needs a process for outreaching to new prospective members, nominating them, and getting approval from Kate, Skyler, and Mike.

## Provenance and Open Lineage

- Addressing many-to-many data exchange requires a more complex approach to provenance.
- Dataset/API-level provenance can be handled via “data guides” (one-to-many publishing).
- Record-level provenance will require specification extensions to accommodate many-to-many sharing.
- OpenLineage is a potential standard for data lineage that warrants further investigation.
- We must evaluate OpenLineage based on its usability/complexity, adoption by others (for interoperability benefits), and its scope (e.g., does it include a registry of API publishers and data sources?).
- There’s a need for clarity on the scope of a “registry of data sources”: Is it for HSDS API publishers, individual data sources, or both?

## Validation

- The UK validator was initially designed for non-normative feedback based on political context and to work only against open API feeds.
- However, the validator tool is more modular than initially thought, with a separate backend that provides a validation service.
- The UK validator requires modifications to:
  - accept an API key for validating non-open APIs
  - load in schemas for other Profiles

- Validating HSDS data is distinct from validating an API.
  - While the API is the main method for publication and distribution; there’s a need to validate data and assess its quality before it’s published on an open API.
  - Some implementations will not publish their data as open data at all, so validation tooling needs to account for this.
  - Validating an API is more complex than validating that data is structured correctly, due to things such as parameters etc.

- In other standards, there are three mechanisms for data input to their validator: copy/pasting JSON, providing a URL to data (can be an API response or a download file link), or uploading a file.
  - [360Giving Data Quality Tool](https://dataquality.threesixtygiving.org/)
  - [OCDS Data Review Tool](https://review.standard.open-contracting.org/)
  - [Open Fibre’s validator](https://ofds.cove.opendataservices.coop)

- API validation involves checking that required endpoints exist and each return conformant data as well as determining that the API behaves correctly as it pertains to parameters.
- The most broadly used mechanism for API keys is a bearer token as a header.
- There’s a strong desire to avoid specifying API key formats within the core HSDS specification, instead treating it as non-normative guidance in “how-to” documentation for the validator.
- There needs to be a clear distinction between a “validator” (checking compliance against the specification) and a “data quality tool” or “ongoing online monitor.”: the latter tools can build off of the former, but we should avoid overcomplicating our notion of what “a validator” does.

## Other Items

- Metadata API/Data Guides and Federation remain important topics.
- Confidentiality is a consideration for some implementers who fear competitors stealing open data.
- How-to documentation and tutorials (Diataxis) are recognized as important but are perhaps not a priority in the coming months

## Actions

Dan

- Split out and archive 2024 and 2023 notes
- Consider adding schedule data to a future agenda, potentially with a new proposal or clarification on the balance between simple and complex scheduling.

@bloom

- Nominate Jen Abels from Inform USA for membership.
- Check in with Devin regarding his availability for continued involvement.
- Investigate rescheduling the August meeting to ensure Kate can attend, particularly for new member approvals.

@mrshll

- Matt to continue investigating OpenLineage:
- Understand its scope and how it claims to address data lineage.
- Assess its alignment with Open Referral’s needs.
- Evaluate the “balance of complexity” – is the benefit of adoption worth any added complexity?
- Research who else uses OpenLineage and if there are additional interoperability benefits.
- Clarify the discrete sets of information that make up dataset-level and record-level provenance.
- Discuss the scope of a “registry of sources” to determine if it should include all data sources or primarily API publishers.
- Matt to continue exploring the modifications needed for the UK validator to accept API keys and load full international schemas.
- Matt and Mike to discuss the “app store links” question, including referencing relevant documentation for handling multiple links and considering if the UK profile needs to be rebased from HSDS 3.0 to 3.1. Mike will be sent an email with URLs to the appropriate documentation.
- Ensure how-to documentation for the validator clarifies API key usage as non-normative guidance, separate from the core specification.

@skyleryoung

- Skyler to share swagger / API key with Mike
- Check the additional [user stories 325, 718](https://docs.google.com/spreadsheets/d/1tszuthH-_xq1vmjOQbUsroGf8R-wScFu6bYhEs9h4eI/edit?gid=482058597#gid=482058597)

@MikeThacker-iStandUK

- Check the additional [user stories 325, 718](https://docs.google.com/spreadsheets/d/1tszuthH-_xq1vmjOQbUsroGf8R-wScFu6bYhEs9h4eI/edit?gid=482058597#gid=482058597)

---

<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 15, 2025, 1:12pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/73 "2025-07-15T13:12:36Z")

</div>

Thanks for these notes, @Dan-ODS. A few minor corrections:

First off, I believe the Confidentiality issue is more about enabling certain kinds of data to be excluded from publication (like records about services whose locations are sensitive, and staff contact information).

Also, re Diataxis (wtf is that name) I personally think that developing tutorials and how-to’s is a priority right after the validator! We should consider what kinds of topics might be the highest priority.

And, I don’t know if I said the Committee “needs a process” for nominating new people – i think there is a sufficient process in place, it’s underway – although outreach to new prospective members should be encouraged.

Finally, rescheduling the next meeting is underway – as per [the previous message in this thread above these notes](https://forum.openreferral.org/t/standing-technical-meetups/454/71). Committee members please let us know your availability.

---

<div class="post-metadata">

**Author:** ![klambacher](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/klambacher/32/65_2.png) [@klambacher](https://forum.openreferral.org/u/klambacher)\
**Post date:** [July 24, 2025, 6:17pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/74 "2025-07-24T18:17:48Z")

</div>

Thursday the 14th works for me

---

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [July 30, 2025, 2:01pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/76 "2025-07-30T14:01:32Z")

</div>

> [@Dan-ODS](#):
>
> Check the additional [user stories 325, 718](https://docs.google.com/spreadsheets/d/1tszuthH-_xq1vmjOQbUsroGf8R-wScFu6bYhEs9h4eI/edit?gid=482058597#gid=482058597)

Hi @skyleryoung @MikeThacker-iStandUK ,

Just following up on this. I know you’ve slept since so I’ve dug out some context below:

> ”thinking from resource federation pov, prefer not to support different mechanisms in for HSDS\> I want to put an API endpoint in, provide a key if needed, and hit go. it’ll fetch data and work out whether everything is working. Validating files in a bucket etc. is totally different”

I believe Gregs request to check user stories 325 and 718 was in response this comment from you @skyleryoung

Can you confirm that the need you expressed is sufficiently covered by those user stories?

cc @bloom @mrshll

---

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [July 30, 2025, 2:49pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/78 "2025-07-30T14:49:28Z")

</div>

@bloom

Sorry for the delayed response but @mrshll is on leave w/c 11th and given the topics we plan to cover it would make sense for him to be there?

How about the usual slot the following week (20th Aug)?

Dan

---

<div class="post-metadata">

**Author:** ![MikeThacker-iStandUK](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/mikethacker-istanduk/32/8_2.png) [@MikeThacker-iStandUK](https://forum.openreferral.org/u/MikeThacker-iStandUK)\
**Post date:** [July 30, 2025, 3:28pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/79 "2025-07-30T15:28:49Z")

</div>

I’m afraid 20 August is one of just two days in August that I can’t make. But do proceed without me.

---

<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. |

---

<div class="post-metadata">

**Author:** ![Dan-ODS](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openreferral.org/dan-ods/32/89_2.png) [@Dan-ODS](https://forum.openreferral.org/u/Dan-ODS)\
**Post date:** [August 14, 2025, 3:32pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/81 "2025-08-14T15:32:47Z")

</div>

Hi all,

Here is the proposed agenda for next weeks meeting. Suggestions for further items welcome.

# Aug Standing Technical Meetup (21st Aug)

## **Committee page on the website**

- What should be on it?

## **Validator**

- 
### **ORUK Validator analysis report**

  - [Forum Post](https://forum.openreferral.org/t/technical-report-on-the-oruk-validator/677) / [Report](https://docs.google.com/document/d/1aVIJmZM8W2HfOFHKvUFZnbQVvjz1lDYL0zcSbzZ0N84/edit?tab=t.0#heading=h.65dxwniyyit9)

  - Matt to give brief overview of the document

  - Immediate questions/comments

  - Question: upstream contribute vs fork vs build something

- 
### **User story check-in**

  - Check-in on whether user stories 325 and 718 satisfy the user need expressed [at the last meeting](https://docs.google.com/document/d/1SYmsSa_U8uQKZW0zhEq8H6CNttNeWPqP7BAV0HDJa2o/edit?disco=AAABodFM4co) ([Request via the forum](https://forum.openreferral.org/t/standing-technical-meetups/454/80))

  - Prioritize among user stories not currently achieved by OR UK validator.

## **Investigative report on OpenLineage**

- Summary and discussion [2025-08-07 Technical Report: OpenLineage and HSDS](https://docs.google.com/document/d/1g2h6ukZe4MvtsWxOgZsgwUYcQuCaoloIRcb1uNN9Y9c/edit)

## **Proposals for HSDS 3.2:**

- 
### Current proposals

  - [2025-07-18 Proposal: Marking OpenAPI Endpoints with Tags to Match the Specification](https://docs.google.com/document/d/17doZpFKtpKZQOZhjHnGJCtAI98YXdFm1JqKJvuELeBE/edit)

  - [Proposal: Extra metadata with API feeds](https://docs.google.com/document/d/1jy1wOShCNypl7OqAIuMTc80blxTBUn5_6YhjvOyF6LI/edit)

  - [Open Referral’s HSDS Publication Policy – Proposal + Template](https://docs.google.com/document/d/1QCBn_oDgH5Wh9FZmCuhPNDhLlPa1LqIhAH6yhRbfyxQ/edit?tab=t.mfc89kmfdrhe#heading=h.ye0dggmm63xe)

- 
### **Questions for the committee:**

  - Open to a vote on them in the next month?

  - Is this sufficient for starting a MINOR upgrade to HSDS 3.2 or would we want to wait to accumulate more actions/proposals?

## **Prioritizing roadmap for the rest of the year:**

Level of urgency?

1. 3.2 proposals \> implementation

2. Data guide implementation

3. Validator adaptation

**AOB (any other business)**

---

<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:** [September 9, 2025, 4:28pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/82 "2025-09-09T16:28:38Z")

</div>

Hi folks – we have an agenda for tomorrow’s Committee meeting [here](https://docs.google.com/document/d/1SYmsSa_U8uQKZW0zhEq8H6CNttNeWPqP7BAV0HDJa2o/edit?tab=t.blv4nr28fynh#heading=h.ny5wml5ieqhg). I’m pasting the high level version below.

Please note that we agreed to vote on the three current proposals on the table – @mrshll just posted about them in this forum, please go review (you can find them linked in the agenda doc as well) and be ready to either approve or express the reason you don’t approve.

see below and linked above, and let us know if you have any questions!

**Agenda:**

- Committee business: Jen, Sasha

- HSDS upgrades: vote on proposals, consider 3.2

- OpenLineage – hear from Matt on his findings

- Validator – discuss with Steve

---

<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:** [September 19, 2025, 2:12pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/83 "2025-09-19T14:12:14Z")

</div>

Hi folks – [Notes from the last meeting are here](https://docs.google.com/document/d/1SYmsSa_U8uQKZW0zhEq8H6CNttNeWPqP7BAV0HDJa2o/edit?tab=t.blv4nr28fynh#heading=h.ny5wml5ieqhg). Below are the key items of business between now and the next Technical Committee meeting on October 8th.

First, please [review the Validator Technical Requirements via this post in the forum.](https://forum.openreferral.org/t/hsds-validator-technical-requirements/736/5)

Second, please review @mrshll’s research on **OpenLineage as a standard for provenance specs:** [2025-08-07 Technical Report: OpenLineage and HSDS](https://docs.google.com/document/d/1g2h6ukZe4MvtsWxOgZsgwUYcQuCaoloIRcb1uNN9Y9c/edit?tab=t.0) – you can [discuss in this thread](https://forum.openreferral.org/t/technical-report-on-openlineage/680/1).

Those are the two significant pieces.

There are other issues popping up in the notes and in other recent fora threads, which are not as pressing but rounding up here for your attention:

- Normalized email object: [Normalized Email object](https://forum.openreferral.org/t/normalized-email-object/741/1)
- [Ranking contact methods across method types](https://forum.openreferral.org/t/how-do-we-rank-contact-methods-across-different-method-types/742/1)

Let us know if you have any other questions or suggestions for the agenda! I will invite @sasha, our new committee Secretariat, to co-facilitate with @mrshll.

cc @devin @MikeThacker-iStandUK @klambacher @JenAbels @switzersc

---

<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:** [October 3, 2025, 9:34pm UTC](https://forum.openreferral.org/t/standing-technical-meetups/454/84 "2025-10-03T21:34:32Z")

</div>

Hi folks - note that **we have shifted our Technical Committee schedule to the second Thursday of each month, at 11a Eastern**.

If you are not on the Technical Committee but interested in sitting in on a meeting, let me know and I’ll add you to the calendar.

[Previous page](https://forum.openreferral.org/t/standing-technical-meetups/454.md?page=3)

[Next page](https://forum.openreferral.org/t/standing-technical-meetups/454.md?page=5)
