> For the complete documentation index, see [llms.txt](https://changes.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://changes.ishare.eu/cab-and-deepdive-meetings/cab-meetings/2024/2024-12-04.md). # 2024-12-04 The next CAB meeting will be held at December 4, 2024 at 15:00 CET. If you would like to be invited for this meeting, or if you would like to add a topic to the agenda, please reach out to us through available channels. ### Agenda 1. Welcome + introduce new participants 2. Update on the implementation of RFCs on the [RFC board](https://gitlab.com/ishare-foundation/cab/rfc/-/boards) 1. Preview of release 2.1 3. Advice on the implementation of RFCs 4. Input/review required 5. Advice on newly incoming RFCs 1. Add CRUD operations to Parties endpoint 6. RFC prioritisation: discuss priority on the [RFC board](https://gitlab.com/ishare-foundation/cab/rfc/-/boards) 7. Wrap up and outlook to next quarter ### Meeting results The slides used are available [here](https://docs.google.com/presentation/d/1FvXSHW4pZASzPXnV3_w3C_JD3EGZ0DU2Mt77fXXxEiY/edit?usp=sharing). 2. The upcoming 2.1 release was extensively discussed and demoed. The anticipated impact is mostly in RFC031, which is about introducing identifiers. CAB requests to explain in more detail how backwards compatibility is designed, particularly on RFC031. 3. No RFCs were discussed. More impact analyses are expected to be prepared for approval for the next CAB session. 4. No RFCs were discussed. 5. CAB advises positively on the RFC about CRUD operations on the Parties endpoint. A deep dive session will be organised on the topic to start gathering requirements. 6. RFC priority was discussed, no changes were made. RFC on CRUD operations has a high priority. 7. The development of the reference onboarding portal was shown as a preview. Everyone is invited to the next CAB, which will be held in the ishare office on March 5, 2025! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://changes.ishare.eu/cab-and-deepdive-meetings/cab-meetings/2024/2024-12-04.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.