Re: sappenin.com eaut template
Will Norris
On Jul 21, 2008, at 9:36 AM, David Fuelling wrote:
> On Mon, Jul 21, 2008 at 5:07 AM, Will Norris <wi...@willnorris.com>
> wrote:
>> David, just noticed that the EAUT template on sappenin.com doesn't
>> have
>> the curly braces properly encoded.
>
> Doh! Great catch -- I'll change that right away.
>
> Might be something to check for in a library, just in case (I don't
> see any
> harm in looking for both, since this could be a common error,
> especially if
> people create a template manually like I did).
ahh, since the spec only says it "should" be percent encoded, you're
right.. we chould check for this. Michael, you should update the
python library to check for both encoded and non-encoded templates
> With that said, what do you think about creating an implementor's
> "best-practices" page on eaut.org so that people creating libraries
> can have
> a reference (if you agree with my above statement, then that could
> be the
> first entry).
sounds good, see note below about the website.
> Also, eaut.org looks great (btw). Would you mind adding some kind
> of link
> to the google group so people can join the discussion list from
> eaut.org?
eh? it looks awful right now :) They're talking about EAUT at OSCON
this week, so I wanted to get the bare minimum up there as quick as
possible. It's needs some serious love, so if anyone is up for the
challenge, go for it. Just checkin everything to the 'website' folder
in SVN, and I'll pull it down on the eaut.org server. Down the road,
we may want to throw a real CMS (drupal, wordpress, whatever) behind
it... not sure.
-will
David Fuelling
On Jul 21, 2008, at 9:36 AM, David Fuelling wrote:
> On Mon, Jul 21, 2008 at 5:07 AM, Will Norris <wi...@willnorris.com>
> wrote:
>> David, just noticed that the EAUT template on sappenin.com doesn't
>> have
>> the curly braces properly encoded.
>
> Doh! Great catch -- I'll change that right away.ahh, since the spec only says it "should" be percent encoded, you're
>
> Might be something to check for in a library, just in case (I don't
> see any
> harm in looking for both, since this could be a common error,
> especially if
> people create a template manually like I did).
right.. we chould check for this. Michael, you should update the
python library to check for both encoded and non-encoded templates
Ahh....I just noticed that, too. I would vote for "MUST" language instead, but still have implementations do the check. Can anyone think of a good reason to use "SHOULD" here?
LOL - That's hllarious!! Lest you all think I have no sense of style, I should clarify that I was thinking it looks great compared to what was up there before (two hyperlinks), but you're right -- it would be awesome to make it look pretty. :)
They're talking about EAUT at OSCON
this week, so I wanted to get the bare minimum up there as quick as
possible. It's needs some serious love, so if anyone is up for the
challenge, go for it. Just checkin everything to the 'website' folder
in SVN, and I'll pull it down on the eaut.org server. Down the road,
we may want to throw a real CMS (drupal, wordpress, whatever) behind
it... not sure.
Very cool.
-will
Will Norris
> On Mon, Jul 21, 2008 at 7:08 PM, Will Norris <wi...@willnorris.com>
> wrote:
>>
>>
>> ahh, since the spec only says it "should" be percent encoded, you're
>> right.. we chould check for this. Michael, you should update the
>> python library to check for both encoded and non-encoded templates
>>
>
> Ahh....I just noticed that, too. I would vote for "MUST" language
> instead,
> but still have implementations do the check. Can anyone think of a
> good
> reason to use "SHOULD" here?
just realized the spec already says they MUST be encoded (section
5.1). The "should" I saw was talking about *decoding* the template.
It says that you "should" decode the template (in order to change them
back to regular braces), and then do replacement. I'll update the php
library in just a second. my bad, guys... the spec is fine as written.
-will