Voting thread: os:Var

[goosemanjack]

Please vote for the <os:Var> proposal on this thread.

[Jalen]

+1

[jorge]

+1

[Evan Gilbert]

Per discussion, can we make it clear that EL isn't allowed in JSON literals? 

We can either remove this line:

"<t>Process to replace EL statements (${} markup)</t>"

or add "if specified in @value attributes"

On Thu, Jan 21, 2010 at 2:34 PM, jorge <jer...@gmail.com> wrote:

+1

--
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
To post to this group, send email to opensocial-an...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.

[goosemanjack]

I thought the discussion was to remove explicit statements about how
to include and process EL in JSON literals (i.e. leave spec mute on EL
in JSON). I can see how the first two statements conflict. I've
committed a change that cleans it up as follows:

1. Process to replace EL statements (${} markup)
2. Attempt to parse it as a JSON value and return the resulting
object if successful.
3. If all other processing does not resolve the value, return as a
string

The line "Process to replace EL statements (${} markup)" must remain
in place to allow for strings with embedded EL and literals.

ex:
<os:Var key="contacted" value="Put them together is ${val1} and $
{val2}" />

If that's not clear enough for your tastes, we can change the second
line to add a "MAY" statement regarding EL in JSON.

2. Attempt to parse it as a JSON value and return the resulting
object if successful. A container MAY honor resolving embedded EL
statements in JSON objects.

Codifying explicitly disallowing EL in in JSON is not an acceptable
edit.
--
clc

On Jan 21, 4:55 pm, Evan Gilbert <uid...@google.com> wrote:
> Per discussion, can we make it clear that EL isn't allowed in JSON
> literals?
>
> We can either remove this line:
> "<t>Process to replace EL statements (${} markup)</t>"
> or add "if specified in @value attributes"
>
> On Thu, Jan 21, 2010 at 2:34 PM, jorge <jer...@gmail.com> wrote:
> > +1
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "OpenSocial and Gadgets Specification Discussion" group.
> > To post to this group, send email to
> > opensocial-an...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > opensocial-and-gadg...@googlegroups.com<opensocial-and-gadgets-spec%2Bunsu...@googlegroups.com>

[Lane LiaBraaten]

@Evan - Are you good w/ the clean up Chris committed?

I'd like to close this thread so we can remove the x:draft tags and publish RC2.

-Lane

To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.

[Evan Gilbert]

+1

woo hoo!

[goosemanjack]

Removed <x:draft> tags.

On Jan 29, 6:19 pm, Evan Gilbert <uid...@google.com> wrote:
> +1
>
> woo hoo!
>

> >> <opensocial-and-gadgets-spec%2Bunsu...@googlegroups.com<opensocial-and-gadgets-spec%252Buns...@googlegroups.com>