Sunday, January 20, 2013

Week One Readings


15th January 2013 Week One:

When I read "The Read-Write Web - Technology that Makes We the Media Possible" from chapter two from a book called We the Media - 2. The Read-Write Web (by Dan Gillmor)  talks about a vision of making the read/write web pages. From the early and the mid  nineties, websites were mainly a read only.  The vision was to make more feasible for a web developer like the guy in this story pointed out a visionary of making a weblog base website.  There are four common ways to get and retrieve information from the weblog:
  • Wiki:
    • is a site that users can alter information based on commenting, or disagreeing.
  • Rich Site Summary or RSS:
    • get the contents of a subscriber's blogs.
  • Peer-to-Peer or P2P:
    • is a server or client based node that share files among one  computer to another. 
  • Short message services
    • is a way that users can send a message to other people with out using a PC. 
When I read "The Business Value of Web Standards" <http://www.adaptivepath.com/ideas/e000266 I learned that making a website with multiple HTML files with one CSS file.  By following this procedure can reduce the bandwidth usage, the time of updating the site, and reduce the cost of hosting the site

When I read "Fix Your Site With the Right DOCTYPE!" by Jeffrey Zeldman, <http://www.alistapart.com/articles/doctype/ there are some sets of rules that need to be followed.  It's very important to abide the required doc-type rules.  If not the website will run in Quirks mode*.

* according to the "Fix Your Site With the Right DOCTYPE!" article, the quirks mode is the browsers assumes to run in old-fashioned, invalid markup and code per the depressing industry norms of the late 1990



 Part two: (the right post)

Version:1.0 StartHTML:0000000167 EndHTML:0000002791 StartFragment:0000000663 EndFragment:0000002775 -->

From reading the “5 Reasons Why You Can Use HTML5 Today” article by Craig Buckler, talked about five good reasons of using HTML5 and CSS3 instead of using an old HTML and CSS format.the first reason was most newer browsers can support HTML5 except the old Internet Explorer browsers. A few tweaks will do the trick for the information part; however, the look of the site will be bad. The second reason was HTML5 is a predecessor of HTML4/XHTML 1.0, so html5 has 26 additional tags. The third reason the specification of HTML5 will never be completed means that W3C currently does not have any restrictions set for the browser vendors to follow. The fourth reason like stated in reason number one most new common browsers (include Internet Explorer 9 and 10) supports the HTML5. Most people are adapting the HTML5 based web page for varies of reasons. The fifth reason for average users, HTML5 based websites is new thing for them. Apple iPads and iPods can run them and play html5-based videos without any problems.




From reading the “HTML vs. XHTML* on standards compliant websites” article by Sean Fraser and “HTML or XHTML?” article by Robert Nyman. Both articles talked about the discoveries about HTML vs. XHTML. Here is few things that both articles mention that using the strict HTML4 strict. XHTML 1.0 and 2.0 are not backward compilable. If XHTML 4.0 strict are used as application/xhtml+xml the Internet Explorer will not work. HTML5 is a backward compilable.



* According to “HTML or XHTML?” A XHTML document is a document that has to be well-formed according to the rules of XML.