[Accepted] SDL 0153 - Support for Short and Full UUID App ID
Closed this issue · 8 comments
Hello SDL community,
The review of the revised proposal "SDL 0153 - Support for Short and Full UUID App ID" begins now and runs through April 24, 2018. The original review of "Support for Short and Full UUID App ID" took place March 28 through April 3, 2018. The proposal is available here:
Reviews are an important part of the SDL evolution process. All reviews should be sent to the associated Github issue at:
What goes into a review?
The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of SDL. When writing your review, here are some questions you might want to answer in your review:
- Is the problem being addressed significant enough to warrant a change to SDL?
- Does this proposal fit well with the feel and direction of SDL?
- If you have used competitors with a similar feature, how do you feel that this proposal compares to those?
- How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
Please state explicitly whether you believe that the proposal should be accepted into SDL.
More information about the SDL evolution process is available at
https://github.com/smartdevicelink/sdl_evolution/blob/master/process.md
Thank you,
Theresa Lech
Program Manager - Livio
theresa@livio.io
Perhaps a good addition would be for the mobile libraries to automatically set the app id when the full app id is set so that developers don't need to worry about it.
Also, the potential downside could be minimized by visiting the algorithm used to generate the UUID and making sure the first 10 characters are the most significant. If it turns out neither the first 10 nor last 10 characters would be unique, we could use a shorter hash on the UUID to avoid collisions.
The Steering Committee voted to return this proposal for revisions. The author will revise to incorporate the suggestions left on the review issue by joeljfischer and AndrewRMitchell.
The author has updated this proposal per the requested revisions, and those revisions are now ready for Steering Committee review. This revised proposal will be in review until April 24, 2018.
Thank you for the investigation and documentation of the results! +1 from me.
The Steering Committee fully agreed to accept this proposal.
Implementation also required in Policy Server. Issue entered: Policy Server