Abstract: An endpoint system provides a REST endpoint for an application. The endpoint system processes request messages based on message pair data for each message that includes an operation and parameter data. The parameter data includes parameter information for each parameter that identifies whether the value for the parameter is to be taken from the URI or payload of a request message. The endpoint system receives request messages that have a URI and payload. The URI includes an operation name. The endpoint system processes each request message in accordance with the message pair data for the operation specified in the request message. For each parameter of the message pair data, the endpoint system extracts the value for the parameter from either the URI or payload as specified by the parameter information for the parameter. The endpoint system then invokes the operation passing the one or more extracted values as actual parameters.

Abstract: An endpoint system provides a REST endpoint for an application. The endpoint system processes request messages based on message pair data for each message that includes an operation and parameter data. The parameter data includes parameter information for each parameter that identifies whether the value for the parameter is to be taken from the URI or payload of a request message. The endpoint system receives request messages that have a URI and payload. The URI includes an operation name. The endpoint system processes each request message in accordance with the message pair data for the operation specified in the request message. For each parameter of the message pair data, the endpoint system extracts the value for the parameter from either the URI or payload as specified by the parameter information for the parameter. The endpoint system then invokes the operation passing the one or more extracted values as actual parameters.

Abstract: An endpoint system provides a REST endpoint for an application. The endpoint system processes request messages based on message pair data for each message that includes an operation and parameter data. The parameter data includes parameter information for each parameter that identifies whether the value for the parameter is to be taken from the URI or payload of a request message. The endpoint system receives request messages that have a URI and payload. The URI includes an operation name. The endpoint system processes each request message in accordance with the message pair data for the operation specified in the request message. For each parameter of the message pair data, the endpoint system extracts the value for the parameter from the URI, payload, headers, or query parameters as specified by the parameter information. The endpoint system invokes the operation passing the one or more extracted values as actual parameters.

Abstract: An endpoint system provides a REST endpoint for an application. The endpoint system processes request messages based on message pair data for each message that includes an operation and parameter data. The parameter data includes parameter information for each parameter that identifies whether the value for the parameter is to be taken from the URI or payload of a request message. The endpoint system receives request messages that have a URI and payload. The URI includes an operation name. The endpoint system processes each request message in accordance with the message pair data for the operation specified in the request message. For each parameter of the message pair data, the endpoint system extracts the value for the parameter from the URI, payload, headers, or query parameters as specified by the parameter information. The endpoint system invokes the operation passing the one or more extracted values as actual parameters.

Abstract: A markup language document has data entry fields corresponding to markup language nodes that are arranged in a hierarchical structure of parents having child nodes. The hierarchical position of each markup language node in the hierarchical structure is expressed as a corresponding fragment of the markup language. For each parent, a markup language fragment is formed so as to have a plurality of portions each corresponding to the fragment of a respective child node without repeating any fragment of the respective child nodes. Portions that respectively correspond to the child nodes are used for data entry with the data entry fields, where an electronic form is displayed on a user interface for interactive data entry. The electronic form has one or more data entry fields each corresponding to one of the data entry fields of the structured markup language document and into which data can be entered.

Abstract: Systems and/or methods enabling creation and/or use of a recursive section for an electronic form are described. In one embodiment, a system and/or method enables alteration, responsive to graphical selection of a recursive section component, of an electronic form's schema to permit a recursive section. In another embodiment, a system and/or method enables a user to modify a recursive section in an electronic form through a rendering of the electronic form.

Abstract: A markup language document has data entry fields corresponding to markup language nodes that are arranged in a hierarchical structure of parents having child nodes. The hierarchical position of each markup language node in the hierarchical structure is expressed as a corresponding fragment of the markup language. For each parent, a markup language fragment is formed so as to have a plurality of portions each corresponding to the fragment of a respective child node without repeating any fragment of the respective child nodes. Portions that respectively correspond to the child nodes are used for data entry with the data entry fields, where an electronic form is displayed on a user interface for interactive data entry. The electronic form has one or more data entry fields each corresponding to one of the data entry fields of the structured markup language document and into which data can be entered.

Abstract: A markup language document has data entry fields corresponding to markup language nodes that are arranged in a hierarchical structure of parents having child nodes. The hierarchical position of each markup language node in the hierarchical structure is expressed as a corresponding fragment of the markup language. For each parent, a markup language fragment is formed so as to have a plurality of portions each corresponding to the fragment of a respective child node without repeating any fragment of the respective child nodes. Portions that respectively correspond to the child nodes are used for data entry with the data entry fields, where an electronic form is displayed on a user interface for interactive data entry. The electronic form has one or more data entry fields each corresponding to one of the data entry fields of the structured markup language document and into which data can be entered.

Abstract: Systems and/or methods enabling creation and/or use of a recursive section for an electronic form are described. In one embodiment, a system and/or method enables alteration, responsive to graphical selection of a recursive section component, of an electronic form's schema to permit a recursive section. In another embodiment, a system and/or method enables a user to modify a recursive section in an electronic form through a rendering of the electronic form.