Name : Roberto Perelman E-mail : rperelma@adobe.com MIME media type name : Application MIME subtype name : Vendor Tree - vnd.adobe.xfdf Required parameters : none Optional parameters : charset, with the recommended value being "UTF-8" (see RFC 2376) Encoding considerations : application/vnd.adobe.xfdf is used over HTTP, and no content-transfer-encoding is necessary (see RFC 2376) Security considerations : This format is used to carry forms data in both directions between a web client and a server. As such, its security implications are dependent on what use that data is put to at both the client and the server ends. At the client, that data is usually presented to an end user in some form. At the server, that data can be stored in databases, or fed to other applications. In all cases, it is important that this data is scrutinized to prevent malicious inputs from causing damage. See also RFC 2376 for additional considerations on the subject of security. Interoperability considerations : Since this is an XML-based format, it can be manipulated by any tool that understands XML Published specification : Included below: Specially important for multi-line text field values, but declare it at the root for compactness, to take advantage of inheritance A null value is equivalent to not including a value tag at all Field names may not contain periods A sample document instance: Once upon a time, there was a king. He had one daughter. 408 536-6000 biking hiking gardening Applications which use this media : Adobe Acrobat Additional information : 1. Magic number(s) : none (see also RFC 2376) 2. File extension(s) : .xfdf 3. Macintosh file type code : "XFDF" Person to contact for further information : 1. Name : Roberto Perelman 2. E-mail : rperelma@adobe.com Intended usage : Common Author/Change controller : (created 22 Jan 2002) (originally created 03 Nov 2000)