Proposal for 1.0 - Clarify case sensitivity rules for DataPipeline/DataContext/EL variables
2 views
Skip to first unread message
goosemanjack
Oct 7, 2009, 5:56:14 AM10/7/09
to OpenSocial - OpenSocial and Gadgets Specification Discussion
Synopsis:
None of the various OpenSocial specs provide clarity on case-
sensitivity rules for variables and EL statements. We would like to
add additional language that specifies all variables to be case-
sensitive.
Currently the spec(s) does not specify case sensitivity rules for any
of the following:
* Variable names of pipeline-tag declared data
* Template-local variables
* Reserved EL variables
Initially we went down a path of allowing variables to be case-
insensitive. Hence the values ${My.person.displayName} would be
equivalent to ${my.person.displayName} and ${Msg.greeting} is the same
as ${msg.greeting}. After some work, however, it proved to be a
source of confusion for developers because the actual data properties
are based on the REST data contracts and are case-sensitive.
We would like to add language to the various specs that clarifies case
sensitivity rules as follows:
* All pipeline-declared variables ARE case-sensitive. Hence using the
two tags below would result in two pieces of data being declared in
the DataContext under the keys "Viewer" and "viewer"
ex:
<os:ViewerRequest key="Viewer" />
<os:PersonRequest key="viewer" method="people.get" userId="@viewer"
groupId="@self" />
* Template-local variables ARE case sensitive.
* All reserved EL variables ARE case-sensitive. This means (provided
"varName" is a valid template-local variable) ${My.varName} would
evaluate, but ${my.varName} would be undefined. This includes the
message-bundle reserved variable ${Msg}. So ${Msg.foo} is valid, but $
{msg.foo} is not.
None of the various OpenSocial specs provide clarity on case-
sensitivity rules for variables and EL statements. We would like to
add additional language that specifies all variables to be case-
sensitive.
Currently the spec(s) does not specify case sensitivity rules for any
of the following:
* Variable names of pipeline-tag declared data
* Template-local variables
* Reserved EL variables
Initially we went down a path of allowing variables to be case-
insensitive. Hence the values ${My.person.displayName} would be
equivalent to ${my.person.displayName} and ${Msg.greeting} is the same
as ${msg.greeting}. After some work, however, it proved to be a
source of confusion for developers because the actual data properties
are based on the REST data contracts and are case-sensitive.
We would like to add language to the various specs that clarifies case
sensitivity rules as follows:
* All pipeline-declared variables ARE case-sensitive. Hence using the
two tags below would result in two pieces of data being declared in
the DataContext under the keys "Viewer" and "viewer"
ex:
<os:ViewerRequest key="Viewer" />
<os:PersonRequest key="viewer" method="people.get" userId="@viewer"
groupId="@self" />
* Template-local variables ARE case sensitive.
* All reserved EL variables ARE case-sensitive. This means (provided
"varName" is a valid template-local variable) ${My.varName} would
evaluate, but ${my.varName} would be undefined. This includes the
message-bundle reserved variable ${Msg}. So ${Msg.foo} is valid, but $
{msg.foo} is not.
Jorge Reyes
Oct 7, 2009, 12:05:18 PM10/7/09
to opensocial-an...@googlegroups.com
+1 This make implementation in general easier.
Evan Gilbert
Oct 7, 2009, 12:30:00 PM10/7/09
to opensocial-an...@googlegroups.com
+1
Lev Epshteyn
Oct 8, 2009, 10:42:03 AM10/8/09
to opensocial-an...@googlegroups.com
+1
Adam Winer
Oct 9, 2009, 8:56:33 PM10/9/09
to opensocial-an...@googlegroups.com
+1.
Louis Ryan
Oct 12, 2009, 12:03:47 PM10/12/09
to opensocial-an...@googlegroups.com
+1
goosemanjack
Nov 2, 2009, 5:13:36 PM11/2/09
to OpenSocial - OpenSocial and Gadgets Specification Discussion
Voting open. We have five +1's, so this period would be for any
voices of dissent or adjustments to patch
Patch http://codereview.appspot.com/143063/show
voices of dissent or adjustments to patch
Patch http://codereview.appspot.com/143063/show
Jalen
Dec 15, 2009, 4:52:18 PM12/15/09
to OpenSocial - OpenSocial and Gadgets Specification Discussion
+1
goosemanjack
Jan 11, 2010, 10:49:12 PM1/11/10
to OpenSocial - OpenSocial and Gadgets Specification Discussion
We need to get this patch committed. I'm not currently cleared as a
committer on this project.
committer on this project.
Patch 143063
http://codereview.appspot.com/143063/show
On Dec 15 2009, 1:52 pm, Jalen <jal...@gmail.com> wrote:
> +1
goosemanjack
Jan 12, 2010, 5:05:50 PM1/12/10
to OpenSocial - OpenSocial and Gadgets Specification Discussion
Applied patch, now that I have committer rights
Reply all
Reply to author
Forward
0 new messages