kltm

Tagging @cmungall

@jamesaoverton This looks like a very well thought out plan. I have a few observations that you may find more or less useful. As far as administration goes, an organization...

For cheap, nothing beats the free infrastructure transfer at an institution. Redundancy and fast DNS control can be supplied by AWS (Route 53, etc.), with the actual file hosting occurring...

Chrome, "Version 100.0.4896.88 (Official Build) (64-bit)" on Linux works for me. Usually, there is a prohibition on mixed schema within a page, to prevent data leaking, trackers, etc.; blocking links...

@matentzn Clicking on that works for me. It sounds like behavior I ran into with an HTTPS everywhere plugin I used to run. I would suggest trying with a temporary...

Alas. We're on the same version and I can guarantee I'm on a completely unaltered installation, so I'd still put the weight on local issue. Possibly work through https://support.google.com/chrome/thread/16888999/links-won-t-open-in-chrome?hl=en It...

kwalify allows a regexp on fields; what are you using?

We now have something like this for something similar: ```regexp /^((ht|f)tp(s?)\:\/\/\w[\/\.\-\:\w]+)|(GOC\:[\w\_]+)$/ ``` Maybe you could have something like: ```regexp /^(https?|ftp)\:\/\/\w[\/\.\-\:\w]+$/ ```

For at least the slashes, I have put in a PR here: https://github.com/OBOFoundry/purl.obolibrary.org/pull/268 I also noticed a few places that could probably be improved, but I'm unsure if there are...

Looking at `products` specifically in the schema, I was going to put in a regexp like: ``` /^[a-zA-Z0-9\.]+\:\s+(https?|ftp)\:\/\/[a-zA-Z0-9][\/\.\-\:\?\=\&\#\%\!\$\~\w]+$/" ``` However, that will not work as the structure that you're using...