idnits 2.17.1 draft-ietf-xmldsig-canonical-01.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3076 5 Title: Canonical XML Version 1.0 6 Author(s): J. Boyer 7 Status: Informational 8 Date: March 2001 9 Mailbox: jboyer@PureEdge.com 10 Pages: 27 11 Characters: 63955 12 Updates/Obsoletes/SeeAlso: None 14 I-D Tag: draft-ietf-xmldsig-canonical-01.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3076.txt 18 Any XML (Extensible Markup Language) document is part of a set of XML 19 documents that are logically equivalent within an application context, 20 but which vary in physical representation based on syntactic changes 21 permitted by XML 1.0 and Namespaces in XML. This specification 22 describes a method for generating a physical representation, the 23 canonical form, of an XML document that accounts for the permissible 24 changes. Except for limitations regarding a few unusual cases, if two 25 documents have the same canonical form, then the two documents are 26 logically equivalent within the given application context. Note that 27 two documents may have differing canonical forms yet still be 28 equivalent in a given context based on application-specific 29 equivalence rules for which no generalized XML specification could 30 account. 32 This document is a product of the XML Digital Signatures Working Group 33 of the IETF. 35 This memo provides information for the Internet community. It does 36 not specify an Internet standard of any kind. Distribution of this 37 memo is unlimited. 39 This announcement is sent to the IETF list and the RFC-DIST list. 40 Requests to be added to or deleted from the IETF distribution list 41 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 42 added to or deleted from the RFC-DIST distribution list should 43 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 45 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 46 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 47 help: ways_to_get_rfcs. For example: 49 To: rfc-info@RFC-EDITOR.ORG 50 Subject: getting rfcs 52 help: ways_to_get_rfcs 54 Requests for special distribution should be addressed to either the 55 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 56 specifically noted otherwise on the RFC itself, all RFCs are for 57 unlimited distribution.echo 58 Submissions for Requests for Comments should be sent to 59 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 60 Authors, for further information.