Was going to attend to try and understand more about the Openactive stuff.
But its not in my diary.
If it is going ahead, can I have a link please?
Was going to attend to try and understand more about the Openactive stuff.
But its not in my diary.
If it is going ahead, can I have a link please?
@Julz I think the meeting reference is more of an organisational one, but Greg might comment.
Iāll be away for the next week but happy to have a one-to-one on the relationship between OpenActive and Open Referal UK any time after that. @Ian-DigitalGaps and/or @andrew-newman might chip in (probably best in this thread). In the meantime, Iāve dug up this short document on a planned OA/ORUK use case MBT10001 - Points for an OpenActive / Open Referral UK use case which might be of interest.
I think the international group hopes to have a meeting on aggregators (aka federation tools) - see here. It would be good for you to join that if/when it is firmed up.
Ta Mike, will keep pushing from our end to help make things work together.
This is mostly over my head but seems were are getting closer.
@Julz @MikeThacker Iād be happy to join a call to discuss ORUK and OpenActive
@bloom I included OR/OA as an agenda item due the amount of related activity across the forum and to see if there weāre emergent discussions to be had; rather than to discuss anything specific.
Same goes for taxonomies really.
Judging by comments, I donāt think we have anything concrete to discuss as a group and as lines of communication are open via the threads leaving it until June makes sense to me.
Iām happy either way, but will not amend the invite until I hear back from you.
I will plan to join during the time, even if just for a quick checkin with whomever drops by.
We could discuss plans for a show-and-tell about federation / aggregation tactics
Hi folks ā looking forward to our standing technical meetup on June 12th. (if youād like to attend but donāt have it on your calendar, let me know and I will send an invite.)
Danās out of office, so Iāll share a link to our notes and draft agenda here.
Here below is what it seems like we have to discuss ā feel free to suggest additional topics!
Draft Agenda:
Hi all,
Hereās the video and transcript from our meeting last week (12th June) then see below for a summary of discussion points and follow-up actions.
Key discussion points
Committee Formation:
3.1 Backlog Review:
Community Survey:
Summit Discussion:
Communications:
Actions:
Upgrade to 3.1:
Community Survey:
Summit
Communications:
Follow-up response to this as we did not really respond to request for this in the meeting itself:
The formation of committee and refinements to the process (which ODS are talking to @devin separately next week) will impact on how quickly we can get to the actual work. That said, our current contract comes to an end at the end of September so weād be keen to get 3.1 released by then (at the latest).
@MikeThacker @skyleryoung tagging you specifically as you expressed a need to move things forward (or atleast have an idea of timescales so expectations can be managed) based on your specific circumstances.
Follow-up response to this as we did not really respond to request for this in the meeting itself:
The formation of committee and refinements to the process (which ODS are talking to @devin separately next week) will impact on how quickly we can get to the actual work. That said, our current contract comes to an end at the end of September so weād be keen to get 3.1 released by then (at the latest).
@skyleryoung Matt will of course be keen to be a part of this. @klambacher I suggested you based on the relevant experience you shared in the meeting (but also aware youāre super busy - hence the ? after your name).
As an example of what this working group will be aiming for see what @mrshll has drafted using our proposal template for Adding Service Area to Service At Location (@skyleryoung feedback welcome on this as this was on of your requests)
Dan
@devin With this in mind, do you see any utility in adding these summaries to the indivudual github issues - 2024-05-09 Summaries of Proposed Issues for 3.1 - Google Docs?
Hi all,
Apologies for the very last minute agenda for tomorrow meeting that both Matt and I are unfortunately unable to attend.
Iāve added a bunch of comments in my absence.
Agenda:
Thanks for joining today, folks.
Notes are here: https://docs.google.com/document/d/1SYmsSa_U8uQKZW0zhEq8H6CNttNeWPqP7BAV0HDJa2o/edit#heading=h.aonfi8yijq7u
Summary of action items here:
Actions:
Greg Bloom to synthesize notes on the charter into a revised draft.
GB to develop language for problem-definition norms in issue generation
Committee members to review ODCS points on v3.1 process
Committee members to suggest outreach targets for community survey.
Put taxonomy topic on future agenda.
Hi all,
Apologies this is very last minute but hereās the proposed agenda for tomorrow. Further suggestions welcome - as always.
Main items
AOBās (depending on attendance/appetite/time)
Thanks,
Dan
I added some comments on our Vacancy / Capacity structure at Capacity to take referrals Ā· Issue #221 Ā· openreferral/specification Ā· GitHub
Hi all,
Sorry I missed the call this week.
Hereās a link to the notes, video and transcription.
Update on things I know have been actioned since the meeting:
- MM forum post summarising what I presented at the meeting, with links for those who werenāt there.
Done. See - Overview of the upcoming HSDS 3.1
- Iteration on the Location Type of āRedactedā proposal to clarify that we are also suggesting that we add guidance to the docs explaining implications and how to use it.
Done. See - PROPOSAL: Add a Location Type of Redacted - Google Docs
- Kate to share example of capacity schema with Matt, and Skyler to ask WellSky for their example schema.
Done. See - Capacity to take referrals Ā· Issue #221 Ā· openreferral/specification Ā· GitHub
Hi all,
Does anyone have suggestions/request with regards to agenda items for next Wednesday meeting?
Dan
I can give an update on UK local government work, including upgraded Validator & Dashboard and planned meeting.