I fully agree with you that just putting the url in the body and doing magic based on the file extension and HEAD request isn't a good solution.
oob isn't of any help here either because it doesn't include the content type or the file size. (and especially not extended information like resolution (as in height and width of an image) or duration (for audio)) There has been discussions on the summit regarding a 'reference' xep that let's you reference arbitrary items via and uri and some additional information. I would really like that xep to cover our use case here as well. For people how haven't been at the summit this reference xep will probably look a bit like how twitter is referencing links or images in their api. I don't have a link right now but maybe someone else can provide this. Cheers Daniel
_______________________________________________ Standards mailing list Info: http://mail.jabber.org/mailman/listinfo/standards Unsubscribe: [email protected] _______________________________________________
