Friday, October 31, 2014

Week 9: CSS

1. W3 School Cascading Style Sheet Tutorial: http://www.w3schools.com/css/
2. CSS tutorial: starting with HTML + CSS http://www.w3.org/Style/Examples/011/firstcss
3. Lie, H. W. Bos, B. (1999). Chapter 2. In Cascading Style Sheets, Designing for the Web (2nd ed.). Indiana: Addison Wesley.

  • CSS
    • 1+ style sheet can influence doc. presentation
      • cascading: diff style sheets as series
    • brevity is a priority
      • short style sheets load faster
      • ++ opps for hand-coding
  • Create CSS either by 
    • hand-coding or 
    • using an editor
  • Hand-coding useful
    • to see how rules "work"
    • for more customization
  • rule: stylistic statement
    • H1 { color: green }
      • where H1: selector (which elements will be affected)
      • { color: green }: declaration (effect)
        •  color: property
        •  green: value
      • all selectors H1 will be declared the same color
  •  selectors can have 1+ declarations
    • H1 { color: green; font-style: bold; } 
  •  for CSS to take effect in  HTML,
    • place after <TITLE> but before <BODY> tags
    • also use CSS-capable browser 
      • <STYLE TYPE="text/css">  <-- declare value
      • <!--
        H1 { color: green; font-style: bold; }
        -->

  • inheritance
    • parent > child elements
    • BODY { color: black } will set all elements as white (unless otherwise stated) by
    • e.g. H1 { color: blue } where
      • everything but H1 will be in black
    •  other inheriting elements
      • font-style (weight); margin-top (bottom, left, right); padding
  • some properties don't inherit
    • BODY { background:url; }
  •  CSS font units
    • em: 1em = current font size
    • ex: 1ex = x-height of font (usu. 1/2 font size)
    • pt: 1pt = 1/72" font
    • pc: 1pc = 12 ps
    • px: pixels (dots on screen)
  •  Aural style sheets
    • combo of speech synthesis + sound effects
    • for ppl who are visually impaired
  •  navbar
    • after <BODY> tag
    • ul.navbar { declarations }
    • style w/ padding, margin, etc.

Thursday, October 30, 2014

Week 8: Muddiest points

If there are different versions of HTML, are CSS standards also being consistently updated?
What also are some rendering issues when trying to read emails written, either partially or completely, in HTML?

Friday, October 24, 2014

Week 8: HTML and web authoring software

1. W3schools HTML tutorial and 2. Webmonkey HTML Cheatsheet

  • HyperText Markup Language
    • where markup lang = markup tags
    • diff versions 1991 (HTML) - present (HTML5)
  • HTML docs described by HTML tags (keywords)
    • <start/opening tag> </end/closing tag>
    • where ea. tag = diff content
  • <!DOCTYPE> = declaration of document type in HTML5
    • all HTML docs must start w/ such a declaration
    • helps display web page correctly
  • <start/opening tag> element content </end/closing tag>
    • <html> web document </html>
    • <body> visible content/doc body </body>
      • nested elements
        • <h1> heading </h1>
          • can go up to <h6>
          • <h1>: main ---> <h6>: least important
        • <p> paragraph </p>
        • <a href="URL"> link </a>
    • <img src="URL"> : imgs, where attributes
      • src = source file
      • alt = alternative text
      • width and height = size
  •  attributes in elements
    • addt'l info
    • always specified in start tag
      • e.g. <img src="URL">
  • lang attribute
    • <html lang="en-US">
  • title attribute
    • <p title="About this blog"></p>
  • href attribute
    • <a href="URL">link</a> 
  •  style attribute
    • style="property: value", where
      • property and value = CSS
    •  <body style="background-color:blue">
    • <p style="font-size:20px">
class elements: define CSS styles
  • <div> = block level element
    • container for other elements, where
      • <style> .cities {color: green; margin:25px;} </style>
      • in body: <div class="cities">content</div>
    • can be used for multiple column layout
  •  <span> = inline element
    • container for text, where
      • <style> span.blue {color: blue;} </style>
      • in body: <span class="blue">Blergh</span>

