-- 作者：deg
-- 发布时间：1/28/2009 6:22:00 PM
--
方便大家浏览，我把全文附在二楼 : ) Form Filling Extensible Markup Language (FFXML) 1.0 (First Edition)
IEAssist Inc Recommendation 25 January 2009 This version:
http://www.ieassist.com/ffxml-20090125.htm Latest version:
http://www.ieassist.com/ffxml.htm Editors:
IEAssist Inc ffxml@ieassist.com Copyright © 2009 IEAssist Inc ® , All Rights Reserved. Abstract
The Form Filling Extensible Markup Language (FFXML) is a subset of XML that is completely described in this document. Its goal is to enable XML contains form filling information to be served, received, and processed on the Web in the way that is now possible with generic XML. FFXML has been designed for ease of implementation and for interoperability with XML. Table of Contents
1 Introduction
2 Documents
2.1 How to organize an FFXML file
2.2 Example
2.3 Root node
2.4 Collection node
2.5 Element node
2.6 TagName node
2.7 Type node
2.8 Id node
2.9 Name node
2.10 Text node
2.11 Value node 1 Introduction
Form Filling Extensible Markup Language, abbreviated FFXML, describes a class of data objects called FFXML documents and partially describes the behavior of form filling programs which process them. FFXML is an database for form filling application or restricted form of XML, the Extensible Markup Language [REC-xml]. By construction, FFXML documents are conforming XML documents. 2 Documents
[Definition: A data object is an FFXML document if it is well-formed, as defined in this specification. In addition, the FFXML document is valid if it meets certain further constraints.] Each FFXML document has both a logical and a physical structure. Physically, the document is composed of units called entities. An entity may refer to other entities to cause their inclusion in the document. A document begins in a "root" or document entity. Logically, the document is composed of declarations, elements, comments, character references, and processing instructions, all of which are indicated in the document by explicit markup. The logical and physical structures MUST nest properly, as described in Well-Formed Parsed Entities. 2.1 How to organize an FFXML file
An FFXML file contains one root node, root node contains a set of "<collection>" nodes, every "<collection>" nodes contain a set of "<element>" nodes, every "<element>" nodes contain a set of nodes used for identifying the HTML element such as "<tagName>", "<type>", "<id>", "<name>", and every "<element>" nodes contain a set of nodes used for filling form such as "<text>", "<value>". Here is an example for FFXML document. 2.2 Example
example.xml <?xml version="1.0" encoding="utf-8"?>
<collections>
<collection name="pick">
<element name="iLastName">
<tagName>INPUT</tagName>
<type>text</type>
<id>iLastName</id>
<name>iLastName</name>
<value>Assist</value>
</element>
<element name="iCountry">
<tagName>SELECT</tagName>
<type>select-one</type>
<id>iCountry</id>
<name>iCountry</name>
<value>US</value>
<text>United States</text>
</element>
<element name="iGenderMale">
<tagName>INPUT</tagName>
<type>radio</type>
<id>iGenderMale</id>
<name>profile_gender</name>
<value>m</value>
</element>
<element name="message">
<tagName>TEXTAREA</tagName>
<type>textarea</type>
<id>message</id>
<name>message</name>
<value>ieassist.com</value>
</element>
</collection>
</collections>
2.3 Root node
Description Root node should be "<collections>", and "<collections>" should be the parent of "<collection>" node, "<collections>" node was used for managing a set of "<element>" nodes.
Format <collections>
Parent Node No
Child Node <collection>
Attribute 1 Name
Text No
2.4 Collection node
Description "<collection>" node should be the child of root element, and should be the parent of "<element>"node , an FFXML file may contains several "<collection>" nodes, "<collection>" node was used for managing a set of <element> nodes.
Format <collection>
Parent Node <collections>
Child Node <element>
Attribute 1 Name
Text No
2.5 Element node
Description "<element>" node should be the child of <collection>, and should be the parent of "<tag>" node, "<element>" node was used for managing a set of <tag> nodes.
Format <element>
Parent Node <collection>
Child Node <tagName>, <type>
Attribute 1 Name
Text No
2.6 TagName node
Description "<tagName>" node should be the child of <element> node, and was used for storing the tagName of HTML element to be filled.
Format <tagName>
Parent Node <element>
Child Node No
Attribute No
Text Specify the tagName of HTML element to be filled.
2.7 Type node
Description "<type>" node should be the child of <element> node, and was used for storing the type(1, 2, 3, 4, 5, 6, 7, 8, 9, 10) of HTML element to be filled.
Format <type>
Parent Node <element>
Child Node No
Attribute No
Text Specify the type(1, 2, 3, 4, 5, 6, 7, 8, 9, 10) of HTML element to be filled.
2.8 Id node
Description "<id>" node should be the child of <element> node, and was used for storing the id of HTML element to be filled.
Format <id>
Parent Node <element>
Child Node No
Attribute No
Text Specify the id of HTML element to be filled.
2.9 Name node
Description "<name>" node should be the child of <element> node, and was used for storing the name(1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11) of HTML element to be filled.
Format <name>
Parent Node <element>
Child Node No
Attribute No
Text Specify the name(1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11) of HTML element to be filled.
2.10 Text node
Description "<text>" node should be the child of <element> node, and was used for storing the text of HTML element to be filled.
Format <text>
Parent Node <element>
Child Node No
Attribute No
Text Specify the text of HTML element to be filled.
2.11 Value node
Description "<value>" node should be the child of <element> node, and was used for storing the value(1, 2, 3, 4, 5) of HTML element to be filled.
Format <value>
Parent Node <element>
Child Node No
Attribute No
Text Specify the value(1, 2, 3, 4, 5) of HTML element to be filled.
|