FYI... I've put together a quick prototype example [1] of a html form
using a URI Template [2]. The processing of the template is performed
in the onsubmit event of the form.
- James
[1] http://www.snellspace.com/wp/?p=832
[2] http://www.snellspace.com/wp/?p=831
Ian Hickson wrote:
On Mon, 17
It's just an example.
Here's another:
form template=http://www.google.com/search?{-join||q,num}
method=GET
input name=q type=text /
input name=num type=range step=1 min=5 max=100 value=5 /
/form
- James
Krzysztof Żelechowski wrote:
Dnia 15-12-2007, So o godzinie 19:28 -0800, James M
.
HTML5 Post:
POST /example.org?a=wb=x
Host: example.org
...
c=yd=z
HTML4 Post:
POST /form_processor
Host: example.org
...
a=wb=xc=yd=z
- James
Henri Sivonen wrote:
On Dec 16, 2007, at 05:28, James M Snell wrote:
The gist of the idea (which I believe may have been brought up
Right. We avoid the issue by using a different attribute for the template.
- James
Julian Reschke wrote:
[snip]
That being said -- James suggested template instead of action anyway.
BR, Julian
While I am certain some folks may not appreciate the departure from the
engaging and entertaining debate over video codecs, I wanted to offer a
minor feature suggestion [1] with regards to HTML5 forms and URI
Templates [2].
The gist of the idea (which I believe may have been brought up before
but
As the note Anne points to indicates, there was simply zero interest on
the part of the Atompub WG to standardize autodiscovery.
FWIW, I still think it would be helpful -- not only for feeds but also
for Atompub service documents.
For the latter, Lotus Connections began using service links. I
the blogs that user can edit.
- James
Ian Hickson wrote:
On Mon, 5 Nov 2007, James M Snell wrote:
rel=service tells us that the link is pointing to a description of
some kind of service api, e.g. an atompub service document.
Ok, but that's very vague -- how is anyone supposed to use this rel
://jcheng.wordpress.com/2007/10/16/how-wlw-speaks-atompub-part-1-autodiscovery/
- James
Ian Hickson wrote:
On Mon, 5 Nov 2007, James M Snell wrote:
Just as an example, Windows Live Writer uses the service link to
discover the location of the Atompub service document; which it then
uses to configure itself
That, I'm afraid, would take away all of the fun of being sarcastic in
the first place.
- James
Charles Iliya Krempeaux wrote:
[snip]
It would be interesting if such a new sarcasm element would provide a
method of specifying the real meaning.
For example...
p
That's sarcasm
Hello,
I've recently been musing over some ideas around sandboxing scripts and
styles within a document [1]. The basic idea is to have some means of
isolating potentially untrustworthy scripts.
From my blog entry: Scripts within the sandbox would only see the DOM
of the sandbox. Methods
Anne van Kesteren wrote:
[snip]
Frames are a terrible solution. The content is after all a part of the
page it's hosted in, but we want to sandbox it to make sure it can't
do any harm.
The proposed alternative is severely underdefined and won't work for the
foreseeable future anyway.
already existing solutions to these problems that can work. What
I'm saying is that having some way of isolating a script would be ideal
and I was curious as to what others had to say about it.
- James
Jorgen Horstink wrote:
On Jan 12, 2007, at 10:30 PM, James M Snell wrote:
Anne van
Actually, for the form application/atom+xml;type=entry it's more
likely that browsers will completely ignore the type param as they do
currently.
- James
fantasai wrote:
[snip]
That means rel=feed won't be implied on an Atom Entry document whether
the
new MIME type syntax is chosen to be
You're right that the differentiation in the content-type is of less
importance but without it there's no way for me to unambiguously
indicate that a resource has both an Atom Feed representation and an
Atom Entry representation. The best I could do is say This things has
two Atom
I could but after the discussions this week I'm not sure its worth it.
Yes, everything can be done using different rel values; the content-type
thing is more just an annoyance than anything else. I'll just make sure
that I never link my Atom entry documents using alternate (even tho
that's what
Hello,
Over on the IETF Atom Syntax mailing list we're discussing whether or
not to pursue the autodiscovery draft that had previously been put on
the table [1] or to simply point to the HTML5 work and be done with it.
While reviewing the HTML5 draft and comparing that to the Atom
auto-discovery
16 matches
Mail list logo
