[ticker-dev] V3.0 Of the tickertape notification format specification - attachments and a suggested addition... (fwd)
David Arnold
arnold at dstc.monash.edu.au
Wed Oct 9 15:06:03 EST 2002
-->"Martin" == <martin.wanicki at boeing.com> writes:
Martin> The use of the attachment field at this point in time seems
Martin> to be predominately for passing url's around.
yes. that's all the majority of clients have supported until very
recently.
Martin> <...> I propose the addition of an optional attribute for
Martin> the purpose of passing url's. A possible name for this might
Martin> just be Url: or Hyperlink: or whatever name on which a
Martin> reasonable consensus can be reached.
this was briefly mentioned during ticker discussion the other day, but
didn't seem to attract much attention.
maybe it's a good half-way step between the 1.3 spec and a future spec
with full attachment ability?
or maybe MIME attachments is not something we really need/want?
Martin> Regarding backward compatibility issues, the old MIME_ARGS
Martin> attribute *may* be considered equivalent since it has been
Martin> predominately used for url's.
i'm happy to ignore backward compatibility :-)
Martin> Perhaps support for multiple url's should be moved to the
Martin> mime attachment or perhaps we define the Url field as
Martin> containing either one or more url's with a caveat on
Martin> separation (i.e. at most one url per line of text)
i worry about usability issues in clients if we have multiple ways to
attach things ...
if we go for a separate mechanism for URL attachment, i'd be tempted
to drop the MIME attachment for now.
d
More information about the ticker-dev
mailing list