3. Pratter, F. E. (2011). Chapter 2, Introduction to HTML. In Web Development with SAS by Example, 3rd ed., pp. 15-30.
  • W3C = standards for HTML; XHTML pref (CSS)
  • diff b/w HTML and XHTML
    • HTML = SGML-based; XHTML = XML-based
    • margin for error in HTML too broad
    • XHTML more rigorous, precise
    • XHTML also easier to maintain
  • all docs encoded in XHTML must
    • be coded in lowercase
    • have proper tags
    • nest correctly
    • enclose attributes in quotes

4. 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.

  • report on CMS for 30 web-based research guides at Georgia State U.
  • CMS design: MySQL & ASP
  • lack of standard for lib guides, so ea. liaison w/ diff idea (no., content)
  • tech and admin issues
    • min. sec. w/ FrontPage implemented system
      • published content quickly
      • but sub-web accidentally deleted
  • solution: w/ 1st web dev librarian 
    • +++ security
    • MySQL to manage dbs, journals, special collections
    • survey content guides

CMS in the library
  • reduce "gatekeeper" approach
  • allow more library staff w/ diverse levels of tech skills to contribute
    • use ASP-generated style sheets
    • common style, navigational consistency
  • accommodate increasing volume and complexity of content
    • flexibility in db-driven apps
  • diff CMS environments
    • commercial v. open source v. in-house
  • keep in mind end user (GSU community)

Thursday, October 16, 2014

Week 7: Internet and WWW Technologies

1. Jeff Tyson, "How Internet Infrastructure Works"
http://computer.howstuffworks.com/internet/basics/internet-infrastructure.htm

Internet: interconnected network of computers
  • no "real" owner --> governance? neutrality?
  • Internet Society est. 1992
computer network hierarchy
  • computer : modem : ISP : network
  • work : LAN : ISP : network
  • POP = point of presence
    • access via local # or dedicated line
  • diff networks connect through NAPs (network access pts)
    • various connections, various geographic locations

router
  •  joining 2 networks: directs info to correct destination
    • examines packets and verifies whether intended for address
    • config table: priorities & rules for traffic --> best route
    • protocol translation?
  • protects networks from each other (see: above pt)
    • avoids clogging, misrouting
  •  +++ network activity, +++ influences on performance

backbone
  • NSFNET (1987) T1
    • T1 fiber optic, good for gen browsing
  •  NSF x IBM x MCI x Merit (1988) T3

IP addresses
  • protocol: specific comm w/ particular service
  • IP address = unique ID
    • 0.0.0.0 (default) = octets (8 pos. in binary form)
    • 1 or 0: 2∧8 (256); 0-255
  • octets for classes of IP addresses
    • 2 sections: net and host
    • net: 1st octet --> network of computer
    • host (node): IDs computer; always incl. last octet
  • 2 standards
    • IPv4: all computers, early Internet
    • IPv6: compensates for IPv4 issues
  • dynamic and static
    • dynamic most common (Dynamic Host Configuration Protocol)
    • static: self-config

DNS
  • early Internet: provide IP address of destination comp
  • solution: Network Info Cener text file
    • map name --> IP address
  • DNS: 1983, Wisconsin
    • automatic mapping (name resolution); "GPS for Internet"
    • connect to DNS server 
    • ex. www.pitt.edu instead of actual IP address
  • conversion to IP
    • recognition
    • contact another server to find address
    • refer to another server
    • error b/c IP address invalid or nonexistent

URL
  • 1st-level domain: .com, .edu, .gov, etc.
  • left-most word: host name
    • domain can have lots of host names, as long as unique

Servers and clients
  • Server: Machines w/ services to other machines
    • ex. web, email, ftp
  • Client: Machines used to connect to services
  • Specific purpose, specific service

Ports and HTTP
  • Services avail. using numbered ports
    • 1 for ea. avail. service
    • Access using specific protocol
  •  HTTP (hypertext transfer protocol)


