HTML (Korean Wikipedia)

Analysis of information sources in references of the Wikipedia article "HTML" in Korean language version.

refsWebsite
Global rank Korean rank
691st place
188th place
1st place
1st place
214th place
109th place
4,871st place
2,203rd place
1,668th place
966th place
low place
low place
629th place
266th place
5,099th place
1,888th place
low place
low place
low place
1,697th place
low place
low place
low place
low place

arquivo.pt

  • “HTML+ Internet-Draft - Abstract”. 2016년 5월 15일에 원본 문서에서 보존된 문서. 2007년 6월 17일에 확인함. Browser writers are experimenting with extensions to HTML and it is now appropriate to draw these ideas together into a revised document format. The new format is designed to allow a gradual roll over from HTML, adding features like tables, captioned figures and fill-out forms for querying remote databases or mailing questionnaires. 

faqs.org

  • Raymond, Eric. 〈IETF and the RFC Standards Process〉. 《The Art of Unix Programming》. 2005년 3월 17일에 원본 문서에서 보존된 문서. 2010년 3월 12일에 확인함. In IETF tradition, standards have to arise from experience with a working prototype implementation — but once they become standards, code that does not conform to them is considered broken and mercilessly scrapped. …Internet-Drafts are not specifications, and software implementers and vendors are specifically barred from claiming compliance with them as if they were specifications. Internet-Drafts are focal points for discussion, usually in a working group… Once an Internet-Draft has been published with an RFC number, it is a specification to which implementers may claim conformance. It is expected that the authors of the RFC and the community at large will begin correcting the specification with field experience. 

hsivonen.iki.fi

htmlhelp.com

ietf.org

ietf.org

  • “RFC 1866: Hypertext Markup Language - 2.0 - Acknowledgments”. Internet Engineering Task Force. 2005년 9월 22일. 2005년 3월 5일에 원본 문서에서 보존된 문서. 2007년 6월 16일에 확인함. Since 1993, a wide variety of Internet participants have contributed to the evolution of HTML, which has included the addition of in-line images introduced by the NCSA Mosaic software for WWW. Dave Raggett played an important role in deriving the forms material from the HTML+ specification. Dan Connolly and Karen Olson Muldrow rewrote the HTML Specification in 1994. The document was then edited by the HTML working group as a whole, with updates being made by Eric Schieler, Mike Knezovich, and Eric W. Sink at Spyglass, Inc. Finally, Roy Fielding restructured the entire draft into its current form. 
  • “RFC 1866: Hypertext Markup Language - 2.0 - Introduction”. Internet Engineering Task Force. 2005년 9월 22일. 2005년 3월 5일에 원본 문서에서 보존된 문서. 2007년 6월 16일에 확인함. This document thus defines an HTML 2.0 (to distinguish it from the previous informal specifications). Future (generally upwardly compatible) versions of HTML with new features will be released with higher version numbers. 
  • “RFC 2119: Key words for use in RFCs to Indicate Requirement Levels”. Harvard University. 1997. 2008년 12월 6일에 원본 문서에서 보존된 문서. 2008년 12월 7일에 확인함. 3. SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. 

datatracker.ietf.org

  • “HTML+ Internet-Draft - Abstract”. 2016년 5월 15일에 원본 문서에서 보존된 문서. 2007년 6월 17일에 확인함. Browser writers are experimenting with extensions to HTML and it is now appropriate to draw these ideas together into a revised document format. The new format is designed to allow a gradual roll over from HTML, adding features like tables, captioned figures and fill-out forms for querying remote databases or mailing questionnaires. 

tools.ietf.org

invisiblerevolution.net

iso.org

tcd.ie

cs.tcd.ie

tut.fi

cs.tut.fi

w3.org

w3.org

lists.w3.org

web.archive.org

  • “First mention of HTML Tags on the www-talk mailing list”. 월드와이드웹 컨소시엄. 1991년 10월 29일. 2013년 5월 17일에 원본 문서에서 보존된 문서. 2010년 3월 3일에 확인함. 
  • 팀 버너스리 (1991년 12월 9일). “Re: SGML/HTML docs, X Browser (archived www-talk mailing list post)”. 2013년 5월 20일에 원본 문서에서 보존된 문서. 2010년 3월 7일에 확인함. SGML은 매우 일반적입니다. HTML은 간단한 구조를 가진 하이퍼텍스트 문서에 적용된 SGML 기본 구문의 응용입니다. 
  • Raymond, Eric. 〈IETF and the RFC Standards Process〉. 《The Art of Unix Programming》. 2005년 3월 17일에 원본 문서에서 보존된 문서. 2010년 3월 12일에 확인함. In IETF tradition, standards have to arise from experience with a working prototype implementation — but once they become standards, code that does not conform to them is considered broken and mercilessly scrapped. …Internet-Drafts are not specifications, and software implementers and vendors are specifically barred from claiming compliance with them as if they were specifications. Internet-Drafts are focal points for discussion, usually in a working group… Once an Internet-Draft has been published with an RFC number, it is a specification to which implementers may claim conformance. It is expected that the authors of the RFC and the community at large will begin correcting the specification with field experience. 
  • “RFC 1866: Hypertext Markup Language - 2.0 - Acknowledgments”. Internet Engineering Task Force. 2005년 9월 22일. 2005년 3월 5일에 원본 문서에서 보존된 문서. 2007년 6월 16일에 확인함. Since 1993, a wide variety of Internet participants have contributed to the evolution of HTML, which has included the addition of in-line images introduced by the NCSA Mosaic software for WWW. Dave Raggett played an important role in deriving the forms material from the HTML+ specification. Dan Connolly and Karen Olson Muldrow rewrote the HTML Specification in 1994. The document was then edited by the HTML working group as a whole, with updates being made by Eric Schieler, Mike Knezovich, and Eric W. Sink at Spyglass, Inc. Finally, Roy Fielding restructured the entire draft into its current form. 
  • “RFC 1866: Hypertext Markup Language - 2.0 - Introduction”. Internet Engineering Task Force. 2005년 9월 22일. 2005년 3월 5일에 원본 문서에서 보존된 문서. 2007년 6월 16일에 확인함. This document thus defines an HTML 2.0 (to distinguish it from the previous informal specifications). Future (generally upwardly compatible) versions of HTML with new features will be released with higher version numbers. 
  • Korpela, Jukka (1998년 7월 6일). “Why attribute values should always be quoted in HTML”. Cs.tut.fi. 2008년 11월 21일에 원본 문서에서 보존된 문서. 2010년 3월 7일에 확인함. 
  • “RFC 2119: Key words for use in RFCs to Indicate Requirement Levels”. Harvard University. 1997. 2008년 12월 6일에 원본 문서에서 보존된 문서. 2008년 12월 7일에 확인함. 3. SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. 
  • “XHTML Reference: blockquote”. 2010년 3월 25일에 원본 문서에서 보존된 문서. 2010년 3월 12일에 확인함. 

xhtml.com