WPF allows for the definition of both 2D and 3D objects, rotations, animations, and a variety of other effects and features. When used in Windows Workflow Foundation contexts, XAML is used to describe potentially long-running declarative logic, such as those created by process modeling tools and rules systems. The serialization format for workflows was previously called XOML, to differentiate it from UI markup use of XAML, but now they are no longer distinguished. However, the file extension for files containing the workflow markup is still "XOML". XAML uses a specific way to define look and feel called "Template"s; differing from Cascading Style Sheet syntax, it is closer to XBL. This Windows Presentation Foundation example shows the text "Hello, world!" in the top-level XAML container called Canvas. The schema (the xmlns="https://web.archive.org/web/20170705010515/http://schemas.microsoft.com/..." part) may have to be changed to work on your computer. Using a schema that Microsoft recommends, the example can also be   This can be integrated into a Web page if WPF is installed using XBAPs (XAML Browser Applications) that are compiled applications running in a sandboxed environment hosted within the browser. Another way is to use the Silverlight plugin. The code cannot be included directly in an HTML page; rather it must be loaded into the page via JavaScript. If .NET 3.0 or later is installed, loose XAML files can also be viewed on their own in a compatible Web browser (including Internet Explorer and Firefox) in conjunction with the .NET Framework 3.0, without the need for the Silverlight plugin. Loose XAML files are markup-only files limited to defining the visual content to be rendered. They are not compiled with an application. The "MySilverlight.js" file must contain the code that loads the above XAML code (as an XML file) under the "MySilverlight" HTML element. A crucial part of utilizing XAML to its full potential is making appropriate usage of binding, as well as being comfortable with creating your own custom user elements as required, for your specific needs. Binding can be done as follows:    There are four Microsoft main implementations of XAML:  These versions have some differences in the parsing behavior. Additionally, the Silverlight 4 XAML parser is not 100% backward compatible with Silverlight 3 files.