LG 4-4 API versioning

[gernotstarke]

This is just one of the LG's where I expect more content: Instead of just giving the "headline" (versioning),
you could at least name a few options:

• versioning by naming (service-v1, service-v2)
• versioning by metadata, by adding headers, by including the version info in the content (aka body)

What about the relation between versioning and compatibility? Backward-, Forward-?

(there are other LG's with similar issues...)

[dret]

This is more of a "philosophical" issue. In my understanding the mission is to keep the curriculum short and not list too may details for the individual learning goals. But you're certainly right that here (and in pretty much every other place) we could go deeper and add details. Before adding these details here I'd like to have a general discussion around the "depth" so that we keep the curriculum at the right level. @StefanZoerner and @programming-wolf, as our shepherds so far, can you please chime in? Thanks a lot!

[gernotstarke]

right, difficult to decide where to add details. imho in versioning at least a few more details would give a decent level of constraint for their trainings...

[dret]

I understand. Let's see what @StefanZoerner and @programming-wolf are recommending. For now I'll add the specifics you mentioned for this issue because these definitely should be in there.

[dret]

If the general feedback is to make many/all LGs more specific, let's open a separate issue to track things over there. Thanks.