[JDEV] Advertising Namespace

[Duncan, Paul]

Excluding an RSS channel wouldn't necessarily solve it.  If the end user has
a choice between 'voluntarily' subscribing to an Ad channel or not, then of
course, who's going to do that?!  That doesn't help the starving developer,
though - not to mention commercially developed IM's (or any multitude of
apps that can use the Jabber protocol).  It would be silly to stifle the
commercial benefits of this technology.

If the message is basically a URL, title, and description, that doesn't
identify it enough.  I'd want to know if it was an ad or a news item or an
invite to the white house.

If I wanted to plug an advertising delivery module into my server, I'd need
some way of delivering that ad w/o interfering (ideally) with headline
information.  No one wants to see an ad for a sprocket within stock
information.

If that indicator is a message type and not a namespace, I don't see a
problem there.  Perhaps the focus should be on more message types and not
more namespaces.

Guaranteed eyeballs is a malleable thing.  What I was saying was the
developer could 'guarantee' certain views/click-thrus in the same way he can
on his web site.  More so with a downloadable, constantly used software
program.  I believe people stick with their IM's much more than a web site.


So maybe we should think on a 'advertising' jabber:x:oob message type and
not a jabber:x:advertising namespace.

- Just an idea. (still banging in my brain)
- Duncan

-----Original Message-----
From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
DJ Adams
Sent: Friday, March 23, 2001 5:22 PM
To: jdev at jabber.org
Subject: Re: [JDEV] Advertising Namespace


On Fri, Mar 23, 2001 at 04:43:48PM -0500, Duncan, Paul wrote:
> 
> Good point, but the display of the banner-ad would be left to the client
> developer to ignore or not, thereby leaving it in the hands of the
developer
> to justify to a company its validity.

I guess the free market means developers are free to develop clients that
display banner ads, and users are free to choose (or write ;-) their client.


Temas has a point though, about 'guaranteed eyeballs'. 

> Todd suggested something about another RSS channel.  I'm not sure what
this
> is so I can't speak to it.  Perhaps more clarification?

RSS - RDF Site Summary - is a way of holding a parseable summary of a 
collection of items, commonly used to succinctly describe the contents of
a news or blog site. These 'news' items don't have to be news - they're
essentially a URL, title, and description. So an RSS channel could
potentially
hold collections of advertisments. The nice thing subscribing to an RSS
channel is that you don't _have_ to ;-) There's a Jabber namespace 
(jabber:x:oob) which fits very well with the RSS item model, and combined
with
the message type 'headline' can be used to deliver RSS info to Jabber
clients,
some of which present such data in a useful way .

(Check out http://www.pipetree.com/jabber/headlines.html for a bit more on
this).

RSS: http://purl.org/rss/1.0/

hth
dj




> 
> - Thanks -
> Duncan
> 
> -----Original Message-----
> From: jdev-admin at jabber.org [mailto:jdev-admin at jabber.org]On Behalf Of
> Thomas Muldowney
> Sent: Friday, March 23, 2001 4:15 PM
> To: jdev at jabber.org
> Subject: Re: [JDEV] Advertising Namespace
> 
> 
> I think the ramifications of being able to ignore the namesapce would make
> it
> very hard for a company to want to join an ad campaign like this.  If I
> don't
> have guaranteed audience or guaranteed views what's the point?  Food for
> thought.
> 
> --temas
> 
> On Fri, Mar 23, 2001 at 03:29:39PM -0500, Duncan, Paul wrote:
> >     Ok.  First of all let me start off by saying I find banner ads on my
> IM
> > clients annoying and invasive.
> >  
> >     I know this.
> >  
> >     However,  for some shareware/freeware developers, the only way they
> can
> > see any cost justification is by the selling of
> >     ad space on thier web sites and through some of their client
software.
> > One of the coolest news readers I've ever seen has
> >     a banner ad at the bottom.  I respect the developer for going this
> route
> > and not charging me for using his tool, as I now have 
> >     this fantastic reader for free.
> >  
> >     Other developers may want this ability.  Others will not.  By
> providing
> > a namespace for this, clients can exclude this, regardless if its sent
or
> > not, or
> >     if they wish, utilize the namespace to help offset the development
> > costs.
> >  
> >     I'd guess it would be something like:        
> >         
> >         jabber:x:advertisement
> >  
> >     <x xmlns="jabber:x:advertisement">
> >         <url>http://www.mysoftware.com/bannerads/buy.jpg</url>
> >         <tracking_no>AE9323DEFGH123</tracking_no>
> >     </x>
> >  
> >     This is not an email to instigate a full-fledge flame war against me
> or
> > my value system.
> >  
> >     Thoughts?
> >  
> >     - Duncan
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev

_______________________________________________
jdev mailing list
jdev at jabber.org
http://mailman.jabber.org/listinfo/jdev