Comments (3)
Yeah, I understand hedging bets on such things. How I see this ecosystem is that the service maintainers want to keep things simple and easy to maintain. Redirect authors want to depend on servers staying up and have fallbacks (and have it all be free of course). Redirect users want URLs to stay valid forever. It may be a pick two situation here.
I can see a couple issues with the mapping you propose. In many semantic web use cases I think users want to pick a URL for a resource and stick with it forever. Apps get static string comparisons and such that make URLs hard to change. w3id was kind of made for that purpose. The URL redirects can change behind the scenes as needed. If someone uses their own domain, then there is the same issue as before that the project might fade or domain change hands and all the old URLs could become invalid. w3id could fail too of course, but maybe the bet is that enough people are using it that someone will step up to keep it going if needed.
Another issue is the https cert issue. I think that will require CNAME config and DNS setup and magic to make it all work?
Unless someone steps up with a plan to make that all happen, I think just mapping purl.example.com to w3id.org will have cert issues.
from w3id.org.
I'm not clear what the ask is here and how it would help.
My guess is:
- do something like github and add a
CNAME
file in.../example/CNAME
, that says it'sexample.org
example.org
domain owner points their servers at a magicw3id.org
server- requests to
https://example.org/foobar/baz
would go tohttps://w3id.org
- those requests remaped to
https://w3id.org/example/foobar/baz
- then those requests finally redirected as configured now to...
https://{elsewhere}/woof/meow/baz.ext
That seems to be getting a bit complex for this service. One of the main reasons this service exists is to avoid that initial domain in the first place! The idea was that semantic web resource naming was using domains or resource paths that change due to expired domains, changed ownership, maintainers that are gone, etc etc. So this service tries to provide URLs that could be stable for decades if needed by just updating redirect rules. But if you put a custom domain in front of that, you are back to the same problem that people might use that domain and then it expires and invalidates anything that was dereferencing those URLs.
I doubt this feature will happen anytime soon since the operational issues seem non-trivial. Would need background tasks to map added/changed/removed CNAMEs over to some load balanced front end that sets up letsencrypt certs and keeps them updated. And then internally maps domains to paths. That's a bit much for what would probably end up being a task for me. :-)
from w3id.org.
For the OBO PURLS, we initially bought the domain obolibrary.org and came to an agreement with purl.org that we could aim purl.obolibrary.org at purl.org, with all our PURLs having the prefix /obo/. This turned out to be a fortuitous choice when PURL service was interrupted.
As it turns out, OBO now runs our own PURL service.
Now I am working with another organization that is considering using PURLs and I would like to do the same, if they decide to go ahead. The situation would be easier than you outline. The domain record for our domain would have a CNAME with w3id.org. We would use a PURL of the form https://example.org//foobar/baz, to https://w3id.org//foobar/baz, so no URL rewriting necessary. If the PURL service is the only domain hosted at w3id.org, then there is no need for further setup. Otherwise, the web server needs a VHOST entry to recognize our domain. The only ongoing cost is our domain registration.
I very well understand the intent of w3id and I hope it is indeed up and running in decades. But purl.org was also supposed to last forever. I don't recall exactly, but IIRC when purl.org came back up a year late at archive.org, the redirects database was not complete and the server had different redirect capabilities so we would have had to be reconfigured. In any case, when it went down it was undetermined if it would ever come back and we didn't want to wait and see. Having our own domain saved the day. I hope you can understand the desire to hedge our bets.
from w3id.org.
Related Issues (20)
- Fix broken redirect in rebase entry HOT 1
- Help needed - why aren't my redirections working? HOT 1
- Scalable id storage
- Add an "How-To-Test" to the description HOT 1
- warning on clone: case sensitive/insensitive file systems HOT 1
- allow browser (html) dereferencing of i-adopt terms to abuse the available local fragment identifiers HOT 1
- bad forward from w3id.org/mediatype/ HOT 4
- W3C Caused by: com.apicatalog.jsonld.JsonLdError: Unexpected response code [429] HOT 1
- Broken link to openspring.net under Management on the w3id.org home page HOT 1
- dggs.org broken HOT 4
- Update w3id.org homepage content with one from the latest README.md HOT 1
- add redirect test workflow / github action
- How to redirect to Ontology documentation with Widoco HOT 3
- Remove directory under /italia HOT 5
- Common format for metadata and test specifications HOT 5
- Redirection issue by certificate when importing in Protege HOT 7
- Verifiable Credential JWS2020 incorrect content-type HOT 6
- build upon @MattBlissett 's gensc PR #3946
- Additional requested static re-directions for `gensc` HOT 1
- add @turbomam as maintainer of `gensc` namespace
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from w3id.org.