Web Standards and Specifications - Revision history

KateHartmann at 15:53, 3 August 2016

2016-08-03T15:53:19Z

MediaWiki spam cleanup: Reverting to last version not containing links to s1.shard.jp

2009-06-03T12:50:07Z

Reverting to last version not containing links to s1.shard.jp

Deleted user at 02:16, 31 May 2009

2009-05-31T02:16:59Z

MediaWiki spam cleanup: Reverting to last version not containing links to s1.shard.jp

2009-05-29T18:00:39Z

Reverting to last version not containing links to s1.shard.jp

Deleted user at 16:34, 29 May 2009

2009-05-29T16:34:18Z

MediaWiki spam cleanup: Reverting to last version not containing links to www.textoubocli.com

2009-05-27T18:29:49Z

Reverting to last version not containing links to www.textoubocli.com

MediaWiki spam cleanup: Reverting to last version not containing links to s1.shard.jp

2009-05-27T16:00:09Z

Reverting to last version not containing links to s1.shard.jp

Deleted user at 12:07, 26 May 2009

2009-05-26T12:07:39Z

Deleted user at 17:49, 22 May 2009

2009-05-22T17:49:25Z

Bikram: sequence of sub-topics

2007-02-05T14:38:21Z

sequence of sub-topics

@@ Line 112: / Line 112: @@
 '''other security related links'''
-http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/security.htm
+http://www.cisco.com/c/en/us/td/docs/internetworking/technology/handbook/ito_doc.html
 == '''References''' ==

@@ Line 1: / Line 1: @@
 == '''Web standards and specifications''' ==
@@ Line 64: / Line 24: @@
 Current list of standards will easily equal many hundreds, and is increasing at a scorching pace; and we can only hope, in time, application library developers can wrap all these behind very easy to use objects and interfaces. Standards generally remain incomprehensible to a general developer. No doubt, for power applications, developers will still need to pour over specifications and design/develop their application code to implement the best possible solution; but majority of the developers will need to rely on the ingenuity of the library developers to make the standards based applications accessible and usable. In either case, knowledge of the underlying specifications will help in overall understanding of the application architecture and improving implementations. This article aims to serve as first step in that direction.
-'''Internet Engineering Task Force (http://www.ietf.org/home.html)''' - One of the primary bodies involved in the development of core internet standards, e.g. networking, routing, mail etc. Their scope is pretty wide, everything âabove the wire and below the applicationâ, as described by "Scott Bradner" in "http://edu.ietf.org/node/view/55" article. Some of the important contributions include: IP, TCP, HTTP, FTP, VPN, LDAP, Telnet, POP3, and many more. Further, in his presentation, Scott describes the scope of other "Standards Development Organisations" (SDOs), as primarily involved in extending and fixing IETF standards, which is correct, as we shall see later in the article.
+'''Internet Engineering Task Force (http://www.ietf.org/home.html)''' - One of the primary bodies involved in the development of core internet standards, e.g. networking, routing, mail etc. Their scope is pretty wide, everything “above the wire and below the application”, as described by "Scott Bradner" in "http://edu.ietf.org/node/view/55" article. Some of the important contributions include: IP, TCP, HTTP, FTP, VPN, LDAP, Telnet, POP3, and many more. Further, in his presentation, Scott describes the scope of other "Standards Development Organisations" (SDOs), as primarily involved in extending and fixing IETF standards, which is correct, as we shall see later in the article.
 A sister organisation is www.irtf.org, which is fixed on defining the future of internet standards.

@@ Line 1: / Line 1: @@
 == '''Web standards and specifications''' ==
@@ Line 24: / Line 64: @@
 Current list of standards will easily equal many hundreds, and is increasing at a scorching pace; and we can only hope, in time, application library developers can wrap all these behind very easy to use objects and interfaces. Standards generally remain incomprehensible to a general developer. No doubt, for power applications, developers will still need to pour over specifications and design/develop their application code to implement the best possible solution; but majority of the developers will need to rely on the ingenuity of the library developers to make the standards based applications accessible and usable. In either case, knowledge of the underlying specifications will help in overall understanding of the application architecture and improving implementations. This article aims to serve as first step in that direction.
-'''Internet Engineering Task Force (http://www.ietf.org/home.html)''' - One of the primary bodies involved in the development of core internet standards, e.g. networking, routing, mail etc. Their scope is pretty wide, everything “above the wire and below the application”, as described by "Scott Bradner" in "http://edu.ietf.org/node/view/55" article. Some of the important contributions include: IP, TCP, HTTP, FTP, VPN, LDAP, Telnet, POP3, and many more. Further, in his presentation, Scott describes the scope of other "Standards Development Organisations" (SDOs), as primarily involved in extending and fixing IETF standards, which is correct, as we shall see later in the article.
+'''Internet Engineering Task Force (http://www.ietf.org/home.html)''' - One of the primary bodies involved in the development of core internet standards, e.g. networking, routing, mail etc. Their scope is pretty wide, everything âabove the wire and below the applicationâ, as described by "Scott Bradner" in "http://edu.ietf.org/node/view/55" article. Some of the important contributions include: IP, TCP, HTTP, FTP, VPN, LDAP, Telnet, POP3, and many more. Further, in his presentation, Scott describes the scope of other "Standards Development Organisations" (SDOs), as primarily involved in extending and fixing IETF standards, which is correct, as we shall see later in the article.
 A sister organisation is www.irtf.org, which is fixed on defining the future of internet standards.

