Structured Data Exchange Format (SDXF)
The information below is for an old version of the document that is already published as an RFC.
|Document||Type||This is an older version of an Internet-Draft that was ultimately published as an RFC.|
|Last updated||2013-03-02 (Latest revision 2000-10-23)|
|RFC Editor Note||(None)|
|IESG||IESG state||RFC 3072 (Informational)|
|Send notices to||(None)|
A new Request for Comments is now available in online RFC libraries. RFC 3072 Title: Structured Data Exchange Format (SDXF) Author(s): M. Wildgrube Status: Informational Date: March 2001 Mailbox: firstname.lastname@example.org Pages: 25 Characters: 48481 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-wildgrube-sdxf-08.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3072.txt This specification describes an all-purpose interchange format for use as a file format or for net-working. Data is organized in chunks which can be ordered in hierarchical structures. This format is self-describing and CPU-independent. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.