We’ve started to define classifications for creatives — and have run into some interesting ads that seem to defy all existing categories:

Great quick post from 37Signals today on why they left certain things out of their new group business chat application Campfire.  The answer most of the time on why they left stuff out?  “It just doesn’t matter”.

The longer this planning process goes the more things that seem to want to creep in.  There’s such a natural human instinct to think of reasons why the product should include as much as humanly possible so that it will have things that people want.

I think people think of the edge case user who will want a specific feature, instead of asking if the majority of users will want it or not.  Does the bloat of features in a product give enough benefit to make that edge case user happy?  The answer is no.  Now to just keep repeating that.

This version again contains fixes for WSDL problems. Some toolkits (gSOAP) don’t like when different services share same XML namespace. One XML namespace shared among all services causes problems for operations having same name in different services. So starting from this version all services use unique XML namespaces. Among other changes in WSDL is that starting from this version enum types are used where appropriate.

DeliveryRulesService was removed from API. Related operations
add/delDeliveryRules were removed from other services. The reason for this that logically delivery rules are integral part of objects which use them (i.e. line item, campaign, creative). In the future versions fields from delivery rules will be exposed as part of line item (already implemented), as part of campaign and creative (not implemented yet).

Some bugs reported by Netblue were fixed.

All available WSDLs are at:

• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.10/campaign.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.10/contact.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.10/creative.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.10/insertion_order.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.10/line_item.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.10/publisher.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.10/section.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.10/site.php?wsdl
• http://ct.yieldmanager.com/ilyaphp/manage/soap-0.10/target_profile.php?wsdl

A group of us are currently sitting here in Seattle at an Adaptive Path seminar on going beyond usability when building a web site or web application. It’s validating many of the things we’ve done so far, but also bringing up some new ideas we can incorporate as we continue to spec and build this project.

One of the first things I noticed is that we can do a better job of defining success. We’ve got general goals, but what will define if it’s successful, and how will it change Right Media’s business if it is? What metrics can we then use to track this? Those are some questions we’ll hope to answer in the next week or so.

Our first public mention in the press came this week with Media Guard being listed in an Adotas article about ad networks and porn as a potential solution for protecting publishers and advertisers.

We’re happy to be mentioned and they’re right on that this product is aimed at protecting both advertisers and publishers from being involved with content/creatives that don’t fit in with their goals.