At 10:06 AM +0800 8/2/07, Qian Sun wrote:
>Hi, Eric
>
>An AD bodypart should be marked "advertisement" if it is intended to be
>displayed in a non-disturbed/non-confusing way.
>The "advertisement" Disposition Type would be a kind of display manner between
>"Inline" and "Attachment".
>For example, a client could display advertisement in a place different from
>the content window.
>
>Cheers,
>Qian
I agree with Eric that "advertisement" is not a disposition; it is a statement
about who
is getting paid. "inline-subordinate" would be a disposition
that said "put this inline, but don't let it block anything with a regular
"inline" tag. You seem to want people to infer what disposition to give
based on the "advertisement" status. As you have seen, some are inferring
that they can cheerfully junk the content. I think there are a number of
problems
even with something like "inline-subordinate" (what do you do when
you are using text-to-speach rendering for blind users?), but I think your
focus should
be on describing what the software should do rather than on the commercial
relationships.
Lastly, I'll point out that introducing a disposition like "advertisement" or
"inline-subordinate" has an impact on the MIME folks in general, and a more
general discussion would be needed before things progressed.
regards,
Ted Hardie
>-----Original Message-----
>From: Eric Burger [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, August 01, 2007 11:42 PM
>To: Dean Willis; Qian Sun
>Cc: 'sip'
>Subject: Re: Content-Disposition in multiparts WAS (Re: [Sip] Draft slides
>forbody (MIME) handling)
>
>Content-Disposition="advertisement" would never pass MIME review. It is not
>a disposition.
>
>Give it up and move on to more important stuff, like running code :-)
>
>
>On 7/31/07 8:37 AM, "Dean Willis" <[EMAIL PROTECTED]> wrote:
>
>>
>> On Jul 30, 2007, at 8:36 PM, Qian Sun wrote:
>>
>>> Hi, Dean
>>>
>>> Sorry for late response. Do you mean "advertisement" content always
>>> is needed to 'render'? So a single content disposition
>>> "advertisement" is enough.
>>
>> Well, I'm wondering if advertisements have any other need than
>> "render". If not, why not just use "render"?
>>
>> If we define an "advertisement" content disposition, we might as well
>> call it "ignore", in which case there's hardly any point in sending
>> it to start with, right?
>>
>> Although I must admit I'm intrigued by the prospect of getting
>> advertisers to self-label stuff so that it can be discarded as
>> efficiently as possible.
>>
>>> In addition, some content body (e.g. Geolocation or advertisement)
>>> may be inserted or modified by intermediary. Could we specify a
>>> common way for indicating the source of inserted content body? For
>>> example, define a new MIME header: Content-Insertedby. A B2BUA may
>>> insert a content body including AD like this:
>>>
>>> Content-Type: text/plain
>>> Content-Disposition: advertisement
>>> Content-Insertedby: AD-Agent <sip: [EMAIL PROTECTED]>
>>
>> I'm sure there has been discussion of this in geopriv, but I don't
>> recall the details. I suspect there have been concerns about
>> mismatches between the "source" and the "information".
>>
>> --
>> Dean
>>
>>
>>
>> _______________________________________________
>> Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
>> This list is for NEW development of the core SIP Protocol
>> Use [EMAIL PROTECTED] for questions on current sip
>> Use [EMAIL PROTECTED] for new developments on the application of sip
>
>
>Notice: This email message, together with any attachments, may contain
>information of BEA Systems, Inc., its subsidiaries and affiliated
>entities, that may be confidential, proprietary, copyrighted and/or
>legally privileged, and is intended solely for the use of the individual or
>entity named in this message. If you are not the intended recipient, and have
>received this message in error, please immediately return this by email and
>then delete it.
>
>
>
>
>_______________________________________________
>Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
>This list is for NEW development of the core SIP Protocol
>Use [EMAIL PROTECTED] for questions on current sip
>Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
