Closed dwinston closed 7 months ago
thanks, @dwinston. I think @sujaypatil96 and I had been tracking something similar in another issue, but I haven't been able to find it yet.
Each of the YAML files in https://github.com/microbiomedata/nmdc-schema/tree/main/src/schema has it's own id
Specifically, the id
for the root of the schema, nmdc.yaml is https://w3id.org/nmdc/nmdc
, so that's what remains when the various imports are all merged together
And therefore, https://w3id.org/nmdc/nmdc
is displayed as the id
for the landing page in the auto-generated documentation. Furthermore, the id is displayed as a clickable (but broken) link.
Note: this landing page is technically information about the nmdc-schema SchemaDefinition
I'm not sure what to say about this one. It would be nice if your resolver were magically aware of all of the id
s in the schema, not just the ones assigned to classes, slots, enumerations, etc. On the other hand, there isn't much utility to this particular link: I believes it only appears on the auto-generated landing page, and presumably the target for the link would just be the auto-generated landing page! That's the behavior on the MIxS documentation landing page
@sujaypatil96 @cmungall what do you think of either removing the SchemaDefinition's id
altogether, or just disabling the link?
The following w3id.org PR has been merged:
Current behavior of the w3id redirections:
...because there is no
nmdc
schema element. Should the w3id.org .htaccess file hard-code this particular redirect? should the redirect be handled by the runtime api?