- From: Stian Soiland-Reyes <soiland-reyes@manchester.ac.uk>
- Date: Fri, 10 Mar 2017 14:41:15 +0000
- To: "Bohms, H.M. (Michel)" <michel.bohms@tno.nl>
- Cc: public-perma-id@w3.org
(I changed the confusing Subject) On Thu, 9 Mar 2017 14:26:02 +0000, "Bohms, H.M. (Michel)" <michel.bohms@tno.nl> wrote: > Can someone tell me how to reserve: > > https://w3id.org/eo > redirected to > http://ontology.tno.nl/eo > > (eo for energy ontology...) You may want to make http://ontology.tno.nl/eo online first.. The best is if you are OK to use GitHub, then log in at https://github.com/perma-id/w3id.org and click the "Fork" button. In your own copy, click "Create new file" and call it eo/.htaccess - with content massaged from one of the others, e.g.: Options +FollowSymLinks RewriteEngine on RewriteRule ^$ http://ontology.tno.nl/eo [R=302,L] Then it might be good to also add a short README.md describing what it is and who is in charge. An example would be Energy Ontology (EO) ==================== Homepage: ?? Vocabularies: https://w3id.org/eo Contacts: * Michel H.M. Bohms <michel.bohms@tno.nl> If you have a README file, then any w3id.org URL in it will be used in the tests - which in your case would reveal the current 404 at http://ontology.tno.nl/eo (Rather than use the GitHub UI you can also do these changes locally with a git clone of your new repository.) Then you should be able to click a "New pull request" button in GitHub to push it back to w3id.org - after review/merge it will be made live. If you prefer we can do the same change for you - but it's good if you are in control so you know how to do such changes later. -- Stian Soiland-Reyes The University of Manchester http://www.esciencelab.org.uk/ http://orcid.org/0000-0001-9842-9718
Received on Friday, 10 March 2017 14:42:03 UTC