Worse, they were probably drowning in XML schema definitions.

Only one mention of XML in the redacted report, but three mentions of SBR1, so that still counts. 😁

Aha!  That leads to a bit of IT tech talk I can sort-of understand:

The MBR’s starting point for the technology architecture was Foster Moore’s 124 registry software, Catalyst. Catalyst was selected as the commercial-off-the-shelf product for the MBR implementation, following a formal approach to market and design validation with Foster Moore. 125 During the course of the program, the implementation changed to a later version of Catalyst called Verne.

Verne is a cloud-hosted registry product that uses Linux/Unix OS and a document database that is suitable for registries. It uses a lesser-known Java-based programming language called Groovy. 126 Verne provides out-of-the-box functionalities for registration management, client management, content management, access management, configuration management, analytics and reporting, data provision, account management, communication management, document management, API management, and fee and revenue management. The user interface framework provides a flexible way to generate XML based APIs.   

I've heard of Groovy, but now I see it's a Java-like static or dynamic language. Foster Moore's Verne software is some gigantic off-the-shelf corporate registry software product that claims to be highly configurable. There's no mention of what back-end database it uses.

Greg K

--
ozdotnet mailing list
To manage your subscription, access archives: https://codify.mailman3.com/