- From: Norm Tovey-Walsh <ndw@nwalsh.com>
- Date: Fri, 19 Aug 2022 12:59:14 +0100
- To: Greg Hunt <greg@firmansyah.com>
- Cc: xmlschema-dev@w3.org
- Message-ID: <m2edxcsacn.fsf@nwalsh.com>
> I'm somewhat familiar with using XML catalogs, but I know very few > people these days who both write code and know what resolvers are for. […] > I have had quite senior people tell me that namespaces are too difficult > (as they remove them from designs). *Shrug* People get all kinds of intuitive ideas about what’s difficult and what isn’t. I wouldn’t be surprised if some of those same senior folks think there’s nothing too difficult about a Kubernetes cluster running on Docker containers in AWS split across two regions supporting a cluster of Node.js applications with 1,600 dependencies that are updating a Mongo database configured to be fault tolerant. There has been a lot of poisonous rhetoric about namespaces in some quarters. I’ve largely given up fighting about it. > It looks like openjdk11 is still using Xerces 2.11 from 2010 so the > idea that people will update their XML parser (that is baked into > their JRE) is highly implausible. Yep. I have no idea if the cost-benefit analysis of suddenly redirecting decades-old HTTP resources to HTTPS is a net positive or net negative. I think the argument to leave them as HTTP because legacy applications will break along with the implicit or explicit promise that “cool URIs won’t change” has a lot of merit. Luckily, it’s not my call. I’ll just do my best to help folks deal with the consequences if it happens. Be seeing you, norm -- Norman Tovey-Walsh <ndw@nwalsh.com> https://nwalsh.com/ > Patriotism is often an arbitrary veneration of real estate above > principles.--George Jean Nathan
Received on Friday, 19 August 2022 12:10:23 UTC