[db-wg] changes to the implementation of "abuse-c:"

> For a handful of customers that is not difficult, although some still 
> believe it is over complicated. If you have tens or hundreds of 
> customers wanting to handle abuse complaints themselves, then it moves 
> into the 'unreasonable' zone if all this has to be handled manually. 

For what does the RIPE have a REST API (and programmers that know how to
use it)? We have to handle RIPE data for 2K+ customers, without the API
that would indeed end in the least possible approach. But there are
libraries out there that can be used so we can do abuse handling the
intended way (via Org/Role).

So maybe we should promote this API (and list client libraries that work
with it) way more than today, to tell people that it is not that
complicated to get it right.

cheers,
Alex

-- 
velia.net Internetdienste GmbH * Hessen-Homburg-Platz 1 * D-63452 Hanau
Geschäftsführer: Franz G. Köhler, Arek Akilli * AG Hanau * HRB 7588
Tel: +49 6181 1898119 * http://www.velia.net
Follow us on twitter: https://twitter.com/velia_net