Reading Notes - Week of October 29, 2012

W3 School Cascading Style Sheet Tutorial: www.w3schools.com/css/

• CSS stands for Cascading Style Sheets
• styles define how to display HTML elements
• HTML was never intended to contain tags for formatting a document; rather it is intended to define the content of a document
• when tags for formatting began to be added to HTML, CSS was created so that all formatting could be removed from an HTML document and stored in a separate CSS file

I have reviewed the rest the W3 CSS tutorial

I have reviewed the CSS Tutorial, starting with HTML and CSS

Hakon Lie and Bert Bos, Cascading Style Sheets, Designing for the Web. 2nd ed. Addison Wesley, 1999.

• a rule is a statement about one stylistic aspect of one or more elements
• a style sheet is a set of one or more rules that apply to an HTML document
• a rule consists of a selector and a declaration
• selector - link between HTML document and the style; specifies what elements are affected by the declaration
• declaration - part of the rule that sets forth what the effect will be
• a declaration has two parts
• part before the colon = property
• quality or characteristic that something possesses
• part after the colon = value
• precise specification of the property
• a selector may have may have more than one declaration
• identical selectors can be grouped together on one declaration
• the style sheet must be "glued" to the document in order to affect the HTML

Muddiest Point - Week of October 22, 2012

I do not believe I have a muddiest point for this week.

Reading Notes - Week of October 22, 2012

I have reviewed the W3Schools HTML tutorial and the HTML cheat-sheet.

F.E. Pratter. "Introduction to HTML." From Web Development With SAS By Example. 3rd Edition.

• HTML = hypertext markup language 
• a webpage is a ASCII text file with markup tags inserted to display and format the text

Doug Goans, Guy Leach, Teri M. Vogel. "Beyond HTML: Developing and Re-imagining Library Web Guides in a Content Management System." Library Hi Tech 24. no. 1. (2006): 29-53

• content management = the process of collecting, managing, and publishing content
• in content mangement systems, content is separated from layout and design, so users do not have to use HTML
• CMS allows users to control how content is distributed and presented
• there are many different types of CM systems

Muddiest Point - Week of October 15th, 2012

I have no muddiest point for this week.

Notes - Week of October 15, 2012

Tyson, Jeff. "How Internet Infrastructure Works."

Every computer that is connected to the internet is part of a network, which is provided by an internet service provider (ISP). Large communication companies have points of presence (POP), which is a place where local users can access the company's network. There is no overall controlling network; there are several high-level networks connecting through network access points. Networks depend on network access points, backbones, and routers to communicate. Every machine on the internet has a unique identifying number called an IP address. The domain name system was created so IP addresses would not have to be memorized. All machines on the internet are either servers or clients. Servers have static IP addresses that rarely change.

"Dismantling Integrated Library Systems."

• the introduction of the web forced change onto integrated library systems
• old softwares were updated to meet customer demand
• creating an entirely new ILS is unrealistic
• integration with the web is key

Sergey Brin and Larry Page. "The Genesis of Google."

• data has to move all over the world quickly, and it is very difficult to do so without lag
• searching is tricky since search engines are not "intelligent"

Muddiest Point - Week of October 8/9, 2012

I'm still a bit confused by the concept of network architecture. Is it the relationship between devices in a network?  

Muddiest Point - Week of October 1, 2012

I do not have a muddiest point for this week, but I do find metadata quite fascinating!