Here is map manifest, not behind Auth:
Manifest: | https://stacks.stanford.edu/image/iiif/tc010rc2373%2FPaloAlto3
-- | --
info.json: | https://stacks.stanford.edu/image/iiif/tc010rc2373/PaloAlto3
Here is a manifest behind Auth:
https://purl.stanford.edu/bd117rc5047/iiif/manifest
Manifest: | https://stacks.stanford.edu/image/iiif/bd117rc5047%2Fbd117rc5047_00_0001
-- | --
info.json: | https://stacks.stanford.edu/image/iiif/bd117rc5047/bd117rc5047_00_0001
All Stanford manifests have this error, and apparently, items behind Auth are dependent upon this mismatch. So non-compliant @ids are a feature, not a bug, at Stanford.
I suppose the only recourse is to reduce the allmaps validation level, since there doesn't seem to be interest in fixing this. From what I'm told, fixing it breaks these manifests in Mirador.
Here is map manifest, not behind Auth:
Here is a manifest behind Auth:
https://purl.stanford.edu/bd117rc5047/iiif/manifest
All Stanford manifests have this error, and apparently, items behind Auth are dependent upon this mismatch. So non-compliant @ids are a feature, not a bug, at Stanford.
I suppose the only recourse is to reduce the allmaps validation level, since there doesn't seem to be interest in fixing this. From what I'm told, fixing it breaks these manifests in Mirador.