Generate metrics.xml in pure Java, without XSLT

[ilyakharlamov]

The current architecture relies heavily on XSLT for data analysis.
If we want to implement issues like #204 with advanced semantic indexing such as ML, LSI, NLP
we'll have to use external Java libraries since it's very challenging to do complex calculations in pure XSLT.
So we need to have an option to generate an XML report by name, that is implemented in Java, not XSLT.

[0crat]

@paulodamaso/z please, pay attention to this issue

[danilomo]

The class Report doesn't follow a contract. It's a concrete class that ties the report generation to the XSL implementation.

Refactoring with extract interface should allow custom metrics to be implemented in Java rather than in XSL.

[ilyakharlamov]

@danilomo Yes, I think Report should become an interface and the current concrete class Report renamed to XslReport or something

[danilomo]

@yegor256

Some graph algorithms are extremely annoying to implement with XSL. They are doable, though, since you can have recursive templates, but nevertheless, it would be way easier to write them in Java.

So, I would like to know what do you think about this issue.

Thanks in advance.

[paulodamaso]

@ilyakharlamov How about making some performance tests to measure xml speed / efficiency and then implement some routines in java to compare both?

[ilyakharlamov]

@paulodamaso This issue is not about the performance.
The original problem is that it's close to impossible to implement graph traversal algorithms that are needed for advanced semantic indexes, like depth-first search, A* algorithm, Dijkstra algorithm etc using XSLT.
Better performance can be a nice bonus, but the real issue is the graph traversal.

[paulodamaso]

@ilyakharlamov Understood the problem. XSL was chosen because its performance, but as it does not have the required features it's time to move on to some more robust implementation.

[paulodamaso]

@0crat in

[0crat]

@0crat in (here)

@paulodamaso Job #296 is now in scope, role is DEV

[0crat]

Bug was reported, see §29: +15 point(s) just awarded to @ilyakharlamov/z

[0crat]

The job #296 assigned to @ebercamargo/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

[0crat]

Resigned on delay, see §8: -30 point(s) just awarded to @ebercamargo/z

[0crat]

The user @ebercamargo/z resigned from #296, please stop working. Reason for job resignation: It is older than 10 days, see §8

[0crat]

The job #296 assigned to @monomonedula/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

[yegor256]

@paulodamaso @danilomo I agree that we should think about Java implementations of Report

[0crat]

The user @monomonedula/z resigned from #296, please stop working. Reason for job resignation: It is older than 10 days, see §8

[0crat]

Resigned on delay, see §8: -30 point(s) just awarded to @monomonedula/z

[0crat]

@paulodamaso/z not enough funds available in the project, can't set budget of job #296, see §21; @RajanAMistry/z will get no money on completion; in order to fix that, add funds to the project and assign the job again

[0crat]

@RajanAMistry/z this job was assigned to you 8days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

[0crat]

The user @RajanAMistry/z resigned from #296, please stop working. Reason for job resignation: It is older than 10 days, see §8

[0crat]

Resigned on delay, see §8: -30 point(s) just awarded to @RajanAMistry/z

[0crat]

@paulodamaso/z not enough funds available in the project, can't set budget of job #296, see §21; @uurl/z will get no money on completion; in order to fix that, add funds to the project and assign the job again

[0crat]

@uurl/z this job was assigned to you 8days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

[0crat]

Resigned on delay, see §8: -30 point(s) just awarded to @uurl/z

[0crat]

The user @uurl/z resigned from #296, please stop working. Reason for job resignation: It is older than 10 days, see §8

[HDouss]

@ilyakharlamov I resolved the main part

So we need to have an option to generate an XML report by name, that is implemented in Java, not XSLT.

The option is now here. That's what can be done in 30min. I don't know if you/we should create separate issues for specific metrics to be implemented in Java, or if you have in mind any specific metric that absolutely must be implemented, I could add a puzzle.

[HDouss]

@paulodamaso any opinion here?

[paulodamaso]

@HDouss We need to have hooks / checkpoints which allows us to continue to break a complex task in many other micro-tasks. These hooks came in forma of puzzles in the code, and using them we will be able to know how much we still have to do and what is left to implement for our feature to be complete. I should have asked you to put these puzzles in the code before the merge. We need these puzzles, so could you please add them?

[HDouss]

@paulodamaso that's what I said in:

The option is now here. That's what can be done in 30min. I don't know if you/we should create separate issues for specific metrics to be implemented in Java, or if you have in mind any specific metric that absolutely must be implemented, I could add a puzzle.

However the puzzle should be precise. Should we implement all the metrics in Java? Are they some must-have implementations in Java. I can't just say "implement some metrics" in Java.

[HDouss]

@paulodamaso puzzle added in PR #389

[0pdd]

@ilyakharlamov the puzzle #390 is still not solved.

[HDouss]

@ilyakharlamov PR #389 added a puzzle and merged. Please close the issue.

[HDouss]

@ilyakharlamov ping

[HDouss]

@ilyakharlamov PR #389 merged. Please close the issue.

[0crat]

@sereshqua/z please review this job completed by @HDouss/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

[sereshqua]

@0crat quality good

[0crat]

Order was finished, quality is "good": +35 point(s) just awarded to @HDouss/z

[0crat]

Quality review completed: +4 point(s) just awarded to @sereshqua/z

[0pdd]

@ilyakharlamov 2 puzzles #396, #397 are still not solved; solved: #390.

[0pdd]

@ilyakharlamov the puzzle #397 is still not solved; solved: #390, #396.

[0pdd]

@ilyakharlamov the puzzle #408 is still not solved; solved: #390, #396, #397.

[0pdd]

@ilyakharlamov 2 puzzles #412, #413 are still not solved; solved: #390, #396, #397, #408.

[0pdd]

@ilyakharlamov 3 puzzles #413, #416, #417 are still not solved; solved: #390, #396, #397, #408, #412.

[0pdd]

@ilyakharlamov 2 puzzles #413, #416 are still not solved; solved: #390, #396, #397, #408, #412, #417.

[0pdd]

@ilyakharlamov 3 puzzles #416, #440, #441 are still not solved; solved: #390, #396, #397, #408, #412, #413, #417.

[0pdd]

@ilyakharlamov 5 puzzles #416, #441, #443, #444, #445 are still not solved; solved: #390, #396, #397, #408, #412, #413, #417, #440.

[0pdd]

@ilyakharlamov 4 puzzles #416, #441, #445, #459 are still not solved; solved: #390, #396, #397, #408, #412, #413, #417, #440, #443, #444.

[0pdd]

@ilyakharlamov 4 puzzles #416, #441, #472, #473 are still not solved; solved: #390, #396, #397, #408, #412, #413, #417, #440, #443, #444, #445, #459.

[0pdd]

@ilyakharlamov 2 puzzles #416, #473 are still not solved; solved: #390, #396, #397, #408, #412, #413, #417, #440, #441, #443, #444, #445, #459, #472.

[0pdd]

@ilyakharlamov 2 puzzles #416, #484 are still not solved; solved: #390, #396, #397, #408, #412, #413, #417, #440, #441, #443, #444, #445, #459, #472, #473.