This document:Public document·View comments·Disposition of Comments·
Nearby:Data on the Web Best Practices Working Group Other specs in this tool
Quick access to LC-3003 LC-3004 LC-3005 LC-3006 LC-3007 LC-3008 LC-3028 LC-3029 LC-3030 LC-3031 LC-3032 LC-3033 LC-3034 LC-3035 LC-3036 LC-3037 LC-3038 LC-3039 LC-3040 LC-3046 LC-3047 LC-3048 LC-3049 LC-3050 LC-3051 LC-3052 LC-3053 LC-3054 LC-3055 LC-3056
Previous: LC-3054 Next: LC-3007
- when it comes to versioning, i am always recommending to focus on openness and extensibility and have robust and well-defined models for those (this almost always requires well-defined processing models for data). this often avoids the need for versioning, which when done badly will be a breaking change. - when it comes to versioning, it is important to distinguish between breaking and non-breaking versioning changes. this comes down to the comment above: good openness and extensibility makes it easier to have non-breaking versioning, which helps tremendously in decentralized ecosystems.