…ned in [URI] (see also [RFC1630] ). Note that URIs include URLs (as defined in [RFC1738] and [RFC1808] ). Relative URIs are resolved to full URIs using a base URI. [RFC1808] , section 3, defines the normative algorithm for this process. For more information about base URIs, pleas…
… (URNs or URLs), encoded according to the URL or URN specifications ( RFC2141 , RFC1738 and RFC2396 ). Each URI shall appear on one and only one line. Very long URIs are not broken in the text/uri-list format. Content-transfer-encodings may be used to enforce line length limitati…
…", T. Berners-Lee, R. Fielding, L. Masinter, August 1998. This document updates RFC1738 and RFC1808. Available at: http://www.ietf.org/rfc/rfc2396.txt [RFC2854] " RFC2854: The text/html Media Type ", D. Conolly, L. Masinter, June 2000. Available at: http://www.ietf.org/rfc/rfc285…
… , T. Berners-Lee, R. Fielding, L. Masinter, August 1998. This document updates RFC1738 and RFC1808. Available at: http://www.ietf.org/rfc/rfc2396.txt [XML] "Extensible Markup Language (XML) 1.0 Specification" , T. Bray, J. Paoli, C. M. Sperberg-McQueen, 10 February 1998. Latest …
…", T. Berners-Lee, R. Fielding, L. Masinter, August 1998. This document updates RFC1738 and RFC1808. Available at: http://www.ietf.org/rfc/rfc2396.txt [RFC2854] " RFC2854: The text/html Media Type ", D. Conolly, L. Masinter, June 2000. Available at: http://www.ietf.org/rfc/rfc285…
…ers (URI): Generic Syntax and Semantics ." RFC2396, IETF, August 1998. [Updates RFC1738 ] Available at http://www.ietf.org/rfc/rfc2396.txt . [ UTF-8 ] F. Yergeau. " UTF-8, a transformation format of ISO 10646 ." RFC2279, IETF, January 1998. Available at http://www.ietf.org/rfc/rf…
…ded using the "%nn" format, where nn is the hexadecimal value of the byte. (See RFC1738 for details.) For a 20-byte hash of \x12\x34\x56\x78\x9a\xbc\xde\xf1\x23\x45\x67\x89\xab\xcd\xef\x12\x34\x56\x78\x9a, The right encoded form is %124Vx%9A%BC%DE%F1%23Eg%89%AB%CD%EF%124Vx%9A Tra…
…ned in [URI] (see also [RFC1630] ). Note that URIs include URLs (as defined in [RFC1738] and [RFC1808] ). Relative URIs are resolved to full URIs using a base URI. [RFC1808] , section 3, defines the normative algorithm for this process. For more information about base URIs, pleas…
… , T. Berners-Lee, R. Fielding, L. Masinter, August 1998. This document updates RFC1738 and RFC1808. Available at: http://www.ietf.org/rfc/rfc2396.txt [XML] "Extensible Markup Language (XML) 1.0 Specification" , T. Bray, J. Paoli, C. M. Sperberg-McQueen, 10 February 1998. Availab…
… attribute whose value is a Uniform Resource Locator, See RFC1808 (June 95) and RFC1738 (Dec 94). --> <!-- Parameter Entities --> <!ENTITY % head.misc "SCRIPT|STYLE|META|LINK" -- repeatable head elements --> <!ENTITY % heading "H1|H2|H3|H4|H5|H6"> <!ENTITY % list "UL | OL | DIR |…
…", T. Berners-Lee, R. Fielding, L. Masinter, August 1998. This document updates RFC1738 and RFC1808. Available at: http://www.ietf.org/rfc/rfc2396.txt [RFC2854] RFC2854: The text/html Media Type ", D. Conolly, L. Masinter, June 2000. Available at: http://www.ietf.org/rfc/rfc2854.…
…RI): Generic Syntax" , T. Berners-Lee, R. Fielding, L. Masinter, 1998年8月. この文書は RFC1738 と RFC1808 とを更新するものである。 で入手可能。 [XML] "Extensible Markup Language (XML) 1.0 Specification" , T. Bray, J. Paoli, C. M. Sperberg-McQueen, 1998年2月10日. 最新バージョンは で入手可能。 [XMLNAMES] "Namespaces in XML"…
…", T. Berners-Lee, R. Fielding, L. Masinter, August 1998. This document updates RFC1738 and RFC1808. Available at: http://www.ietf.org/rfc/rfc2396.txt [RFC2854] RFC2854: The text/html Media Type ", D. Conolly, L. Masinter, June 2000. Available at: http://www.ietf.org/rfc/rfc2854.…
…are replaced by `+' , and then reserved characters are escaped as described in [RFC1738] , section 2.2: Non-alphanumeric characters are replaced by `%HH' , a percent sign and two hexadecimal digits representing the ASCII code of the character. Line breaks are represented as "CR L…
…ned in [URI] (see also [RFC1630] ). Note that URIs include URLs (as defined in [RFC1738] and [RFC1808] ). Relative URIs are resolved to full URIs using a base URI. [RFC1808] , section 3, defines the normative algorithm for this process. For more information about base URIs, pleas…