Abstract: Aspects of the present disclosure provide a convenient user interface using which a user can identify and view electronic resources of interest. In an embodiment, the user enters a string for identifying a next resource to access. A first set of resource identifiers matching the string are determined, with each resource identifier being present in the content of a corresponding electronic resource previously accessed by said user. The identified first set of resources are listed on a display unit. Upon receiving a selection of one of the displayed electronic resources, the electronic resource is retrieved and the corresponding content is displayed on the display unit. In an embodiment, the user interface is provided as the user enters the search string in an address bar of a browser window. The resources previously accessed by the user using the browser application may also be displayed as a group.

Abstract: Aspects of the present disclosure provide a convenient user interface using which a user can identify and view electronic resources of interest. In an embodiment, the user enters a string for identifying a next resource to access. A first set of resource identifiers matching the string are determined, with each resource identifier being present in the content of a corresponding electronic resource previously accessed by said user. The identified first set of resources are listed on a display unit. Upon receiving a selection of one of the displayed electronic resources, the electronic resource is retrieved and the corresponding content is displayed on the display unit. In an embodiment, the user interface is provided as the user enters the search string in an address bar of a browser window. The resources previously accessed by the user using the browser application may also be displayed as a group.

Abstract: An aspect of the present disclosure provides enhanced flexibility for users to transform XML data to a desired format. In an embodiment, a configuration data indicates the specific elements required for generating the output for other elements. During a first pass, any occurrences of the specific elements in an input XML data are populated in a cache. During a second pass, XSL transformation rules are used for transforming the elements of the XML data. When an XSL transformation requires a specific element stored in the cache, the specific element is retrieved and an output portion is formed by incorporating the retrieved element according to the XSL transformation rule. According to another aspect, the configuration data also specifies various context objects that are enabled to interface with corresponding external (data) sources. Accordingly, data from external sources is enabled to be incorporated in the output according to XSL transformation rules.

Abstract: An aspect of the present disclosure provides enhanced flexibility for users to transform XML data to a desired format. In an embodiment, a configuration data indicates the specific elements required for generating the output for other elements. During a first pass, any occurrences of the specific elements in an input XML data are populated in a cache. During a second pass, XSL transformation rules are used for transforming the elements of the XML data. When an XSL transformation requires a specific element stored in the cache, the specific element is retrieved and an output portion is formed by incorporating the retrieved element according to the XSL transformation rule. According to another aspect, the configuration data also specifies various context objects that are enabled to interface with corresponding external (data) sources. Accordingly, data from external sources is enabled to be incorporated in the output according to XSL transformation rules.

Abstract: A web server provided according to an aspect of the present invention provides access to different versions of a document. In an embodiment, the web server sends the last version in response to a first request, and a specific requested version in response to a second request (identifying the specific requested version). According to another aspect, the specific requested version is sent when the request includes a corresponding version identifier along with a document identifier, and the last version is sent when the request includes only the document identifier. According to one more aspect, the web server sends a web page indicating all the versions of a document in response to a request for all the versions.

Abstract: A conference server, provided according to an aspect of the present invention, identifies a participant of a meeting in progress and requests scheduling option for a subsequent meeting from the identified participant. On receiving a scheduling option from the participant, the conference server determines the possible participants (“recipients”) of the subsequent meeting and informs the recipients of the received scheduling option. In one embodiment, the conference server requests the scheduling option when a conflict between the meeting in progress and the subsequent meeting is found and sends notifications to the recipients (determines by examining the calendars of users). In another embodiment, the conference server requests the scheduling option for a follow-up meeting for the meeting in progress, and updates the calendars of the recipients (determined as the participants of the meeting in progress and any users invited).

Abstract: Embodiments of the present invention enable navigation in a web browser to be supported by a session browse history. In embodiments, a session browse history may be an n-ary tree data structure. Embodiments of the present invention integrated into a browser enable a user to access a session browse history tree via browser UI displays such as a navigation bar, a main tool bar, or a combination thereof. In embodiments, a session browse history tree may be exported to persistent storage, and may be imported into and integrated with an active session browse history tree. In embodiments, a stored session browse history tree may be updated in response to handling a caught browser event such as a “browser refresh” event, and in response to processing a user-initiated “go to” request from the browser UI. In embodiments, a currently stored session browse history tree may be returned in response to a request received from the browser UI.

Abstract: A conference server, provided according to an aspect of the present invention, identifies a participant of a meeting in progress and requests scheduling option for a subsequent meeting from the identified participant. On receiving a scheduling option from the participant, the conference server determines the possible participants (“recipients”) of the subsequent meeting and informs the recipients of the received scheduling option. In one embodiment, the conference server requests the scheduling option when a conflict between the meeting in progress and the subsequent meeting is found and sends notifications to the recipients (determines by examining the calendars of users). In another embodiment, the conference server requests the scheduling option for a follow-up meeting for the meeting in progress, and updates the calendars of the recipients (determined as the participants of the meeting in progress and any users invited).

Abstract: A web server provided according to an aspect of the present invention provides access to different versions of a document. In an embodiment, the web server sends the last version in response to a first request, and a specific requested version in response to a second request (identifying the specific requested version). According to another aspect, the specific requested version is sent when the request includes a corresponding version identifier along with a document identifier, and the last version is sent when the request includes only the document identifier. According to one more aspect, the web server sends a web page indicating all the versions of a document in response to a request for all the versions.

Abstract: Embodiments of the present invention enable navigation in a web browser to be supported by a session browse history. In embodiments, a session browse history may be an n-ary tree data structure. Embodiments of the present invention integrated into a browser enable a user to access a session browse history tree via browser UI displays such as a navigation bar, a main tool bar, or a combination thereof. In embodiments, a session browse history tree may be exported to persistent storage, and may be imported into and integrated with an active session browse history tree. In embodiments, a stored session browse history tree may be updated in response to handling a caught browser event such as a “browser refresh” event, and in response to processing a user-initiated “go to” request from the browser UI. In embodiments, a currently stored session browse history tree may be returned in response to a request received from the browser UI.