using web services print('id'item['id']print('attribute'item[' ']codeif you compare the code to extract data from the parsed json and xml you will see that what we get from json loads(is python list which we traverse with for loopand each item within that list is python dictionary once the json has been parsedwe can use the python index operator to extract the various bits of data for each user we don' have to use the json library to dig through the parsed jsonsince the returned data is simply native python structures the output of this program is exactly the same as the xml version above user count name chuck id attribute name brent id attribute in generalthere is an industry trend away from xml and towards json for web services because the json is simpler and more directly maps to native data structures we already have in programming languagesthe parsing and data extraction code is usually simpler and more direct when using json but xml is more selfdescriptive than json and so there are some applications where xml retains an advantage for examplemost word processors store documents internally using xml rather than json application programming interfaces we now have the ability to exchange data between applications using hypertext transport protocol (httpand way to represent complex data that we are sending back and forth between these applications using extensible markup language (xmlor javascript object notation (jsonthe next step is to begin to define and document "contractsbetween applications using these techniques the general name for these application-to-application contracts is application program interfaces (apiswhen we use an apigenerally one program makes set of services available for use by other applications and publishes the apis ( the "rules"that must be followed to access the services provided by the program when we begin to build our programs where the functionality of our program includes access to services provided by other programswe call the approach service-oriented architecture (soaa soa approach is one where our overall application makes use of the services of other applications non-soa approach is where the application is single standalone application which contains all of the code necessary to implement the application