"Introducing the Extensible Markup Language"
For an introduction, this brief article was a bit dense. What I got from it was that XML essentially serves as the language that separates different elements of a file. It differs from HTML in that it doesn't follow a predefined set of tags; it functions more in the structure of documents than in the content. It defines the boundaries of different parts of the document, making it really the structural integrity of digital documents. I would have a hard time explaining it any better than that...
"A Survey of XML Standards"
This gives a technical review of the most important components of XML. Though this article, I'm sure, does an excellent job of providing access to the standards expected of XML use, I'm not sure I really follow what exactly these different components are. For example, are the catalogs a part of the XML language? I wish this site would have given practical examples; I found the suggested tutorial links similarly dense and difficult to work with. However, I suppose the site does serve its function in describing the ISO approved standards- now, if I could only figure out what it is we're standardizing...
"Extending Your Markup"
A MUCH more helpful article. I liked the straightforward introduction that said XML was essentially used for annotating text, something I obviously didn't understand from reading the first article (see my above notes!). The examples helped; for example, comparing HTML layouts to XML pinpointed how the two systems were different and had different goals. Also, some of the extended capabilities make sense; I see the benefit of using namespaces to make meaningful and unique elements. I also like that this site relates XML to a library setting by showing how you can build bibliographic information clearly.
"XML Schema Tutorial"
I really like the W3schools website- it made learning the basics of HTML pretty painless, and this article was similarly straightforward. Basically, a schema sets up the components of an XML document, essentially serving as the guideline for the document you're creating. It creates a framework of ways in which data can be constructed and described. It's fairly easy to use, and supports various data types, which makes it more multifaceted. However, I'm not really seeing how it's any better to use than DTD; in the page where the two are compared, I don't really see how one is simpler than the other.
Subscribe to:
Post Comments (Atom)
Your schema comments were very well done and helped me understand the work better. I also don't really have a clue what we are standardizing, but it goes with the other lectures that standards are good in information tech to stop hazardous learning curves.
ReplyDeleteI had the same question as both of you about what was meant by "standardizing." I like the W3schools tutorials, too... they always seem to make more sense than the other articles. Maybe I should just start with them always and work backwards!
ReplyDeleteI agree with all of you, the whole standardizing thing was really confusing. I also had trouble understanding the first two articles, they seemed to be introducing a concept that you already had to be familiar with in order to understand what they were talking about.
ReplyDelete