Clinton Gallagher
2006-01-19 22:07:12 UTC
I apologize for what I know is OT to the focus of the folks that use this
list but having commented in the past and lurked for a long time thereafter
I do know many of you were involved and argued the initial development of
RSS 2.0. Since the usage of 2.0 is no longer arguable I hope somebody can
help discuss this arcane element; that being the channel element's textInput
sub-element.
I'm building an RSS CMS and I want to implement the entire specification
inclusing the RSS 2.0 <textInput> sub-element. The future is looking bright
for 2.0 and I know this element can come into its own if light-weights like
myself can determine how to implement it. In case you've forgotten how lame
it was written here is what the RSS 2.0 Specification [1] says...
<START>
A channel may optionally contain a <textInput> sub-element, which contains
four required sub-elements.
<title> -- The label of the Submit button in the text input area.
<description> -- Explains the text input area.
<name> -- The name of the text object in the text input area.
<link> -- The URL of the CGI script that processes text input requests.
The purpose of the <textInput> element is something of a mystery. You can
use it to specify a search engine box. Or to allow a reader to provide
feedback. Most aggregators ignore it.
<END>
However, what I want to know is how Dave Winer who created RSS 2.0 and
presumably wrote the specification claims this sub-element is a mystery when
it was Dave Winer who created the element? Should I answer that myself? ;-)
Please don't answer either question as I think we all have at least one
answer that would not be fit to print :-0
Has anybody *ever* implemented textInput? I can think of a couple of ways it
can be very useful but how to implement it? ANYBODY?
Once a parser found the textInput element in the source would it be expected
to generate an HTML form element replete with input of type="text" and so
on?
I have something to say about the cloud element in this context as well (an
XML Web Service call it seems) but for now if you would, let's focus on the
textInput element. What's the story here? Or should I go away?
<%= Clinton Gallagher
[1]
http://blogs.law.harvard.edu/tech/rss#lttextinputgtSubelementOfLtchannelgt
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/rss-dev/
<*> To unsubscribe from this group, send an email to:
rss-dev-unsubscribe-***@public.gmane.org
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
list but having commented in the past and lurked for a long time thereafter
I do know many of you were involved and argued the initial development of
RSS 2.0. Since the usage of 2.0 is no longer arguable I hope somebody can
help discuss this arcane element; that being the channel element's textInput
sub-element.
I'm building an RSS CMS and I want to implement the entire specification
inclusing the RSS 2.0 <textInput> sub-element. The future is looking bright
for 2.0 and I know this element can come into its own if light-weights like
myself can determine how to implement it. In case you've forgotten how lame
it was written here is what the RSS 2.0 Specification [1] says...
<START>
A channel may optionally contain a <textInput> sub-element, which contains
four required sub-elements.
<title> -- The label of the Submit button in the text input area.
<description> -- Explains the text input area.
<name> -- The name of the text object in the text input area.
<link> -- The URL of the CGI script that processes text input requests.
The purpose of the <textInput> element is something of a mystery. You can
use it to specify a search engine box. Or to allow a reader to provide
feedback. Most aggregators ignore it.
<END>
However, what I want to know is how Dave Winer who created RSS 2.0 and
presumably wrote the specification claims this sub-element is a mystery when
it was Dave Winer who created the element? Should I answer that myself? ;-)
Please don't answer either question as I think we all have at least one
answer that would not be fit to print :-0
Has anybody *ever* implemented textInput? I can think of a couple of ways it
can be very useful but how to implement it? ANYBODY?
Once a parser found the textInput element in the source would it be expected
to generate an HTML form element replete with input of type="text" and so
on?
I have something to say about the cloud element in this context as well (an
XML Web Service call it seems) but for now if you would, let's focus on the
textInput element. What's the story here? Or should I go away?
<%= Clinton Gallagher
[1]
http://blogs.law.harvard.edu/tech/rss#lttextinputgtSubelementOfLtchannelgt
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/rss-dev/
<*> To unsubscribe from this group, send an email to:
rss-dev-unsubscribe-***@public.gmane.org
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/