OpenSocial 1.0 spec patch: Clarify custom tag parameter behavior

Adds clarifying text and examples of how parameters to custom tag instances are processed.

[levik, 2009-11-10 18:29:59]

This seems to have a number of changes that were never discussed on the thread.

http://codereview.appspot.com/151062/diff/1/2
File OpenSocial-Templating.xml (right):

http://codereview.appspot.com/151062/diff/1/2#newcode420
OpenSocial-Templating.xml:420: <t>Parameters can be passed into templates as XML
attributes, elements, or with the &lt;os:Var&gt; tag.
I don't recall the <os:Var> proposal mentioning such usage, and no examples are
given in this patch.

This functionality was never discussed.

http://codereview.appspot.com/151062/diff/1/2#newcode430
OpenSocial-Templating.xml:430: &lt;messageColor&gt;blue&lt;/messageColor&gt;
Why was this refactored? This example demonstrated a very useful aspect of ${My}
- dropping support for this was never discussed.

http://codereview.appspot.com/151062/diff/1/2#newcode436
OpenSocial-Templating.xml:436: Custom tag template parameters using the rules
below to determine behavior.
This sentence seems to be missing a verb? Meaning is unclear.

http://codereview.appspot.com/151062/diff/1/2#newcode457
OpenSocial-Templating.xml:457: Nested elements are treated as string content and
subject to any escaping rules or behavior.
I believe there is a section detailing how DOM elements are treated in EL. (
http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/OpenSocial-...
)
Why treat them like strings here?

http://codereview.appspot.com/151062/diff/1/2#newcode459
OpenSocial-Templating.xml:459: <preamble>Below code results in: ${My.message} =
"This is &lt;b&gt;great&lt;/b&gt;"</preamble>
BTW, in the Wiki version, the <b> tag is not escaped on this line. Just to be
clear, you are saying that it will get escaped, right?

http://codereview.appspot.com/151062/diff/1/2#newcode480
OpenSocial-Templating.xml:480: property of the object.
This "value" property was never discussed - it seems designed to do the same
thing as <os:Render>. (It's possible that a similar scheme can be used to
implement <os:Render>, but I don't think it should be codified in the spec)

The name "value" is also way too common to be reserved. (In HTML, <input> and
<option> tags use it, suggesting a pattern developers may chose to replicate for
custom tags.)

[goosemanjack, 2009-12-15 18:44:21]

Updated to address reviewer comments

[goosemanjack, 2010-01-11 23:03:28]

Removing items referencing innerXML property and explicity referencing markup

[levik, 2010-01-12 16:21:57]

I'd also like to see the reference to <os:Var> dropped as I believe we
agreed the mentioned behavior would be left unspecified.

On Mon, Jan 11, 2010 at 6:03 PM, <goosemanjack@gmail.com> wrote:

> Removing items referencing innerXML property and explicity referencing
> markup
>
> http://codereview.appspot.com/151062
>

[goosemanjack, 2010-01-12 22:22:39]

Removing reference to os:Var for this spec round