[NeXus-committee] NeXus Ontology release pipeline and redirects

[Paul Millar]

Hi Tanmay,

On 08/09/2026 20:01, Kulkarni, Tanmay via NeXus-committee wrote:
> One thing to note: The w3id redirects (for example: https://w3id.org/ 
> PaN/NeXus/definitions/v2026.01 <https://w3id.org/PaN/NeXus/definitions/ 
> v2026.01>) are not live yet since that PR has not been merged. 
> Additionally, everything has been built and tested against FAIRmat-NFDI 
> fork's GitHub Pages in the meantime and the redirects point there 
> <https://github.com/Tanmay2028/w3id.org/ 
> blob/5ed80a8ff6b4442d24307a5b31cd886c9cea0ae6/ids/PaN/NeXus/.htaccess> 
> for now.

One rather specific point is how to test the w3id.org redirection 
service configuration.

As part of the PaNET migration, I wanted a way to test both proposed 
changes to w3id.org (i.e., pull requests) and the "live" redirections 
service.  The result is w3id-tester:

	https://github.com/pan-ontologies/w3id-tester

This allows you to verify that a local branch (that contains proposed 
changes) results in the expected redirections.  It does this by 
(locally) simulating the w3id.org service.  With this, one can run 
w3id-tester to check the changes work as expected (and don't break 
anything).

I've attached a (rather minimal) set of tests I developed for the NeXus 
ontology, mostly just to exercise the w3id-tester framework.  This also 
includes a canary test.  A more extensive set of tests is also available 
for PaNET, if that would be helpful.

Please feel free to reuse any of this.

Cheers,
Paul.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: check-nexus.json
Type: application/json
Size: 866 bytes
Desc: not available
URL: <https://lists.nexusformat.org/pipermail/nexus-committee/attachments/20260909/fa4cc85b/attachment.json>