We edit the guidance so that it is clear that if having more than one limitation, other instances DO NOT need to reference INSPIRE
We alter the guidance so that guidance note 5 becomes explicitly for INSPIRE only, and then we introduce a new guidance note that states that other limitations are encouraged to be encoded with an anchor, but that plain text be allowed
We then create an encoding example for the plain text use case.
I think the currently live text answers this issue - it's been "overtaken" by resolving other issues.
I don't think the auto-matched PR had anything to do with it.
Encoding guidance note 5 for this element states that “The free text shall be encoded in a gmx:Anchor element, with xlink:href pointing to the relevant kind of limitation from the INSPIRE Metadata registry: http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess”. I read this as potentially reading that all text should relate back to an entry in the INSPIRE codelist via an xlink anchor. However, the encoding examples in https://www.agi.org.uk/agi-groups/standards-committee/uk-gemini/40-gemini/1062-gemini-datasets-and-data-series#25 show xlink anchors that do not link back to INSPIRE. This also raises another potential area for confusion - does every limitation have to be encoded via an xlink anchor: our guidance at https://www.agi.org.uk/40-gemini/1048-uk-gemini-encoding-guidance#2.2 has examples that include simple free text.
I propose as solutions to this: