
	Where results make sense

Topic: RFC 3023

Related Topics

Biological hazard

Vowel stems

List of WW2 Luftwaffe aircraft by classification

Little Valley (village), New York

Boston Police Department

MicroStrategy

James Key Caird

List of thriller authors

Cabin John, Maryland

In the News (Wed 11 Nov 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	RFC3023 (Site not responding. Last check: 2007-09-10)
		RFC 3023 XML Media Types January 2001 Although XML is a subset of the Standard Generalized Markup Language (SGML) ISO 8879[SGML], which has been assigned the media types text/sgml and application/sgml, there are several reasons why use of text/sgml or application/sgml to label XML is inappropriate.
		RFC 3023 XML Media Types January 2001 Encoding considerations: This media type MAY be encoded as appropriate for the charset and the capabilities of the underlying MIME transport.
		RFC 3023 XML Media Types January 2001 If the receiver comes to rely on the superclass tag being present and applications are deployed relying on that tag (as always seems to happen), then only upgraded senders will be able to interoperate with those receiving applications.
	rfc.net /rfc3023.html (9833 words)

	RFC 3023 - XML Media Types. M. Murata, S. St. Laurent, D. Kohn. (Site not responding. Last check: 2007-09-10)
		RFC 3023 XML Media Types January 2001 8.1 Text/xml with UTF-8 Charset Content-type: text/xml; charset="utf-8" This is the recommended charset value for use with text/xml.
		RFC 3023 XML Media Types January 2001 8.4 Text/xml with ISO-2022-KR Charset Content-type: text/xml; charset="iso-2022-kr" This example shows text/xml with a Korean charset (e.g., Hangul) encoded following the specification in [RFC1557].
		RFC 3023 XML Media Types January 2001 8.16 Application/mathml+xml Content-type: application/mathml+xml MathML documents are XML documents whose content describes mathematical information, as defined by [MathML].
	rfc.sunsite.dk /rfc/rfc3023.html (9927 words)

	RFC 3900 - 3999
		RFC 792, RFC 826, RFC 2119, RFC 2434.
		RFC 2119, RFC 2251, RFC 3383, RFC 3909.
		RFC 2119, RFC 2778, RFC 3023, RFC 3688, RFC 3862.
	www.networksorcery.com /enp/rfc3900.htm (2550 words)

	RFC 3680 - A Session Initiation Protocol (SIP) Event Package for Registrations
		One is Rosenberg Standards Track [Page 8] RFC 3680 SIP Registrations Event March 2004 through an actual SIP REGISTER request (corresponding to the registered event), and the other is when the contact is created administratively, or through some non-SIP means (the created event).
		The "unknown-param" element is used to convey contact header field parameters that are not specified in RFC 3261.
		Encoding considerations: Same as encoding considerations of application/xml as specified in RFC 3023 [8].
	www.packetizer.com /rfc/rfc.cgi?num=3680 (5533 words)

	[No title]
		Standards Track [Page 3] RFC 3023 XML Media Types January 2001 Although XML is a subset of the Standard Generalized Markup Language (SGML) ISO 8879[SGML], which has been assigned the media types text/sgml and application/sgml, there are several reasons why use of text/sgml or application/sgml to label XML is inappropriate.
		Standards Track [Page 10] RFC 3023 XML Media Types January 2001 Encoding considerations: This media type MAY be encoded as appropriate for the charset and the capabilities of the underlying MIME transport.
		Standards Track [Page 34] RFC 3023 XML Media Types January 2001 If the receiver comes to rely on the superclass tag being present and applications are deployed relying on that tag (as always seems to happen), then only upgraded senders will be able to interoperate with those receiving applications.
	wigwam.sztaki.hu /rfc/?3023 (10093 words)

	[No title]
		Encoding considerations: Same as charset parameter of application/xml, defined in RFC 3023 [4].
		Historical Considerations This media type was reserved in RFC 3023 [4], saying: RDF documents identified using this MIME type are XML documents whose content describes metadata, as defined by [7].
		Acknowledgement Funding for the RFC Editor function is currently provided by the Internet Society.
	www.ietf.org /rfc/rfc3870.txt (1425 words)

	I18n WG comments on EMMA
		RFC 1738 is obsoleted by RFC 3986 (URI Generic Syntax).
		RFC 1766 is obsoleted by 3066 (Tags for the Identification of Languages).
		To be able to take its changes into account, it would be good if you could change the reference to RFC 3023 to "RFC 3023 or its successor." Please have a look at How to Register an Internet Media Type for a W3C Specification.
	www.w3.org /International/2005/10/emma-review.html (381 words)

	RFC 3858 - An Extensible Markup Language (XML) Based Format for Watcher Information
		Rosenberg Standards Track [Page 4] RFC 3858 Watcher Info August 2004 In the case where an administrator wishes to learn the current status in the system, the watcher information could contain all watchers for all resources.
		This check is done by Rosenberg Standards Track [Page 5] RFC 3858 Watcher Info August 2004 comparing the ID in the "id" attribute of the "watcher" element with the ID associated with the row.
		Encoding considerations: Same as encoding considerations of application/xml as specified in RFC 3023 [9].
	www.packetizer.com /rfc/rfc3858 (2448 words)

	RFC 3870 (Site not responding. Last check: 2007-09-10)
		RFC 3870 application/rdf+xml September 2004 Interoperability considerations: It is RECOMMENDED that RDF documents follow the newer RDF/XML Syntax Grammar [1] as opposed to the older RDF Model and Syntax specification [7].
		RFC 3870 application/rdf+xml September 2004 Author/Change controller: The RDF specification is a work product of the World Wide Web Consortium.
		RFC 3023 [4], section 10, discusses security concerns for generic XML, which are also applicable to RDF.
	www.armware.dk /RFC/rfc/rfc3870.html (1405 words)

	Character Encoding Detection [Universal Feed Parser]
		RFC 3023 defines the interaction between XML and HTTP as it relates to character encoding.
		For other media types, the default encoding is undefined, which is where RFC 3023 comes in.
		Universal Feed Parser initially uses the rules specified in RFC 3023 to determine the character encoding of the feed.
	feedparser.org /docs/character-encoding.html (448 words)

	RFC3902 (Site not responding. Last check: 2007-09-10)
		Encoding considerations: Identical to those of "application/xml" as described in RFC 3023 [RFC3023], section 3.2, as applied to the SOAP envelope infoset.
		RFC 3902 The "application/soap+xml" media type September 2004 defined semantics of the data carried in the SOAP message (though one must be careful when doing this, as discussed in SOAP 1.2 Part 1 [W3C.REC-soap12-part1-20030624], section Binding to Application-Specific Protocols).
		Fragment identifiers: Identical to that of "application/xml" as described in RFC 3023 [RFC3023], section 5.
	rfc.net /rfc3902.html (1125 words)

	[No title]
		Standards Track [Page 11] RFC 3023 XML Media Types January 2001 because external parsed entities are prohibited from having standalone document declarations or DTDs.
		Standards Track [Page 20] RFC 3023 XML Media Types January 2001 If sent using a 7-bit transport (e.g., SMTP) or an 8-bit clean transport (e.g., 8BITMIME ESMTP or NNTP), the XML MIME entity MUST be encoded in quoted-printable or base64.
		Standards Track [Page 24] RFC 3023 XML Media Types January 2001 Scalable Vector Graphics (SVG) documents are XML documents whose content describes graphical information, as defined by [SVG].
	www.ietf.org /rfc/rfc3023.txt (10079 words)

	RFCs 3000 - 3099 Index (Site not responding. Last check: 2007-09-10)
		Major differences from RFC 2376 are (1) the addition of text/xml- external-parsed-entity, application/xml-external-parsed-entity, and application/xml-dtd, (2) the '+xml' suffix convention (which also updates the RFC 2048 registration process), and (3) the discussion of"utf-16le" and "utf-16be".
		RFC 1591, "Domain Name System Structure and Delegation", laid out the basic administrative design and principles for the allocation and administration of domains, from the top level down.
		MPPE itself (including the protocol used to negotiate its use, the details of the encryption method used and the algorithm used to change session keys during a session) is described in RFC 3078.
	www.potaroo.net /ietf/rfc3000-3099.html (7996 words)

	XML.com: XML on the Web Has Failed
		RFC 3023 (XML Media Types) is the problem.
		RFC 3023 is a valiant attempt to sort out the precedence mess between HTTP and XML, while still respecting all the other software that allows the Internet to work.
		Really good to see the RFC 3023 issues taken to a wider audience, but as the other commentators have said "failed utterly, miserably, completely" is rather an exaggeration.
	www.xml.com /pub/a/2004/07/21/dive.html (4154 words)

	The Atom Syndication Format 0.3 (PRE-DRAFT)
		As specified for "application/xml" in RFC 3023 [RFC3023], section 3.2.
		As specified for "application/xml" in RFC 3023 [RFC3023], section 5.
		As specified in RFC 3023 [RFC3023], section 6.
	www.mnot.net /drafts/draft-nottingham-atom-format-01.html (2181 words)

	PaceShouldBeWellFormed - Atom Wiki
		RFC 3023 defines rules for determining the character encoding of a feed (or any other XML document served over HTTP).
		According to RFC 3023, all of these feeds MUST be parsed as "us-ascii".
		According to RFC 3023, XML documents served as "text/xml" with no charset parameter have a character encoding of "us-ascii".
	www.intertwingly.net /wiki/pie/PaceShouldBeWellFormed (743 words)

	XEP-0081: Jabber MIME Type
		The value of a URI scheme (see RFC 3986 [1]) for Jabber/XMPP communications has long been recognized within the Jabber community, and such a scheme has been formally defined in RFC 4622 [2] as a way of identifying entities that adhere to XMPP Core [3] or its antecedents.
		Detailed security considerations for instant messaging and presence protocols are given in RFC 2779 [11] (Sections 5.1 through 5.4), and for XMPP in particular are given in RFC 3920 (Sections 12.1 through 12.6).
		Encoding considerations: Same as encoding considerations of application/xml as specified in RFC 3023; per Section 11.5 of RFC 3920, the encoding must be UTF-8.
	www.xmpp.org /extensions/xep-0081.html (1605 words)

	Cover Pages: XML and MIME Media-Types
		This feature is designed primarily for use with the XML Media Types defined in RFC 3023, to provide additional hints as to the processing requirements of a given XML resource." From the Introduction: "MIME Content-Type identifiers have proven very useful as tools for describing homogeneous information.
		RFC 3023 defines a set of XML media types capable of indicating, among other things, a 'most important' type for an XML resource.
		Major differences from RFC 2376 are (1) the addition of text/xml-external-parsed-entity, application/xml-external-parsed-entity, and application/xml-dtd, (2) the '+xml' suffix convention (which also updates the RFC 2048 registration process), and (3) the discussion of 'utf-16le' and 'utf-16be'." [cache]
	xml.coverpages.org /xmlMediaMIME.html (5907 words)

	RFC 3023
		An RFC from the IETF, see also the MIME standard,
		Full text of RFC 3023 (http://www.ietf.org/rfc/rfc3023.txt) XML Media Types.
		(Format: TXT=86011 bytes) (Obsoletes RFC 2376[?]) (Updates RFC 2048) (Status: PROPOSED STANDARD)
	www.ebroadcast.com.au /lookup/encyclopedia/rf/RFC_3023.html (31 words)

	RFC 3858
		Watchers are defined as entities that request (i.e., subscribe to) information about a resource, using the SIP event framework, RFC 3265 [1].
		Optional parameters: Same as charset parameter application/xml as specified in RFC 3023 [9].
		Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this
	www.apps.ietf.org /rfc/rfc3858.html (2293 words)

	[No title]
		The definition is based on RFC 3023, which defines the use of the "application/xml" media type [4].
		Encoding considerations: Same as encoding considerations of application/xml in RFC 3023 Security considerations: See Section 6, "Security Considerations", of this document.
		Hoschka Informational [Page 5] RFC 4536 application/smil and application/smil+xml May 2006 An example use of this parameter as part of a HTTP GET transaction would be: Accept: application/smil+xml; profile="http://www.w3.org/2001/SMIL20/HostLanguage" 6.
	www.isi.edu /in-notes/rfc4536.txt (1404 words)

	IANA \| Application for Media Type
		See also RFC 2046, and RFC 4288, sections 3 and 4.2.
		Note: Registrations in the standards tree must be approved by the IESG and must correspond to a formal publication by a recognized standards body.
		See RFC 2046 section 6, and RFC 4288 section 4.8.
	www.iana.org /cgi-bin/mediatypes.pl (191 words)

	RSS Disposition Hinting Proposal
		The reason relevant to this article is that it allows web browsers to recognize a document as an RSS feed and handle it properly without having to probe (or understand) the file (as would be the case if the "application/xml", "text/xml", or "text/plain" MIME types were used).
		It looks ugly but RFC 2045 does not allow you to put any spaces or use a comma in a value [unless it is in a quoted string].
		icepick: The reason that I choose the Dublin Core terminology instead of the MIME terminology (laid out in RFC 2046) of "text", "image", "audio", "video", and "application" is that I feel that the Dublin Core classifications are better; and since the Dublin Core standards already have widespread use I went with that.
	www.advogato.org /article/852.html (2088 words)

	XML.com: TAG: Managing the Complex Web
		For example, Berners-Lee said, "the meaning of a document whose outermost element is RDF is the semantics of the RDF statements defined by the RDF spec and the specs of the properties used in the outermost level of the RDF document".
		He further suggested that for "widely adopted" W3C recommendations which define a namespace that will be used on the root element of XML instances that "it is wise but not essential to make a special MIME type" and that RFC 3023's conventions and requirements should be observed thereby.
		RFC 2912, to specify a finely-grained description of content.
	www.xml.com /pub/a/2002/01/23/tag.html (1895 words)

	TWiki . Javawsxml . Rome05CharsetEncoding
		JAXP SAX parsers are not aware of the HTTP transport rules for charset encoding resolution as defined by RFC 3023.
		Invalid according to the XML 1.0 specification and the RFC 3023.
		Following Section 4.3.3, Appendix F.1 and Appendix F.2 of the XML 1.0 specification, plus RFC 3023 the charset encoding of an XML document served over HTTP is determined as follows:
	wiki.java.net /bin/view/Javawsxml/Rome05CharsetEncoding (1222 words)

	PaceMustBeWellFormed - Atom Wiki
		RFC 3023 defines how to determine the character encoding of XML documents served over HTTP.
		The rules are wholely defined by RFC 3023, but they are summarized here because there has been widespread confusion over how RFC 3023 should be interpreted:
		Clients MUST treat "application/atom+xml" as "application/xml" and determine the character encoding as per RFC 3023 or its successor.
	www.intertwingly.net /wiki/pie/PaceMustBeWellFormed (794 words)

	[No title]
		For example, a particular specification might indicate: "content MUST be represented using media-type application/xml, and the document must either (a) carry an xml declaration specifying version="1.0" or (b) omit the XML declaration, in which case per the XML recommendation the version defaults to 1.0" Murata, et al.
		These registrations MAY reference the applicaiton/xml registration in RFC XXXX in specifying interoperability considerations, if these considerations are not overridden by issues specific to that media type.
		Expires July 5, 2005 [Page 42] Internet-Draft XML Media Types January 2005 Appendix B. Changes from RFC 3023 There are numerous and significant differences between this specification and [RFC3023], which it obsoletes.
	xml.coverpages.org /draft-murata-kohn-lilley-xml-01.txt (11037 words)

	Roxen Community: RFC 3023 XML Media Types (Standards Track)
		The use of the charset parameter is STRONGLY RECOMMENDED, since this information can be used by XML processors to determine authoritatively the charset of the XML MIME entity.
		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
		Funding for the RFC Editor function is currently provided by the Internet Society.
	community.roxen.com /developers/idocs/rfc/rfc3023.html (9508 words)

Try your search on: Qwika (all wikis)