Determine plan for next steps for the Knowledge Layer Connector

[chrizmc]

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:

[chrizmc]

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

[slawr]

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]

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)

[slawr]

@claireqiu @chrizmc can we consider this complete? This is the last open task in the "initial KL epic".
If it should stay open then that is fine, but I would just like to keep the Kanban board updated.

Perhaps if there is some small sub-task left it could be broken out into a new task?

[chrizmc]

@slawr I agree, this is completed with #50 . Remaining open tasks are handled with #77