Friday, October 31, 2008

Friday, October 24, 2008

Week 9 Comments

Comment 1

Comment 2

Muddiest Point 10/21/2008

It was difficult for me to come up with a muddiest point this week. However, I guess I will pose a question: We talked about website editors in class (frontpage, dreamweaver, nvu, kompozer); which would you recommend? Is one easier to use than others? Is one more for someone with extensive experience, and another better for a beginner?

Tuesday, October 21, 2008

Week 9 Readings

Martin Bryan. Introducing the Extensible Markup Language (XML) http://burks.bton.ac.uk/burks/internet/web/xmlintro.htm
This was similar to the cheatsheets we read before, except it is about XML. It also explains more deeply than a cheatcheet. Overall, it gave a good introduction to XML, and wasn't difficult to follow.

Uche Ogbuji. A survey of XML standards: Part 1. January 2004.
http://www-128.ibm.com/developerworks/xml/library/x-stand1.html
This was a good article about XML, discussing the core XML technologies. One thing I particularly liked about this article was all their links: links to various tutorials, references, and other resources as well. You would need to devote much time, though, if every link were to be followed, as each paragraph had several hyperlinks.

Extending your Markup: a XML tutorial by Andre Bergholz http://www.computer.org/internet/xml/xml.tutorial.pdf
(It says I would have to buy the article for $19; it is from IEEE Internet Computing, July 2000, pp.74-79... I will try to read this another way....) About this article, it says: XML introduces a family of languages to provide a more semantic management of information than HTML. (Later...) I finally accessed this article through: http://xml.coverpages.org/BergholzTutorial.pdf (am I the only one who had difficulty with this?). I must say, I liked the other things we've read better (links to tutorials or cheatsheets).

XML Schema Tutorial http://www.w3schools.com/Schema/default.asp
This tutorial teaches how to read and create XML Schemas and how to use the language. It offers many links and is very easy to find certain topics. Overall, I thought this was a great website.

Monday, October 6, 2008

Week 8 Comments

Comment 1

Comment 2

Comment 3

Muddiest Point 10/07/2008

I understand Wi-Fi, what is it, what it does, etc. I was wondering, though, where the "Fi" part of the name comes from? Is it just because it rhymes, or does it stand for something?

Week 8 Readings

***W3schools HTML Tutorial: http://www.w3schools.com/HTML/
Okay, I am VERY excited about this site! I had just been wishing over the past few weeks that I could have this taught to me...and here I am learning it! This site did a great job of explaining how to write HTML, so that any beginner should be able to follow it. I have added this to my 'favorites!'

HTML Cheatsheet http://webmonkey.wired.com/webmonkey/reference/html_cheatsheet/
(or rather: http://www.webmonkey.com/reference/HTML_Cheatsheet/)
I thought this would be just the same as the first site, but was pleasantly surprised. This site laid it all out so the basics were all on one page--very nice! It does just what it says: gives you a cheatsheet for HTML. Again, just what I wanted! This is definitely for a beginner. It also has links to other related articles.

W3 School Cascading Style Sheet Tutorial: http://www.w3schools.com/css/
One thing I liked about this site is that they offer a 'diploma' for developers who want to document their knowledge of HTML, XHTML, and CSS. (Not for me, yet, but could be great for someone who is ready for that!) They also have many links for web hosting or web building, which is very helpful if that is what you need. I will definitely be spending more time with all three of these sites!

Goans, D., Leach, G., & Vogel, T. M. (2006). Beyond HTML: Developing and re-imagining library web guides in a content management system. Library Hi Tech, 24(1), 29-53.
This article got me thinking about some of the issues I may face when I begin working in an Academic Library. As GSU experienced, before they had a web developer everyone did their handouts whichever way they knew how--i.e.: no consistency, and problems such as some being detailed and some being vague. Once they had a web developer, they became more organized, using such things as templates to offer better service and more consistency. With the technological advancements we are seeing, any large library nowadays really needs to have someone filling a 'web development librarian' position. Even with this position filled, technological issues may arise, requiring additional procedures or policies to be put in place.