That's the way it works. You consume it once.
You'll get a mail once processed. But probably not this year

The link points to the leaderboard of 2019

this is 2020 leaderboard  as seen above.

OK. The first time I followed to the end. 
The code I was forced to produce by time pressure is so ugly and dirty that I refuse to publish it.
Nevertheless a  clear demonstration for what was ISOS (aka COS) NOT designed for:
Higher mathematical calculus, matrix transformations, arrays with independent dimensions, ....
[ Though I have to admit that I encountered tensors, rotors, matrix transformations, Mr. Fermat's theories, ... only at university 50+ years ago. And I didn't miss it in between ]

There was no demand for the real strengths of IRIS!
In addition, I verified my personal credo that writing some code in ISOS/COS
only because it is possible makes no sense and is of no commercial value.
Especially with the broad range of options in  IRIS to include external code.   

It is written by the standard ERROR logger ^%ETN.int used allover system routines.
You can see it in SMP/ application errors. And it might be wise to examine it if it is growing so fast.

here it is:
https://www.trustradius.com/reviews/intersystems-iris-2020-12-15-16-53-48
 

A GREAT improvement! 

Though a challenge to the voters: They have to make a decision ! 

THX.  Just verified it.

Hmm. The link to GM says:

Ooops!

Sorry friend, looks like this challenge is no longer available.

My title: " Never say IMPOSSIBLE with IRIS " 

I fully support you.
Out of tradition, there is a tendency to implement already existing solutions though  better
and well-positioned on the markets. 
@Dmitry Maslennikov :
- you might remember times when even a webserver was written inside Caché
- or various text editors, source manager packages, and ..., and ... and ...
JUST because it was possible.

Decades back you had your globals and your language and not even an OS below.
But this was in previous millenium. This time is definitely over.
 

I missed this during a migration from Caché to IRIS.
There were roughly 1500 routines and ~2000 classes. grown over >15 years.
The point was to find out dependencies and estimate the impact of changes.
 

A cross-reference for external Classmethods and/or routines within:

• a routine
• a class
• a package of classes
• a package of routines

this

The key issue I see is: Is there a Related XML schema available.
If YES:
- you can generate a package with the existing tools
- import the file with %XML.Reader
- do an %JSON... export
The XML schema is necessary because straight XML is just TEXT with no datatypes
while JSON has data types. For XML the type of data is documented in XML Schema.

If NO:
You may call any of the public available XML to JSON converters.
They may guess rather easy for numerics vs. strings in most cases.
But detecting Boolean (true /false ) vs. Integer is somewhat mysterious to me.

My personal opinion: re-inventing this wheel is not worth the effort.
Writing an adapter makes sense 
 

Thank you @Nigel Salm !

The buzzword "language"  distracted me.
In IRIS our good old ENSEMBLE was renamed to Interoperability and is there by default.

​​​​​@Heloisa Ramalho you should know it best and could give  a native explanation

Thanks!  

In DC ANALYTICS / Authors what do these column headers stand for?

• Comment Rating
• Post Rating
• VPP Context
• VPP Absolute

For Rating I'd expect Votes ? 
But VPP ? 

   docs sounds boring