Hmm, I need to read more about this and see some more examples and we can follow up.
New perspectives for the new day:
Tue, Nov 19
I'd like to see the schema repositories either bear a direct relation to the name of the EventGate instance that will probably be used, or bear no relation at all and be completely orthogonal (like @Ottomata's latest proposal attempts).
Mon, Nov 18
Fri, Nov 15
I think this is great because it makes the API actually readable in a meaningful way that maps to our documentation and the concepts/abstractions used by MEP and Kafka.
As long as we continue to name our instances properly, we'll have really nice idiomatic endpoint URLs like
Thu, Nov 14
Mon, Nov 11
Tue, Nov 5
@ssastry Okay, time for an update. I spent the last few days re-visiting the PHP library and started the necessary finishing.
Just wanted to chime in here as I'm really glad to see these discussions getting started. In a couple of weeks I'm going to start reaching out to folks on Web to try and do a brief of where we are with the cilent, what exactly will be delivered and when we expect that to happen, and some kind of outline of what the new workflow will look like.
Fri, Nov 1
I updated the description and moved the many tiny confusing subtasks to T237106: EPC Kanban Cards.