Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

https://w3id.org/nmdc/nmdc doesn't resolve to https://microbiomedata.github.io/nmdc-schema/ #1611

Closed
dwinston opened this issue Jan 3, 2024 · 3 comments
Assignees

Comments

@dwinston
Copy link
Collaborator

dwinston commented Jan 3, 2024

...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?

@turbomam
Copy link
Member

turbomam commented Jan 4, 2024

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.

@turbomam
Copy link
Member

turbomam commented Jan 4, 2024

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 ids 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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants