Standing Technical Meetups

Technical
42

Hi all,

Proposed agenda items for the meeting next week:

  • UK Update: Update on UK Local government work including upgraded Validator & Dashboard and planned meeting.
  • Approving 3.1 proposals: Discuss the process for committee approval. Request from ODS to be in a position to begin implementation by close of business 25th September (at the latest), so that Matt has time to complete the work before heading off on 6 months parental leave. Related forum post.
  • Events: Discuss the Add and events schema proposal with a view to deferring this to a future upgrade. Related forum post.
  • New Channel: Access, usage and the purpose of the new Technical Committee channel and its relationship to the standard governance process.
  • Charter: Feedback on Greg’s proposed changes and moving towards approval.
  • Committee engagement: What does this look like going forwards (in practice) when it comes to processing new issue and remaining issues. Some thoughts from me in this issue #508 (the first created since we formalised the committee).

As always, feel free to suggest others.

Dan

43

Might we have a couple of minutes on “documenting profiles” please?

44

Here are the notes and recording of the meeting on the 14th Sept.

Key Takeaways:

  1. UK Local Government Updates:
  • Upgraded Validator & Dashboard released; testing and meeting planned.
  • Cross-Gov Steering Committee setup for cross-department sharing of service information.
  • Looking for volunteers to test the upgraded Validator and API feeds.
  1. Validator Development & Usability:
  • Built in .NET (core), currently UK-based but could be expanded for broader use.
  1. Documenting Profiles:
  • Governance/proposal process must be followed for changes.
  • Public proposal documents should be added to the change log for transparency.
  1. 3.1 Proposal Approval:
  • ODS aiming to implement by 25th September for Matt to complete work before parental leave.
  • Community feedback requested on approval process and event schema proposal.
  1. Events Schema Discussion:
  • Interim guidelines proposed, focusing on disambiguating usage.
  • Community engagement sought for feedback on schedules vs. events.
  1. New Technical Committee Channel:
  • Open for everyone to view, but only committee members can post.
  • Used for standard governance communication.
  1. Charter Feedback & Approval:
  • Updates made to the charter based on feedback, including details on dissolution and removal procedures.

Actions:

  1. UK Validator & Testing:
  • Action: Recruit volunteers to test the upgraded Validator and API feeds.
  1. 3.1 Proposal Approval:
  • Action: DS to create a poll/form to gather committee approval for the 3.1 proposals.
  1. Events Schema Discussion:
  • Action: KL and others with relevant knowledge to contribute via the forum post.
  • Action: SY to request MT to provide feedback on defining schedules/hours for services and disambiguating events.
  1. Charter Feedback:
  • Action: Consider creating a form/survey to gain sign-off on Greg’s proposed changes to the charter.
45

Done - Please vote here

Done - Please vote here

Reminder - @klambacher Forum post is here

46

Hi all,

Proposed agenda for the next meeting on the 8th of October. As always, feel free to suggest further items.

Draft Charter

  • Approval Status: Poll results
  • Next Steps: Consider where we need to communicate/publish/update regarding this.

UK Update

3.1 Update

  • Poll responses: For future reference, was it unreasonable/unrealistic for us to expect responses in the allotted timeframe?
  • Approval Status: Poll results
  • Next Steps: ODS to proceed with the work itself.
  • Revision to proposal “Add a dedicated URL schema”**

Committee Engagement

  • What does this look like (in practice) going forward when it comes to processing new and remaining issues?
    • It would be useful to clarify how we plan to collaborate on this before Kathryn addresses the issues backlog.
    • Some thoughts from me in Issue #508 (the first issue created since we semi-formalised the committee).
    • Devin’s comment in the issue

Documenting Profiles

  • Any relevant updates.

Events/Schedules

  • Forum Post
    • Updated by Skyler, Mike, and Drew Whatley since our last meeting.
    • Reminder to kate@kclsoftware.com to provide an update at some point.
    • Next Steps: Discuss the way forward from here.

Technical Committee Channel

  • Did people receive notifications about the 3.1 Poll?
  • Do people know how to access this channel without a direct link? It took me a while to find it (see screenshot).
    1170×610 53.4 KB
47

Just checking in as the meeting is on Wednesday.

