Page Comparison

<?xml version='1.0' encoding='utf-8'?&gt;
&lt;Module>
<Module title="Simple Gadget"&gt;>
  &lt;Data&gt;
      &lt;os<Data>
<os:ViewerRequest key='vwr' /&gt;
  &lt;/Data&gt;
  &lt;Templates&gt;
    &lt;Template >
</Data>
<Templates>
<Template tag="my:foo"&gt;>
<div>

  &lt;div&gt;
    &lt;img <img src="${My.person.thumbnailUrl}" /&gt; &lt;br/&gt;
    > <br/>

(Picture of ${My.person.displayName})
    &lt;/div&gt;
    &lt;/Template&gt;  
  &lt;/Templates&gt;

  &lt;Content</div>
</Template>
</Templates>


<Content type='osml' &gt;
  &lt;h1&gt;Hello>
<h1>Hello, ${vwr.displayName}&lt;/h1&gt;
  &lt;my</h1>
<my:foo person="${vwr}" /&gt;
 &lt;/Content&gt;
&lt;/Module&gt;
</pre>


== ModulePrefs as optional ==

The ModulePrefs section may be optional in a gadget.  The Module node may contain a @title attribute for the gadget.  When ModulePrefs is not specified the container may infer what features are required.

== Data section ==

A new Data element may be used to specify data pipeline tags. This is a direct child of the Module element. All data pipeline tags are globally registered.  Data may be scoped to a view(s) by specifying the view name(s) in a @scope attribute of the data pipeline tag.

== Templates section ==

A new Templates element may be used to specify data pipeline tags. This is a direct child of the Module element. All custom tag templates are globally registered.  Templates may be scoped to a view(s) by specifying the view name(s) in a @scope attribute of the Template tag.  This utilizes the syntax defined for template libraries.
>
</Content>
</Module>