Abstract: Widgets on a web page may interact with each other in order to provide a rich, responsive content experience. In one example, the widgets that are provided may include a video player, a video gallery, a metadata pane, or any other components. The gallery may allow a user to select a video to be played, and the gallery may communicate the user's choice to the video player. The video player may then play the video that the user has selected. A container may be provided that allows widgets in the container to interoperate with each other. For example, the container may provide an interface that facilitates communication between a widget and the container, and between plural widgets. A tool may be provided that allows a designer to configure the widgets.

Abstract: Methods providing clients with a full contextual metadata experience. Metadata include multiple forms of property data, or information, relating to media accessed by a media player, such as a CD in a CD-ROM drive of a computer. Metadata is transferred from a server to a client. Identification parameters associated with the accessed media file are submitted by the client to a server, and property data is retrieved and forwarded to the client. The metadata provides the user with integrated, contemporaneous property data directly related to the media file being played, providing automatic, integrated access to data from multiple databases, simply by accessing a related media file through a media player, without further direction from the user.

Abstract: Systems and methods are described for declarative client input security screening. A configuration module in a web-based application (or project) that includes one or more web pages is designed to allow client input to be screened for the web pages by declaring particular screening attributes and actions therein. A global section in such a configuration module includes security screens that apply to input of all types, while other individual sections include security screens that apply only to input of particular type. The global section provides a way to consolidate screening that applies to all client input types, thereby precluding redundant screens having to be maintained in each individual section. Client input that survives the security screening is cached and used in normal page processing. By including the security screens in a declarative section, maintenance is made more efficient and reliable.

Abstract: Systems and methods are described for declarative localization of web services. A “localize” attribute is described that uniquely identifies localized content for the final rendered element. The “localize” attribute is stripped out during the rendering process, so it never reaches the client or agent, making the “localize” attribute HTML-compliant. A separate satellite assembly is maintained for each culture. When a request is received, a culture is identified and the “localize” attribute directs processing to utilize content maintained in the satellite assembly associated with the identified culture. Processing then continues normally.