Skip to content

Determine plan for next steps for the Knowledge Layer Connector #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
chrizmc opened this issue May 21, 2024 · 3 comments
Open

Determine plan for next steps for the Knowledge Layer Connector #44

chrizmc opened this issue May 21, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request task Task not fitting other labels, e.g. project ops

Comments

@chrizmc
Copy link
Collaborator

chrizmc commented May 21, 2024

Issue #21 concluded the initial consideration of Why/What for the Knowledge Layer Connector. Now we need to discuss and plan for the next steps in its implementation

Please find here the results:

Image
Image
Image
Image

@chrizmc chrizmc converted this from a draft issue May 21, 2024
@chrizmc
Copy link
Collaborator Author

chrizmc commented May 24, 2024

we are preparing first Pull Request which contains basic folder structure and basic content of readme file

@slawr slawr added enhancement New feature or request task Task not fitting other labels, e.g. project ops labels May 24, 2024
@slawr
Copy link
Collaborator

slawr commented Jan 22, 2025

Hi @chrizmc in last weeks call you mentioned that @claireqiu and yourself had met and had a plan for KL up towards the Spring AMM. As we discussed in the call I would like to get the high level tasks to complete that plan in this Kanban as its part of the project. With that in mind can you create new tickets as needed to represent the plan and we can close this ticket as done as it's 'determine plan' not 'execute plan'? If you have a different idea please discuss.

It doesn't necessarily have to extreme detail its more about people outside BMW understanding the plan.

@claireqiu
Copy link

claireqiu commented Jan 24, 2025

1 ) Migrate Knowledge Layer to Support New API
2) Evaluate of the use case rule set
3) Convert the inference to json
4) Optional (send the json to information layer)

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request task Task not fitting other labels, e.g. project ops
Projects
Development

No branches or pull requests

3 participants