via How we turned JSON into a full programming language — relevant stories — Medium.
This article has received a far stronger response than we expected, so it merits an update: We are not aiming to recreate XSLT, or to “disrupt JSON” in any way. We have built a pretty strong back-end engine to output cards for the Relevant iOS App. And on top of it, we’re presenting this macro-based JSON syntax that is compatible with a (soon to be released) drag-and-drop GUI, much like that of Yahoo Pipes, IFTTT, or similar tools/apps.
The fact that the resulting JSON syntax has, only in theory, the form of a functional programming language, is just an interesting side effect.
via Transforming XML Data with XSLT (The Java™ Tutorials > Java API for XML Processing (JAXP) > Extensible Stylesheet Language Transformations).
The Extensible Stylesheet Language Transformations (XSLT) APIs can be used for many purposes. For example, with a sufficiently intelligent stylesheet, you could generate PDF or PostScript output from the XML data. But generally, XSLT is used to generate formatted HTML output, or to create an alternative XML representation of the data.
In this section, an XSLT transform is used to translate XML input data to HTML output.
via Message Content Filtering with WSO2 ESB | The Pragmatic Integrator.
Every integration architect or developer should be familiair with Enterprise Integration Patterns (EIP)as described by Gregor Hohpe and Bobby Woolf. One of the patterns is the ‘Content Message Filter’ (not to be confused with the Message Filter pattern).
There are multiple ways to achieve this in WSO2 with different Mediator. One way is using the XSLT Mediator where you can simply use an XSLT to do the filtering. The other one (not so obvious based on the name of it) is the Enrich Mediator.
via XML Manipulation With XML Copy Editor | Keyhole Software.
The XML document format, created in 1996, is still widely used to facilitate communication between disparate systems (though for certain implementations is somewhat being replaced by JSON). As a Java developer, I generally interface with data in an XML document via a DOM parser, but there are occasions where being able to manipulate an XML document directly is advantageous or even necessary.
This might be achievable in a simple text editor in unlikely cases where the document in question is particularly small, but often these documents can be quite large. Thus, it would be beneficial to be able to manipulate the document in a program specifically designed for that type of job.
In my case, I don’t need to do this type of thing often enough to justify paying for such a piece of software, but I have found that XML Copy Editor has fulfilled my needs for free.
A project I am working on communicates with another piece of vendor software through SOAP calls. Sometimes the vendor software does not behave as expected, data gets corrupted, and must be remedied. With no way to facilitate this through the client’s UI, the solution is to directly manipulate the XML data and return it to the vendor system via a SOAP call. This process involves often several pieces of data, delineated by locality (in this case, the state). These files can be up to 10 MB in size, with entries for all 50 states. In my experience, XML Copy Editor has never had any struggle in handling large files, which is of great benefit.
In the proceeding paragraphs, I will be describing not only XML Copy Editor, but will also be providing a quick tutorial of XML/XSLT/XPATH. Taking the following as an example, which is a simplified representation of the type of file I usually work with: