Document the evolution principles in the README

[jviotti]

Signed-off-by: Juan Cruz Viotti jv@jviotti.com

[augmentcode]

🤖 Augment PR Summary

Summary: This PR expands the README with an “Evolution” section explaining how the schema library is intended to evolve without breaking consumers.

Changes:

• Documents how schema collection paths map to upstream authorities (ISO/IETF/W3C/etc.)
• Explains per-concept versioning (e.g., v1.json) and explicit deprecation/supersession
• Describes expectations around validation stability, linked-data identifiers, and generation sources

Technical Notes: Emphasizes explicit version pinning to make downstream impact visible when new versions are introduced.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

README.markdown:80 — This says self-published specs live under other/, but in the repo layout they appear under schemas/other/; consider clarifying whether paths here are relative to schemas/ to avoid confusion for readers browsing the tree.

Severity: low

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

README.markdown:83-90 — The “Versions never change their validation behavior” bullet reads like a universal rule, but the next bullet says some “living registries drift in place,” which implies validation can change within a version; consider explicitly scoping the immutability guarantee (or noting the exception) so the principles don’t contradict.

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}