[ticker-dev] new revision of ticker v3 spec

[Phillips, Matthew]

The spec says MIME-Attachment must be multipart. Is there any reason to mandate this? I'd like to attach simple URL's using Content-Type = "text/uri-list" and the URL(s) as the content.

In fact I just noticed the example in the appendix does exactly that.

Cheers,

Matthew.

> -----Original Message-----
> From: David Arnold [mailto:arnold at dstc.monash.edu.au]
> Sent: Thursday, 10 October 2002 4:42 PM
> To: ticker-dev at dstc.edu.au
> Subject: [ticker-dev] new revision of ticker v3 spec
> 
> 
> i've put a revised specification of the Tickertape v3 protocol on
> DSTC's FTP site for your comments
> 
>   ftp://ftp.dstc.edu.au/DSTC/elvin/draft-arnold-ticker-chat-v3-01.txt
> 
> for reference, the previous draft remains at
> 
>   ftp://ftp.dstc.edu.au/DSTC/elvin/draft-arnold-ticker-chat-v3-00.txt
> 
> changes in this revision:
> 
> 1. "Replaces" is now a renamed "REPLACEMENT" with identical semantics.
> 
> 2. attachments now use the "MIME-Attachment" attribute, rather than
>    "Attachment", and are a string, not an opaque.
> 
>    this has been quite controversial, and i'm not sure that this is
>    the best compromise.  i'd encourage people to speak up if their
>    needs are not met ...
> 
> three outstanding issues remain from the first draft (replaces has
> been resolved).  these are: security, the semantics of the
> Distribution attribute, and the lack of explanatory and motivational
> text.  comments and contributions to any of those would be great :-)
> 
> see
> 
>   
> http://elvin.dstc.edu.au/ListArchive/ticker-dev/archive/2002/0
4/msg00002.html


thanks ...




d