Public Release r1.2 for ModelAsAService APIs (Fall25 M4)#18
Public Release r1.2 for ModelAsAService APIs (Fall25 M4)#18lihaojie-CMCC merged 39 commits intomainfrom
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
|
Work in Progress |
|
@lihaojie-CMCC Please merge the main branch into the PR branch and resolve the merge conflicts. If done mark it again as "Ready for review". |
…-base-API-Readiness-Checklist.md
…ssistant-manage-API-Readiness-Checklist.md
…assistant-service-API-Readiness-Checklist.md
|
This PR is ready for review. |
tanjadegroot
left a comment
There was a problem hiding this comment.
Overall looks good !
a few fixes and comments, some of which can be delayed till next release (up to the team).
Side comment, generally in the API yamls some more description fields would be good.
documentation/API_documentation/knowledge-base-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
documentation/API_documentation/qa-assistant-service-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
documentation/API_documentation/qa-assistant-service-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
documentation/API_documentation/qa-assistant-service-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
|
@lihaojie-CMCC, Team, any idea when you can do the updates (most are straightforward fixes) so we can go ahead and approve for merge and release. |
Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
…hecklist.md Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
…ness-Checklist.md Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
…ness-Checklist.md Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
…ness-Checklist.md Co-authored-by: Tanja de Groot <87864067+tanjadegroot@users.noreply.github.com>
Hi @tanjadegroot , Thank you so much for your comments. They are incredibly valuable to our project. We have implemented all the suggestions and completed the updates. Please take a look when you have a moment. |
There was a problem hiding this comment.
Many thanks @lihaojie-CMCC for the quick update !
A left a few comments still but you can decide if you do them before merging or if you leave them to the next release (as they do not impact the API usage)
All the rest looks great ! thanks
LGTM from Release Management
After the merge, please create the release and update the release trackers on the wiki - many thanks !
| It is designed to provide applications with standardized capabilities for knowledge content storage and management, supporting multi-format document storage, fine-grained permission control, and end-to-end traceability. | ||
| It is suitable for building knowledge-intensive systems (such as intelligent customer service platforms and enterprise document platforms) while ensuring compliance. | ||
|
|
||
| It must follow RFC 3339 and must have time zone. Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ. |
There was a problem hiding this comment.
this text should actually be part of the schema definition you can copy it from https://github.com/camaraproject/Commonalities/blob/main/artifacts/CAMARA_common.yaml
Same for all yaml files using date-time type attributes
| description: >- | ||
| This API provides CRUD (Create, Read, Update, Delete) management functions for the Question and Answer (Q&A) Assistant, aiming to equip developers with the capability to configure and manage intelligent question-answering systems based on Large Language Models (LLMs). | ||
| It supports model parameter tuning, knowledge base association, and prompt engineering configuration, making it suitable for building customizable intelligent customer service or question-answering services. | ||
| It must follow RFC 3339 and must have time zone. Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ. |
There was a problem hiding this comment.
Same comment as above on date-time based schemas
| description: >- | ||
| This API provides service interfaces for the Question and Answer (Q&A) Assistant, enabling users to submit query requests to a configured Q&A assistant and obtain answers generated based on the knowledge base and Large Language Model (LLM). | ||
| It is suitable for scenarios such as building intelligent question-answering systems and customer service bots that require real-time responses to user inquiries. | ||
| It must follow RFC 3339 and must have time zone. Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ. |
There was a problem hiding this comment.
Same comment as above on date-time based schemas
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
|
Thanks everyone for the review and feedback! I'm going to go ahead and merge this PR. |
|
@hdamker @tanjadegroot , As we've just revised the "consumer" related content, we would like to seek your assistance for a final confirmation from the Release Management side. We greatly appreciate your support! |
tanjadegroot
left a comment
There was a problem hiding this comment.
All good - thanks very much for the updates !!
LGTM from Release Management
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Create the initial public release of Model As A Service APIs to be included in Fall25 Meta release.
Which issue(s) this PR fixes:
Fixes #