Have you reviewed the charter and indicated your approval or otherwise?

Have you reviewed the proposed 3.1 issues and polled on your approval for them?

Please let us know if you have any other questions or suggestions for the agenda!

NB: I’m cc’ing some people by email, to confirm that you’re receiving these forum messages appropriately. If you’re not, let me know and we can troubleshoot.

48

Hi all,

Here’s the proposed agenda for our meeting on November 13th.

Please comment with updates or suggest additional items before the meeting.

Committee Charter

3.1 update

UK Update

  • Relevant updates from Mike

Validator Use Cases

Events/Schedules

Profiles

Review Project Board

49

Hi all,

Proposed agenda for this weeks meeting. Suggestion for further items welcome.

3.1.1

Validator document consolation

UK update

  • Update on the UK meeting and any other updates

Support Publisher information in the API

Backlog review

50

Regarding Support Publisher information in the API in the backlog, I posted this in the Extra metadata with API feeds forum thread linking to MBT10038 - Use cases for extra metadata with API feeds.

I’d appreciate discussing that. @klambacher might want to take a quick look if she has time before the meeting.

51

Added @MikeThacker - Thankyou

52

Standing Technical Meeting 11-12-2024 - Key Takeaways and Actions

UK Update

  • Positive reception of Greg’s presentation with UK stakeholders.
  • Proposals for a two-year Standard management plan are pending approval.
  • NHS Standards contact returning from maternity leave is a promising development.
  • SY has a testing endpoint available.
  • Actions:
    • MT to link SY with appropriate UK contacts
    • MT to setup a conversation between SY (and his CTO) and UK tech people regarding the international schema and validation needs

International Engagement

  • GB is engaging with stakeholders in France and Australia, fostering international collaboration.
  • Actions:
    • GB to consider how best to engage international stakeholders and networks within the forum.

Validator Document Consolidation

  • User stories spreadsheet has been developed but needs some further consolidation and refinement.
  • Still unsure if there are meaningfully different user groups to consider and orientate around.
  • Actions:
    • Sasha on to consolidate the sheet further where possible.
    • GB, S, MT and SY to get together to consider user groups, refine and develop user stories.

