Learning XML
About four years ago when we started podcasting in the library I had to learn about XML (Extensible Markup Language) to create a functional RSS feed. We were also asked to begin investigating the pros/cons of RSS and RDF as we first started research work in developing our digital library. So XML quickly became a major part of my working life whether I liked it or not.
I initially learned XML by just looking at what other websites, podcasters, and repositories had done and how they were organized. I also went through various web tutorials, W3.org info pages, and even the Apple iTunes help pages on what elements were necessary to make our feeds work. This process was very unconventional and for the most part worked for my needs but was spotty and to be honest confusing.
Unit 7 of our class has been largely focused on the purpose and use of XML. We were instructed to view a series of instructional videos by Mark Long. Those videos, along with our readings, and the course lecture and assignment notes have been invaluable because I not only learned basic XML structure, which I was familiar with, but the basic rules that apply to that structure. I learned that "well formed" XML may not necessarily "Validate" against the rules of the DTD it is associated with. I don't find XML to be quite that confusing anymore but then I haven't even tackled XSLT (Extensible Stylesheet Language Transformations) yet.
The most helpful modules in the videos tutorials were the ones on structure (5 golden rules!), special characters (watch out for those greater than symbols), and most importantly attributes. I'm still not 100% on when to use or not use attributes in XML (I had actually never considered them myself) but it seems as though, most everyone else is still asking that same question.
Practice system update!
So far, so good! I followed the instructions in our Unit 7 assignment and was able to connect to my new "server" remotely, and even though it's a laptop run it in Headless Mode, which for non techies means I didn't use a keyboard or monitor actually attached to the system. In fact, to emulate the sense that the system was indeed headless, I closed it up and stuck it under my desk. Worked like a charm. I have been simultaneously running my VM system as well for added practice and was able to ping both systems and essentially have two separate servers running in my house. Albeit, closed systems. Each system also now has a personal web space for a user, which helped me understand the whole public folders at both the ASU and UofA personal web space accounts.
Tuesday, July 07, 2009
Monday, June 29, 2009
Learning HTML
This week we were asked to talk about how we went about learning HTML and the resources we used.
I probably began learning html around 2001 or 2002 which compared to many people I know was late in the game, but my concentration prior to that only required I view web pages, not write them.
My first resource was my coworker and onetime supervisor Kirk. He gave me a lot of initial pointers and basically said to just look at other web pages and see what they were doing and try to avoid using "flashing" text. I also used the W3 school to get the basics and details down. I still use the school today. In fact, I had gotten so use to Dreamweaver and bouncing back and forth between the code and the WYSIWYG editor that I had to double check hand coding basic things.
Some of the more intermediate or advanced areas I looked at were table cells attributes like padding and alignment. I also looked into CSS which I use regularly in my work related dealings but not from scratch, so at this point I have not integrated a stylesheet into my class webpage. Since I'm coding just one or two pages (at this point) I'm not saving much time but if my page were to grow or become more complex I would need to invest the time into a seperate or inline style sheet to better handle the look of the page.
I really wanted to just hand make my class page without the aid of any GUI interfaces. For example Word (and products like it) is one of the worst ways to build a page as it introduces a lot of span tags and back end code you are not aware of and don't need. Some of those interfaces also have a tendancy to leave empty tags hanging around when you cut or delete content.
On an additional milestone I finally installed my practice system and eveything went well. I was able to ping by host name and assign static IPs to both my practice and VM servers. I was even able to see the webpages via m iPod which is connected to the network wirelessly. Now if I can continue to remember all the steps involved I'll be very impressed with myself. The only hangup I had was when I was pinging my practice system and got "host down." I had forgotten to plug in the ethernet cord.
I probably began learning html around 2001 or 2002 which compared to many people I know was late in the game, but my concentration prior to that only required I view web pages, not write them.
My first resource was my coworker and onetime supervisor Kirk. He gave me a lot of initial pointers and basically said to just look at other web pages and see what they were doing and try to avoid using "flashing" text. I also used the W3 school to get the basics and details down. I still use the school today. In fact, I had gotten so use to Dreamweaver and bouncing back and forth between the code and the WYSIWYG editor that I had to double check hand coding basic things.
Some of the more intermediate or advanced areas I looked at were table cells attributes like padding and alignment. I also looked into CSS which I use regularly in my work related dealings but not from scratch, so at this point I have not integrated a stylesheet into my class webpage. Since I'm coding just one or two pages (at this point) I'm not saving much time but if my page were to grow or become more complex I would need to invest the time into a seperate or inline style sheet to better handle the look of the page.
I really wanted to just hand make my class page without the aid of any GUI interfaces. For example Word (and products like it) is one of the worst ways to build a page as it introduces a lot of span tags and back end code you are not aware of and don't need. Some of those interfaces also have a tendancy to leave empty tags hanging around when you cut or delete content.
On an additional milestone I finally installed my practice system and eveything went well. I was able to ping by host name and assign static IPs to both my practice and VM servers. I was even able to see the webpages via m iPod which is connected to the network wirelessly. Now if I can continue to remember all the steps involved I'll be very impressed with myself. The only hangup I had was when I was pinging my practice system and got "host down." I had forgotten to plug in the ethernet cord.
Monday, June 22, 2009
Reflecting on Learning - course presentation materials for our Networking Unit.
This week in my Applied Technology course we had a variety of learning materials to work with including the standard lecture document, a chapter out of the Linux Administration Handbook, some videos and other links to technical materials.
First we had the course lecture. I had to read this one at least twice to grasp all the details and make sure I understood where Professor Fulton was coming from. That paid off, because as I went throughout the related/suggest links and readings everything came together and was reinforced.
Taking a look at the Linux Administration Handbook's chapter 12 (2nd Edition) on Networking much of the professors lectures were repeated but from a slightly different narrative and as usual full of details. Although the book says its not necessarily designed for beginners, I disagree, its a must have. The historical references and figures were a great compliment to the lecture materials. The footnotes also turned out to be just as important as the paragraph materials, particularly in the section dealing with the "Request For Comments" documentations.
The Wikipedia links were invaluable for their brief synopsis and their structure allows you to skim through if you choose and hit the highlights. Also, being able to drill down through subsequent term links helps build a better understanding of the subjects we're investigating.
We were also asked to watch a few videos about networking. TCP/IP - An Animated Discussion was a basic analogy of how the protocol works. Even though it looked like it was created in Microsoft Paint I found it effective and even entertaining for a subject that had me dose a bit in the Nemeth book. Heavy in humor and analogy the video can be watched several times and goes into the alphabet soup of Internet protocols and systems. The video reminded me of some old Annenburg educational videos I use to like watching in high school, so I found it very easy to watch and retain.
A far more surreal and even effective video was Warriors of the Net. Somehow the creators of the videos were actually able to personify things like "The Ping of Death" and "The Router Switch." This is a highly produced, animated video that takes a look at what happens when you click on a link and request a service (in this case the very video) from a web page. Perhaps seeing Tron as a kid helped me connect with the presentation. Either way, it really drove home the efficiency of information transmission and how "errors" can happen.
I consider myself a visual on hands (Active) learner so the activities we were given are always the most effective. The videos reinforce the readings and the readings reinforce the lectures and provide the details and history we need to move forward. But the complexity of what we are working with in many ways brings out my more "reflective" half as well. At times this is frustrating because I do feel like I'm getting behind (when 3 days after I've started a section and I'm still reading) but I also realize that if I don't do the preliminary work the rest is meaningless. Perhaps it's just getting me back to the way I learned years ago with flash cards and memorization over simple application and experimentation.
This multi-teared way of learning is interactive, interesting and well rounded. I also find the quizzes very helpful as they provide a sort of "self-diagnostics" on what we are learning and how we are interpreting the information. There were a couple of questions that I had to go back over and rethink to realize I was oversimplifying some of the concepts. I hope the rest of the course is structured like this.
First we had the course lecture. I had to read this one at least twice to grasp all the details and make sure I understood where Professor Fulton was coming from. That paid off, because as I went throughout the related/suggest links and readings everything came together and was reinforced.
Taking a look at the Linux Administration Handbook's chapter 12 (2nd Edition) on Networking much of the professors lectures were repeated but from a slightly different narrative and as usual full of details. Although the book says its not necessarily designed for beginners, I disagree, its a must have. The historical references and figures were a great compliment to the lecture materials. The footnotes also turned out to be just as important as the paragraph materials, particularly in the section dealing with the "Request For Comments" documentations.
The Wikipedia links were invaluable for their brief synopsis and their structure allows you to skim through if you choose and hit the highlights. Also, being able to drill down through subsequent term links helps build a better understanding of the subjects we're investigating.
We were also asked to watch a few videos about networking. TCP/IP - An Animated Discussion was a basic analogy of how the protocol works. Even though it looked like it was created in Microsoft Paint I found it effective and even entertaining for a subject that had me dose a bit in the Nemeth book. Heavy in humor and analogy the video can be watched several times and goes into the alphabet soup of Internet protocols and systems. The video reminded me of some old Annenburg educational videos I use to like watching in high school, so I found it very easy to watch and retain.
A far more surreal and even effective video was Warriors of the Net. Somehow the creators of the videos were actually able to personify things like "The Ping of Death" and "The Router Switch." This is a highly produced, animated video that takes a look at what happens when you click on a link and request a service (in this case the very video) from a web page. Perhaps seeing Tron as a kid helped me connect with the presentation. Either way, it really drove home the efficiency of information transmission and how "errors" can happen.
I consider myself a visual on hands (Active) learner so the activities we were given are always the most effective. The videos reinforce the readings and the readings reinforce the lectures and provide the details and history we need to move forward. But the complexity of what we are working with in many ways brings out my more "reflective" half as well. At times this is frustrating because I do feel like I'm getting behind (when 3 days after I've started a section and I'm still reading) but I also realize that if I don't do the preliminary work the rest is meaningless. Perhaps it's just getting me back to the way I learned years ago with flash cards and memorization over simple application and experimentation.
This multi-teared way of learning is interactive, interesting and well rounded. I also find the quizzes very helpful as they provide a sort of "self-diagnostics" on what we are learning and how we are interpreting the information. There were a couple of questions that I had to go back over and rethink to realize I was oversimplifying some of the concepts. I hope the rest of the course is structured like this.
Monday, June 15, 2009
Unit 4 Class Assignment: Adding Users and Groups
For the first time I had almost no problems running through our course exercises. Unit 4 deals largely with permissions and adding users and groups. Our main focus was learning how to add a user and group via the command line and then comparing that with a couple of GUI management tools.
To aid myself in working in the shell, and for future reference, I began writing the basic commands and articles on post it notes and putting them around my desk for easy reference. I used a simple name I could remember for the second user and using the various "sudo" commands as directed was able to add the new user, who was automatically added to a group, and then verify that all went well.
Next we used the Gnome Desktop Utility and being a GUI it not only went well it not only was very intuitive but allowed me to add additional information like contact phone number and address. That was a feature I didn't notice right away with the other adduser utilities. Also Gnome is a feature within the Ubuntu desktop. Opening it was a simple as going to the drop down menus and selecting the application.
Finally we used Webmin and of the three it was probably the easiest to use for actually adding users. The installation was a little more complex as we had to run some aptitude commands to install and configure it. Again I had no problems but had I made one typo or overlooked something I probably would have had different results. Webmin has a very friendly user interface but lacks the advantage of being fully integrated into the desktop (like Gnome) or as simply a part of the system like like the command line.
Altogether I really liked all three ways to add users and if I had to choose would probably use Webmin. However, one thing I wonder about is if you didn't just stick with one utility to add users and groups what issues would you have. Would one utility wipe out the functionality of a user that was created with a different utility if their formatting does not makes sense to each other.
To aid myself in working in the shell, and for future reference, I began writing the basic commands and articles on post it notes and putting them around my desk for easy reference. I used a simple name I could remember for the second user and using the various "sudo" commands as directed was able to add the new user, who was automatically added to a group, and then verify that all went well.
Next we used the Gnome Desktop Utility and being a GUI it not only went well it not only was very intuitive but allowed me to add additional information like contact phone number and address. That was a feature I didn't notice right away with the other adduser utilities. Also Gnome is a feature within the Ubuntu desktop. Opening it was a simple as going to the drop down menus and selecting the application.
Finally we used Webmin and of the three it was probably the easiest to use for actually adding users. The installation was a little more complex as we had to run some aptitude commands to install and configure it. Again I had no problems but had I made one typo or overlooked something I probably would have had different results. Webmin has a very friendly user interface but lacks the advantage of being fully integrated into the desktop (like Gnome) or as simply a part of the system like like the command line.
Altogether I really liked all three ways to add users and if I had to choose would probably use Webmin. However, one thing I wonder about is if you didn't just stick with one utility to add users and groups what issues would you have. Would one utility wipe out the functionality of a user that was created with a different utility if their formatting does not makes sense to each other.
Subscribe to:
Posts (Atom)
