"using" is one of those weird words: the Maven XML build file (and its settings, and a few others) still have versioned XML Schemas: e.g. https://maven.apache.org/xsd/maven-4.0.0.xsd and its friends https://maven.apache.org/xsd/

If you mean "stood up a consumer-facing service whose contract is dictated by WSDL and/or XML Schema," then I'm guessing the broad answer will be no because it's not kewl

As a TSC member of JSON Schema, the best DX thing you can push through would be the xsi:schemaLocation replacement because right now mapping files to their schema is some damn tomfoolery

> As a TSC member of JSON Schema, the best DX thing you can push through would be the xsi:schemaLocation replacement because right now mapping files to their schema is some damn tomfoolery

I'm not an XML Schema expert, and I might be missing something, but I believe what you are looking for is the "$schema" keyword (https://www.learnjsonschema.com/2020-12/core/schema/). You set it to a URI reference that can either point to a remote resource (i.e. over HTTP) or a local one using the "file://" scheme.

Peppol (https://peppol.org/) for the exchange of electronic business documents

Heavily used within energy industry systems and standards we have to work with in Germany to integrate with. A couple of examples:

- Electronic delivery receipts for metering hardware (from standard body)

- API spec for smart meter interfacing software (from vendor, feels legacy-like)

- API to interact with official sub-CAs (from government authority)

- Definitions for EDIFACT files (from standard body)