Why aren't we using the built-in Logic Apps expressions json & xml instead exposing our own XML-JSON component?

[stijnmoreels]

The Logic Apps expressions include json and xml to transform between the two, without the need for external calls or Azure Integration Accounts. It was specifically designed to be built-in, fast, and independent.
Why would we then expose such XML-JSON component ourselves?

[pim-simons]

I personally have not used these components, but did find information in this thread which also includes the initial design.

Your question is not new, see:

how is this component different than the standard json() and xml() statements available in Logic Apps?

At one of my customers we map json to xml by using the xml() statement and using that output to call the transco component. What does this component offer as extra functionality?

well, does this component still makes sense if you can map json to xml by using the xml() statement directly on Logic Apps?

What this component apparently adds is to be able to also execute a mapping, which I still think is a strange place to do so (we should use the transco for that) but that was my comment in that thread back than also.

As you said, I just use the built in Logic App expressions for this, no need for an extra call to our framework. I do see some value in these components if you would need to move from JSON to XML or vice-versa outside of Logic Apps maybe.
@GoutsmitSam @Pauwelz we should checkout which projects this component is used and what the usecase for it is.