Open RaggedStaff opened 2 months ago
I have a draft of this ready to go in my fork.
But I need to know where to point the redirects.
Can we agree if we are using github pages to publish to docs.datafoodconsortium.org or continuing to use the github releases functionality ?
ping @simonLouvet @lecoqlibre
I don't think we need a variable (.*)$ to point to the latest. It might be used if you want to get a version, but in that case I would have used these URLs
dfc/ontology/(.*)/context
dfc/ontology/(.*)
dfc/taxonomy/(.*)
@RaggedStaff NOT github pages
Update on this. I've updated to handle versioned file redirects & tested using a remote Apache deployment.
The CORS headers are not working... I think GitHub may have it's own headers set to force downloading. 😖
I think we need to revisit using GitHub pages to publish the files & w3id for permanent redirection.
I'm thinking of developing a mini-server dedicated to publishing ontologies (owl, rdf), contexts and taxonomies based on github releases. Doing what we wanted to do with w3id.org, but ourselves.
We could add content negotiation (having a taxonomy in json-ld or xml for example)
depending on the degree of genericity and functionality (being able to configure the github / gitlab repo by interface; having connection and rights management, being able to reference several repos, etc. ), it could take me between 2 and 8 days. To be funded by DFC or another organisation. I think that the virtual assembly also needs this type of tool.
Translated with DeepL.com (free version)
w3id.org offer a permanent redirect service to support linked data projects to stablise URI's.
We are proposing to utilise this to add CORS headers & redirection (currently to github release page, could be updated in the future)