Re: comments regarding versioning

Hello Erik,

one more thing, the comments bellow were addressed in the Best Practice 
10: "Avoid Breaking Changes to Your API"[1], are you okay with it?

- 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.

Thank you! Kind regards,
Bernadette, Caroline and Newton

[1] http://w3c.github.io/dwbp/bp.html#provideVersioningInfo


On 14/03/16 16:31, Newton Calegari wrote:
> Hi Erik,
>
> Regarding your comment [1] about the public mailing address. I've 
> changed the document and updated on github [2]. It will appear on the 
> next publication.
>
> cheers,
> Newton
>
> 1: https://lists.w3.org/Archives/Public/public-dwbp-wg/2015Jul/0009.html
> 2: 
> https://github.com/w3c/dwbp/commit/3414813c9467c02587f1e4c2b45db1b72733a885
>
> Em 14/03/16 15:11, Caroline Burle escreveu:
>> Hello Erik!
>>
>> Thank you for your comments. The former Best Practice 18: Vocabulary 
>> versioning was removed from the document. The current version of the 
>> document doesn't deal with vocabulary versioning.
>>
>> Kind regards,
>> Caroline
>>
>> On 25/06/15 19:13, Erik Wilde wrote:
>>> hello.
>>>
>>> great work on the new WD! i have three comments regarding versioning:
>>>
>>> - what is the difference between "Best Practice 8" and "Best 
>>> Practice 18"? it seems that they are very similar, and if there 
>>> indeed is a subtle difference, maybe create one practice that spans 
>>> both, or make it more clear what the difference is?
>>>
>>> - 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.
>>>
>>> thanks and cheers,
>>>
>>> dret.
>>>
>>
>>
>
>