Where we're just being a little more formal about how we do this and basically, at some point we'll just switch from it's moving data back and forth to these are are APIs, application program interfaces. And the act of going from an internal representation on one computer out to a sort of interchange format is called serialization. And that kind of engineering of an interchange that is not particularly suited to any language better than any other language, is part of the argument of building these data oriented documents versus sort of human readable oriented documents.

XML doesn't really care what extra spaces you put in, but it certainly helps us as human beings to understand what's going on. We can pull these things up, we tend to indent them like any kind of programming environment to help our own reading. Serialization and deserialization is the act of taking from an internal structure in one programming environment, sending it across the network.

We're not going to spend a lot of time with this, but it's an important concept to sort of imagine and understand how contracts between cooperating applications have to be developed. I'm mostly talking about the one that kind of won or the one you're most likely these days to encounter called the XML Schema from the World Wide Web Consortium. And so I'm not trying to teach you how to be an XSD wizard, just the notion that there is this syntax that's used to establish a contract so that you can resolve disagreements between cooperating applications.

stuff is a tree of information that's parsed and gives us methods and attributes that we can use to go through the data. Go find the Id tag and then go grab the text field so that's going to print out 001 and we can go get the item and then there is the attribute that is directly under it. Up next, we're going to talk about a more lightweight way to store data called JSON, or JavaScript Object Notation.

And so later we'll be pulling XML and JSON from the web, but for now I'll just going to put it in a triple coded string, so data. Now we have to call this ET from string to read this and give us back a tree object. And so, that's just a basic run through of the XML from the chapter in the Python book, okay?

At the time, most of the Web was built informally using a mailing list, primarily, as our coordination mechanism. And it just worked out that being in that position was great, in that I could have a hand at making the Web better because at the time it had grown out in every direction at once. And the team that was working on the specification, mostly myself and Henrik Frystyk Nielsen at the W3C, we were asked to write the HTTP standard.

We've had a great conversation about Internet history, technology, security, and Python programming for everybody, and so I'd like to introduce you to some of the students in the class and have them say hi to you and whatever. I'm learning Python to contribute to a bunch of open-source tools I use every day. It's gonna be a couple of weeks before I have another office hour.

My background had been working in medical informatics and developing what we would now call ontology languages and reasoning systems. And I went to a meeting of a European Network, met people like Franklin Hamlin, Dieter Fencil, who were also interested in the beginnings of this area. The huge impact of OWL was just the fact that being these kind of KR languages around for donkey's years, as you know.