Renaming paths or files in xref'd repo leads to 404

[kordwarshuis]

Scenario:

• link to term in external reference via “[[xref: term]]
• term in external reference is renamed (from “term-1.md” to “example-term-1.md”) or path to “term-1.md” is renamed (from “terms-definitions/term-1.md” to “terms-and-definitions/term-1.md”
• xref does not work anymore

[kordwarshuis]

To do: Test linking to file version with commit hash.

[henkvancann]

Although it's ugly, we could also add a governance constraint: If you ever change a definition, then add:

[[def:oldterm]] 
~ [[ref:newterm]]

Other solutions like adding a .htaccess forwarder might be neater. Or maybe even an xref to a synonym might work. So then the {oldterm} could be added to the list of synonyms. Therefore:

To do: Test linking to file version with commit hash.

To do 2: We would also like to test whether xref to synonym works

[kordwarshuis]

Although it's ugly, we could also add a governance constraint: If you ever change a definition, then add:

Other solutions like adding a .htaccess forwarder might be neater.

This is when an external reference changes, so it is outside our governance.

[henkvancann]

This is when an external reference changes, so it is outside our governance. ->
Yes, I understand. But you'd have control over this:

[[xref:term , example-term, another-alias-term]] when term has changed into example-term out of your control, but you could still investigate the host github repo to see what happened and adjust your xref accordingly?