Clarify dependency management best practices

[fosdev]

Document management guidelines to prevent externally consumed profiles that change causing ripple effects if you reference or extend them. Promises of consistency.

Applies To:

• https://github.com/alps-io/misc-docs/blob/master/dependency_management_guidelines.asciidoc

[fosrias]

So, this is the dreaded versioning issue. I can see guidelines being similar API guidelines:

1. Don't take anything away.
2. Don't change the meaning of something in an ALPS doc
3. Don't make something required.

If you do version it.

As a consumer, you should ignore something that is in a profile but not in a related resource. In that way if new elements are in the ALPS profile but not the relate response, things are ok. This would also mean that code generated or using ALPS profile should ignore things it can't resolve, etc.

Do we need to address this now @mamund? I think it relates to #5 and maybe should be discussed as part of the thread/discussion I need to start there.