2. Andrew Pace, "Dismantling Integrated Library Systems." Library Journal 129(2): 34-36. http://lj.libraryjournal.com/2004/02/ljarchives/dismantling-integrated-library-systems/
  • interoperability still more myth than reality
    • where interoperability is only w/in each system (and not across)
  • competitive advantage:  how to maintain?
    • vendors must market products
    • but not necessarily "better" --> efficient economically? in use?
  • legacy systems, new layers
  • starting from 0 may be unproductive
  • users want 1-stop search/retrieval
    • implications for critical media literacy?
  • potential of OSS?
    • Koha only basic functionality
  • verdict: vendors also need to reassess own efforts


3. Sergey Brin and Larry Page, "The genesis of Google." http://www.ted.com/talks/sergey_brin_and_larry_page_on_google
  • Google --> ++ equitable access
    • but digital inequality remains pressing issue
    • dearth in certain locations, esp. African countries
  • Montessori education of founders
    • play and creativity
    • 20% time = "free" time for Googlers to work on own projs
    • can potentially be translated to official G proj, ex. News
  • transformation into global co.
    • how to work with intl colleagues?
    • how to work across diff geo locations?
  • ultimate search engine = AI
    • related searches
    • algorithms for relevance
  • AdSense: tailored ads
    • payment for ads, not results

Friday, October 3, 2014

Week 6: Muddiest points

The following queries may be beyond the scope of the class, but they are what confused me the most:

  1. How does a switch function as a "multi-port bridge"?
  2. How is backbone network different from a campus, or wide area network?
  3. What are the technical and financial implications of adopting E2EE on a wider scale?
  4. What constitutes the physical layer of a protocol stack?

Week 6: Computer networks and wireless networks

1. LAN
  • ltd coverage: smaller geographic area (ex: home, school)
  • most common: Ethernet and wifi
  • can incl. many devices: switches, firewalls, routers, etc.
  • simple LANs: 1+ switches
    • switch: connects devices in network
  • complex LANs
    • spanning tree protocol (??) to prevent loops


History
  • evolution from late 1960s
    • ex: Cambridge Ring: 1974; ethernet: 1973-5; ARCNET: 1976-7
  • PCs (1970s) + DOS-based (80s) --> ++ computers
    • share storage, printers
  • issues: match physical layer and network protocol implementations
    • ea. vendor own structures
  • appearance of Novell, Windows NT/Workgroups, Unix-based workstations

Types of cabling
  • early cabling based on coaxial cabling
    • (((tubular conducting shield (( insulating layer ( inner conductor ) )) )))
  • then shielded, unshielded twisted pair (Star LAN Cat3)
    •  2 conductors of single circuit together to cancel external interference
    •  unshielded = same for tel. systems
  • 10Base-T, aka ethernet over twisted pair, etc.
    • can mix diff. gens. of equipment: higher-speed implementations w/ lower-speed standards
  • current: structured cabling
    • smaller elements forming structures in building/campus
    • ex.: wifi, fiber optic

Network topology
  • arr. of links, nodes, etc. in network
    • physical: placement of components (ex. devices, cables)
    • logical: data flows
  • most common: switched ethernet, IP (TCP/IP)
  • bus
    • node :: cable
    • "singularity"/uniqueness, match :: match = can easily track failure to source
    • linear bus: 2 endpoints
    • distributed bus: 2+ endpoints
  • mesh
    • fully connected network: nodes connected to each other; not useful for large networks
    • partially connected: nodes connected to 1+, but not all to each other; take advantage of redundancy but avoid complexity of fully connected
  • ring
    • circular, uni-directional
    • ea. device = repeater; nodes work as server
    • network dependent on ability to travel around
    • one node breaks, entire network stops functioning
  • star
    • each network host :: central hub/switch via pt<>pt connection
    • central hub = signal repeater; all traffic passes through
    • easy to add addtl nodes
    • hub = point of failure


2. Computer/data network
  • Telecom network : computer << data >> computer
  • network links est. via cable or wireless --> Internet
  • network nodes
    • create, route, terminate data, "hosts"
    • ex. :  PC, phones, servers

History
  • experiments and tests late 1950s-70s
    • 1960s: ARPANET
    • 1973: Ethernet
    • 1976: ARCNET
  • 1995: +++ speed capacity for Ethernet