@@ Line 1: / Line 1: @@
 == '''Web standards and specifications''' ==
@@ Line 64: / Line 24: @@
 Current list of standards will easily equal many hundreds, and is increasing at a scorching pace; and we can only hope, in time, application library developers can wrap all these behind very easy to use objects and interfaces. Standards generally remain incomprehensible to a general developer. No doubt, for power applications, developers will still need to pour over specifications and design/develop their application code to implement the best possible solution; but majority of the developers will need to rely on the ingenuity of the library developers to make the standards based applications accessible and usable. In either case, knowledge of the underlying specifications will help in overall understanding of the application architecture and improving implementations. This article aims to serve as first step in that direction.
-'''Internet Engineering Task Force (http://www.ietf.org/home.html)''' - One of the primary bodies involved in the development of core internet standards, e.g. networking, routing, mail etc. Their scope is pretty wide, everything âabove the wire and below the applicationâ, as described by "Scott Bradner" in "http://edu.ietf.org/node/view/55" article. Some of the important contributions include: IP, TCP, HTTP, FTP, VPN, LDAP, Telnet, POP3, and many more. Further, in his presentation, Scott describes the scope of other "Standards Development Organisations" (SDOs), as primarily involved in extending and fixing IETF standards, which is correct, as we shall see later in the article.
+'''Internet Engineering Task Force (http://www.ietf.org/home.html)''' - One of the primary bodies involved in the development of core internet standards, e.g. networking, routing, mail etc. Their scope is pretty wide, everything “above the wire and below the application”, as described by "Scott Bradner" in "http://edu.ietf.org/node/view/55" article. Some of the important contributions include: IP, TCP, HTTP, FTP, VPN, LDAP, Telnet, POP3, and many more. Further, in his presentation, Scott describes the scope of other "Standards Development Organisations" (SDOs), as primarily involved in extending and fixing IETF standards, which is correct, as we shall see later in the article.
 A sister organisation is www.irtf.org, which is fixed on defining the future of internet standards.

@@ Line 1: / Line 1: @@
 == '''Web standards and specifications''' ==
@@ Line 24: / Line 64: @@
 Current list of standards will easily equal many hundreds, and is increasing at a scorching pace; and we can only hope, in time, application library developers can wrap all these behind very easy to use objects and interfaces. Standards generally remain incomprehensible to a general developer. No doubt, for power applications, developers will still need to pour over specifications and design/develop their application code to implement the best possible solution; but majority of the developers will need to rely on the ingenuity of the library developers to make the standards based applications accessible and usable. In either case, knowledge of the underlying specifications will help in overall understanding of the application architecture and improving implementations. This article aims to serve as first step in that direction.
-'''Internet Engineering Task Force (http://www.ietf.org/home.html)''' - One of the primary bodies involved in the development of core internet standards, e.g. networking, routing, mail etc. Their scope is pretty wide, everything “above the wire and below the application”, as described by "Scott Bradner" in "http://edu.ietf.org/node/view/55" article. Some of the important contributions include: IP, TCP, HTTP, FTP, VPN, LDAP, Telnet, POP3, and many more. Further, in his presentation, Scott describes the scope of other "Standards Development Organisations" (SDOs), as primarily involved in extending and fixing IETF standards, which is correct, as we shall see later in the article.
+'''Internet Engineering Task Force (http://www.ietf.org/home.html)''' - One of the primary bodies involved in the development of core internet standards, e.g. networking, routing, mail etc. Their scope is pretty wide, everything âabove the wire and below the applicationâ, as described by "Scott Bradner" in "http://edu.ietf.org/node/view/55" article. Some of the important contributions include: IP, TCP, HTTP, FTP, VPN, LDAP, Telnet, POP3, and many more. Further, in his presentation, Scott describes the scope of other "Standards Development Organisations" (SDOs), as primarily involved in extending and fixing IETF standards, which is correct, as we shall see later in the article.
 A sister organisation is www.irtf.org, which is fixed on defining the future of internet standards.

@@ Line 53: / Line 53: @@
 http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/index.htm
-== '''HTML family of Standards''' ==
 == '''Web Service Standards''' ==
 == '''Standards for non-textual data transfer''' ==