Closed wrygiel closed 8 years ago
I started a complete rewrite of the EWP Mobility Process Explained document this Tuesday. I will be updating all the descriptions and all the flowcharts. Hopefully, I'll finish with a revamped API design proposal by the end of next week.
@StefanJahnke, I have just reviewed your report (revision 5cba3fc) and I'm happy to say that I'm 99% sure that all requirements will be met in the next revision of our design document :) I will be publishing a detailed side-by-side comparison next week.
Ok! I think I'm finished for now and I am ready for your reviews.
v0.2.0
). Read it here.I am closing this issue now. If any of you see any missing features in our API design, please submit each such problem in a separate issue (one issue per one class of problem) - most probably in the ewp-specs-mobility-flowcharts
repository - here.
@erasmus-without-paper/wp3
@StefanJahnke wrote:
Ok, thanks. I'll try to have a look at it tomorrow!
In general, we use GitHub issue tracker and try to be public with all conversations like this one, so I'm going to reply you here. @geirmv (and other watchers) should receive notification.
To answer your question, since:
So, I think this would be the most effective order:
First thing to do is to fix my "EWP Mobility Process Explained" document. This document describes the overall design of all the APIs and how the data flows (without getting into the detailed models). We will later build all APIs based on this document, so it should be consistent with your document on use cases. Fixing this document will be my job. While working on it, I will also build stub versions of all APIs.
Then, I guess, WP3s job will be to fill these stubs with a detailed model (i.e. adding and documenting new elements to the XML Schema files).
Of course, we can all help each other with each of these steps.