Hearing the music on the eleventh day by improving JSON Patch with Graft
When only a part of a JSON document has changed, JSON Patch can be a quicker way of finding change within your files. Not only have we improved upon the widely known JSON patch but have created JSON graft. This service is far more useful than a standard patch which can only apply a patch to the original file. We consider Graft to be a more robust and extensible version as you can generate (and customise) a changeset which can be applied to a Graft target.
Consider this example – a company’s phone system with configuration stored in JSON. You’ve hired some new employees and need to add their details to everyone’s phonebook. However, each phone’s configuration file is slightly different. You can generate a full-context JSON Delta from one phone’s configuration to an updated version with the new phone numbers. This is used as the “Changeset” when using our Graft tool to apply these changes to the various other configuration files. Try it for yourself.
And on the twelfth day we’re reporting our wins by comparing XBRL
XBRL is the standard for digital business reporting. The business reporting standard said it best:
“XBRL lets reporting information move between organisations rapidly, accurately and digitally.”
And when content is being moved around so quickly changes can be missed, unless of course you’re including using XML Compare in the process.
Merry comparisons to all
And there you have it, the 12 days of comparisons. Whether you’re working with XML or JSON it’s evident that content will change, be moved around, sent to various people and changed and moved around again. Human error can play a mighty role in slowing down production or processes but by inserting a trusty comparison tool with 100% reliability it’s like you’re giving yourself a golden wrapped present with a big red bow. If you think you would benefit from a comparison solution we’re always here to give you a helping hand.