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

Redirect https://w3id.org/mod and https://w3id.org/mod/xx to relevant files #92

Open
4 of 8 tasks
jonquet opened this issue May 31, 2024 · 15 comments
Open
4 of 8 tasks

Comments

@jonquet
Copy link
Contributor Author

jonquet commented May 31, 2024

If possible... we need to deal with redirect to HTML page also per content negociation

Related to #47

@biswanathdutta Could yu take care of this ?

@biswanathdutta
Copy link
Collaborator

Hi, @jonquet I have activated the redirections for the following versions 1.2 (https://w3id.org/mod/1.2), 1.4 (https://w3id.org/mod/1.4), and 2.0 (https://w3id.org/mod/2.0).
Once the other versions are ready, we will activate them.

@jonquet
Copy link
Contributor Author

jonquet commented Jun 2, 2024

ok thanks.
Can you do the others now too (even if file is not yet in version folder, from v3.1)
Also, can you retrieve v1.0 and v1.1 and add them to the version folder ?

@jonquet
Copy link
Contributor Author

jonquet commented Jun 2, 2024

After, we will come back to HTML negociation

@jonquet
Copy link
Contributor Author

jonquet commented Jun 25, 2024

@dgarijo this is the issue. @biswanathdutta any news about the redirection of the " https://w3id.org/mod" this becomes necessary.

@jonquet
Copy link
Contributor Author

jonquet commented Jun 25, 2024

@biswanathdutta in the v3.2 of MOD I have used w3id everywhere as URIs of the different versions of MODs, so its important that now you make all the versions redirect to the right files. See 43a52ed
Can you point to document to edit to anage redirection and content negociation on w3id ?

@dgarijo
Copy link
Contributor

dgarijo commented Jun 26, 2024

@jonquet a suggestion:

  • Why don't you keep a consistent structure in the repo, so it is possible to automate version redirections?
    For example, if you rename these files:
https://w3id.org/mod/1.4 => https://raw.githubusercontent.com/FAIR-IMPACT/MOD/main/versions/mod-v1.4_ontology.owl
https://w3id.org/mod/1.2 => https://raw.githubusercontent.com/FAIR-IMPACT/MOD/main/versions/mod-v1.2.3.owl

to be

https://w3id.org/mod/1.4 => https://raw.githubusercontent.com/FAIR-IMPACT/MOD/main/versions/mod-v1.4.owl
https://w3id.org/mod/1.2 => https://raw.githubusercontent.com/FAIR-IMPACT/MOD/main/versions/mod-v1.2.owl

then we can do a redirection that is:

https://w3id.org/mod/$1 -> https://raw.githubusercontent.com/FAIR-IMPACT/MOD/main/versions/mod-v$1.owl

If you agree, I can do a PR here with the redirects and also one to w3id.

@jonquet
Copy link
Contributor Author

jonquet commented Jun 26, 2024

Good to me.
Please CC me also on the w3id PR so I see where this is ;)

@biswanathdutta
Copy link
Collaborator

@dgarijo please put me in CC too, so that I am aware of the changes

@dgarijo
Copy link
Contributor

dgarijo commented Jun 26, 2024

Sure, I will do 2 PRs: one for this repo with a slight structure changes and another one to w3id pinging you both.
I will do this today

@dgarijo dgarijo mentioned this issue Jun 26, 2024
@jonquet
Copy link
Contributor Author

jonquet commented Jun 26, 2024

Took the PR related to this. Will also take the one on W3id and we will need to update the readme and check that everything work for past versions.

Then we will practiceon new version in order to release 3.2 ;)

@dgarijo
Copy link
Contributor

dgarijo commented Jun 26, 2024

perma-id/w3id.org#4221 please have a look and approve if appropriate

@dgarijo
Copy link
Contributor

dgarijo commented Jun 26, 2024

Ok, it's done. However, a caveat:

I made the versions adopt semantic versioning. So every MOD release has a 3 digit, not two. For example:
https://w3id.org/mod/3.0.0 --> https://raw.githubusercontent.com/FAIR-IMPACT/MOD/main/versions/3.0.0/mod-v3.0.0.owl

I did this because some versions like 1.2.3 had 3 digits, but others like 3.0 only had two.
URIs will need to be adapted accordingly

@dgarijo
Copy link
Contributor

dgarijo commented Jun 26, 2024

Also the latest version goes to 3.0.0 because that's the latest one in version. If you want a 3.2.0, then create the folder and it would work

@jonquet
Copy link
Contributor Author

jonquet commented Jul 29, 2024

I have created a folder for 3.2 (not 3.2.0) with the content that was associated to the release fo 3.2.
In addition I have rename folders after 2.0 to 2 digits to be sure histociral URIs still work (including in MOD source file themselves). Thinking about it, we are not going to archive (in the version folder and consequently with version URIs) version with 3 digits... its too much details/work.

Will change w3id accordingly if necessary.

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

No branches or pull requests

3 participants