Distributed computing
  • network-wide resources for tasks (ex. P2P apps, progs)
    • processor << messages >> processor
  • each entity: autonomous, own memory
    • "independent", localized failure

Network packet
  • most info carried in packets (appropriately-sized blocks)
    • 2 kinds of data in packet data
      • control info: ex. network addresses
      • user data (payload)
  • network packet: formatted unit of data (bits/bytes) carried by packet-switched network
  • framing
    • network address
    • error detection and correction
    • hop counts
      • hop: pt of path between source and destination
      • hop count: intermediate device, ex. router; detect fault in network
      • closed circuit > no action > congestion > failure > discard
    • packet length
    • class/priority
    • payload

IP packet
  • header and payload
  • but often as payload w/in Ethernet frame  

Consultative Committee for Space Data Systems (NASA)
  • packet length can vary
    • transmitted b/w frames
    • size fixed during dev.
  • error-correcting codes
  • principal type of data loss: deleted, undecodable whole frames (??)

Packetized elementary stream (MPEG)
  • elem. stream / packets > MPEG transport or program stream (TS, PS) > distributed ("multiplexed" ??) 

Networked links
  • electrical cable
  • optical fiber: pulses of light ~~ data
  • radio waves (wireless)
  • price significant consideration


Networked nodes
  • interface controller
    • hardware accessing transmission media
    • low-level info
    • ex. Ethernet MAC address
  • repeater and hub
    • repeater: receives info > clean > regenerate
    • hub: repeater
  •  bridge: join segments to form 1 network
    • local: direct connection
    • remote: can be used for WAN
    • wireless: join LANs, or remote devices to
  •  switch
    • fwds and filters b/w MAC-based physical ports
    • "multi-port bridge"
  • router
    • processes routing info incl. in packets
    • fwds packets b/w networks
  • modem
    • via wire: connect info not orig. for dig net traffic
    • 1+ freq. modulated by dig signal >> analog
    • analog sig >> can be modified for transmission (ex. telephony)
  • firewall 
    • network sec. and access

Communications protocols
  • protocol suite
    • definition of protocols
  • protocol stack 
    • software implementation
    • HTTP : application
    • TCP : transport
    • IP : internet/network
      • foundation of modern networking
    • Ethernet : data link
    • ? : physical

Scale
  • personal, local, storage, campus, metropolitan, wide area, global area
  • backbone (?)
  • enterprise private network
    • single orgs, maybe diff. locs
  • VPN
    • open connections, virtual circuits

Org. scope
  • intranet
  • extranet
    • single admin control
    • external connection to ex., business partners, etc.
  • internetwork -- Internet
  • darknet
    • accessible via spec. software
    • sharing is anonymous

Network service and performance
  • services hosted on servers
    • ex. www, email
  • performance
    • = grade of service
    • congestion: deterioration
  • resilience
    • acceptable service level despite faults

Security and surveillance
  • prevent and monitor unauthorized access, misuse
  • controlled by network admin
  • surveillance: data monitoring
    • social control?
    • Electronic Frontier Foundation, ACLU
  • end-to-end encryption (E2EE)
    • sender encrypts data for receiver decrypting
    • confidentiality and integrity

3. Coyle, K. (2005). Management of RFID in Libraries. Journal of Academic Librarianship, 31(5), 486-489. doi: 10.1016/j.acalib.2005.06.001.

  • RF: radio frequency
  • ID: identifier
  • similar to barcodes, but read by electromagnetic field
  • RFID tag doesn't have to be visible to be read
  • variety
 Implementation in libs: one tag, many fxns
  • privacy issues
  • useful for tracking inventory/circ fxns
    • ID tag re-used multiple times --> justification of expense?
  • payment systems?
  • security mechanism not worse than other techs

ROI
  • efficiency via automation (checking in/out items)
  • pitfalls of self-checkout: lack of human interaxn
  • check user satisfaction

Further issues
  • RFID tags for "non-trad" items, shapes (ex. optical discs)
    • if no RFID, alternative check-out system
  • reprogramming tags