Support Publisher Information in the API

  • Extra metadata for API feeds is being reviewed (see related GitHub issues #508 and #524).
  • Actions:
    • KL to review the current proposal and provide input.
    • DS to email KL the relevant details.

Backlog Review

  • ODS-related work paused until the new year.
  • Opportunity to flag or discuss pressing backlog items in the interim.
  • Actions:
    • Committee flag anything that may need attention in the near term
    • ODS will review, tag and summarise issues in the new year

Community Survey

  • Blog post about the survey has been published.
  • Looking to get more engagement
  • Actions:
    • GB consider adding the survey/blog to the website
    • All - Give names of those it would be work GB contacting directly
53

Hi all,

Apologies this is very last minute due to Xmas leave:

Backlog Review:

Suggested documentation updates - would these be useful?

UK Update:

  • MT on leave
  • Actions from last meeting:
    • MT to link SY with appropriate UK contacts
    • MT to setup a conversation between SY (and his CTO) and UK tech people regarding the international schema and validation needs

International community

  • Any relevant updates on Australian / French engagement
  • Plans to manage this within the forum?

Validator Use Cases

  • Update on Sasha’s great work since the last meeting
  • Any updates/progress on the questions raised at the last meeting:
    • ‘Who are the users (can we categorise or sub-divide?)
    • Are there meaningfully different types of users?’

Support Publisher information in the API

  • KL has given her input in the form thread
  • Agree next steps (if possible in Mike’s absence?)

Community survey

  • Update on outreach plans.
54

Thanks @Dan-ODS. I suggested some minor revision in the doc, and I’d also like the technical committee to review this proposed approach to transforming data here via @CheetoBandito

1 Like
55

Hi all,

Please see the proposed agenda for meeting next Wednesday.

There a few things we’d appreciate people look at prior to the meeting if possible (see emboldened).

Agenda:

  • UK update

  • Validator features

    1. Full vs Partial validation – what do we mean?
    2. What kind of feedback do users need at a minimum? What should we aim to deliver?
    • what kinds of information on failure we want?
      • “Description of errors”
    1. Routine validation with automated notification? (see also row 28)
    2. See also rows 56 onward
  • Transformer proposal – is this of interest? What questions do people have?
  • ‘related standards’
56

Thanks, Dan.

For other folks on the Committee, I hope you can at least take a look at the questions about the Validator features (the shorthand bullets here reflect longer comments in the notes under each item in the spreadsheet)

57

Key Actions and Takeaways from the Standing Technical Meetup 02-12-2025

UK Update & Validator Deployment

Validator Features & Considerations

  • Define Full vs Partial validation:
    • Partial: Subset of records, fields, or endpoints?
    • Consider developing a separate “sampler” tool for partial validation.
  • Determine whether to extend the UK validator or build a new one:
    • Skyler: .Net approach seems straightforward.
    • Matt: Distinguish between schema validation (compliance) and data quality checks.
    • Kate & Skyler: Formatting and completeness ≠ quality.
    • Mike: Define key quality aspects—validity, completeness (for a use case), and accuracy.

Distinctions:

  • Partial vs Full: Sample vs entire dataset.
  • Basic vs Complete: Minimum validation vs complete spec/profile validation.
  • Spec Compliance vs Custom Quality: Schema validation vs quality checks.
  • Syntactic Correctness vs Truthing: Validation vs verification/provenance.
  • Schema vs Endpoint: What level is being validated?

User Feedback & Error Handling

  • Define minimum required feedback for users:
    • “Description of errors” and clear problem identification.
  • Routine validation with automated notifications?
  • Allow users to revalidate after fixing errors.

Validator Accessibility & Future Planning

  • Interest in downloading and running a validator locally (tabled until April).
  • Added to bike rack

Transformer proposal (Interest? Questions?)

  • Stimulated a conversation around the initiatives general approach to community tooling which could involve the following:
    • Encouragement: To promote innovation
    • Input: To ensure alignment
    • Endorsement: To support uptake

Metadata API Enhancements

  • Discussion in the forum thread developed into a proposal
  • Consider record-level metadata in the next subversion.
  • Define “Organization” as publisher and align with “Contact” schema.
  • Kate to work with us to further specify for longer term
58

Thanks, @Dan-ODS. I just want to note here that these distinctions haven’t been affirmed – and some may be more on the mark than others. I’d like to hear more feedback (especially on “custom quality” and “truthing” – those don’t feel quite right to me yet)…

Distinctions in terminology re data validation:

  • Partial vs Full: Sample vs entire dataset.
  • Basic vs Complete: Minimum validation vs complete spec/profile validation.
  • Spec Compliance vs Custom Quality: Schema validation vs quality checks.
  • Syntactic Correctness vs Truthing: Validation vs verification/provenance.
  • Schema vs Endpoint: What level is being validated?
1 Like
59

We’ve iterated on the validator user stories – see the post here – and I hope to get final input on those formulations in the upcoming technical committee meeting.

Technical committee folks, please review and respond if possible in advance of the meeting – thanks!

60

Hi all,

Please the proposed agenda for next Wednesday Standing Technical Meeting below. Suggestion for further items are welcome as always.

Validator / Tooling

  • Forum post updating on further iteration on use cases

Minor Upgrades

  • Adding extra metadata to API feeds - Proposal / Forum post & Vote
  • Approval process
  • Implementation - Act now, or hold for batching with other issues?

Handling confidential addresses in HSDS 3.0

Versioning

UK Updates

  • Status of UK validator
  • Revised ORUK site to come
  • Arrangements for UK work after March 2025

Demo of taxonomy/terminology alignment tool

Resource Data Federation discussion

  • Forum thread
  • Proposed agenda?
  • Key questions for HSDS >3.1? For tooling?
  • Scheduling?
61

The following items would benefit from review/engagement ahead of next weeks meeting if people are able to find the time:

Validator / Tooling

  • Forum post updating on further iteration on use cases

Handling confidential addresses in HSDS 3.0

Resource Data Federation discussion

  • Forum thread
  • Proposed agenda?
  • Key questions for HSDS >3.1? For tooling?
  • Scheduling?

Thanks in advance,

Dan